> For the complete documentation index, see [llms.txt](https://docs.airops.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.airops.com/developers.md). # Developers - [Insights API](https://docs.airops.com/developers/api.md): The AirOps Insights API: an AEO and AI citation tracking API with programmatic access to mention rate, share of voice, citations, and page performance, for custom dashboards, ETL, and reporting. - [MCP Overview](https://docs.airops.com/developers/mcp-server.md): Connect AI assistants to your AirOps workspace using MCP - [MCP Connectors](https://docs.airops.com/developers/mcp-connectors.md): Connect external MCP servers to your workspace and give LLM steps access to external tools. - [Claude Connector](https://docs.airops.com/developers/claude-connector.md): Native AirOps integration for Claude with Interactive Apps - [Codex Plugin](https://docs.airops.com/developers/codex-plugin.md): Set up the AirOps MCP plugin in Codex with Interactive Apps - [Getting Started](https://docs.airops.com/developers/getting-started.md): Setup instructions for AI assistants using MCP - [Use Cases](https://docs.airops.com/developers/use-cases.md): AirOps use cases with your AI assistant: manage your Brand Kit, report on AI visibility, find pages losing AI citations and prompt gaps, and create action grids from Claude. - [Tools](https://docs.airops.com/developers/tools.md): The AirOps MCP server tools reference: give Claude, Cursor, and other AI assistants programmatic access to AEO analytics, Brand Kits, Grids, Knowledge Bases, Playbooks, and Workflows in your AirOps wo - [FAQ](https://docs.airops.com/developers/faq.md): Frequently asked questions about AirOps MCP, the Codex Plugin, and Claude Connector --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.airops.com/developers.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.