Material corporate events rarely wait for the quarterly earnings cycle. An unexpected CEO departure, a goodwill impairment, or a credit agreement amendment can reprice a stock in minutes. The information is public the moment the 8-K hits EDGAR. The edge goes to teams that route it to the right person fastest.
The challenge is not finding 8-Ks. They are public and voluminous, but separating signal from the daily flood of routine items. Press releases dressed as 8-Ks, administrative changes, and immaterial agreements drown the filings that actually change a thesis.
Vantafin gives you multiple surfaces for 8-K monitoring: the F WebSocket channel streams live SEC filing metadata (not full text), GET /filings/{ticker}?form= returns filing metadata over REST, the app supports semantic document search across filing text, and the MCP search_filings tool queries by keyword and form type. Vantafin does not offer webhook or Slack delivery. Alerts go to email only. This guide shows how to build a monitor that surfaces the events risk teams care about first.
Stream and query filings
Subscribe to the F channel for tickers in your watchlists with {"action":"subscribe","params":"F.AAPL"}. Filing metadata arrives as submissions hit EDGAR (accession number, form type, filed-at timestamp, and related fields) so you can react before you have read the full document. For full text, use the app's filing search on the company SEC filings page or search_filings via the MCP server.
Over REST, GET /filings/{ticker}?form=8-K fetches recent 8-K metadata for batch processing and overnight digests. Combine form filters with keyword search in the app or MCP ("impairment," "going concern," "restatement," or "data breach") to catch language that item numbers alone miss. Map results to company pages like Amazon for instant financial context so the reader does not context-switch across three tools to decide urgency.
Store the accession number and filed-at timestamp with every hit. Those two fields deduplicate retries and anchor audit trails if compliance asks what you knew and when.
Route to humans via email alerts
Detection without routing is an academic exercise. Configure email alerts for filing events on your coverage universe. Price, filing, and news alerts all deliver via email. Tune severity by creating separate alert rules: officer-departure keywords on 8-Ks might go to a high-priority rule; routine quarterly items can batch into a daily digest you review over coffee.
Write alert rules that name owners in your process even though delivery is email. A filing alert that lands in a shared inbox with forty members often gets read by nobody. Forward rules or distribution lists that map tickers to coverage analysts keep accountability clear.
For agent-assisted triage, connect the MCP server so Cursor can call search_filings and summarize an 8-K, citing the exact paragraph that triggered your rule. The human still decides; the agent shrinks time-to-first-read from ten minutes to two.
Operational tips
Cache accession numbers to avoid duplicate alerts when your poller overlaps a filing that straddles two windows. Respect rate limits documented on pricing; exponential backoff on errors prevents a brief outage from becoming a ban. Cross-link to management guidance workflows when Item 2.02 drops alongside earnings) guidance revisions and results filings often arrive in the same session and belong in one note.
Review false positives monthly. Keywords like "breach" catch cybersecurity incidents and also catch "no breach occurred" boilerplate in legal disclaimers. Tighten rules with negative filters when you see patterns. Learn more about our filing coverage on about.
Filtering what matters to your desk
Form 8-K Item 1.01 through 8.01 covers acquisitions, officer departures, impairments, credit agreements, and other events that move stocks intraday. Vantafin's filings metadata routes and the F WebSocket channel on wss://socket.vantafin.com/v1/stocks) deliver new submissions the moment EDGAR indexes them for tickers you subscribe to. Each F message carries form type, filed date, accession number, and EDGAR URL; fetch full document text through REST or search inside filings in the app.
Tune monitoring to the items you actually trade. Credit agreements matter for distressed desks; officer changes matter for governance-focused funds; impairments matter for value investors. Source symbols from watchlists and screener exports, and refresh the list weekly so IPO additions and spin-offs stay covered. The in-app filing search supports semantic queries across chunked text. Pair metadata alerts with keyword searches for "impairment," "going concern," or "restatement" when item numbers alone miss the operative language.
Store accession number and filed-at timestamp with every hit. Those two fields deduplicate retries and anchor audit trails if compliance asks what you knew and when.
Routing to humans with email alerts
Detection without routing is an academic exercise. Configure email filing alerts by form type (8-K, 10-K, 10-Q) and bind the universe to watchlists you already maintain. Tune severity by form and keyword: officer departures might go to a coverage analyst immediately; routine quarterly filings can batch into a lower-priority rule you review at midday.
On alert, snapshot price via bulk quote snapshots and compare to the prior close. Material news with muted price response may mean the market already knew, or it may mean the headline requires a second read of the exhibit. Either interpretation is useful; treating every 8-K as automatically bullish or bearish wastes reaction time.
Connect the MCP server to draft a three-bullet summary with citations (search_filings finds the triggering paragraph; list_filings confirms you have the latest accession. Human review before trading remains mandatory, but the first pass saves twenty minutes per event.
Production checklist
Confirm entitlements on pricing, handle rate-limit responses with backoff, and dedupe repeat filings for the same event. Upstream systems occasionally deliver retries that look like new events if your consumer lacks idempotent keys. Separate Form 144 planned sales into a different alert rule when insider supply deserves its own inbox folder rather than mixing with operational 8-K items.
Treat the monitor as infrastructure, not alpha. The edge comes from interpretation speed and historical pattern recognition, not from merely receiving the filing first. Archive alert metadata alongside subsequent price paths to study which item types predicted sustained moves in your universe.