Token Cost Radar

Token Cost Radar

October 22, 2026

Today's token-cost story is about the engineering decisions hiding inside the AI bill. Cloudflare has published one of the clearest production case studies yet, showing how it reduced AI code-review costs 68% by fixing prompt caching, eliminating unnecessary tool calls, and selecting models according to measured performance. DeepSeek has opened the inference engine behind its commercial Flash model, while IBM's new llm-d 1.0 release demonstrates how distributed serving can improve the economics of large-scale agent workloads. Fresh announcements from DDN, Nutanix, and Cisco show infrastructure vendors competing to reduce the cost of producing and delivering tokens. Meanwhile, new research reports up to 1.72 times greater cost efficiency from heterogeneous inference hardware, up to 2.51 times higher decoding throughput through better cache management, and 5.7 to 8.3 times lower inference costs by transferring expensive-model capabilities into reusable agent skills. The vocabulary arc from tokenmaxxing through tokenminimizing toward token yield is becoming measurable. The emerging lesson is that cheaper tokens help, but eliminating unnecessary computation and measuring successful outcomes can matter considerably more.

Top Developments (October 19-22)

1How did Cloudflare cut its AI code-review bill 68% without abandoning capable models?

Cloudflare's October 19 engineering report documents how its internal AI code reviewer reduced average inference costs from $2.43 during its two most expensive weeks to $0.77 per review. Median completion time fell from four minutes and nine seconds to one minute and 32 seconds. The investigation began after average review costs climbed from $1.19 in April to approximately $2.46 by late August, despite no major architectural redesign. Cloudflare discovered that output tokens represented only 23% of spending, while cache writes accounted for 43% and cache reads another 34%. Although the overall cache-hit rate had reached 97%, the first request in a session reused a cached prefix only 14% to 26% of the time. Repository-specific information was preventing otherwise identical instructions and tool definitions from sharing cache entries. Fixing the prefix structure, removing inaccessible tools, eliminating redundant model turns, skipping unnecessary repeat reviews, and stopping canceled jobs accounted for approximately 40% of the reported savings. Model and reasoning-effort changes produced the remainder. Cloudflare also evaluated review quality, reporting that developers acted on 59% of serious code-quality findings after optimization, compared with 34% previously. These are internal measurements rather than independently verified defect-detection benchmarks. The important finding is that a rising AI bill can reflect inefficient execution and context handling rather than simply higher model prices.

Cloudflare Engineering ↗

2DeepSeek opens DeepInfer, exposing the inference machinery behind its commercial API

DeepSeek released DeepInfer on October 20, with substantial developer attention continuing October 21. The Apache 2.0 project exposes core inference technology used in DeepSeek's production services, initially supporting DeepSeek V4.1 Flash. Its capabilities include optimized attention and matrix-multiplication kernels, mixture-of-experts parallelism, asynchronous batch scheduling, speculative decoding through DSpark, confidence-scheduled verification, deterministic sampling, and structured output generation. Supported accelerators include NVIDIA SM100 GPUs and Huawei Ascend 950 NPUs. DeepSeek also released a companion project, deepseek-recipe, that reproduces important request-encoding and response-decoding behavior from its hosted API. The release is significant because it makes production-oriented inference optimizations available to developers pursuing self-hosted alternatives to commercial token billing. Important limitations remain: the published DeepInfer implementation supports offline inference and does not include the complete KV-cache management system, prefill/decode disaggregation infrastructure, or replica load balancing needed for a production serving service. Its published performance results are DeepSeek's own and have not been independently reproduced across comparable deployments. The release lowers the barrier to studying efficient inference, but does not make production deployment or its operating costs trivial.

DeepSeek GitHub ↗

3DDN and Nebul report nearly tenfold faster first-token delivery through reusable context

