Provided by SEC API
Get Financial Statements of One SEC Filing as JSON from XBRL (SEC API)
Get the XBRL financial data of one EDGAR filing, such as a 10-K or 10-Q, converted to JSON: income statement, balance sheet, cash flow statement and stockholders' equity, each line item with its period and unit. Supply exactly one of accessionNo (like 0000320193-23-000106), htmUrl (the sec.gov URL of the filing document) or xbrlUrl (the URL of its XBRL instance file). A filing without XBRL attached returns no statements and is not charged.
Contract snapshot: 2026-09-29. Inspect in Glasser for current terms.
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"htmUrl": {
"type": "string",
"pattern": "^https:\\/\\/www\\.sec\\.gov\\/Archives\\/edgar\\/data\\/\\d{1,10}\\/\\d{18}\\/[A-Za-z0-9][A-Za-z0-9._-]*$",
"maxLength": 300
},
"xbrlUrl": {
"type": "string",
"pattern": "^https:\\/\\/www\\.sec\\.gov\\/Archives\\/edgar\\/data\\/\\d{1,10}\\/\\d{18}\\/[A-Za-z0-9][A-Za-z0-9._-]*$",
"maxLength": 300
},
"accessionNo": {
"type": "string",
"pattern": "^\\d{10}-\\d{2}-\\d{6}$"
}
},
"additionalProperties": false
}{
"accessionNo": "0000320193-23-000106"
}This Endpoint publishes no output schema. You get the Provider's own response body, unchanged — we do not warrant a shape we cannot guarantee.
How to run it
Two fields identify it: the Provider and the endpoint key. The key looks like a path because it usually mirrors the Provider's own, but it is an opaque identifier — not a URL you can open. The same provider:endpoint pair is what your Policy lists.
Once: paste this into your agent's chat. The Skill installs the CLI and logs in by itself. For an agent that cannot use a shell, connect it over MCP instead.
set up https://glasser.ai/SKILL.mdThen ask for this Endpoint:
Run the SEC API Endpoint /xbrl-to-json on Glasser with input {"accessionNo":"0000320193-23-000106"}glasser run -p secapi -e '/xbrl-to-json' -i '{"accessionNo":"0000320193-23-000106"}' --endpoint-version 1Pinned to version 1, the one this page shows: if a newer version is published first, the Run is refused instead of charged under new terms. Install and log in first on Get Started.
Once per Run:
IDEMPOTENCY_KEY=$(uuidgen)Run it, and copy this same block to send it again:
curl -X POST https://api.glasser.ai/v1/runs \
-H "Authorization: Bearer gl_..." \
-H "Idempotency-Key: $IDEMPOTENCY_KEY" \
-H "Content-Type: application/json" \
-d '{"provider":"secapi","endpoint":"/xbrl-to-json","input":{"accessionNo":"0000320193-23-000106"},"endpoint_version":1}'Reuse the same Idempotency-Key to send it again: the second send is a read of the first Run. A new key is a new Run and a new Charge. Pinned to version 1 for the same reason as the CLI.
What each outcome charges
| No result | The Provider answered: nothing matched. | $0.00 |
|---|---|---|
| Provider error | The Provider failed to answer. | $0.00 |
| Timed out | The deadline won. | $0.00 |
| Internal failure | Our defect. | $0.00 |