See every provider's AI spend in one place
You don't run on one provider anymore, and your costs are scattered across a dozen consoles that each count differently and only ever show you the past. Pull all of it into one running month-to-date total and a forecast, and you see the month forming instead of waiting for the invoice.
A developer ships a feature on a Friday. Over the weekend a retry loop hammers a large prompt far more often than anyone meant it to, and a traffic spike starts routing calls through a pricier model. The code works fine. The invoice arrives at the end of the month and it's several times what they expected, and by then the money is already spent. No single screen had shown the line bending upward while it was still bending.
That's the trap with AI and compute spend. The damage is quiet and it adds up daily, and the one document that finally shows you the total is the invoice, which lands after you can do anything about it.
Why don’t provider dashboards warn you about a rising bill?
Every provider’s console is a rear-view mirror. It tells you, accurately, what you have already spent. None of them tell you where the current month is heading, so a runaway cost first becomes a number you can read after it has finished running.
Most projects don’t run on a single provider anymore. A real one leans on Claude for one job and OpenAI for another, generates voices on ElevenLabs, rents a GPU on RunPod, and serves itself through Cloudflare. Each has its own login and its own unit of measure. One counts tokens, another characters, a third bills GPU-seconds, a fourth requests and bandwidth. There’s no single number anywhere for “what is AI costing me this month,” so a sharp spike stays hidden, split across half a dozen dashboards nobody adds up.
What does scattered AI spend actually cost you?
Spreading spend across providers without rolling it up costs you four concrete things, even when no single bill looks alarming on its own.
- No total. Answering the most basic question, what am I spending on AI this month, means logging into every console and summing it by hand.
- No forecast. Every dashboard is rear-view. None project ahead, so you learn you overspent once the invoice lands.
- No comparison. Without building a spreadsheet you can’t see which provider is your biggest line item, or that one tripled this month while another held flat.
- Apples to oranges. Tokens, characters, GPU-seconds, and gigabytes aren’t the same unit, so eyeballing the pieces side by side is guesswork.
What is multi-provider AI cost tracking?
Multi-provider AI cost tracking is one view that reads every provider’s usage, converts each provider’s own units into money, and adds them into a single running total, kept current the moment you click Refresh and carrying a forecast of what next month will cost. It addresses every one of the four costs above.
How a provider meters its usage decides what its raw numbers even mean, so here’s what each one counts before any of it becomes money:
| Provider | Billing unit | What it counts |
|---|---|---|
| OpenAI | tokens | input + output tokens per model |
| Claude | tokens | input + output tokens per model |
| tokens | input + output tokens per model | |
| DeepSeek | prepaid balance | balance drawn down between refreshes (approx.) |
| OpenRouter | tokens (credits) | per-model token price, paid from credit |
| ElevenLabs | characters | characters of synthesized speech |
| RunPod | GPU-hours | seconds a GPU pod stays running |
| Cloudflare | requests / bandwidth | requests served and data transferred |
| GitHub | minutes / credits | Actions minutes, Codespaces, Copilot |
Tokens, characters, GPU-seconds, requests, minutes: none of them are money until you apply a price. The benefit here isn’t a notification; it’s a number worth checking. One click re-pulls every provider and moves the forecast with it, so a spike shows up the next time you refresh, days before the invoice while the month is still open.
How does CostCompass track costs across every provider?
CostCompass is a spend-intelligence dashboard built around exactly this. It reads each provider’s own usage and billing data instead of routing your traffic or living in your code, which is one of three ways cost tools collect billing. You connect each provider once, and from then on:
- Everything becomes a cost. Each provider’s usage is read from its own API and turned into money — priced at published per-unit rates, or taken from the provider’s own reported figure where it gives one — so all those different meters land as one comparable number.
- One running month-to-date total across every provider you’ve connected. It’s the single figure none of the individual consoles can give you.
- A forecast that projects next month from your burn rate so far. The mechanics of that projection are covered in forecasting your AI spend.
- A per-provider breakdown — and a per-model one wherever a provider exposes it, so when the total moves you can see which provider, and often which model, moved it.
- Your keys are encrypted with your vault password before they reach us, so what we store is ciphertext only you hold the key to. The security model documents how.
Which AI providers can you track in one place?
CostCompass connects to a growing list of providers; the full set lives on the providers page, each with a short setup walkthrough. Billing works differently on every one. Separate keys, separate usage APIs, units and quirks that never quite line up. The guides below go deeper on how each provider bills and what it takes to keep a running total for it. Pick the ones you run on:
By provider
- How to Track Anthropic (Claude) API Costs How Anthropic bills Claude by model and token, and how to track usage, forecast next month, and keep your key encrypted in your browser.
- How to Track Cloudflare Workers, Workers AI & R2 Costs Cloudflare bills Workers in requests, Workers AI in Neurons, and R2 in gigabyte-months and operations. Price it into one running cost and a forecast.
- How to Track DeepSeek API Costs DeepSeek API cost tracking — how its prepaid, balance-only billing works, and how CostCompass turns the draining balance into a running total and forecast.
- How to Track ElevenLabs API Costs ElevenLabs bills voice work in characters and credits, not money. Here's how its billing works — and how to track the real cost with a live forecast.
- How to Track GitHub Actions, Codespaces & Copilot Costs Track GitHub Actions, Codespaces, and Copilot costs — how the minute, core-hour, and AI-credit metering works, turned into a running cost and forecast.
- How to Track Google Cloud & Gemini Costs How Google bills your whole Cloud account — Gemini, Vertex AI, Compute, Storage — and how to track usage, exact billed cost, and a forecast in one view.
- How to Track OpenAI API Costs Track your OpenAI API costs — read org-wide spend with an Admin key, break it down by model, and forecast next month, key encrypted in your browser.
- How to Track OpenRouter API Costs How OpenRouter bills one prepaid balance across many model vendors, and how CostCompass breaks that spend out by model with a running total and forecast.
- How to Track PostHog Costs PostHog bills analytics by the event and replay by the recording, past each free tier. Here's how pricing works and how to track real cost with a forecast.
- How to Track RunPod GPU, Serverless & Volume Costs How RunPod bills GPU pods and serverless by the second, volumes by the gigabyte, against a prepaid balance — and how to track the cost with a live forecast.
By topic
- AI Cost Tracking Tools: The 3 Ways They Get Your Numbers AI cost tracking tools get your spend three ways: routing traffic, instrumenting code, or reading the bill. How they compare, and where CostCompass fits.
- CostCompass vs. a Spreadsheet for AI Cost Tracking CostCompass vs. a spreadsheet for AI cost tracking — where by-hand roll-up goes stale, and what a one-click dashboard with forecasts does instead.
- How to Forecast Your AI Spending Before the Bill Lands Forecast your AI spending before the bill lands — CostCompass turns seven days of usage into a next-month estimate across every provider.
- How to Track AI Costs Across Multiple Providers Four ways to track what you're spending on AI across every provider — and how to keep one running total and a forecast without changing any code.
- LLM Cost Management: How to Control What Your Models Cost LLM cost management is a loop: see which model drives cost, pull the right lever, then check the bill moved. Here are the levers and how to read them.
- The Hidden Economics of AI Coding AI coding costs come from more than generated code. See how context, prompt caching, model routing, gateways, and observability shape the real bill.
- What an AI API Cost Dashboard Is — and How to Get One An AI API cost dashboard prices every provider's usage into one money figure and forecasts the month. What one shows, and the two ways it gets its numbers.
- Why Cutting Generated Code Barely Lowers Your AI Bill AI coding agents spend most of their tokens reading and re-reading your repo, not writing code. See where the tokens really go — and what lowers the bill.
Frequently asked questions
- Which providers can CostCompass track?
- A growing list of the AI and compute services developers build on — model providers like Anthropic's Claude, OpenAI, and Google, plus voice, GPU, hosting, and analytics services. The full current list, each with a short connect walkthrough, lives on the providers page. Connect the ones you use and they fold into the same total.
- How can one number cover providers that bill so differently?
- CostCompass reads each provider's own usage data and turns it into a cost — pricing metered usage at the provider's published rates, or using the provider's own reported figure where it gives one. Tokens for Claude and OpenAI, characters for ElevenLabs, GPU time for RunPod, requests and bandwidth for Cloudflare. Each provider meters differently, but everything arrives in your total already expressed in money, so the amounts line up and add together.
- Does it forecast, or just show what I've spent?
- Both. You get a running month-to-date total of what you've spent so far, and a forecast that projects what next month will cost at your burn rate to date. Provider dashboards give you the history; the forecast is the part they leave out.
- Will I know if my spend suddenly jumps?
- Yes, when you pull your running total. CostCompass doesn't send alerts, so the jump won't reach out to you. Each time you click Refresh it re-reads every connected provider, and a sudden jump shows up in your month-to-date figure and pushes the forecast up. You catch a spike forming while there are still days left in the month to act on it.
- Where do my provider API keys live?
- Stored on our servers as ciphertext, and only you hold the password that decrypts it. Your keys are encrypted in your browser with your vault password before they're saved, so what we hold is ciphertext. The password stays in your browser. When CostCompass fetches your usage, the key is decrypted in your browser and forwarded to the provider through a broker built not to log it, keeping the plaintext out of our database and logs. The security page documents exactly how.
- Why might CostCompass's total differ from a provider's invoice?
- Where CostCompass prices usage itself, it uses each provider's published rates at the moment usage is recorded, so that part of the figure is reproducible and doesn't shift when a provider later changes prices. Discounts that don't appear in the raw usage (batch-API rates, automatic prompt caching, promotional credits, committed-use deals) can make the actual invoice a little lower, and a few providers report their own cost or are read from a draining balance, which carries its own small approximation. Treat the CostCompass total as a close, slightly conservative running estimate.
- Why use CostCompass instead of checking each provider's own dashboard?
- Each provider's dashboard shows only its own slice, only what you've already spent, in its own units. So answering "what is AI costing me this month" means logging into a dozen consoles and adding it up by hand, after the fact. CostCompass turns that into one running, forward-looking number — a month-to-date total, a forecast, and a per-provider breakdown, down to the model wherever a provider exposes it, across everything you connect. You watch the month form instead of reading about it on the invoice.
About the author
Joubert Berger builds CostCompass, a spend-intelligence dashboard that pulls usage from AI and compute providers into one month-to-date total, a forecast, and a per-provider breakdown. This guide reflects how CostCompass reads each provider's own usage API — see the security model for how your keys are handled.
See your whole AI bill in one place
Connect each provider once and pull a single month-to-date total and forecast across all of them with one click, rolled up for you.