Event Explain API: Explain one indexed filing — free lookup
Explain one indexed filing — returns its form, 8-K items and labels, and every derived event with flags and salience score, free. Use to audit any signal from our paid SEC endpoints against the underlying filing.
Free — no key, no signup, rate-limited to 60 calls per minute per client.
How do you call it?
GET /v1/sec/event — product id
sec_event_explain. Over MCP, call answerpool_get with
product_id=sec_event_explain.
curl "https://answerpool.io/v1/sec/event?accession=0001193125-26-380280"Live call: https://answerpool.io/v1/sec/event?accession=0001193125-26-380280 · JSON sample: /v1/samples/sec_event_explain
What does the answer look like?
A representative response, the same static sample served at /v1/samples/sec_event_explain.
as_of | 2026-09-16T21:31:38Z |
|---|---|
accession | 0001193125-26-380280 |
form | 8-K |
filed_at | 2026-09-02 |
company | MICROSOFT CORP |
ticker | MSFT |
filing_url | https://www.sec.gov/Archives/edgar/data/789019/000119312526380280/0001193125-26-380280-index.htm |
items | 7.01, 9.01 |
labels | regulation_fd, exhibits |
refresh_after | 2026-09-17T11:15:00.000Z |
events
| event_id | accession | cik | ticker | company | form | event_type | occurred_at | flags | score | payload.items | payload.labels |
|---|---|---|---|---|---|---|---|---|---|---|---|
| ev_7941f719cb394dfab6d9 | 0001193125-26-380280 | 0000789019 | MSFT | MICROSOFT CORP | 8-K | form_8k | 2026-09-02 | regulation_fd | 0.1 | 7.01, 9.01 | regulation_fd, exhibits |
The same sample as raw JSON
{
"as_of": "2026-09-16T21:31:38Z",
"accession": "0001193125-26-380280",
"form": "8-K",
"filed_at": "2026-09-02",
"company": "MICROSOFT CORP",
"ticker": "MSFT",
"filing_url": "https://www.sec.gov/Archives/edgar/data/789019/000119312526380280/0001193125-26-380280-index.htm",
"items": [
"7.01",
"9.01"
],
"labels": [
"regulation_fd",
"exhibits"
],
"events": [
{
"event_id": "ev_7941f719cb394dfab6d9",
"accession": "0001193125-26-380280",
"cik": "0000789019",
"ticker": "MSFT",
"company": "MICROSOFT CORP",
"form": "8-K",
"event_type": "form_8k",
"occurred_at": "2026-09-02",
"flags": [
"regulation_fd"
],
"score": 0.1,
"payload": {
"items": [
"7.01",
"9.01"
],
"labels": [
"regulation_fd",
"exhibits"
]
},
"filing_url": "https://www.sec.gov/Archives/edgar/data/789019/000119312526380280/0001193125-26-380280-index.htm"
}
],
"refresh_after": "2026-09-17T11:15:00.000Z"
}How fresh is it, and where does the data come from?
The fastest source behind this answer can change every 15 minutes, so every response carries a refresh_after timestamp — right now it would be 2026-09-17T11:15:00.000Z. Schedule the next call on that value rather than on a guess.
- SEC EDGAR (US federal public domain) — upstream:
https://efts.sec.gov
Method version 0.1.0 ·
serving cache 1 day ·
every response carries a result_id you can resolve at
/v1/provenance.
When should you use it?
Verifying or debugging a flag from any events endpoint.
What you skip building
- re-deriving flags
- cross-referencing filings to events
When should you not use it?
Discovery — it takes one known accession number.
Where else can you find this?
- Catalog entry (JSON, free)
- OpenAPI schema — input and output types, prices, the 402 flow
- llms.txt — every product in one plain-text document