More Tokens, Smaller Bill

AT&T grew daily token usage 3.4x, from 8 billion to 27 billion, across more than 100,000 employees while its AI cost fell 90%, Deloitte reports. That's the opposite of what most finance teams assume: usage up, bill down. OpenRouter's own platform volume backs up how fast the wave is moving, 5 trillion weekly tokens in November 2025 to 25 trillion by May 2026, and Deloitte's enterprise survey puts a healthcare company on the same growth curve on the other side of the outcome, $6 million in unplanned annualized cost from 8-10% monthly token growth with no architecture change. This post lines up the three data points, compares what AT&T changed against what the healthcare enterprise didn't, and lays out what decouples a rising token count from a rising bill.

Published 2026-09-02 by Dor Amir on the Nadir blog.

Filed under FinOps & Governance.

AT&T's daily token usage more than tripled. Its AI bill fell 90% anyway.

The instinct in most finance teams is to treat AI cost and AI usage as the same line moving together: more tokens, bigger bill. Deloitte's account of AT&T's rollout breaks that assumption in public. AT&T scaled generative AI across more than 100,000 employees and was processing roughly 8 billion tokens a day. After it restructured the work around multi-agent systems, that volume grew to 27 billion tokens a day, a 3.4x increase, while the company's AI cost fell by 90%. Source: Deloitte, "AI token economics for CFOs," 2026 Same company, more work getting done, a smaller bill. The lever wasn't spending less. It was changing what each token was spent on.

The figures in this post come from Deloitte's published account of AT&T's deployment and from OpenRouter's own funding announcement, not from Nadir's production data. Treat the specific multipliers as one documented case and one platform's self-reported growth curve, not universal constants every enterprise will replicate.

Two panels. Left: OpenRouter's platform-wide weekly token volume, growing from 5 trillion in November 2025 to 25 trillion in May 2026, a 5x increase in six months. Right: AT&T's relative AI cost index falling from 100 to 10, a 90% drop, in the same window its daily token volume climbed 3.4x from 8 billion to 27 billion.
Two panels. Left: OpenRouter's platform-wide weekly token volume, growing from 5 trillion in November 2025 to 25 trillion in May 2026, a 5x increase in six months. Right: AT&T's relative AI cost index falling from 100 to 10, a 90% drop, in the same window its daily token volume climbed 3.4x from 8 billion to 27 billion.

The volume wave is bigger than any one company

AT&T's growth curve isn't an outlier shape, it's the shape everywhere finance teams are looking right now. OpenRouter's own Series B announcement put its weekly platform-wide token volume at 5 trillion in November 2025 and 25 trillion by late May 2026, a 5x jump in six months, with the company on pace to process over a quadrillion tokens across all of 2026. Source: OpenRouter, "Series B" announcement, May 2026 Google separately reported processing 480 trillion tokens a month in 2025, a 50x year-over-year increase. Deloitte's own survey of 550 US enterprise AI leaders found 37% already consuming between 1 and 10 billion tokens a month, and another 30% above 10 billion. Source: Deloitte, "AI token economics for CFOs," 2026 None of this is a forecast anymore. It's the current run rate, measured across three independent sources that don't talk to each other.

Why usage keeps climbing even as the price per token falls

The obvious question is why volume is accelerating at all, given how far per-token prices have dropped over the same period. We've written about the price side of this separately: a blended average of $1.16 to $1.18 per million tokens in August 2026, down 43% in about ten weeks. Cheaper tokens should mean a flatter bill, not a steeper one. Two mechanisms explain the gap. First, reasoning and agentic workloads generate tokens a chatbot never did, thinking tokens before an answer, tool calls, multi-step trajectories, and Deloitte names this shift explicitly as a driver of the consumption curve. Second, this is the standard Jevons paradox pattern we've covered before: when the cost of doing a unit of work drops, teams don't hold spend flat and pocket the difference, they do more units of work. A cheaper token doesn't reduce the bill. It removes the reason not to run ten more agent loops than you would have last quarter.

The same growth curve, two different outcomes

Deloitte's report also carries the other half of the story: a healthcare enterprise whose token consumption grew 8% to 10% a month, compounding to roughly 1 trillion tokens over six months, and translating into more than $6 million in unplanned annualized cost. Same underlying force as AT&T, usage climbing on its own trajectory as adoption spreads through the organization. Different result, because nothing changed about how the work was architected. Every additional token flowed through the same undifferentiated path to the same model tier it always had.

Healthcare enterpriseAT&T
What grewToken volume, 8-10%/month, ~1T tokens over 6 monthsToken volume, 8B to 27B tokens/day
What changed architecturallyNothing reportedMoved to multi-agent systems
Cost outcome$6M+ unplanned annualized costCost index fell ~90%
The differenceGrowth absorbed at the existing per-token costGrowth absorbed at a lower cost per unit of work

