Lago serves an AI Catalog
manifest at /.well-known/ard.json on doc.getlago.com, declaring
5 agentic resources
that a discovery service can index without asking anyone’s permission.
did:web:doc.getlago.com —
resolving it returns 404. A did:web: that does not resolve is a string, not an identity, and does not earn the identity affordance here.
/.well-known/ard.json — the path ARD v0.91 says a consumer MUST fetch.
specVersion in the manifest. 1.0 is current for the AI Catalog data model; anything lower is an earlier draft. ARD reads this field as transport-defined and ignores it.content-type-not-ai-catalog-jsondid-web-does-not-resolveRead-only search and retrieval tools for Lago guides, API references, examples, and operational documentation.
Open-source Dockerized MCP server for authenticated access to Lago billing data and operations.
OpenAPI 3.1 discovery profile for authentication, usage events, customers, subscriptions, plans, invoices, and typed errors.
Instructions for agents building usage metering, pricing, subscriptions, invoicing, payments, and billing operations with Lago.
Portable Agent Plugin manifest for Lago billing guidance and the read-only Lago Docs MCP server.
Content-Type: application/json —
yesAccess-Control-Allow-Origin: * —
yeshttps://doc.getlago.com/.well-known/ard.json on 2026-09-13, HTTP
200. The verbatim body is stored alongside its manifest in the
Lago repository
as ai-catalog/lago-ai-catalog.json. Nothing on this page is derived
or generated: an AI Catalog manifest is served from the publisher’s own domain or it does not
exist, which makes it — like an
A2A Agent Card — one of the few agent artifacts that cannot be
produced on a provider’s behalf. Grades are recomputed on every build; the specification is a
v0.9 draft and
these verdicts will move when it does.
Every descriptor here is available over the APIs.io API and to AI agents over MCP. Agent Discovery is not yet its own endpoint on the v1 API. Reach it through catalog search and the tag graph, or the MCP server.