Discovery

Where an agent finds each Restoman document: llms.txt, every page's markdown, the catalogs, the cards and auth.md.

Each Restoman site says what it offers agents in documents found at well-known places.

The sites

Site	What it is
`https://restoman.com.ar`	What Restoman is, its prices and features
`https://docs.restoman.com.ar`	This guide and these pages
`https://menu.restoman.com.ar`	The published restaurants' menus
`https://api.restoman.com.ar`	OAuth and the Restoman MCP

Markdown: every public page has its markdown version at the same address plus .md (the home page at /index.html.md), and the same address asked for with Accept: text/markdown answers in markdown. A page that doesn't exist, asked for that way, answers a markdown 404.
llms.txt at each site's root says what's there and when to use each one. The Guide also has llms-full.txt, with every guide and every one of these pages.
robots.txt lets everyone in, with Content Signals (search=yes, ai-input=yes, ai-train=yes), and names the sitemap.

Document	Where
API catalog (RFC 9727), `api-catalog`	Every site
ARD manifest, `ai-catalog.json` and `ard.json`	Every site
MCP server card, `mcp/server-card.json`	The Guide, the menus and the API
A2A agent card, `agent-card.json`	The Guide and the menus
Agent skills, `agent-skills/index.json`	The Guide and the menus
OAuth, `oauth-authorization-server` and more	The API

Restoman's site redirects the MCP card, the agent card and the skills to the Guide, and auth.md to the API: nothing is copied.

https://api.restoman.com.ar/ is an index of what's there.
https://api.restoman.com.ar/auth.md tells an agent how to get access.
https://api.restoman.com.ar/openapi.json describes, in OpenAPI 3.1, what third parties call: OAuth, the MCP and these documents. The routes Restoman's own apps use aren't a public API and aren't in it.

DNS-AID SVCB records under each site's _agents (_index, _mcp, _a2a) point at whatever serves each one.