DDN announced October 21 that European AI cloud provider Nebul is using DDN Infinia to store and reuse key-value cache state across its NVIDIA-powered infrastructure. The deployment targets sovereign AI inference workloads where data residency, performance, and infrastructure utilization must be managed together. According to testing reported by DDN, its system delivered nearly ten times faster time to first token than Nebul's existing CPU-memory cache configuration, up to five times faster token responses than evaluated alternatives, and 2.5 times more input tokens per second from the same GPUs. The mechanism is straightforward: retaining and efficiently retrieving previously computed context can reduce repeated prompt processing and free accelerator capacity for additional requests. These figures are vendor-reported performance comparisons, not independently verified reductions in customer invoices. The benchmarks also compare particular storage and caching configurations rather than establishing universal gains across inference workloads. Nevertheless, the announcement illustrates how the economics of long-context agents increasingly depend on memory architecture and cache reuse rather than model execution alone.

DDN via Business Wire ↗

4Nutanix and Supermicro target the cost per token of private AI

Nutanix and Supermicro announced October 21 that they plan to develop a jointly engineered infrastructure system for private AI inference. The proposed solution combines Supermicro servers containing eight NVIDIA Blackwell Ultra GPUs per node with Nutanix infrastructure software, NVIDIA Spectrum-X networking, integrated storage, and agent-management capabilities. The companies position the system as a way to reduce deployment complexity, improve GPU utilization, support open-weight models, and give enterprises more control over inference economics. Planned capabilities include model-as-a-service deployment, a secure agent gateway, integrated context caching, and centralized infrastructure management. The announcement is a product-development commitment, not evidence that the completed system already delivers a specific reduction in token costs. No independently verified cost-per-token benchmark accompanies the release. Its significance lies in the expanding market for private inference systems that compete on total operating economics, including hardware utilization, storage, networking, deployment overhead, and governance. For enterprises with sustained workloads, the comparison increasingly involves the total cost of owned or dedicated infrastructure versus consumption-based API pricing.

Nutanix via GlobeNewswire ↗

The AI Bill Moves From Model Pricing to System Architecture

Tokenmaxxing is the practice of maximizing AI token consumption, sometimes treating usage volume as evidence of productivity. Tokenminimizing is the practice of reducing unnecessary token consumption while preserving acceptable results. Modelmaxxing means matching model capability and cost to the requirements of each task rather than automatically selecting the most powerful available model. Token yield measures useful completed work relative to the number of tokens consumed. Today's evidence reinforces the progression from tokenmaxxing through tokenminimizing toward token yield. Cloudflare's production measurements show why prompt structure, cache behavior, tool access, and execution loops can matter more than advertised token prices. Alternative spellings including tokenminning and tokenmining remain worth monitoring, but today's searches did not establish a new increase in their adoption.

IBM

IBM and its collaborators announced llm-d 1.0 on October 20, introducing a production-oriented release of the open-source distributed inference stack governed by the Cloud Native Computing Foundation. The system combines cache-aware routing, KV-cache offloading, prefill/decode disaggregation, expert parallelism, and workload-aware scheduling. IBM reports that a deployment serving GLM 5.2, an approximately 753-billion-parameter open-weight model, achieved more than 6.6 million output tokens per minute at peak while supporting up to 3,000 concurrent coding agents without preemptions. Using current cloud rental rates, IBM estimates that the demonstrated configuration could produce tokens at five to ten times lower cost than comparable commercial API pricing for certain agentic workloads. In another research application, IBM reports approximately 98% prefix-cache reuse and a blended serving cost of $0.11 per million tokens. These are project-reported benchmarks and modeled cost comparisons, not universal commercial prices. They demonstrate how open-weight models and distributed inference infrastructure can change the economics of high-volume agent workloads.

IBM Newsroom ↗

Cisco

