IPO Lifecycle API: One issuer's complete path to going public — SEC EDGAR

One issuer's complete path to going public — registrations, amendments, prospectuses, effectiveness and withdrawals in order with a current stage label, merged live from EDGAR plus our 2021+ index. Look up by CIK or name substring.

$0.05 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/company — product id ipo_company. Over MCP, call answerpool_get with product_id=ipo_company.

curl "https://answerpool.io/v1/ipo/company?cik=320193"

# with a prepaid credit key
curl -H "Authorization: Bearer ck_live_..." "https://answerpool.io/v1/ipo/company?cik=320193"

Live call: https://answerpool.io/v1/ipo/company?cik=320193 · JSON sample: /v1/samples/ipo_company

What does the answer look like?

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

events

{
 "as_of": "2026-09-02T23:00:00Z",
 "cik": "0001999999",
 "company": "EXAMPLE ROBOTICS INC",
 "stage": "priced",
 "count": 2,
 "events": [
  {
   "form": "S-1",
   "filed": "2026-06-10",
   "accession": "0001999999-26-000001",
   "url": "https://www.sec.gov/Archives/edgar/data/1999999/000199999926000001-index.htm"
  },
  {
   "form": "424B4",
   "filed": "2026-08-29",
   "accession": "0001999999-26-000009",
   "url": "https://www.sec.gov/Archives/edgar/data/1999999/000199999926000009-index.htm"
  }
 ],
 "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.

• SEC EDGAR (US federal public domain) — upstream: https://efts.sec.gov

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 follow one candidate and want its full registration history + stage.

What you skip building

• submissions parsing
• form classification
• stage logic

When should you not use it?

Market-wide pipeline snapshots — use the calendar.

Where else can you find this?

• Catalog entry (JSON, free)
• OpenAPI schema — input and output types, prices, the 402 flow
• llms.txt — every product in one plain-text document