Every dollar, assigned to a department and a person.
Billing exports tell you which key spent money. They don't tell you which team it belongs to. camaze closes that gap in two ways — one for the spend you already have, one for the spend as it happens.
Get startedMap what you already have
Every API key, workspace, and project camaze has seen spend from shows up as an attribution entity. Assign each one to a department and, optionally, a person — unassigned entities are highlighted and sorted first, so nothing silently stays unattributed. Departments carry their own headcount and monthly budget, which is what turns raw spend into cost per employee.
Example data — not your account.
Attribute at the request, not just the invoice
A billing export can only tell you what a key spent in total. camaze's gateway sits in the request path instead: point your app at camaze with a camaze-issued key rather than your provider's, and every call is forwarded to the real provider, streamed back byte for byte, and logged for cost afterward — attribution at the granularity of an individual call, scoped to whichever key made it.
Each gateway key is scoped to one provider and can be revoked at any time — nothing is buffered before it reaches your app, so a slow client only slows itself down.
Ready to see your own numbers?
Connect Anthropic, OpenAI, or Google in a couple minutes.
Get started