Events tagged by the item reported, not a text search

Find out what just happened

What has NVIDIA filed an 8-K about in the last six months?

An 8-K declares what kind of event it reports, in its item numbers, and those item numbers are structured data. So this does not search text: it lists the filings in a window, labels every item code, and returns body text only for the items that matter, with citations. An agent asking whether the CFO changed wants item 5.02, not a keyword.

Recorded NVIDIA Corp, 8-Ks filed 2026-04-27 to 2026-10-24, on 23 October 2026 against parser version 3. Responses are trimmed to the fields the example is about; elisions are marked.

`recent_8k_events`

Sweep a window of 8-Ks and get them back classified.

Request

{
  "tool": "recent_8k_events",
  "arguments": {
    "ticker": "NVDA",
    "lookback_days": 180,
    "limit": 5,
    "max_tokens_per_filing": 300
  }
}

Response

{
  "data": [
    { "accession": "0001045810-26-000078", "filed_at": "2026-09-03",
      "items": [ { "code": "8.01", "label": "Other Events",
                   "category": "other" } ] },
    { "accession": "0001045810-26-000073", "filed_at": "2026-08-26",
      "items": [ { "code": "2.02",
                   "label": "Results of Operations and Financial Condition",
                   "category": "earnings" },
                 { "code": "9.01",
                   "label": "Financial Statements and Exhibits",
                   "category": "exhibits" } ],
      "events": [ { "code": "2.02", "category": "earnings",
                    "text_found": true, "paragraph_count": 4,
                    "chunks": [ {
                      "text": "On August 26, 2026, NVIDIA Corporation, or the
                                Company, issued a press release announcing its
                                results for the quarter ended July 26, 2026. ...",
                      "para_idx": 1,
                      "citation": "0001045810-26-000073 item_2_02 para 1 chars 2097-2322 parser v3"
                    } ] } ] },
    { "accession": "0001045810-26-000069", "filed_at": "2026-08-17",
      "items": [ { "code": "1.01", "category": "material_agreement" },
                 { "code": "2.03", "category": "debt" },
                 { "code": "7.01", "category": "reg_fd" } ] },
    { "accession": "0001045810-26-000060", "filed_at": "2026-07-02",
      "items": [ { "code": "5.02", "category": "leadership" } ] },
    { "accession": "0001045810-26-000056", "filed_at": "2026-06-30",
      "items": [ { "code": "5.07", "category": "governance" } ] }
  ],
  "meta": {
    "lookback_days": 180, "date_from": "2026-04-27", "date_to": "2026-10-24",
    "date_basis": "filed", "filings_in_window": 9, "filings_matching": 9,
    "returned": 5, "truncated": false, "returned_tokens": 1327
  }
}

Nine filings in the window, five returned because five were asked for, and truncated is false because no budget dropped anything. Pass event_types to narrow: event_types: ["leadership"] returns the 5.02 and never reads the text of the rest.

What to take from this

category is ours and code is the SEC's. Filter on category when you want "anything about debt" and on code when you know exactly which item you mean.
date_basis says the window is on the filing date, not the event date. An 8-K about a July event filed in August falls in the August window, and that distinction decides whether a backtest is looking at information it could actually have had.
Body text is fetched only for the items that matter, which is why nine filings cost 1,327 tokens instead of nine whole documents.

Next: Compare growth against the industry. Or run these tools against a filer of your own in the filing explorer, or read the full argument reference under the filings API.