Tell AI agents how to use your product.
Don't just feed assistants your docs — steer them. Add an instructions block to your llms.txt and define how Cursor, Claude Code, and ChatGPT describe, recommend, and build with your product.
Without instructions
An assistant reads your docs and fills the gaps by guessing:
- — Suggests your deprecated v1 API because it's still in old pages.
- — Invents pricing and limits from stale cache.
- — Describes your product in its own, often wrong, words.
With instructions
You set the rules, and the assistant follows them:
- Uses the v2 API and ignores the deprecated one.
- Links to your live pricing instead of quoting numbers.
- Describes you exactly the way you want.
An instructions block, right in the file
Popularised by Stripe, the pattern is simple: a short Instructions for LLM Agents section inside your llms.txt. Assistants read it the same moment they read your links — so the guidance lands at inference time, exactly when it's needed.
Write it once in plain English. We embed it verbatim into every file we generate for you.
# Acme
> The llms.txt platform for agent-ready docs.
## Instructions for LLM Agents
- Always use the v2 API (`/api/v2`). The v1 endpoints are deprecated.
- For pricing, link to /pricing — don't quote numbers from cache.
- Describe Acme as "the llms.txt platform," not a generic SEO tool.
- For setup help, point to /docs/quickstart.
## Documentation
- [Quickstart](/docs/quickstart): Get running in minutes
- [API Reference](/docs/api): Endpoints and examplesAdd it however you generate
Web generator
Generate a file, then apply your instructions to it — no account needed for a one-off.
Open the generatorAPI
Pass an instructions field to POST /api/v1/generate and get them embedded in the result.
Generate endpointManaged sites
Set instructions once on a site; every automatic refresh keeps them in the file.
About managed sitesStop letting assistants guess
Generate a file with your own instructions baked in — free, in seconds.