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

# Using AI/LLMs with Pilot Status

> Point any AI tool at llms.txt for the canonical machine-readable reference, or connect agents directly through the hosted MCP server.

There is no copy/paste prompt to maintain. To teach an AI everything about Pilot Status, point it at the canonical machine-readable sources.

## llms.txt

The master reference for AI tools lives at the docs domain:

```text theme={null}
https://pilotstatus.com.br/llms.txt
```

It indexes endpoints, webhook schemas, concepts, and error codes. Paste the URL into your coding agent or LLM tool and it can navigate to the deep documentation pages it needs — each topic is linked from the index, so the model reads only what is relevant instead of a giant prompt.

<Tip>
  When asking a coding assistant to build a Pilot Status integration, give it the `llms.txt` URL first. It will pull the exact request/response shapes (e.g. the three modes of `POST /v1/messages/send`) instead of hallucinating endpoints.
</Tip>

## MCP server

For agents that should **act** (send messages, read conversations, manage numbers) rather than just read docs, use the official Model Context Protocol server — a hosted connector at `https://mcp.pilotstatus.com.br/mcp` exposing the public `/v1` API as tools, with OAuth or `x-api-key` authentication.

See [MCP Server](/integrations/mcp-server) for the tool list and setup, and [AI Agents](/guides/ai-agents) for webhook-driven bot patterns.

## Related

* [AI Agents guide](/guides/ai-agents)
* [MCP Server](/integrations/mcp-server)
* [SDKs & n8n](/integrations/sdks)