I built FilingFirehose because manually monitoring SEC EDGAR is genuinely unreliable. You can set up RSS feeds and email alerts, but they only surface the filer-reported item codes — if a company routes a cybersecurity incident through Item 8.01 ("Other Events") instead of Item 1.05, every alert you've set up will miss it. That was the moment I realized the problem: EDGAR data at the metadata level is incomplete by design, because the item codes are self-reported. The wedge is a stat we found in our own data: 7.3% of 8-K Item 8.01 filings contain body text that matches patterns we'd associate with more specific item codes — things like cybersecurity language, officer departure language, or material agreement language. That's roughly 1 in 14 filings with a buried event that nobody else surfaces. We built the classifier, ran it against 4,251 filings from the past 21 business days, and found 54 cases. We publish the full analysis at filingfirehose.com/research/buried-events. We ship FilingFirehose across four distribution surfaces: a REST API (JSON responses, no auth for the past 72h), an MCP server for AI agents, a ChatGPT GPT for natural-language queries, and a GitHub Action for repo-level alerting. The free public tier covers the past 72 hours with no authentication required — just hit /v1/public/8k. Paid plans start at $29/month (Starter), go up to $299/month (Pro), and we offer a $999 lifetime deal for folks who want to pay once. Happy to answer any questions about the data, the classifier, or the API.

FilingFirehose

SEC EDGAR filings API that catches buried disclosures

SEC EDGAR filings API that catches buried disclosures