Agent guidance for Lago documentation
Use this repository to improve Lago’s public developer documentation. Preserve the established Lago visual design and navigation unless a task explicitly requests a redesign.Sources of truth
- Use
docs.jsonfor site navigation and Mintlify configuration. - Use
https://swagger.getlago.com/openapi.yamlandhttps://github.com/getlago/lago-openapifor the exhaustive production API contract. - Use
openapi.jsononly as the concise same-origin discovery profile. - Verify product, pricing, authentication, security, and operational claims against current Lago documentation or primary Lago sources.
Content rules
- Prefer task-oriented guidance and exact links over generic marketing copy.
- Do not invent endpoints, fields, authentication flows, permissions, prices, limits, or product availability.
- Keep API keys and customer data out of examples.
- Explain approval and validation boundaries for financial or destructive actions.
- Keep agent-discovery pages machine-readable without adding them to visible navigation unless requested.
Validation
- Run
pnpm exec mint validateafter documentation or configuration changes. - Check changed JSON files with a JSON parser.
- Verify important routes and Markdown fallbacks in the deployed Mintlify preview.
- Confirm the visible homepage still matches the established design after changing
welcome.mdx.