AnswerPool

Priced Offerings API: Offerings that just priced — SEC EDGAR

Offerings that just priced — final 424(b)(4) prospectuses in your window, each flagged likely-IPO when the issuer has no earlier 424(b) in our 2021+ index, separating debuts from follow-ons. One call, minutes-fresh.

$0.02 per call — pay with prepaid card credits (Authorization: Bearer ck_live_…, packs from $1) or with USDC over x402: call it, get 402 with the price, retry signed. Failed calls are never charged.

How do you call it?

GET /v1/ipo/priced — product id ipo_priced. Over MCP, call answerpool_get with product_id=ipo_priced.

curl "https://answerpool.io/v1/ipo/priced?days=30"

# with a prepaid credit key
curl -H "Authorization: Bearer ck_live_..." "https://answerpool.io/v1/ipo/priced?days=30"

Live call: https://answerpool.io/v1/ipo/priced?days=30 · JSON sample: /v1/samples/ipo_priced

What does the answer look like?

A representative response, the same static sample served at /v1/samples/ipo_priced.

as_of2026-09-02T23:00:00Z
window_days30
count1
refresh_after2026-09-17T11:15:00.000Z

offerings

accessioncikcompanytickerformfiledurllikely_ipo
0001437749-26-0289200001999999EXAMPLE ROBOTICS INCEXRB424B42026-08-29https://www.sec.gov/Archives/edgar/data/1999999/000143774926028920-index.htmtrue
The same sample as raw JSON
{
 "as_of": "2026-09-02T23:00:00Z",
 "window_days": 30,
 "count": 1,
 "offerings": [
  {
   "accession": "0001437749-26-028920",
   "cik": "0001999999",
   "company": "EXAMPLE ROBOTICS INC",
   "ticker": "EXRB",
   "form": "424B4",
   "filed": "2026-08-29",
   "url": "https://www.sec.gov/Archives/edgar/data/1999999/000143774926028920-index.htm",
   "likely_ipo": true
  }
 ],
 "refresh_after": "2026-09-17T11:15:00.000Z"
}

How fresh is it, and where does the data come from?

The fastest source behind this answer can change every 15 minutes, so every response carries a refresh_after timestamp — right now it would be 2026-09-17T11:15:00.000Z. Schedule the next call on that value rather than on a guess.

Method version 0.1.0 · serving cache 1 day · every response carries a result_id you can resolve at /v1/provenance.

When should you use it?

You act on completed pricings and want debuts distinguished.

What you skip building

When should you not use it?

Registration starts — use the registrations endpoint.

Where else can you find this?