AI and Automation
Have an AI assistant read the documentation on demand, and understand the current status of machine-readable entry points and the documentation MCP.
You can ask an AI assistant to read the documentation on this site first, then assist with configuring tools or writing calling code. Reading ordinary documentation and calling a model API are two different things: reading public documentation does not require an API key.
Available machine-readable entry points
Section titled “Available machine-readable entry points”| Entry point | Purpose |
|---|---|
| llms.txt | Discover documentation by section, and choose the pages you need to read |
| Documentation index | Get page titles, the section each belongs to, and the web and Markdown URLs |
| Full documentation text | Read all pages at once; the content is long, so prefer reading page by page |
| Homepage Markdown | Read the source documentation content without the site navigation |
Every article has a corresponding Markdown address; for example, /en/docs/quickstart-claude-code/ corresponds to /en/docs/quickstart-claude-code.md. You can also use “Copy this page” at the top of a page. The Markdown may retain documentation component markup such as cards.
Handoff tasks for AI
Section titled “Handoff tasks for AI”Copy the task instructions so the assistant first checks the scope of support, then configures and verifies it.
Choose the protocol, address and model configuration according to the tool.
Documentation MCP status
Section titled “Documentation MCP status”This site does not currently provide a connectable documentation MCP server. Please use the documentation addresses above first, or copy the page content to the assistant; do not treat a model API’s Base URL as an MCP address.
The purpose of a documentation MCP is to search and read public materials. Operations such as account queries and key management are a different class of capability and cannot be obtained through the public documentation entry points.