llms.txt

Give your agent all of this documentation in one file, or just the page it needs. There are two files for that, and each page also exists as Markdown.

File	What it is	When to give it to an agent
`/llms.txt`	The index: each page with one line saying what it contains	Always. It is small and enough for the agent to know what to ask for
`/llms-full.txt`	The whole site in a single Markdown	When the agent can’t browse, or to put it all in context
`/<page>.md`	One page, in plain Markdown	When you want it to read a single thing

https://docs.crossup.ai/llms.txt
https://docs.crossup.ai/llms-full.txt
https://docs.crossup.ai/en/empezar/primera-recomendacion.md

On any page, the contextual menu copies the page as Markdown or opens it in Claude.

The recommended order

If the agent reads only some pages, make it these, in this order:

The six moments: what each request needs.
Your first recommendation: the full path, with the snippets.
Report signals: track.* and when to send each signal.
Errors: the eleven types, with their exact shape.
The OpenAPI contract, for the shape of each request: it is in the repository, in packages/contracts.

What an agent has to know, in five lines

In case context is short:

- The store doesn't travel: it comes from the key. There is no store_id in any request.
- results: [] is valid; reason_codes says why. Display nothing.
- An absent field is unknown, not zero. sellable is a string; title is per language.
- Signals are tied to a decision_id this connection received; stable signal_id = retrying is safe.
- 60 requests per minute per key; on 429, wait Retry-After, never retry in a loop.

The skill

The path, as a file for your agent.

The MCP

The tools to talk to the API.

​The recommended order

​What an agent has to know, in five lines

The skill

The MCP

The recommended order

What an agent has to know, in five lines