Today's token-cost story is splitting between financial control and computational efficiency. New reporting on AI FinOps cites a survey in which 73% of AI projects exceeded their budgets, while DeepSeek's newly introduced Search and Fetch APIs challenge token-based billing with a flat $0.75 per 1,000 successful requests. AWS engineers report that changing how inference servers transfer cached context can improve time to first token by approximately threefold. Meanwhile, an Nvidia-backed startup claims its code-execution technology reduced one customer's computing expenses by 67%. The research is particularly interesting today. Newly listed papers report a 10% to 46% reduction in multi-agent communication tokens, a 20% reduction in inference cost per token through better infrastructure planning, and an adaptive reasoning system that accounts for the changing energy cost of computation. The vocabulary is catching up with the engineering. Tokenmaxxing is giving way to tokenminimizing, token yield, and a newer term gaining traction: valuemaxxing. The emerging principle is that organizations should measure what AI accomplishes, not simply how much computation it consumes or how cheaply that computation can be purchased.
Top Developments (October 19-20)
1Why are 73% of AI projects exceeding their budgets?
The Elec published the first installment of an AI FinOps series on October 20, examining why conventional cloud cost-management practices struggle with generative AI. Citing Harness's 2026 State of AI in FinOps survey of approximately 700 enterprise IT leaders, the publication reports that more than 67% of surveyed organizations spend at least $250,000 monthly on AI, while 73% of AI projects exceeded their budgets. Harness also estimated that approximately 26% of monthly AI budgets are wasted. The report identifies four major complications: token-based pricing, multimodel deployments, rapidly changing model capabilities, and increasingly complex agent workflows. Unlike predictable infrastructure workloads, agents can produce different output lengths, reasoning paths, and tool-call sequences for similar requests. Providers also impose different rate limits, caching policies, capacity commitments, and excess-usage rules. The survey figures are vendor-reported findings from the sampled organizations, not independently established rates for the entire enterprise market. The practical implication is that AI cost governance increasingly requires request-level observability, workload attribution, and budget enforcement rather than retrospective invoice analysis.
The Elec ↗2AWS reports threefold faster first-token delivery by changing KV-cache transfers
AWS engineers published an October 19 technical report describing a push-based key-value cache transfer mechanism for disaggregated inference using vLLM. Disaggregated serving separates prompt processing from token generation, allowing each phase to run on independently optimized infrastructure. However, the resulting KV cache must move between the prefill and decode servers. Conventional pull-based transfers introduce coordination and setup operations after prefill completes, delaying generation. The new implementation registers destination memory earlier and moves transfer preparation into a background thread. In AWS benchmarks using Qwen3-32B on EC2 P5en instances connected through Elastic Fabric Adapter, push-based transfers improved time to first token by up to approximately threefold and time per output token by up to 30%. At eight queries per second with 16,000-token inputs, first-token latency fell from approximately 1,744 milliseconds to 540 milliseconds. Prefix caching was deliberately disabled to isolate transfer performance. These are workload-specific latency measurements, not demonstrated reductions in commercial token prices. The work shows that inference efficiency depends on coordination and memory movement as well as model computation.
Amazon Web Services ↗3DeepSeek introduces per-call retrieval pricing as agents challenge token-based billing
Forkast's October 19 analysis examines DeepSeek's newly released Search and Fetch APIs, which charge $0.75 per 1,000 successful requests for each endpoint. Unlike model inference, which remains priced according to input and output tokens, these retrieval operations have a fixed charge independent of the amount of returned text. DeepSeek's documentation confirms that unsuccessful requests, empty results, and timeouts are not billed. Server-side Search and Fetch calls through supported coding-agent integrations are temporarily free, with billing scheduled to begin October 31 at 16:00 UTC. At the published rate, 10,000 successful search requests would cost $7.50, excluding subsequent model inference and any separate fetch operations. Forkast compares the rate with established retrieval providers charging approximately $5 to $12 per 1,000 requests, depending on service and configuration. DeepSeek imposes a five-request-per-second limit per endpoint and account. The development does not eliminate token-based inference billing, but it introduces a more predictable pricing unit for a common agent operation. Separating retrieval charges from reasoning charges could make high-frequency agent workflows easier to budget and evaluate.
Forkast ↗4Nvidia-backed doubleAI claims a 67% reduction in customer computing costs
The Wall Street Journal reports October 20 that doubleAI, a Tel Aviv startup co-founded by Amnon Shashua, is introducing a technology category it calls code execution models. Its first model, Maxwell, is designed to improve the execution efficiency of software running on CPUs and GPUs rather than serving as another general-purpose conversational model. According to the company's claims reported by the Journal, the technology reduced one early customer's computing costs by 67%. DoubleAI has raised approximately $220 million from investors including Nvidia, Lightspeed Venture Partners, Bessemer Venture Partners, and Dell. The company intends to charge customers a percentage of the savings its technology generates. The reported savings are an early customer result, not an independently verified universal benchmark. The relevance to token economics is indirect but substantial: improvements in the software executing inference workloads can lower infrastructure expenditure without requiring changes to model weights, prompts, or token counts. Whether those savings reach API customers depends on deployment economics and provider pricing.
The Wall Street Journal ↗From Tokenmaxxing to Measurable Token Yield
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. Token yield measures useful completed work relative to the tokens consumed. The progression from tokenmaxxing through tokenminimizing to token yield is increasingly visible in enterprise spending controls, inference architecture, and model-selection strategies. Alternative spellings including tokenminning and tokenmining remain worth monitoring, but today's coverage does not establish a new increase in their adoption. The strongest emerging distinction is between minimizing the amount of computation purchased and maximizing the useful work obtained from that computation.
The Australian
The Australian's October 19 reporting describes Accenture's warning that enterprises are entering a period of escalating AI expenditure as autonomous agents become more common. Accenture executive Stacy Pence argues that corporate finance leaders often lack sufficient understanding of token-based AI economics. According to research cited in the article, agent workflows currently account for approximately 11% of enterprise token spending but represent a rapidly growing consumption category. The report also states that more than half of enterprise AI requests are routed to expensive frontier models even though approximately 90% of workplace tasks do not require the most advanced capabilities. These are Accenture's reported estimates, not independently verified market-wide measurements. Pence recommends more deliberate model routing and improved context engineering. The broader lesson is that agent costs depend on repeated reasoning, tool use, and context processing throughout a workflow, making a single model's advertised token price an incomplete measure of operational expense.
The Australian ↗Reuters
Reuters reported October 19 that the US Department of Homeland Security has directed civilian federal agencies to remove DeepSeek AI products and associated services from government information systems because of security concerns. The restrictions also prohibit acquiring affected services. DHS cited potential data-transfer risks and vulnerabilities associated with the Chinese-developed technology. The development introduces an important qualification to comparisons based exclusively on token prices. DeepSeek and other inexpensive non-US models can offer substantial inference savings, but organizations must also evaluate data residency, regulatory requirements, security controls, and deployment restrictions. A model that is economically attractive on a public API may be unavailable for particular government workloads. Self-hosted alternatives can change the data-handling equation, but introduce infrastructure and operational expenses. The restriction does not establish that every deployment of a Chinese-origin open-weight model presents the same risks or is subject to the same rules.
Reuters ↗Flexera
Flexera's October analysis examines the transition from measuring AI adoption through consumption toward measuring results through completed tasks, time saved, quality improvements, and business outcomes. The company cites its 2026 State of ITAM research, in which only 31% of organizations reported accurate visibility into AI software and 59% reported increasing wasted AI software spending. Flexera also cites KPMG research indicating that 49% of surveyed organizations had scaled back, delayed, or paused agent deployments when expected costs threatened anticipated value. These are findings from the respective surveys, not universal enterprise statistics. The article recommends shared financial and technical ownership, model routing, prompt caching, and outcome-based evaluation. It also notes that FinOps FOCUS version 1.5 is expected to incorporate AI model identity and token-consumption information, with release targeted for December 2026. The practical direction is toward measuring successful business outcomes alongside consumption rather than using either token volume or token reduction as the sole performance indicator.
Flexera ↗OpenAI Developer Documentation
OpenAI's established tool-search documentation provides a useful architectural reference for the growing cost of MCP and agent tool schemas. The Responses API supports deferred tool loading, allowing an agent to discover relevant function definitions during execution instead of receiving every available schema at the beginning of a request. Developers can organize related tools into namespaces or MCP servers with searchable descriptions and import complete definitions only when required. This reduces the amount of tool metadata that must initially occupy model context. The documentation also describes how dynamically loaded definitions can preserve existing cached prefixes. Tool discovery introduces its own overhead and can affect latency or selection accuracy, so reducing the initial schema footprint is not automatically equivalent to reducing total task cost. The capability predates today's edition, but remains important as enterprise agents acquire access to increasingly large collections of APIs and tools. The architectural principle is that available capabilities need not all be resident in active context.
OpenAI Developer Documentation ↗DeepSeek API Documentation
DeepSeek's current pricing documentation illustrates how inference bills increasingly depend on caching and execution timing. DeepSeek V4.1 Flash is listed at $0.15 per million uncached input tokens and $0.60 per million output tokens during off-peak periods, with rates doubling during designated weekday peak hours. Cached input costs $0.003 per million tokens off-peak and $0.006 during peak periods. The API supports a one-million-token context window and both reasoning and non-reasoning modes. DeepSeek's newly introduced Search and Fetch endpoints add a separate per-request pricing dimension. These are published list prices, not guarantees of completed-task quality or actual customer savings. A workload with substantial reusable context may have very different economics from one generating long reasoning traces or repeatedly missing the cache. The documentation demonstrates why comparisons should account for cached and uncached input, output generation, time-dependent pricing, and external tool charges rather than relying on one headline token rate.
DeepSeek ↗Research Watch
Neuro-Inspired Inhibitory Message Passing for Accurate and Token-Efficient Multi-Agent Reasoning
Submitted October 17 and appearing in the October 20 arXiv listings, this paper introduces a training-free communication mechanism inspired by inhibitory signaling in biological neural systems. Instead of allowing agents to repeatedly exchange entire messages, reasoning traces, and overlapping evidence, the method identifies evidence sentences that recipients have not already received. It forwards useful information once while suppressing redundant material and excluding the sender's reasoning and answers. Across three benchmarks, the researchers report improvements of 39 to 77 percentage points in peer-group accuracy while reducing tokens per run by 10% to 46%. The gains were evaluated across seven open-weight models, two commercial models, groups containing up to 64 agents, and several communication architectures. These are experimental results under the tested configurations, not guaranteed reductions in commercial inference bills.
Why it matters: Multi-agent collaboration can become expensive when every participant repeatedly processes information already known to the group. The research demonstrates that selectively transmitting new evidence can improve both reasoning quality and token efficiency. It provides a concrete alternative to simply shortening messages or imposing smaller context limits.
arXiv ↗Koi: Evidence-Guided, Self-Calibrating Planning for Multi-Cloud, Heterogeneous LLM Inference Fleets
Submitted October 17 and newly listed October 20, Koi investigates how to configure inference infrastructure across heterogeneous clouds, accelerators, and workloads. The researchers identify approximately 140 interacting deployment variables, including hardware selection, parallelism, engine configuration, and replica counts. Koi combines language-model-assisted planning with deterministic performance prediction, candidate evaluation, and placement controls. It maintains a causal representation linking infrastructure decisions to runtime behavior, cache pressure, communication overhead, throughput, and latency. Across its benchmarks, Koi achieved 1.18 times the goodput of the strongest evaluated baseline while reducing cost per token by 20% in a real heterogeneous cluster. Ablation experiments showed that adding deterministic tools and structured planning improved results over using a language model alone. These findings apply to the evaluated infrastructure and workloads.
Why it matters: Model selection is only one part of inference economics. Hardware placement, utilization, cache behavior, and serving configuration also determine the effective cost of generating tokens. The research demonstrates how structured planning and deterministic measurement can improve those economics without requiring a new model architecture.
arXiv ↗ATEST: Adaptive Resource-Aware Test-Time Scaling for LLM Inference
Submitted October 18 and appearing in the October 20 research listings, ATEST examines how reasoning systems should allocate additional inference when GPU operating conditions change. Conventional test-time scaling generates multiple candidate answers according to a fixed sampling budget, regardless of question difficulty or current infrastructure load. The researchers measured up to a 4.1-fold increase in energy consumption for the same four-sample query as GPU contention increased. ATEST-Online monitors answer stability and current GPU conditions, learns the energy cost of additional samples, and decides when to stop. Across four evaluated datasets using Phi-3-mini on an NVIDIA A100, the method maintained competitive accuracy while respecting energy budgets. On GSM8K under high load, it achieved 60% accuracy without deferrals, compared with 44% accuracy and 42.4% deferrals for the calibrated alternative. Including offline profiling, the online approach used 42 times less GPU time and 48 times less energy in the evaluated comparison.
Why it matters: The cost of another reasoning attempt is not constant. It depends on both the expected improvement in answer quality and the current cost of computation. Adaptive reasoning budgets can account for these conditions instead of treating every additional sample as equally valuable or equally expensive.
arXiv ↗KVCompass: A Discovery Plane for Internet-Scale Prefix Cache Sharing in LLM Serving
Submitted October 16 and newly listed October 20, KVCompass investigates how inference providers can reuse previously computed key-value cache state across geographically distributed serving regions. Conventional prefix caching generally operates within individual clusters, leaving identical prompts to be processed again when requests arrive elsewhere. KVCompass introduces a discovery mechanism that identifies which workers hold reusable cached prefixes and routes requests according to cache availability, server load, and network distance. Its evaluation includes a simulated 64-worker deployment and a 14-worker testbed spanning three continents. The researchers report 1.3 to 14 times lower 99th-percentile time to first token than evaluated baselines, up to 3.7 times lower tail end-to-end latency, and up to 4.7 times higher throughput. These are experimental serving-performance results, not direct measurements of commercial API price reductions.
Why it matters: Repeated context processing can waste GPU capacity even when identical information has already been processed elsewhere. Sharing reusable cache state across regions offers another route to improving inference efficiency, although network-transfer costs, cache discovery overhead, and workload locality remain important considerations.
arXiv ↗Cache2LoRA: Understanding and Improving Context Internalization
Submitted October 16 and appearing in the October 20 listings, Cache2LoRA investigates representing document knowledge through compact model adaptations rather than retaining the complete source text in active decoding context. The method retrieves relevant evidence from a reusable frozen document cache and constructs low-rank adaptation updates that preserve information needed for answering. Across 17 evaluated tasks, Cache2LoRA achieved a macro F1 score of 0.663, approaching the 0.671 obtained with full-context in-context learning. For 32,000-token documents and 256-token outputs at batch size 16, the researchers report decoding throughput 5.9 times that of the full-context baseline. The paper also examines how well compressed representations retain facts and follow instructions when additional information intervenes. These are research results from the evaluated models and workloads, not established reductions in commercial API charges.
Why it matters: The paper explores a distinction between information a system can access and information that must remain in its active decoding context. Reusable representations may reduce repeated processing of large documents, but their economic value depends on construction costs, reuse frequency, factual fidelity, and the ability to recover relevant details when needed.
arXiv ↗Phrase of the Day
“Valuemaxxing”
Valuemaxxing is the practice of maximizing measurable business value from AI rather than maximizing token consumption, model usage, or other activity metrics.
- AI adoption
- Tokenmaxxing
- Token shock
- Tokenminimizing
- Token discipline
- Model routing
- Token yield
- Valuemaxxing
Flexera's October analysis explicitly documents the term and describes its growing relevance to enterprise IT and finance leaders. The vocabulary reflects a change in what organizations consider evidence of successful AI adoption. Early experimentation often rewarded consumption because token counts and usage statistics were readily available. As expenses increased, organizations began emphasizing smaller prompts, cheaper models, and tighter budgets. Those controls remain useful, but reducing consumption alone does not establish that a system creates value. Today's research provides a useful illustration. The inhibitory message-passing study reports lower token consumption alongside higher task accuracy, while Koi demonstrates that infrastructure optimization can lower cost per token without changing the model's underlying intelligence. Conversely, an inexpensive system that repeatedly fails or requires substantial human rework may deliver poor economic results. The emerging objective is to measure completed work, quality, latency, human effort, and total cost together. Token yield is one component of that evaluation, not a substitute for measuring actual business outcomes.
- cost per successful outcome
- quality-adjusted token yield
- task-specific model routing
- adaptive reasoning budgets
- selective context retrieval
- on-demand tool-schema loading
- deterministic workflow execution
- reusable inference caches
- agent execution limits
- departmental spending attribution
- human-plus-AI productivity measurement
- outcome-based AI governance
Using fewer tokens is useful. Getting more work done with them is better. Getting the right work done is where the money is.
Flexera ↗