SEC Reg A+ Crowdfunding Tracker — Form 1-A Offerings
Pricing
from $150.00 / 1,000 crowdfunding filings
Track Reg A+ crowdfunding (Form 1-A) offerings from SEC EDGAR — parsed, source-linked JSON for analysts, funds and AI agents.
Which Reg A / Form D-A family to scrape. '1-A' is the original Reg A offering circular; '1-A/A' is an amendment to a 1-A; '1-K' is the annual report on a qualified Reg A offering; 'D/A' is a Form D amendment (Reg D private-placement upsizes / repricings). 'all' returns every variant.
Lower bound on the offering's total aggregate amount in USD. Default $5,000,000 surfaces the crowdfunding mid-tier (Reg A Tier 1 floor / typical mid-band Reg D amendment). Set to 0 to disable. Only applied to filings that publish an explicit offering amount (so 1-K annual reports are never filtered out).
Upper bound on the offering's total aggregate amount in USD. Default $75,000,000 caps at the Reg A Tier 2 statutory ceiling — set to 0 (or omit) for no upper bound. Useful for separating Reg A+ from large Reg D amendments.
Look-back window in days. Reg A filings are infrequent (a few hundred per quarter), so 90 days is the comfortable monitoring default. Use 30 for weekly watchlists or 365 for backtesting.
Hard cap on filings pushed to the dataset. Each filing fans out to 1 primary XML fetch + 1 issuer submissions fetch (for ticker + Reg A qualification date enrichment). 100 covers most monitoring use cases; up to 500 for backtests.
Optional. Connect your Notion workspace and the leads are also written as a Notion page in the same run — the Actor never sees your Notion credentials. Authorize a Notion MCP connector in Apify Console → Settings → API & Integrations, then select it here.
Optional. The Notion page ID to create the page under. If blank, Notion creates a private page in your workspace.
Optional. Connect your own Supabase project and the results are also inserted into a table in the same run — the Actor never sees your Supabase credentials. Authorize a write-scoped, project-scoped Supabase MCP connector in Apify Console (Settings -> Integrations), then select it here.
Target table in the public schema (created if missing, with id, a jsonb data column, and a scraped_at timestamp). Default: nexgendata_leads.
Your Supabase project reference (e.g. abcdefghijklmnop). Required unless your connector URL is already project-scoped. Find it in your project URL: supabase.com/dashboard/project/THIS_PART.
