Reg A+ Offering Lifecycle & Outcomes Monitor (SEC EDGAR)

Track Regulation A / Reg A+ offerings end to end — not just the raise, but what happened after it. This actor reads SEC EDGAR's full-text search API plus each filing's structured XML and returns one clean, flat row per lifecycle event:

• 1-A — the offering statement (tier, price, aggregate offering, a one-year financial snapshot, auditor, jurisdictions)
• 253G2 (and 253G1/G3/G4) — the qualified offering circular
• 1-K — the annual report (the "did they survive / are they still reporting" signal)
• 1-SA — the semiannual report
• 1-U — the current report / material events (with the item codes)
• 1-Z — the exit report (how much of the qualified offering actually sold, net proceeds, holders of record)

Reg A+ lets a company raise up to $75M from the public — a much larger universe than Regulation Crowdfunding's $5M. Existing tools sell the offering (Form 1-A) and stop there. Nobody sells the outcome lifecycle. This actor does: it follows each issuer from offering statement through annual reports to exit, so you can see who is still reporting, who quietly went dark, and how their raises actually turned out.

Keyless. No login, no scraping of anti-bot pages — just SEC EDGAR, the authoritative source.

Who it's for

• Reg A+ investors and analysts — screen the whole market: which offerings qualified, which are still filing annual reports, which sold only a fraction of what they qualified, which filed a 1-Z and shut down.
• Crowdfunding platforms (StartEngine, Republic/DealMaker, Dalmore, etc.) — monitor your issuers' post-raise filings and benchmark against the market.
• Securities lawyers & compliance — a dated, structured feed of every Reg A lifecycle event, filterable by state and form type.
• Journalists & researchers — the raw record of who raised, how much, and what became of them.
• B2B lead generation — funded, growth-stage companies with public financials, addresses, auditors and legal counsel, one row each.
• AI agents — a clean, self-describing MCP tool (see below).

Modes

Mode	What it returns
feed	Reg A lifecycle events across form types in a date window, filterable by formTypes, state and a full-text platformQuery. XML enrichment is opt-in.
outcomes	Form 1-K annual reports (always XML-enriched) — the survival / still-reporting signal, with reporting period, fiscal year end, shell-company flag and securities outstanding.
issuer	Every Reg A lifecycle filing for one company (cik or issuerQuery), XML-enriched — the full arc for a single issuer.
delta	Only filings new since your last run for this scope, tracked in a named key-value store. The first run stores a baseline and fails with an explanatory message rather than billing the whole feed as new.

Example input

Recent Reg A+ lifecycle events with structured detail:

{
  "mode": "feed",
  "startDate": "2026-08-01",
  "formTypes": ["1-A", "253G2", "1-K", "1-SA", "1-U", "1-Z"],
  "enrichXml": true,
  "maxResults": 200
}

One issuer's full lifecycle by CIK:

{ "mode": "issuer", "cik": "2083128", "maxResults": 200 }

Who's still filing annual reports (the survival signal):

{ "mode": "outcomes", "startDate": "2026-01-01", "maxResults": 200 }

Only filings that appeared since your last run (schedule this):

{ "mode": "delta", "formTypes": ["1-A", "1-Z"], "maxResults": 500 }

Output fields (highlights)

Every row is flat and CSV/JSON friendly. Full documentation is in the dataset schema.

• Identity: form, form_base, is_amendment, event_class, accession, cik, issuer_name, file_date_iso, biz_state, biz_city, incorporation_state, filing_index_url, primary_doc_url
• Offering (1-A): offering_tier (Tier1/Tier2), securities_offered_type, price_per_security, security_offered_count, issuer_aggregate_offering_usd, total_aggregate_offering_usd, outstanding_securities, num_offering_jurisdictions, financial_statement_audit_status, auditor_name, legal_service_provider
• Financial snapshot (1-A, single most-recent period): fin_total_assets, fin_total_revenues, fin_net_income, fin_total_stockholder_equity, fin_cash_equivalents, fin_long_term_debt, fin_is_profitable
• Annual report (1-K): reporting_period_iso, fiscal_year_end_iso, shell_company_flag, issued_securities_titles
• Exit (1-Z): exit_securities_qualified, exit_securities_sold, exit_sell_through_pct (how much of the qualified offering actually sold), exit_issuer_net_proceeds_usd, exit_approx_record_holders, exit_offering_qualification_date_iso
• Current report (1-U): current_report_items (material-event item codes)
• Provenance & honesty: xml_status, data_source, drift_gate_status, matched_total, results_truncated, run_max_results_cap

