> 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 Monitor tracked prompts and find new questions to add to your AI search visibility program. Use Prompts to understand how your brand appears in answers to specific questions across AI platforms. AirOps monitors accepted prompts daily, which helps you compare visibility, examine citations, and find gaps where competitors appear. The Prompts section includes: * [**Your prompts**](/insights/prompts/your-prompts.md): Review the prompts you track, organize them, and analyze their performance. * [**Recommended prompts**](/insights/prompts/recommended-prompts.md): Review weekly suggestions or explore a topic to find prompts on demand. * [**Prompt Coverage**](/insights/prompts/prompt-coverage.md): Review the distribution of tracked prompts across topics and intent stages. * [**Query Fanouts**](/insights/prompts/query-fanouts.md): Inspect the search queries AI platforms use while researching tracked prompts. Recommendations use your Brand Kit context, region, language, and market data. Accept a recommendation to add it to **Your prompts** and begin tracking it. --- # 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.