Share Offering & Dilution Monitor - SEC Disclosures

SOURCE COVERAGE & PRACTICAL LIMITS

Full product guide

Documentation captured from build 1.0.2. Example outputs retain their original sample context; they are not live results.

Put each financing disclosure in context

Build a review queue from SEC offering documents: what was registered or offered, which stage the disclosure describes, and which shares or prices are explicitly stated. Keep primary offerings, resales and shelf capacity distinguishable in your research.

Use it for a financing watchlist, filing review or a source-linked research feed. No API key or proxy is required. Every row includes review reasons and should be checked against its cited document.

Open Actor · Read the results · Saved monitoring · Coverage and reference

Try one offering document

Start with Seaport Therapeutics’ fixed priced IPO prospectus to inspect a filing’s stage, stated share count and per-share price together.

1. Open the Actor and select the JSON input editor.
2. Paste the input below and click Start.
3. Open the output table. Read Offering stage and Review reasons, then follow SEC source to the document.

{
  "documentUrls": [
    "https://www.sec.gov/Archives/edgar/data/2042347/000119312526201758/d73463d424b4.htm"
  ],
  "maxResults": 3
}

Prefer a current sample? Click Start with the default input to inspect Seaport Therapeutics’ recent filings (CIK 2042347). The fixed prospectus above is a historical example; the default follows the SEC’s current recent-filings response.

Read the results

A shelf registration is capacity; a priced offering is not automatically completed issuance. Missing supported terms remain null. Each document is a separate observation, so multiple filings may discuss the same deal. The Actor does not calculate percentage dilution or trading returns.

Check coverage before using the export

Export the dataset as JSON or CSV from the run’s output panel. Each observation includes the original SEC URL, accession, filing date, acceptance timestamp when available, and observation time.

In the Output tab, open Run report for a readable coverage report or Coverage and history summary (SUMMARY) for machine-readable source coverage, unsupported cases, failures, saved rows and limits. Reports create no paid dataset rows. A successful run can have partial coverage; SUMMARY marks it explicitly.

Usage and pricing

$5 per 1,000 saved observations on the FREE plan ($0.005 per observation), plus the applicable Actor Start charge. The Pricing tab is authoritative for your plan and current charges.

One confirmed saved observation is one result. Failure messages and run reports are never charged as result rows. Set Apify’s spending limit and maxResults before scheduling. The Actor checks the remaining dataset-item charge allowance before writing.

Build a saved financing watchlist

Follow recent company filings

Review Seaport’s recent offering and registration documents with distinct filing identities.

{
  "ciks": [
    "2042347"
  ],
  "maxFilingsPerCompany": 3,
  "maxResults": 10
}

Replace the sample CIK with your companies’ exact SEC identifiers. Current SEC ticker arrays are included for convenience; they are not historical ticker mappings.

Save a baseline, then follow changes

1. Keep your chosen watchlist and enable Compare with saved observations (comparePrevious).
2. Choose a History name (snapshotName) and dedicated History storage (stateStoreName), then run once. First observations establish a new baseline.
3. Save the input as an Apify task. Reuse the same watchlist, filing limit, date filter and history names on later runs.
4. Enable Save only new or changed observations (onlyChanges) for incremental output. An unchanged repeat can correctly save zero rows.

Schedule the saved task at a cadence suited to your research. Use one writer per history scope; overlapping runs are unsupported.

Compare with the earlier registration

Review the earlier amended registration without treating a proposed offering as completed.

{
  "documentUrls": [
    "https://www.sec.gov/Archives/edgar/data/2042347/000119312526178716/d73463ds1a.htm"
  ],
  "maxResults": 3
}

Run this fixed document separately to inspect an earlier disclosure stage. It remains a distinct filing observation; the Actor does not automatically merge it with the priced prospectus.

Coverage and reference

Supported disclosures

The Actor reads selected recent S-1/S-3 registrations and amendments, 424B1–5 prospectuses and 8-K disclosures under Items 1.01, 3.02, 7.01 or 8.01. If an 8-K primary document has no supported disclosure, the first HTML EX-99.1 is checked. It distinguishes priced offerings, completed issuance, proposed/registered offerings, resale registrations, shelf capacity and at-the-market sales-agreement capacity using explicit source wording.

Terms, currency and review flags

Stated share counts, per-share prices, gross proceeds, registration/sales capacity and warrant share counts are optional fields. They are populated only for supported wording and otherwise remain null. Currency is dollar_unspecified when the text uses a dollar sign without an unambiguous ISO currency. Evidence excerpts and review reasons accompany every observation. Financing prose is varied: every row is marked rule_based_review_required. Review the cited document before treating extracted terms as a complete deal description.

Pure share-count observations can have a null currency. A missing term is not treated as zero.

Filing identity and extraction limits

One filing document is one observation. Different accessions are separate disclosures, and may discuss the same financing. The Actor does not merge deals automatically, assume a shelf has been sold, infer percentage dilution, treat share authorizations as issued shares, compute discounts to a market price, or predict trading returns. Warrant and convertible mentions do not decode all exercise/conversion terms. The parser binds terms to the first supported financing paragraph and a narrow explicit current-offering pricing supplement. Later financing paragraphs are not merged, and a review reason records that limitation. The parser focuses on the document’s front cover or opening event discussion; it is not a comprehensive cap-table model.

Conflicting historical and current event wording is flagged for review rather than combined into a completed current offering.

Inputs and saved-history boundaries

• ciks: up to 10 exact SEC company identifiers. The source checks company identity before parsing filings.
• documentUrls: up to 10 specific official SEC HTML documents, validated against their accession index. Direct documents suppress the sample fallback. Combine them with explicit CIKs when intentional.
• maxFilingsPerCompany: 1–10 matching filings from the SEC’s current recent-submissions response; default 3. Old archive pages are not scanned.
• filedFrom: optional inclusive filing-date filter. Historical direct documents with unavailable filing dates do not pass a date filter.
• comparePrevious: save and compare observations in your named key-value store. The first run is a new baseline.
• onlyChanges: implies comparison and suppresses unchanged observations. A repeat can correctly save zero rows.
• snapshotName / stateStoreName: isolate workflows. Scope includes the exact watchlist, document URLs, date filter and filing bound. Use one writer per scope; overlapping runs are unsupported.

Only confirmed saved dataset rows advance history. A source failure cannot erase previous observations. No disappearance or deletion is inferred from bounded or missing filings.

Source access and run limits

SEC requests are sequential with at least 1.1 seconds between request starts; every request has a deadline and an 8 MiB response cap. There are no paid providers, proxies, generative-model calls or credential requirements. SEC refusals and timeouts remain visible in SUMMARY. Coordinate parallel runs to respect the SEC’s aggregate fair-access policy.

Source and interpretation

Data comes from official SEC submissions APIs and the EDGAR archive. See SEC developer resources for fair access. Filing acceptance time, disclosure/event date and observation time are different; this Actor does not promise real-time exchange data or a trading signal.

Questions about an extraction? Include the run ID, source URL and relevant excerpt when reporting it through the Actor’s Issues tab.

Explore Maydit data tools · Quality dashboard · Workflow recipes