XBRL Concept API: Get one as-reported XBRL metric series for a filer — SEC XBRL

Get one as-reported XBRL metric series for a filer — revenue, net income, cash and more, or any us-gaap tag — deduplicated 10-K/10-Q values with periods and source URL. Use instead of downloading companyfacts for one number.

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

How do you call it?

GET /v1/sec/xbrl/concept — product id sec_xbrl_concept. Over MCP, call answerpool_get with product_id=sec_xbrl_concept.

curl "https://answerpool.io/v1/sec/xbrl/concept?ticker=NVDA&metric=revenue"

Live call: https://answerpool.io/v1/sec/xbrl/concept?ticker=NVDA&metric=revenue · JSON sample: /v1/samples/sec_xbrl_concept

What does the answer look like?

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

points

{
 "as_of": "2026-08-31T14:00:00Z",
 "cik": "0000320193",
 "metric": "revenue",
 "tag": "Revenues",
 "unit": "USD",
 "points": [
  {
   "end": "2026-06-28",
   "value": 94000000000.0,
   "form": "10-Q",
   "fy": 2026,
   "fp": "Q3",
   "filed": "2026-08-01"
  }
 ],
 "source": "https://data.sec.gov/api/xbrl/companyconcept/CIK0000320193/us-gaap/Revenues.json",
 "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?

One metric, one company.

What you skip building

• companyfacts download
• tag hunting
• dedup across restatements

When should you not use it?

Full statements — use financials; cross-company — use compare/frame.

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