Cisco's October 21 announcement introduces an AI Inference Routing blueprint developed with NVIDIA for service providers operating distributed computing infrastructure. The architecture uses established networking mechanisms, including Segment Routing over IPv6, Flexible Algorithm, and Border Gateway Protocol, to direct inference requests toward infrastructure that satisfies latency, jurisdiction, resilience, and cost requirements. Cisco argues that operators can improve utilization by coordinating existing regional and edge resources rather than simply purchasing additional capacity. The blueprint also describes verifying that routing decisions satisfy promised service objectives. This is an architectural proposal rather than a measured reduction in inference costs, and the announcement does not provide a universal throughput or token-price benchmark. The broader development is important because model routing is expanding beyond choosing which model answers a request. Infrastructure location, network path, data sovereignty, and available accelerator capacity are becoming additional variables in the cost-routing decision.

Cisco ↗

Amazon Web Services

An October 20 AWS engineering article examines i14's Laplace 3B, a linear-attention model designed to avoid the continually expanding KV cache associated with conventional transformer inference. Instead of retaining attention state that grows with conversation length, Laplace maintains a fixed recurrent state of approximately 29.5 MB per sequence. AWS reports that the model achieved approximately 120,000 training tokens per second on a Trainium2 instance and served 11,544 output tokens per second across 1,280 concurrent sequences. These are model-specific throughput measurements, not controlled comparisons showing equivalent quality or cost against leading transformer models. The architectural distinction is nevertheless substantial. If serving state remains bounded as context grows, infrastructure can potentially support longer interactions and greater concurrency without proportionally increasing cache memory requirements. The approach also introduces tradeoffs involving model architecture, specialized kernels, and the fidelity of retained historical information.

Amazon Web Services ↗

Couchbase

Couchbase announced an expansion of its AI Data Plane on October 20, adding native Amazon Bedrock integration, semantic caching, managed agent memory, and additional search and data-management capabilities. The company claims its integrated architecture can reduce token consumption by up to 45% in evaluated scenarios. Semantic caching attempts to reuse suitable previous results when new requests are sufficiently similar, avoiding unnecessary model calls. Persistent agent memory can also reduce repeated retrieval and reconstruction of information across interactions. These are vendor-reported capabilities and savings claims, not independent benchmarks demonstrating that every workload will benefit. Semantic similarity does not guarantee that two requests require identical answers, and inappropriate cache reuse can introduce accuracy or freshness problems. The development illustrates the increasing importance of deciding whether inference is necessary before paying for another model invocation.

Couchbase via PR Newswire ↗

Uber Engineering

Uber's earlier engineering report has renewed relevance following Cloudflare's findings about unnecessary tool calls and context overhead. Uber describes a unified gateway supporting more than 1,000 MCP servers and explains that conventional tool initialization could introduce approximately 50,000 to 70,000 tokens of schema overhead when more than 100 tools were installed. Its alternative approaches include resolving tool calls through command-line interfaces, searching tool catalogs on demand, and executing multi-step operations programmatically without returning every intermediate result to model context. In one internal comparison, a wide-table database query generated approximately 1.43 million tokens through conventional model-mediated tool interaction, compared with 900 tokens through code-mode execution. That extreme example is workload-specific and should not be generalized to all database queries. Uber also reports that cost per session fell 52% from its June peak while usage expanded. The original report was published August 27, not this week, but its findings directly illuminate today's renewed discussion of context overhead and unnecessary agent turns.

Uber Engineering ↗

VentureBeat

VentureBeat's October 16 reporting examines Gartner's forecast that inference costs per agentic workflow will increase more than fivefold through 2028 even as producing individual tokens becomes cheaper. Gartner calls this the Inference Paradox. The firm argues that increasingly capable agents perform more reasoning, tool calls, and intermediate operations than ordinary chatbot interactions. Its research estimates that agentic workflows can consume five to thirty times more tokens per task than simpler interactions. A September VentureBeat survey of 109 respondents found that 21% of organizations using orchestration platforms had no automatic mechanism to stop agents from exceeding token budgets. Another 31% reported routing routine, high-volume work to cheaper models. These are survey results and forecasts rather than observed future expenditure. The practical recommendations include request-level observability, inference tiering, bounded execution, and cost-per-outcome measurement. The report provides an economic explanation for why the infrastructure improvements announced this week may not automatically translate into smaller enterprise AI budgets.

