Markdown & llms.txt | Sarvam API Docs

These docs are published in formats that large language models read cleanly. Use them to give any LLM accurate, current context about the Sarvam API — no scraping, no stale training data.

What’s available

Resource	What it contains	Best for
`llms.txt`	A structured index of every page with titles, links, and summaries	Retrieval — let a tool pick the right pages to load
`llms-full.txt`	The entire documentation concatenated into one file	Pasting the whole corpus into a large context window
Per-page `.md`	The clean Markdown source of any single page	Loading just one topic

These follow the llms.txt convention. llms-full.txt and per-page .md exports are regenerated on every deploy; the llms.txt index is curated in fern/agents/llms.txt in this repository.

Read any page as Markdown

Append .md to any documentation URL to get the raw Markdown, with no navigation or styling:

$ curl https://docs.sarvam.ai/api-reference-docs/getting-started/quickstart.md

This is the quickest way to drop a single page into an LLM prompt or a RAG index.

How to use it

Give an assistant the whole API

Paste the contents of llms-full.txt into a model with a large context window when you want it to reason over the complete API in one shot.

Index for retrieval

Fetch llms.txt, then load only the linked pages you need (each is available as .md). This keeps prompts small and relevant.

Pin a single topic

Add .md to one page’s URL and include just that page when the task is narrow (e.g. only text-to-speech streaming).

When to use `llms.txt` vs the MCP server

Both make the docs available to AI — they suit different workflows:

	`llms.txt` / Markdown	MCP server
How it works	You fetch files and put them in the model’s context	The assistant searches the docs live, on demand
Best for	Bulk ingestion, RAG indexes, offline/one-shot context, scripts	Interactive coding sessions in Cursor / Claude Code
Freshness	A snapshot from when you fetched it	Always queries the current docs
Setup	None — just a URL	One-time client configuration

Rule of thumb: use the MCP server when an assistant should pull docs while you code; use llms.txt when you want to load documentation into a model yourself.

For docs contributors

The published llms.txt is sourced from fern/agents/llms.txt in this repo. When you add, rename, or remove a documentation page, update that file with a one-line entry: title, canonical .md URL, and a short summary copied from the page’s frontmatter description.

llms-full.txt and per-page .md exports are regenerated automatically on deploy — only the curated index needs a manual update.