Skip to content

llms.txt and raw docs

Fetch these docs as clean Markdown, one page or all of them, so an agent can read them in a single request.

Updated Oct 8, 2026 · 1 min read

Every page of these docs is available as plain Markdown. An agent can read one page, the index, or everything at once, without parsing HTML.

URLWhat you get
/llms.txtAn index of every docs page with a one-line description, plus links to the OpenAPI spec, the data model and the MCP server (llmstxt.org format).
/llms-full.txtAll public docs as Markdown in one file.
/docs/<page>.mdOne page as Markdown, e.g. /docs/guides/payouts.md. The docs home is /docs.md.

Markdown pages are served as text/markdown; charset=utf-8. Every HTML docs page also advertises its Markdown version with <link rel="alternate" type="text/markdown">.

How components appear in Markdown#

The HTML docs use a few components. In Markdown they become plain equivalents:

  • Callouts become blockquotes that start with Note:, Tip:, Warning:, Important: or For agents:.
  • Steps become bold Step 1: … labels followed by the step's text.
  • Tabbed code examples become consecutive code blocks, each preceded by its label.
  • Cards become a list of links with descriptions.
  • The plan limits table becomes a Markdown table built from the live plan values.

Links to other docs pages point at their .md versions, so an agent can keep following them.

Stable anchors#

Heading anchors (#section-name) are derived from heading text, and we avoid renaming published headings. If a heading is renamed, the old link still lands on the page, just without scrolling to the section.

From the docs page#

Every page has a Copy page menu next to its title: copy the page as Markdown, open the .md version, or open it in Claude or ChatGPT with a prompt that points at the page.