SEC Form Glossary API: List SEC form types with plain-English meaning and a covered flag — free lookup

List SEC form types with plain-English meaning and a covered flag for our 15-minute index — returns code, name, description per form. Free. Use to orient an agent before choosing which SEC endpoint to call.

Free — no key, no signup, rate-limited to 60 calls per minute per client.

How do you call it?

GET /v1/sec/forms — product id sec_form_glossary. Over MCP, call answerpool_get with product_id=sec_form_glossary.

curl "https://answerpool.io/v1/sec/forms"

Live call: https://answerpool.io/v1/sec/forms · JSON sample: /v1/samples/sec_form_glossary

What does the answer look like?

A representative response, the same static sample served at /v1/samples/sec_form_glossary.

entries

{
 "as_of": "2026-08-31T14:00:00Z",
 "count": 1,
 "entries": [
  {
   "code": "8-K",
   "name": "current_report",
   "description": "Material corporate events, itemized (we index all items).",
   "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?

First call when deciding which SEC product fits a task.

What you skip building

• reading SEC.gov form documentation

When should you not use it?

You already know the form type you need.

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