How to read a null

A null financial or date means not reported, not fetched, or not applicable to that form — never a fabricated zero. A 0 means the filing literally reported 0.00. Forms that file an HTML/PDF primary document (253G2, 1-SA, 1-U, DOS) carry xml_status = "not_applicable" and their structured columns are null by design.

Reg A vs Reg CF — one important difference

If you also use our Reg CF (crowdfunding) monitor, note this: Regulation Crowdfunding's Form C-AR annual report carries structured two-year financials in its XML. Regulation A's 1-K does not — Reg A audited financial statements are filed as HTML/PDF exhibits, not machine-readable fields. So on this actor the financial columns come from the 1-A offering (a one-year snapshot at the time of the raise) and the outcome economics come from the 1-Z exit report (securities qualified vs sold, net proceeds, record holders). The 1-K is the continuation / survival signal — that the issuer is still meeting its ongoing reporting obligations — plus its securities-outstanding detail.

Trust & reliability

• Live drift gate before any billable row. Every run first verifies the source three ways: a floor check on the live 1-A corpus, a positive canary (a real, pinned 1-A filing that must still parse to the same issuer, tier and financials), and a negative control (a nonsense form must return exactly zero). If the source has drifted or is unavailable, the run fails loudly and bills nothing.
• The state filter is post-validated on every row. EDGAR's locationCode (singular) parameter is silently ignored server-side; we use locationCodes (plural) and re-check every returned row, so a TX-only query can never quietly return a national feed.
• A hard, single billing cap. maxResults bounds exactly how many rows are emitted and billed, enforced by one code path with a tripwire; every row carries matched_total and results_truncated so a capped answer is never mistaken for a complete one.
• No silent zero. An outage, an unparseable response or an HTML rate-limit page fails the run — it never becomes a green, empty "no filings" answer.

Pricing & cost

Pay-per-result: you are billed per row emitted (one lifecycle event = one row), capped by your maxResults. A typical scoping run of 200 rows costs a small, predictable amount; set maxResults low to preview. Failed runs (source unavailable, bad input) emit nothing and bill nothing beyond the negligible actor start. XML enrichment adds one polite EDGAR request per 1-A/1-K/1-Z row (slower, same per-row price).

Use as an MCP tool

This actor is callable by AI agents (Claude, Cursor, etc.) via mcp.apify.com. Its input and output fields are fully described, so an agent can pick mode, set a date window or a cik, and chain the results. Example agent prompt:

"Using the Reg A+ lifecycle monitor, list every Reg A offering (form 1-A) filed in Texas in 2026 with its tier, aggregate offering amount and net income, then show which of those issuers has since filed a 1-Z exit report and what percentage of the qualified offering actually sold."

FAQ

Where does the data come from? SEC EDGAR full-text search (efts.sec.gov) for the filing index, and each filing's primary_doc.xml on sec.gov/Archives for the structured detail. It is the authoritative, public record.

Is it keyless? Yes. No API key, no account. Requests carry the SEC fair-access User-Agent and are rate-limited politely.

Why is exit_sell_through_pct so interesting? It is the single clearest outcome number: a 1-Z exit report states how many securities were qualified and how many actually sold. A raise that qualified 15,000 units and sold 2,382 has a 15.9% sell-through — a very different story from the offering statement alone.

Can I monitor only new filings? Yes — use delta mode on a schedule. The first run seeds a baseline; subsequent runs return only genuinely new lifecycle events for that scope.

What about Form D or QUALIF filings? Form D is Regulation D, a different regime, and is excluded. The SEC's QUALIF qualification notice is filed under a special SEC filer CIK (not the issuer's), so it is deliberately excluded to keep the dataset issuer-centric — the issuer-filed 253G2 is the qualification signal instead.