> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getlago.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Lago Developer Resources: API, OpenAPI, SDKs, Webhooks, and MCP

> The canonical entry point for Lago API authentication, OpenAPI schemas, SDKs, webhooks, MCP, examples, status, and support.

Use this page as the canonical developer portal for Lago. It links the contracts, guides, packages, tools, and operational resources needed to build and maintain a production billing integration.

## API and authentication

Lago Cloud uses `https://api.getlago.com/api/v1` as its REST API base URL. Authenticate server-to-server requests with the API key from your Lago organization settings. Send the key only over HTTPS, store it in a secret manager, and never expose it in browser code, logs, or source control.

* [API overview and authentication](/api-reference/intro)
* [API standards](/api-reference/api-standards)
* [API versioning and deprecation policy](/api-reference/versioning)
* [Pagination](/api-reference/pagination)
* [Rate limits](/api-reference/rate-limits)
* [Structured API errors](/api-reference/errors)
* [Authentication guide for agents and developers](/auth)
* [Interactive Swagger reference](https://swagger.getlago.com/)

## OpenAPI schemas

Use the same-origin [OpenAPI discovery schema](/openapi.json) for automated discovery, function generation, and error-shape inspection. It describes representative high-value operations and points to the production server. Use the [complete Lago OpenAPI specification](https://swagger.getlago.com/openapi.yaml) for code generation and exhaustive endpoint coverage. The source is maintained in the [Lago OpenAPI repository](https://github.com/getlago/lago-openapi).

Agents can also discover these surfaces through the [Agentic Resource Discovery catalog](/.well-known/ai-catalog.json) and the [RFC 9727 API catalog](/.well-known/api-catalog). The root-level JSON files provide version-controlled aliases of those well-known documents.

## SDKs and clients

Lago maintains open-source clients for common server-side languages. Check each repository's README and release history before selecting a version.

* [JavaScript client on npm](https://www.npmjs.com/package/lago-javascript-client) and [source](https://github.com/getlago/lago-javascript-client)
* [Python client on PyPI](https://pypi.org/project/lago-python-client/) and [source](https://github.com/getlago/lago-python-client)
* [Ruby client on RubyGems](https://rubygems.org/gems/lago-ruby-client) and [source](https://github.com/getlago/lago-ruby-client)
* [Go module](https://pkg.go.dev/github.com/getlago/lago-go-client) and [source](https://github.com/getlago/lago-go-client)
* [Java client](https://github.com/getlago/lago-java-client)
* [PHP client](https://github.com/getlago/lago-php-client)
* [C# client](https://github.com/getlago/lago-csharp-client)
* [Rust client](https://github.com/getlago/lago-rust-client)
* [Lago Agent SDK on PyPI](https://pypi.org/project/lago-agent-sdk/)

## Webhooks and asynchronous processing

Use [webhooks](/guide/webhooks) to react to customer, subscription, invoice, credit note, payment, and wallet changes. Consumers should verify authenticity, acknowledge delivery quickly, deduplicate retries, and move expensive work to a queue. Treat the API as the source of truth when a webhook payload and locally cached state disagree.

## AI agents and MCP

Connect supported AI clients to the documentation [MCP server](/guide/ai-agents/mcp-server) at `/mcp`. It exposes search and retrieval capabilities through Streamable HTTP. For application-level billing agents, begin with the [agent SDK overview](/guide/ai-agents/agent-sdk/overview), then select the guide for your model provider. Keep financial mutations behind human approval and enforce the same authorization rules used by non-agent integrations.

## Examples and self-hosting

* [Billing examples](https://github.com/getlago/lago-billing-examples)
* [Main Lago repository](https://github.com/getlago/lago)
* [Self-hosted overview](/guide/lago-self-hosted/overview)
* [Docker deployment](/guide/lago-self-hosted/docker)
* [Kubernetes Helm charts](https://github.com/getlago/lago-helm-charts)
* [Integration testing](/guide/integration-testing)

## Operations and support

Check [Lago status](https://status.getlago.com/) for current service health. Use the [contact page](/contact) to find community, support, sales, and security routes. For automated discovery, start with [llms.txt](/llms.txt); for a complete text export, use [llms-full.txt](https://doc.getlago.com/llms-full.txt).

For packaging and commercial availability, use the [pricing summary](/pricing) and verify decisions against the [current Lago pricing page](https://getlago.com/pricing).