AnswerPool

IPO Registrations API: New S-1 and F-1 registration statements filed in the last N days — SEC EDGAR

New S-1 and F-1 registration statements filed in the last N days — companies that just started going public, newest first with CIKs and filing links; amendments excluded by default. One call replaces EDGAR form-feed polling.

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

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

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

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

What does the answer look like?

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

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

filings

accessioncikcompanytickerformfiledurl
0001437749-26-0289200001999999EXAMPLE ROBOTICS INC—S-12026-08-29https://www.sec.gov/Archives/edgar/data/1999999/000143774926028920-index.htm
The same sample as raw JSON
{
 "as_of": "2026-09-02T23:00:00Z",
 "window_days": 30,
 "count": 1,
 "filings": [
  {
   "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"
  }
 ],
 "note": null,
 "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 track newly surfacing IPO candidates.

What you skip building

When should you not use it?

Pricing or completion events — use the priced-offerings endpoint.

Where else can you find this?