Topic starter
24/10/2026 8:51 pm
TL;DR: AI token spend is hard to govern when usage cannot be tied back to teams, people, and models, according to Tetrate. Gateway telemetry is the record that links identity, cost, and model behavior, so budgets and ownership need that join to work.
Editorial analysis by NHI Mgmt Group, based on content published by Tetrate: “Token Optimization: How Engineering Leaders Control AI Token Costs”.
By the numbers:
- Organization scope, last 30 days: 42B tokens, of which 37.6B cache reads, 2.2B cache creation, 2B fresh input, and 228.7M output.
Key questions
Q: Why do AI token totals and actual cost often diverge?
A: Because model pricing is not linear.
Q: What breaks when AI usage is not mapped to the right team?
A: Chargeback and budget ownership break first, followed by any attempt to compare spend across departments.
Q: How should teams govern AI consumption when spend is spread across multiple tools?
A: Start by assigning one control owner for AI consumption governance and require shared evidence from finance, IT, and security.
Practitioner guidance
- Implement gateway-level cost attribution Capture caller identity, model, token counts, and team mapping in the same control plane so spend can be decomposed consistently across providers.
- Reconcile identity-provider team mappings Audit every No team record and every mismatched user-to-team assignment before using usage data for chargeback or budget enforcement.
- Review effective cost per million tokens Compare token volume, cache reuse ratio, and model mix together so you can spot expensive workloads that a simple token cap would miss.
Bottom line: AI token spend is hard to control when usage data cannot be tied back to teams, people, and models.
Glossary terms: AI Gateway, Passthrough Mode, Effective Cost Per Million Tokens, Cache Reuse Ratio
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
This topic was modified 6 days ago by NHI Mgmt Group
25/10/2026 11:13 am
AI spend governance is now an identity problem, not a billing problem. Once token usage spans coding agents, shared gateways, and multiple provider paths, the control question becomes who used what and under which ownership chain. Finance-only views cannot enforce budgets if the identity-provider mapping is wrong, because chargeback and accountability both collapse. Practitioners should treat AI gateway attribution as part of identity governance.
A few things that frame the scale:
- Claude Code-assisted commits leaked secrets at a rate of 3.2%, more than double the human-only baseline of 1.5%, with peaks reaching 31 secrets per 1,000 commits in August 2025, according to the State of Secrets Sprawl 2026.
- According to PwC, 79% of organizations have already adopted AI agents to some degree.
A question worth separating out:
Q: How should organisations decide who needs a Claude Code subscription?
A: Compare each person’s passthrough value against the seat price. If the person is generating far more metered usage than the subscription costs, keep the seat. If the passthrough value is far below the seat price, reclaim it and shift that workload to metered access.
👉 Read our full editorial: AI token spend control depends on decomposing cost by team
This post was modified 6 days ago by NHI Mgmt Group