> 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/insights/prompts.md). # Prompts Compare topic and prompt performance and find questions to expand your AI search coverage. Use Prompts to understand how your brand appears in answers across AI platforms. AirOps monitors accepted prompts daily so you can compare visibility, examine citations, and find gaps where competitors appear. The Prompts section includes: * [**Topics**](/insights/prompts/topics.md): Compare categories, inspect topic performance, and review tracked and recommended prompts. * [**Prompts**](/insights/prompts/your-prompts.md): Analyze individual tracked prompts and their answers. * [**Coverage**](/insights/prompts/prompt-coverage.md): Review the distribution across topics and intent stages, then find recommendations to expand it. * [**Query Fanouts**](/insights/prompts/query-fanouts.md): Inspect the search queries AI platforms use while researching tracked prompts. [Recommended prompts](/insights/prompts/recommended-prompts.md) now appear in Coverage and the topic detail panel. Accept a recommendation to begin tracking it. To add prompts or manage topics, tags, regions, personas, and platforms, open **Insights → Settings → Configuration**. --- # 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/insights/prompts.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.