Use the same documentation as a human reader, with plain Markdown and explicit contracts for reliable retrieval.
On a deployed site
/llms.txtlists the public guides, descriptions, and Markdown URLs./llms-full.txtcontains all published guides in one text response.- Each guide has a View Markdown link and a Copy page action.
/openapi.jsondescribes customer REST operations, schemas, scopes, and errors./docs/search-index.jsoncontains the public documentation search index./sitemap.xmllists canonical public HTML pages.
These resources require no login and contain documentation only. They do not grant access to projects, customer records, or operator tools. Use scoped API credentials for application operations.
In a checkout
Start with the documentation index, then select a feature. The codebase map identifies source ownership. OpenAPI, CLI commands, and admin MCP tools are machine-readable references.
Read AGENTS.md before editing. It points to the repository's required coding and documentation rules; public API guides are not a replacement for contributor instructions.
Choose the smallest useful context
Read a feature overview first, then its linked API or implementation details. Use stable page and heading links when citing behavior. For deployed limits and model choices, query the authorized API: documentation defaults do not override the account's effective policy or model catalog.
llms.txt is a discovery convention. It does not guarantee adoption by every agent or inclusion in search results.