Retrieve Filing Markdown
filings_markdown_retrieveRetrieve the raw processed content of a single filing in Markdown format.
When to use this tool: Use to get the full text of a filing as Markdown. Supports pagination via offset/limit for long documents. Start with offset=0 and repeat with increasing offsets until the truncation marker is gone, you have found what you were asked for, or you have made 10 calls — whichever comes first. Stop at the cap and say the document was truncated rather than paginating a long filing indefinitely against the request budget.
When NOT to use this tool: Don't use to search for filings — use filings_list first. Not every filing has Markdown content. If a filings_list row shows a processing_status other than "COMPLETED", that filing has no Markdown available (it may still be processing, or may never get any) — if the user asked for THAT filing (e.g. the latest), say so rather than silently answering from an older one. If the field is null or absent, that means unknown — call this tool anyway; a not-found error means no Markdown is available for that filing (do not promise it will appear), while any other error is about access or availability.
Examples:
Show me Apple's 10-K risk factors -> filing_id=, offset=0, limit=50000 (Summarize specific sections — don't dump the whole document)
Returns the full processed Markdown content of a filing in pageable chunks. For long filings, call this tool repeatedly with increasing
offsetvalues until the response no longer contains the truncation marker. Use a limit of 50000 chars (default) for most LLM context windows; the per-call cap is 150000 chars for the whole result (Claude.ai's documented tool-result ceiling), so a full-size slice is trimmed by the length of the header.
[Server current date: 2026-10-09 — treat this as today.]
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| offset | No | ||
| filing_id | Yes |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |