Index / ARD publishers / getlago.com

getlago.com

getlago.com publishes an Agentic Resource Discovery manifest at /.well-known/ai-catalog.json, declaring what an AI agent can call on this domain. Everything below is read from that file. First seen by our crawler on 31 August 2026.

3declared resources
3with a callable endpoint
not yetchecked for reachability
0verified tools

Declared resource	Type
Lago Agent Discovery MCPnot yet checkedv1.0.0 Discover Lago capabilities and canonical public developer resources through a read-only MCP server. endpoint: `https://getlago.com/.well-known/mcp/server-card.json` identifier: `urn:air:getlago.com:server:documentation` published to be found for: how do I send usage events to Lago · how does Lago authenticate API requests · show me Lago's subscription and invoicing API documentation billing documentation api mcp FindLagoDeveloperResource ReadLagoCapabilities trust identity: `https://getlago.com`	application/mcp-server-card+json
Lago Billing APInot yet checked Create customers and subscriptions, ingest usage, calculate charges, and manage invoices through Lago's REST API. endpoint: `https://getlago.com/openapi.json` identifier: `urn:air:getlago.com:api:billing` published to be found for: send a customer usage event to Lago · create a usage-based subscription · retrieve invoices for a Lago customer billing metering subscriptions invoices openapi UsageMetering CustomerBilling SubscriptionManagement	application/vnd.oai.openapi+json;version=3.1
Integrate with Lago Billingnot yet checked Guidance for agents implementing secure, reliable Lago billing integrations. endpoint: `https://getlago.com/.well-known/agent-skills/lago-billing/SKILL.md` identifier: `urn:air:getlago.com:skill:billing-integration` published to be found for: help me integrate Lago into my application · design usage metering with Lago billing integration skill LagoIntegrationPlanning LagoApiImplementation	application/ai-skill+md

Source: https://getlago.com/.well-known/ai-catalog.json, this publisher's own file. Identifiers are reproduced exactly as published. Note: this is the pre-v0.91 path. The specification renamed the manifest to /.well-known/ard.json, and most of the ecosystem still serves the older name. None of these endpoints has been probed for reachability yet, so nothing here says whether they answer. "Answers" and "no response" describe only whether an endpoint replied when last probed: services go down and come back, and an entry is demoted rather than removed. None of this is a trust, quality or safety rating.

Search this publisher's resources alongside every other indexed resource at https://neuronto.com/search, or connect an agent to https://neuronto.com/mcp. If this is your domain, the free console shows what a registry sees when it reads your manifest.