Provided by SEC API
Get One Section of a 10-K, 10-Q or 8-K Filing as Text by URL (SEC API)
Get the plain text of one item section from a single 10-K, 10-Q or 8-K filing whose sec.gov document URL you already have. Supply url (the www.sec.gov/Archives/edgar/data path of the main document) and item: 10-K items like 1A (risk factors) or 7 (management's discussion and analysis), 10-Q items like part2item1a, 8-K items like 2-2. The item must belong to the form of that URL. Returns only that section's text, no HTML and no other sections; it does not search across filings.
Contract snapshot: 2026-09-29. Inspect in Glasser for current terms.
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"url",
"item"
],
"properties": {
"url": {
"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
},
"item": {
"enum": [
"1",
"1A",
"1B",
"1C",
"2",
"3",
"4",
"5",
"6",
"7",
"7A",
"8",
"9",
"9A",
"9B",
"9C",
"10",
"11",
"12",
"13",
"14",
"15",
"part1item1",
"part1item2",
"part1item3",
"part1item4",
"part2item1",
"part2item1a",
"part2item2",
"part2item3",
"part2item4",
"part2item5",
"part2item6",
"1-1",
"1-2",
"1-3",
"1-4",
"1-5",
"2-1",
"2-2",
"2-3",
"2-4",
"2-5",
"2-6",
"3-1",
"3-2",
"3-3",
"4-1",
"4-2",
"5-1",
"5-2",
"5-3",
"5-4",
"5-5",
"5-6",
"5-7",
"5-8",
"6-1",
"6-2",
"6-3",
"6-4",
"6-5",
"6-6",
"6-10",
"7-1",
"8-1",
"9-1",
"signature"
],
"type": "string"
}
},
"additionalProperties": false
}{
"url": "https://www.sec.gov/Archives/edgar/data/320193/000032019323000106/aapl-20230930.htm",
"item": "1A"
}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 /extractor on Glasser with input {"url":"https://www.sec.gov/Archives/edgar/data/320193/000032019323000106/aapl-20230930.htm","item":"1A"}glasser run -p secapi -e '/extractor' -i '{"url":"https://www.sec.gov/Archives/edgar/data/320193/000032019323000106/aapl-20230930.htm","item":"1A"}' --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":"/extractor","input":{"url":"https://www.sec.gov/Archives/edgar/data/320193/000032019323000106/aapl-20230930.htm","item":"1A"},"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 |