The economics of AI are becoming clearer at both ends of the business. A November 2 analysis of Anthropic's IPO filing shows that compute and infrastructure expenses fell from 251% of revenue in early 2025 to 48% in the second quarter of 2026, even as the absolute compute bill continued climbing. Meanwhile, Reuters reports that SAP is replacing expensive models with cheaper alternatives when performance permits, and major banks are using smaller models and intelligent routing to control inference expenditure. A new enterprise survey finds that 89% of organizations have scaled back or redesigned AI plans because of token costs. Research published October 30 points toward the next efficiency gains: transferring cached context between models, intelligently managing agent prefix caches, and scheduling inference without expensive prediction models. The emerging picture is less about buying the cheapest tokens and more about eliminating unnecessary computation while preserving the value of completed work.
Top Developments (October 28 to November 2)
1How did Anthropic cut compute costs from 251% to 48% of revenue?
A November 2 analysis by FourWeekMBA examines Anthropic's October 26 Form S-1 and finds a dramatic improvement in the company's compute economics. Anthropic reported $5.558 billion in compute and infrastructure expenses during the second quarter of 2026, representing approximately 48% of quarterly revenue. In the first quarter of 2025, the corresponding ratio was 251%. Revenue grew faster than infrastructure expenditure, but the absolute compute bill increased substantially. Anthropic spent $8.945 billion on compute and infrastructure during the first half of 2026. The filing also disclosed approximately $265.6 billion in future fixed or minimum compute commitments as of June 30, with additional agreements signed afterward. These figures combine training, inference, and infrastructure expenses rather than isolating the cost of generating customer tokens. The improvement demonstrates stronger revenue generation relative to computing expenditure, not a comparable reduction in the physical cost of inference. Anthropic also faces substantial contractual obligations that will require continued demand growth and efficient infrastructure utilization.
FourWeekMBA ↗2SAP replaces expensive AI models with cheaper alternatives while targeting €2 billion in efficiency gains
Reuters reported October 28 that SAP is replacing expensive AI models with lower-cost alternatives when those alternatives meet its performance requirements. CFO Dominik Asam said SAP uses more than 70 models from providers including OpenAI, Anthropic, and Google. The company increasingly selects the least expensive model capable of completing each task to the required standard. SAP expects the approach to contribute toward more than €2 billion in AI-driven efficiency gains, although that figure should not be interpreted as savings attributable exclusively to model substitution. SAP expects total AI expenditure to continue increasing as adoption expands. Its commercial model makes inference efficiency especially important because customers pay for completed tasks rather than the underlying computing resources. Lower execution costs can therefore improve margins without requiring lower customer prices. Reuters also reports that customers in regulated industries increasingly restrict model selection according to geographic origin and data requirements, adding compliance considerations to cost routing.
Reuters ↗3Bank of America and Capital One demonstrate why smaller models belong in enterprise AI
Banking Dive reported October 29 that Bank of America and Capital One are using smaller models to improve the economics of enterprise AI. Bank of America's technology chief Hari Gopalkrishnan described Orchestra, an internal routing layer that uses a small classifier to select financially appropriate models for different requests. The bank plans to double its AI budget in 2027 while avoiding unnecessary dependence on expensive frontier models. Capital One's chief enterprise AI officer Prem Natarajan described distilling open-weight models into smaller, specialized models for its Chat Concierge application. According to Natarajan, the approach reduced latency fivefold and increased dealership customer engagement by 50%. These are company-reported outcomes rather than independently verified benchmarks. Bank of America also emphasized agent guardrails that restrict execution time and autonomous task scope. The examples demonstrate that model routing, specialization, and execution controls can support greater AI adoption without assigning the most expensive available model to every operation.
Banking Dive ↗4Enterprise survey finds 89% have scaled back or redesigned AI plans over token costs
ITPro reported October 28 that Cloudera's State of Enterprise AI 2026 survey found 89% of responding organizations had scaled back or redesigned AI plans because of token costs. Another 45% reported moving workloads in response to cost volatility. Although 55% increased AI investment, only 23% said their initiatives generated more value than they cost. Some 58% reported approximately equivalent value and expenditure, while 27% reported little or no measurable business impact. Cost visibility remains incomplete: 90% said they could measure end-to-end AI costs at least somewhat accurately, but only 27% expressed strong confidence in that measurement. These are survey findings, not an independent audit of corporate AI expenditure. The report illustrates a growing distinction between AI adoption and economically sustainable deployment. Organizations are increasingly revisiting model selection, infrastructure placement, and FinOps controls rather than assuming that declining advertised token prices will automatically produce lower bills.
ITPro ↗Cheaper Tokens, Smarter Routing, and the Cost of Context
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 useful results. Token yield measures useful completed work relative to the tokens consumed. The progression from tokenmaxxing through tokenminimizing toward token yield is increasingly reflected in enterprise purchasing and engineering decisions. Today's evidence also highlights a distinction between lower prices, lower consumption, and better financial returns. Those outcomes can reinforce one another, but none guarantees the others. Searches did not establish meaningful fresh adoption of tokenminning, tokenmining, or modelmaxxing as distinct new terminology.
Axios
Axios reported October 28 that OpenAI's GPT-6.1 Terra model was introduced at up to half the per-token price of its predecessor. The article also cites Ramp's corporate-spending-based token price index, which reached approximately $0.59 per million tokens during the preceding week, roughly 35% below its late-June level. Ramp's index reflects observed corporate spending across selected providers rather than a universal API list price. Axios identifies an important tension: falling prices can encourage greater token consumption while simultaneously reducing the revenue generated by each unit of usage. Investors are therefore watching total expenditure and provider revenue, not simply token volumes. Strong adoption does not automatically establish that infrastructure investments will earn adequate returns.
Axios ↗Cloudflare
Cloudflare's enterprise MCP reference architecture provides a concrete example of tool-surface optimization. In its internal deployment, four MCP servers exposed 52 tools requiring approximately 9,400 context tokens for their definitions. Cloudflare's Code Mode approach replaced those definitions with two discovery and execution tools requiring approximately 600 tokens, a reported 94% reduction in initial schema footprint. The architecture also incorporates an AI gateway for model selection and employee token-budget enforcement. These are Cloudflare's own implementation measurements, not independently verified reductions across complete agent sessions. The approach is especially relevant to large enterprise tool catalogs because initial schema loading can consume context before an agent performs any useful task. Its effectiveness depends on reliable tool discovery, secure execution, and avoiding unnecessary intermediate output.
Cloudflare Blog ↗OpenAI Developer Documentation
OpenAI's tool-search documentation recommends deferring large function and MCP schemas until an agent actually needs them. Rather than loading an entire catalog, the model can search available namespaces or MCP servers and import relevant definitions during execution. OpenAI recommends grouping tools into clearly described namespaces, generally containing fewer than ten functions, to improve discovery and reduce unnecessary context. The documentation also emphasizes preserving prompt-cache continuity by appending newly discovered definitions rather than repeatedly changing existing context. This is established functionality rather than a November 2 product announcement. The architectural tradeoff remains important: deferred loading reduces initial token consumption but introduces discovery operations that can affect latency and accuracy. Developers should compare complete task costs and successful outcomes rather than relying exclusively on schema-token reductions.
OpenAI Developer Documentation ↗Gartner
Gartner's August 17 forecast remains an important framework for interpreting the latest enterprise spending reports. The research firm predicts that inference costs per agentic workflow will increase more than fivefold through 2028, despite improvements in the cost of individual tokens. Gartner calls this the Inference Paradox: cheaper unit computation enables more complex workflows that consume substantially greater resources. The firm estimates that routing a task through an agentic reasoning model increases provider inference costs by at least five times compared with a basic chatbot interaction, often more for complex tasks. These are forecasts and modeled comparisons, not measurements of every production deployment. The implication is that organizations need model tiering, execution limits, caching, and workflow-level accounting. Falling token prices alone cannot establish whether an autonomous application will become less expensive to operate.
Gartner ↗Research Watch
HiState: Hierarchical Prefix Cache Management for Hybrid LLM Serving in Agentic Workloads
Submitted October 30, HiState addresses prefix-cache management for hybrid language models combining attention and recurrent layers. Agent workflows frequently revisit earlier context, but conventional cache policies may discard the checkpoints required to reuse that computation. HiState stores historical recurrent checkpoints on SSD while prioritizing key-value cache entries in faster memory. Adaptive checkpoint intervals and coordinated eviction policies balance storage overhead against repeated computation. Evaluated using public coding-agent traces, the system achieved up to 5.73 times faster 99th-percentile time to first token than vLLM-Marconi and up to 5.44 times faster than SGLang-HiCache.
Why it matters: Long-running agents repeatedly revisit accumulated context. Better cache management can reduce expensive recomputation without requiring agents to shorten every conversation. The reported improvements concern tail latency in the evaluated serving configurations, not guaranteed reductions in commercial API bills.
arXiv ↗ACCT: Asymmetric Cross-LLM Context Transfer
Submitted October 30, ACCT investigates transferring cached context between language models of different sizes within the same model family. Conventional model routing can require the destination model to process the entire prompt again, erasing some of the savings from switching to a cheaper model. ACCT transforms a source model's key-value cache into sparse states usable by the destination model. Its components identify relevant context tokens, allocate cache capacity, and compile the transferred representation. Across the evaluated benchmarks, the researchers report comparable or better task performance while reducing KV-cache size by 75%. At approximately 19,000 context tokens, cache conversion was 6.5 to 21.2 times faster than reprocessing the context with the destination model.
Why it matters: Model routing is less economical when every switch requires another full-context prefill. Cross-model cache transfer could make dynamic routing more attractive for long agent sessions. The technique remains limited to compatible model families and the evaluated experimental configurations.
arXiv ↗LEAP: Efficient LLM Inference Scheduling with Generalizable Length Prediction
Submitted October 30, LEAP improves inference scheduling by predicting response lengths using information already generated during model prefill. Conventional length predictors can require substantial additional computation and perform poorly when workloads change. LEAP extracts a lightweight signal from the serving model's hidden states and updates its predictions asynchronously on the CPU. In the researchers' experiments, LEAP reduced average per-token latency by 15.9% to 40.8% relative to evaluated length-prediction baselines. It also achieved 1.9% higher throughput while using approximately 30,569 times fewer predictor parameters than the strongest compared baseline.
Why it matters: An optimization system can become expensive enough to undermine the efficiency it was designed to create. LEAP demonstrates that useful scheduling decisions may be extracted from existing model computation rather than requiring another substantial model. The results are workload-specific latency and throughput measurements.
arXiv ↗Trainable Vector Quantization for Large Language Models
Submitted October 30, this paper introduces a trainable approach to vector quantization intended to reduce language-model memory requirements while preserving quality. Extreme low-bit quantization can substantially reduce model size but often damages accuracy. The researchers use trainable latent weights and knowledge distillation to improve compressed models after quantization. Their experiments demonstrate compatibility with existing vector-quantization methods and report near-lossless two-bit quantization of LLaMA2-70B, with approximately a one-percentage-point accuracy reduction on selected question-answering benchmarks. The study does not establish a universal inference-cost reduction across models or hardware platforms.
Why it matters: Memory requirements remain an important constraint on economical inference, particularly for self-hosted and smaller-scale deployments. Better low-bit compression can expand hardware options, but real savings depend on execution speed, supported kernels, model quality, and the cost of producing the compressed model.
arXiv ↗Phrase of the Day
“Return on token spend”
Return on token spend is a measure of useful work produced per dollar of attributable AI expenditure. Weave Index uses the expression for its engineering-productivity metric, which compares estimated expert engineering effort associated with merged code changes against observed AI tool spending. The concept provides a useful counterweight to both unrestricted token consumption and indiscriminate spending caps.
- AI adoption
- Tokenmaxxing
- Token shock
- Tokenminimizing
- Token discipline
- Token yield
- Return on token spend
- Cost per successful task
- Verified business value
The latest enterprise findings demonstrate why token expenditure cannot be evaluated independently of completed work. SAP expects to improve profitability by selecting less expensive models for tasks that do not require frontier capabilities. Bank of America uses model routing while planning to increase its overall AI investment. Capital One reports improvements in latency and customer engagement from smaller specialized models. Anthropic's financial disclosures demonstrate that compute expenditure can rise substantially while becoming a smaller proportion of revenue. Each example separates the quantity of computation purchased from the value generated by that computation. Weave Index attempts to measure this relationship directly. Its October 7 snapshot reports 0.106448 estimated expert engineering hours per dollar of attributable AI spending for September 2026. The metric covers engineers with both observed spending and merged code output. It does not measure actual employee hours saved, establish causation, or represent every engineering organization. Nevertheless, the methodology points toward a more useful approach to AI financial management. Organizations can compare complete workflow costs with accepted results, track the effect of model routing and retrieval improvements, and distinguish productive additional computation from unnecessary repetition. The objective is not to maximize tokens or minimize them without regard to quality. It is to understand what the expenditure accomplishes.
- accepted engineering output
- cost per completed workflow
- quality-adjusted token efficiency
- verified task success
- model routing with measured outcomes
- reduced redundant context processing
- cache-preserving execution
- lower retry expenditure
- attributable AI spending
- measurable business productivity
- sustainable inference margins
- useful work per dollar
The cheapest token is not necessarily the best bargain. The one that helps finish the job has a stronger case.
Weave Index ↗