Reg CF Crowdfunding Lifecycle & Outcomes Monitor (SEC EDGAR)

Track the full Regulation Crowdfunding lifecycle — not just new offerings. Every Reg CF company files a paper trail with the SEC, and this actor reads all of it, straight from EDGAR, keylessly:

Form	What it means	event_class
C	New crowdfunding offering launched (with target/max amounts, security type, deadline and the funding portal)	new_offering
C-U	Progress update — including the outcome text "Offering closed successfully" / "Offering closed unsuccessfully"	progress_update
C-AR	Annual report — the issuer's two-year financials: total assets, cash, receivables, short/long-term debt, revenue, COGS, taxes, net income, employees	annual_report
C-TR	Termination of reporting	termination
C-W	Offering withdrawal	withdrawal

Most crowdfunding data products stop at the Form C feed. The lifecycle is where the real questions live: What happened to the companies after they raised? Which offerings closed successfully? What revenue are last year's crowdfunded startups actually reporting now? Form C-AR answers that with audited-or-not but SEC-filed numbers, and this actor parses them into flat, CSV-friendly rows with derived revenue_growth_pct, net_income_delta and is_profitable_current.

Who this is for

• Crowdfunding investors — see the C-AR financials of companies you backed (or are about to back), and catch C-TR terminations / C-W withdrawals early.
• Funding portals & platforms — monitor your own issuers' compliance filings, or benchmark a competitor portal's deal flow (portalQuery).
• Journalists & researchers — the Reg CF outcomes story (success rates, post-raise revenue, shutdowns) is sitting in these five form types.
• B2B lead generation — a company that just raised via Reg CF has money and momentum; a C-AR filer reports real revenue, employees, a website and a business address. Filter by state for territory-scoped lists.
• AI agents (MCP) — every input and output field is described; see below.

Modes

feed — lifecycle events in a date window

{
  "mode": "feed",
  "formTypes": ["C", "C-U", "C-AR", "C-TR", "C-W"],
  "startDate": "2026-08-01",
  "maxResults": 200
}

One row per filing, newest first, with issuer name, CIK, state/city, incorporation state, SEC file number, accession, and direct EDGAR URLs. Add "enrichXml": true to also pull each filing's XML for the funding portal, offering amounts, C-U progress text and financials (one polite EDGAR request per row — slower, richer).

outcomes — C-AR annual reports with two-year financials

{ "mode": "outcomes", "startDate": "2026-07-01", "state": "TX", "maxResults": 100 }

Always XML-enriched. Each row carries both fiscal years of all nine financial metrics plus derived deltas. This is the "what happened after the raise" mode.

issuer — one company's whole Reg CF history

{ "mode": "issuer", "cik": "1373217", "maxResults": 50 }

Every C / C-U / C-AR / C-TR / C-W the issuer ever filed, XML-enriched — the company's crowdfunding biography in one call. Use issuerQuery: "Bean Box" when you do not know the CIK.

delta — only what is new since your last run

{ "mode": "delta", "formTypes": ["C-TR", "C-W"], "maxResults": 200 }

Cross-run tracking in the named key-value store reg-cf-lifecycle-baseline, keyed by your query scope. The first run for a scope stores a baseline and fails with an explanatory message — it will never bill you the whole feed labelled "new". Schedule it and get genuinely new events (e.g. every new termination — a churn signal no one else sells).

Cost — read this first

Pricing is pay-per-result: you pay only for rows written to the dataset, at the listed price per 1,000 results. maxResults (prefill 200) is a hard cap on the bill enforced by a single audited code path — every row carries run_max_results_cap, rows_emitted_this_run, matched_total and results_truncated, so a capped answer can never masquerade as a complete one.

Typical runs at $10/1,000 results:

Run	Rows	Cost
Last 10 days of all lifecycle events (feed)	~150-250	~$1.50-2.50
A month of C-AR outcomes, one state	~30-80	~$0.30-0.80
One issuer's full history	2-15	~$0.02-0.15
Daily delta of terminations/withdrawals	0-10	usually pennies

A run that cannot produce a trustworthy answer — EDGAR unreachable, the source drift gate failing, an unusable input — fails loudly and bills nothing. A 0-row SUCCESS only ever means the query verifiably matched nothing.

Data quality & honesty guarantees

