Skip to main content
Meteora provides structured documentation files purpose-built for LLMs and AI agents, following the llmstxt.org standard.
Use llms.txt when your agent needs a compact map of the docs. Use Documentation MCP when your AI tool can call MCP tools and should search or read pages interactively.

​
llms.txt

A plain Markdown file containing a structured index of Meteora documentation with titles and descriptions for each indexed page:
  • Site title as an H1 heading
  • Sections for major areas such as Get Started, User Guides, Core Products, Helper Products, Developer Guides, Invent, Agents, Protocol, and Resources
  • Links with descriptions for product guides, SDK references, API references, and resources
  • OpenAPI spec links where API reference specifications are indexed

llms.txt

Open the llms.txt for Meteora docs
This is the best first fetch for agents that need to decide which Meteora product, guide, SDK reference, API reference, or raw Markdown page to read next.

​
llms-full.txt

llms-full.txt

Open the llms-full.txt for Meteora docs
While llms.txt provides a concise index, llms-full.txt contains the entire documentation site as context, including descriptions, code examples, guides, API references, and product explanations. Use llms-full.txt when:
  • Your AI tool needs complete, granular context for deep indexing
  • You’re building custom RAG pipelines over Meteora docs
  • You want every code example available for reference

​
Raw Markdown Pages

Any documentation page can be accessed as raw Markdown, making it easy for AI agents to consume individual pages programmatically. Method 1: Append .md to the URL
Method 2: Use the Accept header
Both methods return the page content as text/markdown.

​
How Agents Should Use These Files

For most agent workflows, start with llms.txt, fetch only the relevant .md pages, and use llms-full.txt only when you intentionally want the full corpus in one document.