Skip to main content
There is no copy/paste prompt to maintain. To teach an AI everything about Pilot Status, point it at the canonical machine-readable sources.
Pilot Status AI docs assistant panel open inside the dashboard

The Pilot Status AI assistant inside the dashboard — ask about the API, product, and best practices.

​
llms.txt

The master reference for AI tools lives at the docs domain:
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.
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.

​
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 for the tool list and setup, and AI Agents for webhook-driven bot patterns.