Event Flag Glossary API: List every event flag our SEC pipeline emits — free lookup
List every event flag our SEC pipeline emits — insider_buy_cluster, distress, accounting_red_flag, large_raise and more — with meanings. Free. Use once to filter the events and watch endpoints precisely.
Free — no key, no signup, rate-limited to 60 calls per minute per client.
How do you call it?
GET /v1/sec/flags — product id
sec_flag_glossary. Over MCP, call answerpool_get with
product_id=sec_flag_glossary.
curl "https://answerpool.io/v1/sec/flags"
Live call: https://answerpool.io/v1/sec/flags · JSON sample: /v1/samples/sec_flag_glossary
What does the answer look like?
A representative response, the same static sample served at /v1/samples/sec_flag_glossary.
as_of | 2026-08-31T14:00:00Z |
|---|---|
count | 1 |
refresh_after | 2026-09-17T11:15:00.000Z |
entries
| code | name | description | covered |
|---|---|---|---|
| insider_buy_cluster | insider_buy_cluster | Several distinct officers/directors buying the same issuer within a week. | true |
The same sample as raw JSON
{
"as_of": "2026-08-31T14:00:00Z",
"count": 1,
"entries": [
{
"code": "insider_buy_cluster",
"name": "insider_buy_cluster",
"description": "Several distinct officers/directors buying the same issuer within a week.",
"covered": true
}
],
"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?
Before filtering any flagged feed.
What you skip building
- guessing flag semantics
When should you not use it?
n/a - free reference data.
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