IPO Calendar API: The IPO pipeline staged in one call — SEC EDGAR

The IPO pipeline staged in one call — just-filed S-1/F-1 issuers, amendments in progress, priced 424(b)(4) offerings and withdrawals for your window, each bucket newest first. Replaces composing four EDGAR form feeds.

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

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

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

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

What does the answer look like?

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

filed

{
 "as_of": "2026-09-02T23:00:00Z",
 "window_days": 30,
 "filed": [
  {
   "accession": "0001437749-26-028920",
   "cik": "0001999999",
   "company": "EXAMPLE ROBOTICS INC",
   "ticker": null,
   "form": "S-1",
   "filed": "2026-08-29",
   "url": "https://www.sec.gov/Archives/edgar/data/1999999/000143774926028920-index.htm"
  }
 ],
 "amending": [],
 "priced": [],
 "withdrawn": [],
 "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 brief or monitor the pipeline as a whole, on a schedule.

What you skip building

• multi-feed composition
• stage classification
• dedup across amendments

When should you not use it?

Single-stage feeds — the per-stage endpoints are cheaper.

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