New SEC Registrants API: First-time-ever EDGAR filers in your window, derived from our — free lookup
First-time-ever EDGAR filers in your window, derived from our multi-year filing index — new companies and funds entering the SEC system, with first forms. A question EDGAR's own API cannot answer. Free, no key.
Free — no key, no signup, rate-limited to 60 calls per minute per client.
How do you call it?
GET /v1/sec/registrants/new — product id
sec_new_registrants. Over MCP, call answerpool_get with
product_id=sec_new_registrants.
curl "https://answerpool.io/v1/sec/registrants/new?days=7"
Live call: https://answerpool.io/v1/sec/registrants/new?days=7 · JSON sample: /v1/samples/sec_new_registrants
What does the answer look like?
A representative response, the same static sample served at /v1/samples/sec_new_registrants.
as_of | 2026-09-03T02:00:00Z |
|---|---|
window_days | 7 |
index_covers_since | 2021-07-01 |
index_covers_until | 2026-09-02 |
count | 1 |
disclaimer | Derived from public SEC EDGAR filings; not investment advice. |
refresh_after | 2026-09-17T11:15:00.000Z |
registrants
| cik | company | first_filed | forms | filings |
|---|---|---|---|---|
| 0002099999 | EXAMPLE LABS INC | 2026-09-01 | D | 1 |
The same sample as raw JSON
{
"as_of": "2026-09-03T02:00:00Z",
"window_days": 7,
"index_covers_since": "2021-07-01",
"index_covers_until": "2026-09-02",
"count": 1,
"registrants": [
{
"cik": "0002099999",
"company": "EXAMPLE LABS INC",
"first_filed": "2026-09-01",
"forms": [
"D"
],
"filings": 1
}
],
"disclaimer": "Derived from public SEC EDGAR filings; not investment advice.",
"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 want net-new registrants, not just recent filings.
What you skip building
- maintaining your own EDGAR history
- full-index scans
When should you not use it?
All recent filings regardless of history — /v1/sec/filings/latest.
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