Skip to content

SEC S-1/F-1 IPO pipeline intelligence (weekly)

Commercial use OKFresh
Query in workbench

Follow this dataset

Get a notice in your feed when a new snapshot is published. Optionally, we also POST it to your webhook.

Must be a public https address. We never follow redirects.

The full snapshot isn't published yet — check back after the next refresh.Download sample CSVDownload sample JSONSample rows only (up to 20) — not the complete dataset.

Weekly company-grain panel of the live IPO pipeline from the official keyless SEC EDGAR quarterly master index: every company with an S-1/S-1/A (domestic) or F-1/F-1/A (foreign) registration filing in the trailing 9 months, resolved to one row per company with pipeline stage (filed/amended/priced/listed/withdrawn from the S-1 -> S-1/A -> 424B4/RW/8-A12B form chain; standalone 8-A12B filings by already-public issuers are excluded by chaining), SIC industry + closed sector mapping, HQ city/state and ISO alpha-3 country, days in pipeline, amendment velocity, and a documented 0-100 ipo_heat_score (45% recency + 35% amendment velocity + 20% stage weight) with a deterministic heat_rank. Per-CIK enrichment comes from the keyless data.sec.gov submissions JSON (SIC, HQ address); enrichment failures keep the row with nulls and are reported as SIC coverage. Who joins this: a sales team joins (initial_filing_week, hq_state) to lead scoring — active S-1 filers are high-propensity B2B buyers scaling into a listing, freshly priced rows are newly-funded accounts; a merchant joins weekly IPO counts by sector to demand models as a capital-markets optimism regressor (primary key (as_of, cik); join keys cik, company_name, ticker, hq_state, country_code, initial_filing_week). Caveats: heat scores are within-snapshot relative; withdrawn pipelines score low by design; foreign filers' HQ country resolves via hub.normalize. No filing text is stored.

Rows
1,121
Columns
28
Source cadence
Weekly
Last refreshed
Oct 1, 2026
Theme
finance

Use your own AI key

Once today's free allowance is used up, AI features can run on your own provider account.

Kept in this browser tab only (cleared when you close it) and sent with each AI request. Our servers use it for that request and never store or log it.