AI assistants

These docs are also meant to be read by an AI assistant. There are three ways in, from simplest to richest:

1. llms.txt

An index in the llmstxt.org format: what the API is, the rules an assistant must know before writing code, and a link to every page in Markdown.

File	What for
https://docs.tucapi.app/llms.txt	The index. Paste it into the chat or hand it to your tool.
https://docs.tucapi.app/llms-full.txt	The whole documentation in a single file.
https://api.tucapi.app/v2/llms.txt	The same index, served by the API.

The machine-readable files are in Spanish; models handle them fine in either language.

2. Every page in Markdown

Every guide also exists as plain Markdown at https://api.tucapi.app/v2/docs/<page>.md, for example empezar.md. It is the format models read best: no menus, no styles, just the content.

3. The MCP server

So the assistant can look at your account (catalog, balances, operations and events) with your own key, read-only. See MCP server to connect it over HTTP or stdio.

Claude Code

claude mcp add --transport http tucapi https://api.tucapi.app/mcp \
  --header "Authorization: Bearer $API_KEY"

The contract

The OpenAPI 3.1 is the single source of truth: these docs, the SDKs, the MCP server and the API reference all come from it. If an assistant is going to generate a client, it should generate it from there.