# Monitor Infrastructure Costs Before you can control AI spend, you need to know where it's actually coming from. Revenium connects directly to your AI provider accounts and immediately surfaces the complete picture — what you're spending, where it's going, and how much of it you actually have visibility over. Head to **Integrations > Providers** to connect your accounts, then navigate to **Overview** to see your spend broken down across three views. > 💡 **Getting the most from this section:** Provider-level data gives you top-down visibility across your entire AI footprint. For deeper attribution — by customer, product, or feature — make sure you are also passing metadata when you [Instrument Your Code](/track-and-control-costs/instrument-your-code.md). The two work together. *** ### 1. Providers: How Much of Your Spend Can You Actually See? The most important number here isn't your total cost — it's your **Coverage Ratio**. This tells you what percentage of your provider bill is actively metered and under Revenium's financial control. Anything below 100% is unaccounted spend: workloads running outside your instrumented infrastructure, forgotten scripts, or environments that haven't been connected yet. Until those gaps are closed, you're making budget decisions on incomplete information. Alongside coverage, you can see: * **Cost by workspace:** Break spend down by internal team or environment — production vs. staging, one business unit vs. another — so cost ownership is clear rather than pooled into a single bill nobody owns. * **Period-over-period comparison:** See immediately whether total spend is trending up or down, without waiting for a monthly invoice to tell you something went wrong two weeks ago. * **Provider credits and net spend:** For providers such as AWS Bedrock and Google Vertex AI, Revenium can track provider-issued credits and apply them to billing analytics. This helps distinguish gross AI usage from the net spend you actually pay after credits are applied.
*** ### 2. Models: What Are You Actually Paying Per Token? Provider pricing pages show list prices. Revenium shows you what you're actually paying, calculated against your real usage patterns. **Model Efficiency** gives you the true cost per million tokens for every active model in your organization, normalised across providers so you can make direct comparisons. A model that looks cheap in a benchmark can look very different once your specific workloads are factored in. * **Model Efficiency table:** Rank every active model by cost percentage, request volume, average tokens per USD, and trend. Use it to identify models whose cost share is growing faster than their request share — a reliable signal that usage patterns have shifted in a way worth investigating. * **Period-over-period comparison:** Validate whether a recent model swap has delivered the savings it promised, or whether costs have quietly crept back up. *** ### 3. API Keys: Find the Spend You Didn't Know You Had API keys are where financial accountability breaks down in most organizations. The number of active keys is almost always higher than anyone expects, and a meaningful portion of them are typically operating entirely outside your metering coverage. * **API Key Analytics:** See every active key across your connected providers with a full breakdown of cost, token volume, request count, and trend. Keys that are spending without appearing in your metered traffic are either candidates for instrumentation or candidates for deactivation — either way, they shouldn't stay invisible. * **Cost concentration:** Quickly identify whether spend is distributed across many keys or driven by a handful. Knowing where it's concentrated tells you where to focus your instrumentation effort first. > **Through MCP, conversationally.** The questions this page is built around — where is my spend, what's driving it, which keys are responsible — are exactly the kind of questions an AI assistant connected to Revenium via the MCP Server can answer in chat. Ask "what's my total AI spend this month and which providers does it break down to?", "which models have the highest cost share right now?", or "are any API keys driving an unexpected portion of the bill?" The agent runs the queries, breaks the data down across providers, models, customers, agents, or API keys, and tells you what it finds. Useful for the kind of monthly or weekly check-in that's easy to skip when there's no room in the dashboard rotation. --- # Agent Instructions: 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: ``` GET https://docs.revenium.io/track-and-control-costs/monitor-infrastructure-costs.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.