> For the complete documentation index, see [llms.txt](https://docs.bito.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bito.ai/help/billing-and-plans/advanced-ai-requests-usage.md).
# Advanced AI requests usage
View and manage your workspace usage to avoid unexpected expenses.
If you are on a paid plan, such as the **Team Plan**, and are the owner or admin of a workspace, you can easily view the **Advanced AI Model requests** included for the current month and the number of requests used by your workspace members and AI Agents.
{% hint style="info" %}
If you are on the **Free Plan**, this plan does not include Advanced AI Model requests, so this feature is not relevant to your plan.
{% endhint %}
To view your usage, simply visit the [**Settings > Requests Usage**](https://alpha.bito.ai/home/bito-premium/ai-request-usage) dashboard.
## What is an Advanced AI Model Request?
Bito uses best-in-class AI models to offer its services. These are known as **Advanced AI models** and are only accessible through our [paid plans](https://bito.ai/pricing/).
When your **Advanced AI Model Request** quota is used up, [AI Chat](/ai-code-reviews-in-ide/ai-chat-in-bito.md) requests will be blocked for the rest of the day and will become available again the next day.
---
# 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.bito.ai/help/billing-and-plans/advanced-ai-requests-usage.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.
