---
title: "AI and Automation"
description: "Have an AI assistant read the documentation on demand, and understand the current status of machine-readable entry points and the documentation MCP."
headingIds: {"Available machine-readable entry points":"section-1","Handoff tasks for AI":"section-2","Documentation MCP status":"section-3"}
---

<aside className="docs-publication" data-pagefind-ignore>

Documentation maintained by [1ZheAI](https://1zheai.com/en/editorial/#publisher). [Sources and corrections](https://1zheai.com/en/editorial/).

Found an error? [Contact support](mailto:support@1zheai.com) with the page address and a description. Do not send API keys or account credentials.

</aside>
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

| Entry point | Purpose |
| --- | --- |
| [llms.txt](/en/docs/llms.txt) | Discover documentation by section, and choose the pages you need to read |
| [Documentation index](/en/docs/docs-manifest.json) | Get page titles, the section each belongs to, and the web and Markdown URLs |
| [Full documentation text](/en/docs/llms-full.txt) | Read all pages at once; the content is long, so prefer reading page by page |
| [Homepage Markdown](/en/docs/index.md) | 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

<CardGroup cols={2}>
 <Card title="AI integration workflow" href="/en/docs/agent-workflow/">Copy the task instructions so the assistant first checks the scope of support, then configures and verifies it.</Card>
 <Card title="Tool integration directory" href="/en/docs/integrations/">Choose the protocol, address and model configuration according to the tool.</Card>
</CardGroup>

## 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.