> For the complete documentation index, see [llms.txt](https://docs.revenium.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.revenium.io/track-and-control-costs.md). # Track & Control Costs - [Instrument Your Code](https://docs.revenium.io/track-and-control-costs/instrument-your-code.md) - [Monitor Infrastructure Costs](https://docs.revenium.io/track-and-control-costs/monitor-infrastructure-costs.md) - [How Revenium Prices a Transaction](https://docs.revenium.io/track-and-control-costs/how-revenium-prices-a-transaction.md): Where Revenium's Invoiced (Billed) and Metered figures come from, how the gap between them is shown, and how to make Metered cost reflect a negotiated rate. - [Data Freshness and Provisional Figures](https://docs.revenium.io/track-and-control-costs/data-freshness-and-provisional-figures.md): Where Revenium shows when each data source last delivered data, what you see when a feed stops, and which Invoiced figures may still change. - [Analyze ROI & Unit Economics](https://docs.revenium.io/track-and-control-costs/analyze-roi-and-unit-economics.md) - [Build Custom Dashboards & Charts](https://docs.revenium.io/track-and-control-costs/build-custom-dashboards-and-charts.md) - [Set Budgets & Alerts](https://docs.revenium.io/track-and-control-costs/set-budgets-and-alerts.md) - [Cost Controls](https://docs.revenium.io/track-and-control-costs/cost-controls.md): Use Cost Controls to define rules that block AI requests when configured usage limits are reached. - [Attribute Spend to Departments](https://docs.revenium.io/track-and-control-costs/attribute-spend-to-departments.md) - [AI Assistants](https://docs.revenium.io/track-and-control-costs/analyze-ai-tooling-spend.md) - [Configure AI Assistant Pricing Mode](https://docs.revenium.io/track-and-control-costs/analyze-ai-tooling-spend/configure-coding-assistant-billing-models.md): Choose whether each team's AI assistant usage counts as real spend (API-rate) or stays an API-equivalent estimate (subscription or seat-based). - [Seats and Licenses](https://docs.revenium.io/track-and-control-costs/analyze-ai-tooling-spend/seats-and-licenses.md): See how many of the AI assistant seats you pay for went unused, what those seats cost each month, and how your Claude Code seats split by plan tier. - [Setup Claude Code](https://docs.revenium.io/track-and-control-costs/analyze-ai-tooling-spend/setup-claude-code.md) - [Claude Code Dashboard](https://docs.revenium.io/track-and-control-costs/analyze-ai-tooling-spend/setup-claude-code/claude-code.md) - [Setup Claude Cowork](https://docs.revenium.io/track-and-control-costs/analyze-ai-tooling-spend/setup-claude-cowork.md) - [Claude Cowork Dashboard](https://docs.revenium.io/track-and-control-costs/analyze-ai-tooling-spend/setup-claude-cowork/claude-cowork.md) - [Setup GitHub Copilot](https://docs.revenium.io/track-and-control-costs/analyze-ai-tooling-spend/setup-copilot.md) - [Setup Cursor](https://docs.revenium.io/track-and-control-costs/analyze-ai-tooling-spend/setup-cursor.md) - [Setup Gemini CLI](https://docs.revenium.io/track-and-control-costs/analyze-ai-tooling-spend/setup-gemini.md) - [Setup Codex CLI](https://docs.revenium.io/track-and-control-costs/analyze-ai-tooling-spend/setup-codex.md) - [AI Assistant Data Reference](https://docs.revenium.io/track-and-control-costs/analyze-ai-tooling-spend/ai-coding-data-reference.md): Complete reference of all data points collected from AI assistant integrations, including Claude Code, Gemini CLI, Cursor IDE, Claude Cowork, Codex CLI, and GitHub Copilot. - [Skill Origin Classification](https://docs.revenium.io/track-and-control-costs/analyze-ai-tooling-spend/ai-coding-data-reference/skill-origin-classification.md): How Revenium classifies the origin of Claude Code skills: the exact mapping from OpenTelemetry attributes to the Origin badges on the Skills page. - [GitHub Integration](https://docs.revenium.io/track-and-control-costs/analyze-ai-tooling-spend/github-integration.md): Connect your GitHub organization to surface PR attribution and productivity metrics alongside AI coding assistant usage in Revenium. - [GitLab Integration](https://docs.revenium.io/track-and-control-costs/analyze-ai-tooling-spend/gitlab-integration.md): Connect your GitLab group to surface merge-request attribution and per-user productivity metrics alongside AI coding assistant usage in Revenium. - [PR Health](https://docs.revenium.io/track-and-control-costs/analyze-ai-tooling-spend/pr-health.md): Find the pull requests that are stuck, abandoned or going stale, and the AI spend behind them. - [Tickets](https://docs.revenium.io/track-and-control-costs/analyze-ai-tooling-spend/tickets.md): See what coding assistant work costs for each engineering ticket, and find spend that carries no ticket. --- # 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.revenium.io/track-and-control-costs.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.