# llms.txt examples

> Annotated llms.txt patterns — a minimal file, a docs-heavy file, and the llms-full.txt pairing — so you can copy the structure that fits your site.

The fastest way to write a good llms.txt is to start from one that works. Here are three patterns you can adapt.

## 1. The minimal file

Perfect for a small product or landing site. Title, summary, one section of key links.

```
# Acme

> Acme turns CSV files into charts. This file links to the docs an LLM needs to help users.

## Docs

- [Quickstart](https://acme.com/start): Upload a CSV and get a chart in 60 seconds
- [Pricing](https://acme.com/pricing): Plans and limits
```

## 2. The docs-heavy file

For API/SDK sites. Group by purpose, link the Markdown versions of pages, and use an Optional section for secondary material.

```
# Acme API

> REST API for chart generation. Authentication, endpoints, and SDKs below.

## Getting started

- [Authentication](https://acme.com/docs/auth.md): API keys and scopes
- [Quickstart](https://acme.com/docs/quickstart.md): First request in 5 minutes

## Reference

- [Endpoints](https://acme.com/docs/api.md): Every endpoint and parameter
- [Errors](https://acme.com/docs/errors.md): Error codes and handling

## Optional

- [Changelog](https://acme.com/changelog.md): Release history
```

## 3. The llms.txt + llms-full.txt pairing

Big documentation sets often publish both: llms.txt as the index, and [llms-full.txt](/guide/llms-full-txt) with the full content inlined so an agent can ingest everything in one fetch.

## Copy the structure, not the content

Whichever pattern you pick, keep descriptions specific, use absolute HTTPS links, and make sure each one resolves. Then [run it through the validator](/) to confirm it scores 100.