Both are Deloitte-documented cases from the same 2026 survey. The variable that separated a $6 million surprise from a 90% reduction wasn't the growth rate. It was whether anything sat between the request and the most expensive model available to answer it.

What actually decouples the bill from the volume

AT&T's own account credits multi-agent orchestration, not usage restraint, and the mechanism generalizes past their specific stack:

Where this fits next to routing

This is the same argument we made about Gartner's 90%-cheaper-inference forecast: a falling unit price doesn't lower a bill that's growing on volume, only a falling cost per unit of work does, and those are two different numbers. Nadir exists to be the layer AT&T's account describes in the abstract, deciding per request which model tier a given task actually needs, verifying the cheap answer before accepting it, and surfacing cost per request in the dashboard so growth in usage stops being indistinguishable from growth in spend. The token wave documented here isn't going to reverse. Whether it shows up on the invoice as AT&T's outcome or the healthcare enterprise's is an architecture decision, not a forecasting problem.

Conclusion.

Three independent sources agree the token volume flowing through AI systems is climbing fast, and none of them expect it to slow down. What separates a company that absorbs that growth from one that gets a surprise invoice isn't how much AI usage grows. It's whether every one of those tokens still routes to the same model tier it did a year ago, or whether something in the path is deciding, request by request, what that token actually needs to cost.


Sources: [Deloitte, "AI token economics for CFOs," 2026](https://www.deloitte.com/us/en/services/consulting/articles/cfo-guide-ai-token-economics.html); [OpenRouter, "Series B" announcement, May 2026](https://openrouter.ai/blog/announcements/series-b/).

More on finops & governance

What Nadir is

Nadir is an LLM router. Nadir sends each prompt to the cheapest model that can handle it. A small decision model reads each prompt against your model menu and picks the lowest-cost model it expects to handle it. When the decision model is uncertain or unavailable, the request goes to the strongest model on the menu. The routing step makes no call to your model provider.

Nadir runs two ways. The decision API returns a model, reasoning-effort, cache, context, and policy recommendation without calling a model provider, beside the gateway you already run. That is how a shadow-mode evaluation works, and its projected savings stay advisory. The OpenAI compatible managed proxy executes the route, and migration is a two-line change: point the base URL at api.getnadir.com and set model to auto. On that path an optional verifier can score a complete non-streaming answer and escalate to a stronger model when it misses the configured bar. Streaming bypasses post-generation verification. BYOK is supported on every tier.

For coding agents, Nadir Auto is a terminal launcher for Claude Code or Codex that asks Nadir for the main-session model before each turn, with your configured model as the fallback and cost ceiling. Delegation integrations for Claude Code, Codex, or Cursor instead recommend a model tier for subagent work, and the agent decides; the Claude plugin can also move a main-thread turn to Haiku when Nadir's cache check prices it cheaper, unless its switch_main_model option is off. Either way inference runs on your own provider account, so Nadir holds no provider keys on that path.

What the numbers are, and what they are not

Nadir publishes each evaluation with its scope. On checkable code, run-check-escalate solved 392 of 395 common HumanEval and MBPP problems (99.2%), graded by running the canonical tests; that applies only to tasks with runnable deterministic tests. Nadir-Tumbler posts an arena_score of 72.3 on RouterArena's public scorer, 5th of 23 routers, which measures the routing decision on RouterArena's own model pool. A reference-assisted RouterBench evaluation over 11,420 held-out triples produced a 60% lower projected cost than always-Opus with about 98% retained quality and a 1.7% catastrophic-route rate. That experiment gave the verifier the expensive-model reference answer, which production does not have, so it is a research ceiling and not the deployed path.

None of these is a production guarantee, a universal savings rate, or a forecast for any particular workload. Customer savings are reported from measured execution against a declared baseline, and customer quality only from outcome-labelled traffic. Projected savings and realized savings are separate artifacts and are never blended.

Design-partner program

Three rungs, picked by risk appetite. Rung 0 Shadow runs advisory decision calls alongside live traffic and returns a projected receipt, with nothing in the request path changed. Rung 1 Hosted is the two-line swap on a production slice and returns a realized receipt. Rung 2 On-prem is a supervised six-week proof of concept inside the partner's VPC, where no prompt, response, or usage reaches Nadir. The commitments are the same at every rung. Apply for a rung directly: Rung 0 Shadow, Rung 1 Hosted, or Rung 2 On-prem. Not sure which fits? Start at getnadir.com/contact/?reason=design-partner.

Licensing

NadirClaw is the self-hosted core, source-available under the PolyForm Noncommercial License. Source-available is the correct label; NadirClaw is not open source. Nadir Route's hosted plan has no base fee and charges a variable fee only on measured savings from requests Nadir executed.

Pages on this site

Machine-readable summaries of this site: llms.txt and llms-full.txt.