VentureBeat ↗

Research Watch

D-Skill: Distilling Teacher Knowledge through Agent Skills

Submitted October 20 and appearing in the October 22 research listings, D-Skill investigates transferring the behavioral advantages of expensive language-model agents to smaller models without changing model weights. The researchers analyze paired execution traces from teacher and student agents, identify meaningful behavioral differences, and consolidate the resulting lessons into natural-language skill documents. These skills are then supplied to the smaller model during inference. Across SpreadsheetBench-Verified, ALFWorld, and chess-puzzle evaluations, the authors report closing 75% to 95% of the performance gap between teacher and student models. Under the same model family, student inference costs were 5.7 to 8.3 times lower per task than those of the teacher. The method operates offline after collecting the paired trajectories and does not require further environment interaction during skill construction.

Why it matters: This is a concrete alternative to paying frontier-model prices for every execution. Expensive reasoning can be used to discover reusable procedures that improve cheaper agents. The economics depend on how often the skills are reused, how well they generalize, and whether the cost of creating and maintaining them is recovered through subsequent execution savings.

arXiv ↗

HGM-Dual: Lineage-Aware Guided Agent Harness Optimization for Long-Horizon Planning

Submitted October 21, HGM-Dual examines the cost of improving an agent's prompts, tools, and workflows through repeated experimentation. Conventional recursive improvement methods can waste substantial evaluation budgets exploring changes that do not address the agent's actual weaknesses. The proposed framework maintains structured records of previous modifications, including which behaviors improved, which regressed, and which changes proved ineffective. It then generates both general improvements and specialized candidates targeting identified planning failures. Across the evaluated planning tasks, HGM-Dual improved case accuracy by up to 14.45% relative to the strongest baseline and matched the final performance of existing Huxley-Godel Machine variants using two to four times less evaluation budget. These are benchmark-specific results, not measured reductions in production API bills.

Why it matters: Agent improvement itself consumes tokens and evaluation resources. A system that remembers which modifications failed can avoid paying repeatedly to rediscover the same lessons. The paper extends token-efficiency thinking beyond runtime execution into the development and optimization of agent workflows.

arXiv ↗

UlaCache: Unified Logical Addressing for Sparse LLM Serving

Submitted October 21, UlaCache introduces a memory-management system for sparse-attention inference. Sparse attention reduces computation by selecting relevant historical tokens, but the corresponding KV-cache entries must remain available for subsequent decoding. UlaCache separates logical cache references from physical placement across GPU memory and optional CPU storage. Its design retains frequently needed entries locally and transfers missing entries when required. A parallel eviction mechanism manages shared GPU cache capacity. Under matched CPU and GPU memory budgets with speculative decoding enabled, the researchers report peak decoding throughput improvements of 1.16 times for data-parallel attention and 1.70 times for tensor-parallel attention on NVIDIA H200 hardware. On B300 hardware, the corresponding improvements reached 1.73 and 2.51 times. These are experimental throughput results rather than direct measurements of commercial inference prices.

Why it matters: Reducing attention computation is only useful if cache management does not erase the savings. UlaCache demonstrates that efficient retrieval and placement of intermediate model state can materially improve token throughput. The principle applies broadly to inference systems where memory movement competes with computation for time and resources.

arXiv ↗

HAWK: Heterogeneity-Aware KV Cache Transfer for Efficient GPU-NPU Phase-Disaggregated LLM Inference

Submitted October 21, HAWK investigates using different accelerator types for the prefill and decoding stages of language-model inference. The researchers observe that GPUs are particularly effective at compute-intensive prefill, while NPUs can offer advantages during memory-bound decoding. Combining the devices requires transferring KV-cache state between architectures with different memory layouts and communication mechanisms. HAWK uses remote direct memory access and layout-aware destination buffers to transfer cache state without requiring additional data rearrangement. In experiments using commercially available GPUs and NPUs, the heterogeneous system achieved performance within 7.88% of a GPU-only configuration under equivalent service-level constraints while delivering up to 1.26 times greater power efficiency and 1.72 times greater cost efficiency. The results apply to the evaluated hardware and workloads.

