Expand AI logo
DocsDocs
Glow Active
API Reference
Login

Documentation

Get Started

OverviewWhy ExpandQuickstartWays to Use Expand

Agent Quickstarts

OverviewExpand SkillClaude CodeCursorCodexOpenCodeSkill-Based AgentsOther MCP Clients

Fetch

OverviewHow Fetch WorksOutput ModelInclude OptionsBrowser BehaviorHighlightsPlayground & ReplayBatched Fetch

Reference

API ReferenceCLI CommandsMCP Tools & ResourcesTypeScript SDKPython SDK

Account & Billing

Pricing & UsageTiersFAQ

Machine-Readable Docs

start.mdllms.txtllms-full.txtDocs as Markdown
Browse docs

Get Started

OverviewWhy ExpandQuickstartWays to Use Expand

Agent Quickstarts

OverviewExpand SkillClaude CodeCursorCodexOpenCodeSkill-Based AgentsOther MCP Clients

Fetch

OverviewHow Fetch WorksOutput ModelInclude OptionsBrowser BehaviorHighlightsPlayground & ReplayBatched Fetch

Reference

API ReferenceCLI CommandsMCP Tools & ResourcesTypeScript SDKPython SDK

Account & Billing

Pricing & UsageTiersFAQ

Machine-Readable Docs

start.mdllms.txtllms-full.txtDocs as Markdown

Docs as Markdown

Read authored docs and API Reference pages as Markdown.

Every Expand docs page is available as Markdown. Append .md to any docs URL when you want to give an agent one specific page without the surrounding docs UI.

HTML
https://expand.ai/docs/get-started/quickstart

Markdown
https://expand.ai/docs/get-started/quickstart.md

Fetch the page from a terminal or pipe it straight to your clipboard:

curl https://expand.ai/docs/get-started/quickstart.md
curl https://expand.ai/docs/get-started/quickstart.md | pbcopy
  • Open Markdown — /docs/get-started/quickstart.md
  • Copy URL — https://expand.ai/docs/get-started/quickstart.md
  • Open llms.txt — /llms.txt

    • .md endpoints

    Append .md to an Expand docs URL to get the Markdown version of that page.

    Human pageMarkdown page
    /docs/get-started/quickstart/docs/get-started/quickstart.md
    /docs/fetch/how-fetch-works/docs/fetch/how-fetch-works.md
    /api-reference/api-reference.md

    .mdx routes are also supported, but .md is the recommended form to share with agents.

    What the Markdown contains

    The Markdown opens with the page title and its canonical human URL, then the processed page content:

    # Quickstart (https://expand.ai/docs/get-started/quickstart)

...

    Each Markdown response includes:

    • page title;
    • canonical human URL;
    • processed Markdown content;
    • code blocks and tables as Markdown;
    • links preserved as Markdown links where the docs renderer emits them;
    • no docs navigation, sidebar, or page chrome.

    Docs-as-Markdown returns processed Markdown, not raw MDX source. It is meant for reading and retrieval, not for reconstructing the docs page implementation.

    Copy as Markdown

    On authored docs pages, use the Copy Content menu to copy the current page as Markdown or open the Markdown URL directly. The copied content is the same processed Markdown the .md URL serves, so a teammate or agent reading the link sees exactly what you copied.

    Using Markdown with agents

    Single page context

    Use one .md page when the agent needs help with one feature or workflow.

    Read https://expand.ai/docs/fetch/output-model.md and show me how to access main Markdown and State JSON from the SDK.

    Multiple page context

    Use two or three .md pages when the task spans a workflow.

    Read these Expand docs before answering:

- https://expand.ai/docs/fetch/output-model.md
- https://expand.ai/docs/fetch/highlights.md
- https://expand.ai/docs/fetch/playground-and-replay.md

Then explain how to build a deep research agent with user-visible citations.

    Full docs context

    For one topic, prefer the specific .md page. Use /docs/llms-full.txt only when the agent needs broad authored-docs context and has enough context budget.

    Content negotiation

    This is advanced behavior, not the primary path. Tools that support request headers can ask for Markdown from the human URL with Accept: text/markdown.

    curl -H "Accept: text/markdown" https://expand.ai/docs/get-started/quickstart

    This is useful for agents that prefer to keep canonical human URLs. For explicit links, .md URLs are easier to inspect and share. Negotiation applies to /docs and /api-reference pages, not to every route on the site.

    Docs versus API Reference

    Use authored docs Markdown for workflows and explanations. Use API Reference Markdown for exact endpoint schemas, parameters, errors, and generated examples.

    Authored docs
https://expand.ai/docs/fetch/output-model.md

API Reference
https://expand.ai/api-reference/fetch/fetch.fetch.md

    Which machine-readable route should I use?

    NeedUse
    Agent setup/start.md
    First orientation/llms.txt
    Docs table of contents/docs/llms.txt
    One authored docs page

    Agent guidance

    • Prefer current Markdown docs over memorized behavior.
    • Use API Reference Markdown for exact request and response shapes.
    • Use specific .md pages before pulling the full docs bundle.
    • Do not assume undocumented endpoints, CLI flags, SDK methods, or schemas exist.
    • Follow canonical URLs in Markdown headers when citing or revisiting docs.

    Related pages

    • start.md
    • llms.txt
    • llms-full.txt
    Previousllms-full.txt

    On This Page

    .md endpointsWhat the Markdown containsCopy as MarkdownUsing Markdown with agentsSingle page contextMultiple page contextFull docs contextContent negotiationDocs versus API ReferenceWhich machine-readable route should I use?Agent guidanceRelated pages
    /api-reference/fetch/fetch.fetch
    /api-reference/fetch/fetch.fetch.md
    /docs/...md
    One API Reference page/api-reference/...md
    Full authored-docs bundle/docs/llms-full.txt