Track AI API spend across your whole team — by project, if you isolate keys
Reviewed and updated 2026-07-26
On a team, AI spend fragments fast — one developer on OpenAI, another testing Anthropic, a shared OpenRouter key for prototypes. Provider dashboards show an account-level total, not who or what caused it, because spend is attributed to the key that made the request, not a person or a project.
"Track AI API costs by project" is really a labeling problem, not a missing feature: no provider bills by project natively. The practical fix is the same one that works for isolating any cost source — create a separate API key per project (or per developer), then connect every key so each shows up as its own line instead of one blended total.
TryTokka's Team plan is built around a simple split: the workspace owner connects and controls the provider keys and Scout alert thresholds, while up to four other members get read-only visibility into the same combined number. Nobody but the owner can add, rotate, or remove a key — the most common way a workspace gets accidentally broken.
Scout checks the combined total daily (or on demand with Sync now) and emails the owner — the person accountable for the budget — when it crosses the configured threshold. Members see the same dashboard without needing their own alert configured.
This does not fabricate a per-person or per-project dashboard TryTokka does not have. If you need that level of detail, the isolated-key approach above is what makes it possible — TryTokka then shows each key's spend on its own, and you label the difference outside the product.
Setup checklist
- Decide whether you need one combined team total, or a breakdown by project/developer.
- For a breakdown: create one API key per project or developer at the provider level.
- Connect every key in TryTokka Connections — the workspace owner controls this step.
- Set one Scout threshold across all keys, or per-key if you need finer alerts.
- Invite up to four team members with read-only access to the combined dashboard.
Quick answers
Can I see AI spend broken down by project?
Not automatically — providers bill by API key, not by project. Create a separate key per project and connect each one in TryTokka; every key then shows its own spend instead of one blended total.
Can I see AI spend per developer?
Same answer as per-project: issue a separate key per developer and track each one. TryTokka shows spend per connected key, not per person, because that is what the provider billing data actually contains.
Who receives the Scout alert on a team?
The workspace owner — the person accountable for the budget and the one who controls the keys and thresholds. Members see the same combined dashboard but do not need their own alert configured.
How many people does the Team plan cover?
Up to five members sharing one workspace: one owner who controls keys and alerts, and up to four members with read-only access to the combined spend number.
Deep-dive guides
- How to Track AI API Costs Across a TeamOne developer watching one dashboard is easy. A team sharing four providers across a dozen keys is where AI spend quietly gets out of hand. Here is how to get one number everyone trusts.
- How to Avoid Surprise AI API BillsA $300 invoice rarely starts as a $300 charge. It starts as a forgotten batch job nobody was watching. Here's how to actually catch it early.
- Best AI API Cost Tracker for Indie Devs in 2026Most "AI cost" tools are built for enterprise FinOps teams with a budget line for tooling. Here's what actually fits a one-person side project.
🦎 From Scout's desk
Get weekly AI cost insights — free
Every Sunday: what AI models are costing developers like you, which switches save money, and one thing you can do this week to spend less.
No spam. Unsubscribe anytime.
Related cost-tracker pages
Comparing tools? See the TryTokka compare hub.