← Blog

SEC 8-K Event Triage for AI Agents — Auto-Classified, Severity-Ranked

Every US public company files an 8-K when something material happens. Pipeworx's sec-events pack pre-classifies every filing by severity so AI agents get the news that mattered, not just a list.

When something material happens to a US public company — a restatement, a CEO departure, an acquisition, a cybersecurity incident, a bankruptcy — they file an SEC Form 8-K within four business days. Roughly 100–500 of these land at EDGAR every business day across thousands of public filers.

The data is gold for any AI agent answering “what just happened with $TICKER” or “any breaking corporate news today.” But every existing tool we evaluated just hands the agent a raw list of recent 8-Ks. The agent then has to figure out which Item codes mean what, which filings are noise, and which actually matter — burning context on triage that should happen upstream.

Pipeworx’s sec-events pack does that triage for you. Every 8-K is pre-classified by SEC Item code into one of four severity tiers, surfaced through a clean MCP interface, and refreshed every 30 minutes during US market hours.

How severity works

SEC’s 8-K form has 23 official Item codes — categories like “Item 4.02: Non-Reliance on Previously Issued Financial Statements” (a restatement, very bad) or “Item 9.01: Financial Statements and Exhibits” (procedural, barely news). The codes are already in every filing; nobody has to interpret them. We just map them to severity:

  • high — restatements (4.02), change of control (5.01), bankruptcy (1.03), cybersecurity incidents (1.05), material impairments (2.06)
  • medium — M&A close (2.01), earnings (2.02), material agreements (1.01), officer changes (5.02), delisting notices (3.01)
  • low — Reg FD disclosures (7.01), unregistered equity sales (3.02), auditor changes (4.01)
  • noise — shareholder vote results (5.07), generic “other events” (8.01), exhibit filings (9.01)

The default severity filter in our query tools is high+medium, so an agent asking “what mattered today” automatically skips the procedural noise.

The tools

sec_8k_recent

Recent 8-K filings for a specific ticker, severity-sorted. The agent calls this when asked “did Apple file anything?” or “what’s new with $NVDA?”.

sec_8k_recent(ticker: "NVDA", days: 30)
→ {
    ticker: "NVDA",
    events: [
      { severity: "medium", filed_at: "2026-05-20", items: ["2.02","9.01"],
        item_descriptions: ["Results of Operations and Financial Condition", ...],
        summary: "NVIDIA reported Q1 fiscal 2027 results with revenue of $X..." },
      ...
    ]
  }

sec_8k_by_item

Cross-market scan for a single Item code. “Every restatement (Item 4.02) this month” returns every public company that disclosed they couldn’t rely on their prior financials — a signal that historically precedes share-price corrections.

sec_8k_by_item(item: "1.05", days: 30)
→ every cybersecurity incident disclosed across the entire US public market

sec_8k_today

What 8-K material events filed today (or in the most recent trading session), severity-ranked, defaults to high+medium only. The “any breaking corporate news?” tool.

sec_8k_detail

Full structured record for one filing by accession number — after one of the above surfaces a filing of interest, fetch the complete metadata + LLM-extracted summary.

The enrichment pass

For high and medium severity filings, a second cron pass fetches the actual 8-K body from EDGAR, runs Workers AI extraction, and populates three fields:

  • summary — 1–2 sentence plain-English description that leads with the news (“Travelers Companies shareholders approved a $5M increase to the 2023 Stock Incentive Plan”) instead of the SEC boilerplate (“On May 21, 2026, the Company filed…”)
  • counterparties — array of named third parties (acquired company, departing officer, contracting vendor)
  • amount_usd — the headline dollar figure when one is stated

Low and noise severity rows skip enrichment entirely — they’re filed for completeness but rarely worth an LLM call.

What lives in the table right now

As of this post, the sec_8k_events table holds roughly 8,000 filings covering the last 30 days, refreshing every 30 minutes during US market hours. Real high-severity events surfaced in that window include:

  • Bitcoin Depot ($BTM) — bankruptcy filing (Item 1.03 + triggering events 2.04)
  • West Pharmaceutical ($WST) — material cybersecurity incident (Item 1.05)
  • NeuroOne Medical ($NMTC) — restatement of prior financials (Item 4.02)
  • Canopy Growth ($CGC) — restatement
  • Multiple change-of-control deals under Item 5.01 across mid-cap biotech and energy

None of these would be surfaced by a vanilla “recent SEC filings” tool that just lists everything chronologically.

Why this matters for an agent

The cost of a bad answer to “what just happened to $TICKER” is high. If your agent quotes outdated info from training data and there’s been a restatement, an officer departure, or a bankruptcy filing in the meantime, the answer is worse than no answer. Existing approaches:

  1. Web search — slow, unstructured, hallucinates dates, often returns secondary reporting rather than the primary filing.
  2. Raw 8-K listing tools — agent has to read every filing’s Item codes and decide what matters, burning context.
  3. sec-events — pre-classified, severity-ranked, with LLM-extracted summaries on the events that matter. The agent gets “high-severity material events for $NMTC in the last 30 days” in one sub-second call.

Try it from any MCP-enabled agent connected to Pipeworx — the tools are live now, no API key required.