Why it matters: The most economical accelerator for processing a prompt may not be the most economical accelerator for generating its answer. Separating inference phases across different hardware creates opportunities to reduce operating costs, provided communication overhead remains controlled. HAWK demonstrates a practical approach to managing that tradeoff.

arXiv ↗

RISK-KV: Quality-Aware Selective KV Cache Reconstruction for Distributed LLM Inference

Submitted October 21, RISK-KV investigates reducing the amount of historical KV-cache state that must be retained or transferred when inference requests migrate between servers or resume after interruption. Instead of preserving every cache entry, the method reconstructs selected missing layers using information from neighboring layers. A quality-aware selection process evaluates the effect of reconstruction on model predictions before deciding which layers can be omitted. Across three evaluated language models, representative configurations omitted 18.2% to 33.3% of historical KV-cache state while keeping perplexity changes below 0.5%. In a local recovery experiment using 512 tokens of history, RISK-KV achieved speedups ranging from 1.51 to 3.31 times compared with replaying the complete token history. These results concern the evaluated recovery conditions rather than general-purpose inference throughput.

Why it matters: Keeping every previously computed state consumes memory and transfer bandwidth, while recomputing everything wastes processing time. Selective reconstruction offers a middle ground that trades limited computation for reduced storage and communication. The paper illustrates how inference efficiency increasingly depends on deciding what information is worth preserving exactly.

arXiv ↗

Phrase of the Day

“Token discipline”

Token discipline is the systematic management of AI token consumption through measured budgets, efficient execution, appropriate model selection, and accountability for useful results.

  1. AI adoption
  2. Tokenmaxxing
  3. Token shock
  4. Tokenminimizing
  5. Modelmaxxing
  6. Token discipline
  7. Token yield
  8. Cost per successful outcome

The phrase has appeared in industry coverage for months, including TechRadar's reporting on Gartner's warning that developer choice alone will not produce sufficient spending discipline. Today's Cloudflare case study gives the concept unusually concrete engineering substance. Cloudflare did not simply tell its developers to consume fewer tokens. It measured where the money went, discovered that repeated context processing dominated expenditure, corrected cache boundaries, eliminated unnecessary tool access, stopped redundant execution, and tested alternative models against actual review outcomes. The result was a reported 68% reduction in cost per review alongside substantially shorter execution times. The distinction matters because arbitrary spending caps can prevent useful work, while lower token counts can conceal deteriorating quality. The research published this week extends the same principle into infrastructure and agent design. D-Skill transfers expensive-model capabilities into reusable instructions, HGM-Dual reduces wasted agent-evaluation effort, and cache-management systems avoid unnecessary storage transfers and recomputation. Together, these developments illustrate a progression from simply consuming AI, to minimizing avoidable consumption, to measuring whether the remaining expenditure produces valuable work. Token discipline is the operational practice connecting those stages.

The cheapest token is one you never needed. The most valuable token is one that helped finish the job.

TechRadar ↗

The jCodeMunch read

Cloudflare's findings provide a particularly relevant lesson for coding agents: context management is an engineering decision with measurable financial consequences. The company's experience shows how unnecessary tool definitions, repeated file access, and redundant model turns can inflate costs even when cache-hit rates appear healthy. jCodeMunch addresses one part of that problem by reducing code-reading tokens through tree-sitter symbol retrieval and byte-precise context. Rather than requiring agents to process entire source files to locate specific functionality, it makes targeted retrieval possible. Today's broader lesson is that efficient inference begins with deciding what information and computation the task actually requires.

See how the 95%+ cut is measured →

← All editions