An agent holding only https://luniumpay.com has to get here on its own. That cannot depend on it knowing a convention of ours.
GET https://luniumpay.com
↳ Link: </.well-known/api-catalog>; rel="api-catalog" (RFC 8288)
GET https://luniumpay.com/.well-known/api-catalog (RFC 9727)
Content-Type: application/linkset+json
↳ service-desc → OpenAPI
↳ service-doc → documentation, llms.txt
↳ service-meta → /mesh, agent-card, mcp.json, apis.json
GET https://api.luniumpay.com/mesh
↳ capabilities, intents, execution, limits, how to startllms.txt leads to the same place, but it is a convention, not a standard. That is why the chain above exists: an agent that only knows RFCs gets here all the same.Each capability declares what it accepts and what it returns. An agent whose intent is “I have USDT and want BRL over PIX” filters on input_assets, output_currencies and payment_rails — without ever learning the route is called /cash-outs.
Intents indexed today (—):
…
| Address | What for |
|---|---|
/.well-known/api-catalog | RFC 9727 — the domain’s API catalog |
/.well-known/agent-card.json | A2A — capabilities and skills |
/.well-known/mcp.json | MCP server descriptor |
/.well-known/apis.json | APIs.json, for directories |
/openapi.json | Executable contract |
/llms.txt | Contract in prose, for models |