Body-text-classified 8-Ks for systematic strategies.

If your alpha includes any signal from corporate filings, you've already discovered that filer-reported 8-K item codes are noisy. We re-classify every 8-K from body text and flag the 7.3% of Item 8.01 filings that actually contain Item 1.05 (cyber) or 5.02 (officer departure) language.

Sound familiar?

• You built an EDGAR scraper, then re-built it after a sec.gov layout change. Twice.
• You're relying on filer-reported item codes that miss material events buried in 8.01.
• Backfill across 10 years of filings would take weeks of compute on your end.
• You need parsed structured data, not raw HTML.

What you can do with FilingFirehose

Example

import requests
r = requests.get(
    "https://filingfirehose.com/v1/filings/8-k",
    headers={"X-API-Key": "ff_live_..."},
    params={"items": "1.05", "since": "2024-01-01", "limit": 1000},
)
for f in r.json()["filings"]:
    print(f["company_name"], f["filed_at"], f["suspected_buried_events"])

Pricing

Recommended tier: Pro at $99/mo for single-strategy backtests, or Quant at $299/mo for production systematic use (5-min SLA, contracts endpoint, multi-seat). See pricing →

Other personas using FilingFirehose

• For compliance officers — Monitoring competitor 13D filings is a job, not a hobby.
• For fintech journalists — Find buried disclosures before the WSJ does.
• For fintech developers — SEC EDGAR as a JSON API your AI agent can hit.
• For activist investors / 13d watchers — Track every Saba 13D within 30 seconds of filing.