• Live drift gate before any billable row: (1) the C-AR corpus total must clear a floor of 5,000 (measured 5,650 live); (2) a pinned canary filing (TRADESTAR RESOURCES CORP C-AR, accession 0001096906-26-001311) must parse with the right issuer, period and financials; (3) a negative control (a nonsense form type) must return exactly 0 — if EDGAR ever starts ignoring query parameters, the run fails rather than shipping a mislabeled feed.
• State filter is verified twice. EDGAR's locationCode (singular) parameter is silently ignored by the API — measured live. This actor uses the working locationCodes parameter AND re-validates every returned row; a regression fails the run instead of selling a national feed as one state.
• null is never 0 and never false. A missing financial value is null (not reported / not fetched — see xml_status); 0 means the filing literally reported 0.00. is_profitable_current is null when net income was not read, never a guessed false.
• Dates are normalized, never guessed. EDGAR XML dates (MM-DD-YYYY) are converted to ISO with calendar validation; an impossible date becomes null. Caller dates are strict YYYY-MM-DD — a slash date or month name fails the run loudly with a message naming the field, because a guessed date window is a silently wrong answer.
• Paging can never truncate silently. EDGAR's search API caps result windows at 10,000; maxResults is capped at 5,000 and the pager hard-stops before the window, so the cap is structurally unreachable — and any truncation that does occur is disclosed on every row.

Output fields (63 columns, flat and CSV-friendly)

Identity & event: event_class, form, form_base, is_amendment, accession, cik, cik_padded, file_number, issuer_name, file_date_iso, period_iso, filing_index_url, primary_doc_url.

Location: biz_state, biz_city, biz_location_raw, incorporation_state.

From the filing XML (when fetched — see xml_status / xml_error): issuer_website, legal_status_form, date_incorporation_iso, funding_portal_name, funding_portal_cik, funding_portal_file_number, funding_portal_crd, progress_update_text, security_offered_type, price_per_security, offering_amount, max_offering_amount, offering_deadline_iso, oversubscription_accepted, current_employees.

Two-year financials (C-AR, and also present on C/C-U filings): total_assets_current/prior, cash_equivalents_current/prior, accounts_receivable_current/prior, short_term_debt_current/prior, long_term_debt_current/prior, revenue_current/prior, cost_goods_sold_current/prior, taxes_paid_current/prior, net_income_current/prior — plus derived revenue_delta, revenue_growth_pct, net_income_delta, is_profitable_current.

Delta: is_new_since_last_run, delta_baseline_status.

Run provenance & billing arithmetic: mode, data_source, retrieved_at, drift_gate_status, drift_negative_control_status, matched_total, results_truncated, run_max_results_cap, rows_emitted_this_run, query_forms, query_start_date, query_end_date, query_state, query_portal.

Note: funding_portal_* fields come from Form C / C-U XML — C-AR and C-TR filings do not carry an intermediary block, so those rows have null portal fields with xml_status: "ok" (present in the source as absent, not a fetch failure).

Use as an MCP tool

This actor is callable by AI agents through Apify's MCP server (https://mcp.apify.com). Every input field has a described schema and every output column a description, so an agent can chain it: "find Reg CF companies in Texas that filed an annual report this quarter with revenue over $1M, then screen their addresses". Billing is unchanged when called as a tool; a run that cannot answer fails without billing.

Example agent prompt:

Use reg-cf-lifecycle-monitor with mode "outcomes", startDate 90 days ago and state "CA". Return the ten issuers with the highest revenue_current, with their websites and funding portals.

FAQ

Where does the data come from? SEC EDGAR — the full-text search API (efts.sec.gov) for the filing index and each filing's primary_doc.xml from the EDGAR Archives for details and financials. No API key needed; requests are serialized with SEC's fair-access identification.

How fresh is it? EDGAR indexes filings within minutes of acceptance; a scheduled delta run catches new lifecycle events same-day.

Are the financials audited? Form C-AR financials are issuer-reported per Reg CF's tiered review requirements (reviewed or audited depending on raise size). They are the SEC-filed record, reproduced exactly — this actor never adjusts or estimates a number.

Can I get everything since 2016? Yes — leave startDate blank for the full history (Reg CF began 2016-05-16). For very large pulls, use date windows; matched_total on every row tells you the full universe size behind your page.

Why did my first delta run fail? By design: there was no baseline yet, so "new since last run" had no honest answer. The run stored a baseline, billed nothing, and the next run returns genuinely new filings.

What's a funding portal CRD? The FINRA identifier of the intermediary (Wefunder, StartEngine, Honeycomb, ...) — useful for joining portal-level deal-flow analytics.