Token Cost Radar

Token Cost Radar

August 29, 2026

Today's token-cost story is about the shape of consumption, not just its size. Uber says agent requests grew 9.4 times while total AI spending stayed relatively stable, a fresh audit found that the top 1% of agent runs generated 46% of spend, and market data attributed to JPMorgan shows token volume rising much faster than token spending as cheaper models absorb traffic. The vocabulary arc from tokenmaxxing to tokenminimizing and token yield is getting a new practical obsession: token burn, especially the long tail of expensive runs that averages conceal.

Top Developments (Last 24 Hours)

1How did Uber grow agent requests 9.4 times without growing the AI bill with them?

Uber Engineering reports that weekly agent requests grew 9.4 times from February to August while total AI spending remained relatively stable from April. Holding one model constant, cost per 1,000 model requests fell almost 34% from its peak and cost per session fell 52% from its June peak. Uber attributes the improvement to model routing, caching, prompt and tool optimization, attribution, and on-demand MCP tool loading.

Uber Engineering ↗

2The average agent run is cheap. The expensive tail is not.

Metapress reports on an internal Revenium audit of 14,680 agent runs in which the top 1% generated 46% of total spending and the top 5% generated 77%. One unattended coding-agent session ran for four days, made 4,819 calls, and cost $3,762. Revenium's findings argue that average cost per run can hide the portion of agent spending most likely to break a budget.

Metapress ↗

3Token volume rises 47% while spending rises 7%

KuCoin reports that a JPMorgan research update found OpenRouter token volume increased 47% month over month while token spending increased 7%. The reported volume-weighted average price fell 28%, with lower-priced models such as GPT-5.6 Luna accounting for most of the incremental volume. If the trend holds, cheaper tokens are expanding consumption considerably faster than the bill.

KuCoin ↗

4DeepSeek makes the weekend an inference discount

DeepSeek's current V4 pricing charges half its peak rate during off-peak periods, with the entire UTC weekend classified as off-peak. V4 Flash is listed at $0.22 per million input tokens and $0.66 per million output tokens off-peak, versus $0.44 and $1.32 at peak. For delay-tolerant evaluation, batch, and background workloads, scheduling has become a literal cost-routing decision.

DeepSeek API Docs ↗

From Tokenmaxxing to Managed Token Burn

Tokenmaxxing is the practice of maximizing AI token consumption as a proxy for productivity. Tokenminimizing is the practice of removing avoidable consumption while preserving the required result. Modelmaxxing means selecting the best-value model capable of completing each task. Token yield measures useful output relative to the resources consumed. Today's freshest signal is that aggregate efficiency is not enough when a small number of runaway trajectories can dominate the bill.

Nate's AI Token Burn

A newly updated public dashboard explicitly uses token burn to track daily consumption across Codex, Claude, and ChatGPT. Its August 28 data recorded 55.4 million tokens for the day and 47.4 billion across the displayed history, illustrating how the language of burn is becoming a natural way to discuss sustained agent consumption rather than isolated prompts.

Nate's AI Token Burn ↗

BenchLM

BenchLM's current pricing dataset reports an 82% median blended API-price discount for open-weight models compared with proprietary models. The widening price surface strengthens the economic case for modelmaxxing because the cost difference among models is now large enough to overwhelm small prompt-level optimizations.

BenchLM ↗

FinOps Foundation

The FinOps Foundation treats token economics as a value-management discipline spanning attribution, cost per inference, token efficiency, token yield, caching, model right-sizing, budgets, anomaly detection, showback, and chargeback. The emerging unit of control is increasingly the workflow or outcome rather than a seat or aggregate monthly token number.

FinOps Foundation ↗

Tokenminning

The variant spelling tokenminning remains in active use for deliberate reduction of LLM consumption while preserving useful output quality. Its published practice combines model routing, context control, caching, output limits, attribution, and hard agent budgets instead of equating efficiency with shorter prompts.

Tokenminning ↗

Anthropic

Anthropic's retrieval-based tool discovery remains a primary reference for reducing tool-surface bloat. Instead of placing every available tool definition into context upfront, relevant schemas are retrieved when needed. Anthropic reports an 85% token reduction in its evaluation while preserving access to the complete tool library.

Anthropic ↗

Research Watch

CacheRouter: Tool Discovery Without Sacrificing Prompt Caching

CacheRouter identifies a conflict between progressive tool disclosure and prompt caching: changing the visible tool list can shrink the prompt while invalidating reusable prefixes. Its dual-path architecture keeps a small fixed tool surface in the main prompt and handles long-tail discovery separately. Prototype experiments reported token-level cache-hit rates of 90.99% and 95.2%, reducing modeled input cost to roughly 12% and 8% of a no-cache baseline under the DeepSeek pricing used by the authors.

Why it matters: Tokenminimizing and caching can work against each other. The cheapest prompt is not necessarily the cheapest execution if changing it destroys discounted reusable context.

arXiv ↗

SchemaRouter: Field-Aware Tool Routing for Efficient Agentic RAG

SchemaRouter chooses both which tools to call and which response fields to retrieve. On its 110-query benchmark, it used 227 retrieved-context tokens versus 2,066 for a fetch-everything baseline while maintaining comparable answer accuracy. A more aggressive minimum-field configuration lost accuracy.

Why it matters: The target is relevant context, not minimum context. Tool payloads can be narrowed dramatically, but removing evidence beyond the useful threshold turns token savings into lower token yield.

arXiv ↗

Paritok-4B: Intent-Conditioned Context Compression for Coding Agents

Paritok-4B compresses large file reads and tool outputs before they are passed to coding models. Across all 300 SWE-bench Lite instances, it reduced context to 25.7% of its original size while retaining 86.5% of uncompressed single-shot solve quality. The authors also found that using GPT-5 itself as the compressor was economically negative at list prices because compression cost more than the downstream tokens it saved.

Why it matters: Compression has its own invoice. A token optimization is only a cost optimization when the machinery performing it costs less than the inference it eliminates.

arXiv ↗

Resource-Aware Consensus for Multi-Agent AI

This recent arXiv paper models multi-agent communication topologies according to both consensus speed and token cost, then adds the remaining computational budget directly to the system state. Its framework derives conditions for reaching agreement without exhausting the token budget and evaluates adaptive switching among differently priced coordination patterns.

Why it matters: Multi-agent systems can consume tokens simply by talking among themselves. Budget-aware coordination makes inter-agent communication an explicit resource allocation problem rather than assuming more discussion is always better.

arXiv ↗

Phrase of the Day

“Token burn”

Token burn is the rate or volume at which an AI system consumes tokens over time, especially across sustained agent sessions, repeated tool calls, and other long-running workflows.

  1. AI adoption
  2. Tokenmaxxing
  3. Token shock
  4. Tokenminimizing
  5. Modelmaxxing
  6. Token discipline
  7. Token burn
  8. Token yield

The likely winners are teams that can see token burn at the run level, detect expensive tails early, and reduce unnecessary model, context, tool, and retry consumption without suppressing productive work.

Monthly spend tells you how much fuel disappeared. Token burn tells you which engine was still running in the driveway.

Nate's AI Token Burn ↗

The jCodeMunch read

Today's strongest theme is controlling what an agent repeatedly consumes before the long tail compounds. jCodeMunch applies that principle to code reading through tree-sitter symbol retrieval and byte-precise context, reducing the tokens spent presenting code that has no bearing on the task.

See how the 95%+ cut is measured →

← All editions