Adoption
- % of developers with active token usage this month
- Teams below adoption target — count and token gap
- Week-over-week usage trend by team
- Model diversity — are teams using capable models or defaulting to the cheapest?
The Adoption Mandate
Headcount and budget decisions have been made on the assumption that AI makes teams more productive. If teams aren’t using AI, then they aren’t more productive. See who is using AI and push the ones that aren’t.
The ROI Mandate
Is AI spend producing something? Knowing who is spending tokens isn’t enough. Finding out why tokens are being spent needs data.
Most cost tools show you spend by provider. That's a billing report, not an operational signal. Agent Router attributes every token to the caller — and because agents call other agents, attribution follows the full chain.
Every request carries the authenticated identity of the developer or service account that made it. See exactly which engineers are using AI and how much — down to the individual. Identify power users and people who haven't made a single request this month.
Roll individual usage up to the team level for budget reporting, showback, and chargeback. See which teams are on track for adoption targets and which teams are heading toward a budget overrun. Set per-team token budgets that enforce before the bill arrives.
Attribute spend to the specific application or workflow that consumed it. When three teams use the same underlying agent platform, you can see which application drove which spend — not just which team's API key was used. Useful for product ROI analysis and deprecation decisions.
Slice attribution data by any combination of these dimensions. "Show me all spend by the risk team on the compliance-check application, attributed to individual engineers." No custom reporting required — every request carries all four dimensions and you filter from the dashboard.