> For the complete documentation index, see [llms.txt](https://infronai.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://infronai.gitbook.io/docs/billing-apis/usage-and-cost/overview.md). # Overview Infron provides built‑in Usage Accounting that allows you to monitor AI model usage and cost breakdowns directly from your API responses. This feature includes detailed insights into token consumption, associated costs, and caching behavior. **Benefits** * Efficiency: Retrieve usage information without additional API calls * Accuracy: Token counts are computed using each model’s native tokenizer * Transparency: Track real-time cost and cached token utilization * Detailed Breakdown: Separate reporting for prompt, completion, reasoning, and cached tokens **Usage Information** When enabled, the API returns comprehensive usage metrics, including: * Prompt and completion token counts calculated with the model’s native tokenizer * Total cost in credits * Reasoning token counts (when supported by the model) * Cached token counts (when applicable) This usage information appears in the final SSE message for streaming responses, or in the full response body for non‑streaming requests. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://infronai.gitbook.io/docs/billing-apis/usage-and-cost/overview.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.