> For the complete documentation index, see [llms.txt](https://docs.hablla.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hablla.com/hablla-docs-en/reports/hablla-reports-and-logs/total-ai-consumption.md).
# Total AI consumption
Complete report of token consumption and overall AI usage
#### Total AI Consumption
The report of **Total AI Consumption** provides a comprehensive view of the use of artificial intelligence models on the platform, allowing measurement of efficiency, costs and performance in different application contexts.
With this dashboard, you can:
* Track the **number of tokens consumed** per AI model (such as GPT-3.5 Turbo, GPT-4.1, GPT-4o, among others).
* Compare usage between different **models and versions**, identifying which ones have greater representation in operations.
* Assess the **percentage distribution of consumption**, ensuring balanced management between performance and cost.
* Monitor usage time in **audio transcriptions**, essential for measuring efforts in voice bots and omnichannel interactions.
* Export reports in **PDF** or **CSV**, facilitating external analyses and integrations with financial controls.
This report is essential for managers and analysts who want to **optimize AI resources**, understanding real demand, projecting future costs and aligning the use of models with business needs and customer experience.
---
# 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.hablla.com/hablla-docs-en/reports/hablla-reports-and-logs/total-ai-consumption.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.
