> ## Documentation Index
> Fetch the complete documentation index at: https://dev.jup.ag/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# llms.txt

> Structured documentation index optimised for LLM and AI agent consumption.

Jupiter provides structured documentation files purpose-built for LLMs and AI agents, following the [llmstxt.org](https://llmstxt.org) standard.

<Note>
  Jupiter's `llms.txt` is auto-generated from the documentation structure. Every page includes an `llmsDescription` field in its frontmatter, a description specifically optimised for LLM consumption, separate from the human-readable description. This ensures AI tools get the most relevant context for each page.
</Note>

## llms.txt

A plain Markdown file containing a structured index of all Jupiter documentation with titles and descriptions for each page:

* **Site title** as an H1 heading
* **Sections** for each major area (Docs, API References, Guides, Tool Kits, etc)
* **Links with descriptions** for every page

<Card title="llms.txt" href="https://developers.jup.ag/docs/llms.txt" icon="file" horizontal>
  Open the llms.txt for Jupiter docs
</Card>

```mdx theme={null}
# Jupiter

## Docs

- [Build with Jupiter](https://developers.jup.ag/docs/index.md)
- [Get Started](https://developers.jup.ag/docs/get-started/index.md): Welcome to Jupiter's Developer Docs...
- [Overview](https://developers.jup.ag/docs/swap/index.md): One API for all swap use cases on Jupiter.
- [API Reference](https://developers.jup.ag/docs/api-reference/index.md): Overview of Jupiter API Reference
```

This is the perfect entrypoint for LLMs and AI agents to get started. It allows them to efficiently locate relevant content at a high level without processing the entire documentation.

## llms-full.txt

<Card title="llms-full.txt" href="https://developers.jup.ag/docs/llms-full.txt" icon="file" horizontal>
  Open the llms-full.txt for Jupiter docs
</Card>

While `llms.txt` provides a concise index, `llms-full.txt` contains the **entire documentation site** as context, including every description, code example, and parameter detail.

Use `llms-full.txt` when:

* Your AI tool needs **complete, granular context** for deep indexing
* You're building **custom RAG pipelines** over Jupiter docs
* You want **every code example** available for reference

## Markdown Export

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**

```bash theme={null}
curl https://developers.jup.ag/docs/swap.md
curl https://developers.jup.ag/docs/swap/order-and-execute.md
```

**Method 2: Use the `Accept` header**

```bash theme={null}
curl -H "Accept: text/markdown" https://developers.jup.ag/docs/swap
```

Both methods return the page content as `text/markdown`.