Glassity Blog
AI cost attribution is now available in Glassity
From today, you can see how many tokens your AI uses, what they cost, and which team, key or service spent them. The numbers update every hour. They sit next to your cloud billing data, and you can ask the Glassity Agent questions about both.
Table of contents
It's available now already on the free tier.
Why we built it
Over the last year, many companies gave their teams free access to AI. Some teams built real things with it. Others asked the same model to redo the same task again and again. All of it used tokens, and all of it landed on the same bill.
Most companies we talk to have two groups looking at this. The FinOps team knows how to split cloud costs between teams, but their tools can't read tokens. The engineers understand tokens very well, but what they know never reaches the reports finance uses.
So two simple questions go unanswered. Which team spent this AI budget? And how much did a service cost last month, including the AI it used?
What's in the release
You can connect seven sources, all read-only. Five are gateways: LiteLLM, Helicone, OpenRouter, Cloudflare AI Gateway and Bifrost. Two are cloud AI services: Amazon Bedrock and Microsoft Foundry. There's also managed by Glassity, our own gateway, which shows what the Glassity Agent itself costs you.
Before you connect anything, you see a preview of your own usage. If it looks wrong, you close the tab. Nothing is imported until you say so.
After that, the AI Usage page updates every hour. You see tokens and cost by source, key, model and provider. Input, output, cache and reasoning tokens are counted separately. This matters because cache and reasoning tokens often grow without anyone noticing, and one total on an invoice won't show you that.
The technical detail is on the product page.
Every night, the same data is written in FOCUS format. FOCUS is the standard format cloud providers use for billing, so your AI costs and your cloud costs end up in one place, in one format.
The Glassity Agent can answer questions about both, in plain language:
Why did our AI costs go up last week?
Which team spent the most on reasoning tokens in August?
What did the checkout service cost last quarter, cloud and AI together?
We only store hourly totals: token counts, request counts and cost. We never store your prompts or the model's responses. The data is kept in AWS eu-west-1, in Ireland, and we are ISO 27001 certified.
Connect your account and see your own numbers.
Free tier, read-only, fifteen minutes.
Why a gateway makes a difference
It's worth knowing this before you connect.
If your engineers send AI requests through a gateway, you get detail for every key. LiteLLM also gives you team id, end user and request tags. Helicone gives you user id, custom properties and prompt id. Bifrost gives you custom metadata. Cloudflare gives you gateway id and request type.
If they call Amazon Bedrock or Microsoft Foundry directly, you still get real token counts and cost, but only by account, region and model. You won't see which key, team or person made the request. A team calling Bedrock from one account shows up as one line.
There's also no shared "team" field across gateways. If you want to see costs by team everywhere, name your keys or tags after your teams, and Glassity will group by them.
What it doesn't do yet
- We can show you what your AI costs and who spent it. We can't yet show you what that spending gave you back.
- You can't export the data to your own storage yet. For now, you reach it through the Glassity Agent and our open-source FOCUS MCP.
- Your gateway needs to be reachable over HTTPS from the internet. Gateways kept inside a private network aren't supported yet.
- Direct calls to OpenAI, Anthropic or Google aren't a source. They only show up if they go through a supported gateway or a cloud AI service.
- The Glassity Agent reads from the FOCUS data lake, which updates once a night. The AI Usage page updates every hour. So the Agent's answers can use data up to 24 hours older than what you see on the AI Usage page.
One thing you can do now
Look at how your API keys are named.
If they're called prod-key-1 and test-2, no tool will tell you which team spent what. If they're named after teams or projects, the answer is already in your data.
It costs nothing, and it's the most useful thing most teams could do about AI costs already now.
How much history you get
If you use Amazon Bedrock, Glassity can read up to six months of past usage from your AWS bill when you connect. So you don't start from zero. You see half a year of history on the first day.
Gateways work differently. When you connect one, Glassity reads the last 48 hours and everything after that. Anything older stays in the gateway and isn't imported. So if your team uses a gateway, it's worth connecting it early.
How to start
Connecting takes about fifteen minutes. You need a read-only key for your gateway, or you can use the AWS account you already connected for Bedrock. You'll see a preview of your usage before anything is imported. There's no card and no call.