Today's token-cost story is hiding in the cache line. Anthropic kept Fable 5.1's headline input and output rates unchanged but cut cache-read pricing by 75%, estimating roughly 25% lower cost for typical workloads and as much as 45% for highly agentic ones. Yuki launched granular AI-spend attribution for Snowflake Cortex, while IBM published a fresh explainer declaring that corporate tokenmaxxing has already begun to wane. The vocabulary arc is catching up with the architecture: tokenmaxxing created the appetite, tokenminimizing challenged the waste, and token yield increasingly depends on what can be routed, retrieved, and reused.
Top Developments (Last 24 Hours)
1What if the most important token price is the one nobody puts in the headline?
Anthropic released Claude Fable 5.1 on September 1 with base pricing unchanged at $10 per million input tokens and $50 per million output tokens, but cache reads fell from $1.00 to $0.25 per million tokens. Anthropic estimates the change reduces typical token-billed workloads by about 25% and highly agentic workloads by up to approximately 45%, making repeated-context economics a central part of the model's cost proposition.
Anthropic ↗2Snowflake AI spend gets attributed to the agent, user, role, and model
Yuki launched its Cortex Control Center on September 1 to break Snowflake Cortex spending down across agents, direct inference, SQL functions, search, coding tools, products, users, roles, and models. The dashboard pairs token and compute credits with latency and query volume, addressing the increasingly common problem of a single AI credit pool hiding which workflow actually caused the bill.
Yuki ↗3IBM gives tokenmaxxing the encyclopedia treatment just as companies move past it
IBM published a new tokenmaxxing explainer on September 1, defining the term as incentivizing employees to maximize AI token usage and arguing that the practice peaked in spring 2026 before beginning to wane. IBM points to usage leaderboards, unpredictable agent spending, and Goodhart's law as reasons organizations are shifting from raw consumption toward measurable productivity and ROI.
IBM ↗From Tokenmaxxing to Reusable Token Yield
Tokenmaxxing is the practice of maximizing AI 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 important wrinkle is reuse: the same nominal token can have radically different economics depending on whether the system has to process it from scratch.
Anthropic
Fable 5.1 turns cache economics into a headline product feature. Cache hits and refreshes now cost 2.5% of the base input rate, compared with the more typical 10% multiplier on other Claude models. Long-running agents that repeatedly revisit stable system prompts, conversation history, documents, or tool instructions therefore benefit much more than one-shot workloads.
Anthropic Pricing ↗Tokenando
Tokenando's September pricing tracker now covers 682 models across 66 providers and reports a median blended price of about $0.80 per million tokens under its 70/30 input-output weighting. The tracked range stretches from effectively free models to hundreds of dollars per million tokens, giving modelmaxxing an enormous price surface to exploit.
Tokenando ↗Bargo
Bargo's Token Demand Index reports 65.2 trillion tracked inference tokens per week as of August 31, up 22% over 30 days, with open-weight models carrying 79.3% of tracked volume. Its demand-weighted effective price sits near $0.78 per million tokens, reinforcing the pattern that cheaper inference is expanding consumption rather than simply shrinking total demand.
Bargo ↗Anthropic
Anthropic's retrieval-based tool discovery remains a primary reference for tool-surface bloat. Rather than loading every available tool definition into the model context upfront, relevant schemas can be retrieved on demand. Anthropic reports an 85% token reduction in its evaluation while preserving access to the complete tool library.
Anthropic Engineering ↗Alibaba Cloud
Alibaba Cloud's current DataWorks pricing shows how sharply non-US model economics can vary by model and region. In US regions it lists DeepSeek V4 Flash at roughly $0.168 per million input tokens and $0.336 per million output tokens, compared with $1.98 and $3.96 for V4 Pro, making capability-tier routing a first-order cost decision.
Alibaba Cloud ↗Research Watch
CacheRouter: Tool Discovery Without Sacrificing Prompt Caching
CacheRouter studies a collision between two popular optimizations. Dynamically shrinking the visible tool set saves schema tokens, but changing that prefix can destroy prompt-cache reuse. Its dual-path design keeps a stable core tool surface while discovering long-tail tools separately, producing token-level cache-hit rates above 90% in prototype experiments.
Why it matters: Tokenminimizing can make the bill worse when it destroys cheaper reusable context. Tool-surface optimization therefore has to balance resident token count against cache stability rather than optimizing either number alone.
arXiv ↗ReCache: Efficient KV Cache Reuse and Compression for Tool-Augmented LLM Agents
ReCache independently caches recurring tool and skill representations so they remain reusable even when resources appear in different combinations or orders. Across seven public tool and skill datasets, its resource-wise attention produced a 3.655 times time-to-first-token speedup while the full system reduced allocated KV-tensor memory by 92.43%.
Why it matters: Tool-surface cost exists below visible prompt tokens. Preserving reusable inference state can make broad agent capability cheaper without repeatedly rebuilding every tool representation.
arXiv ↗One Model, Many Minds: Replacing Multi-Agent Chatter with Mixture of Roles
This late-August arXiv paper replaces repeated text communication among multiple agents with dynamically combined latent roles inside one model invocation. Across its reported reasoning and personality evaluations, the approach matched multi-agent-system performance while reducing token cost by 20 times.
Why it matters: Agent-to-agent conversation can become its own token bill. If useful specialization can be preserved without repeatedly serializing reasoning into text, coordination becomes a major new tokenminimizing surface.
arXiv ↗Token Reduction Is Not Cost Reduction
This provider-billed study analyzed 2,848 coding-agent runs across 103 tasks, seven repositories, and three models. Prompt-cache traffic accounted for about 80% of the actual bill, while one compression configuration removed 38.4% of estimated tool-output tokens but increased paired billed cost by 6.8%.
Why it matters: The paper puts a hard boundary around simplistic tokenminimizing. Fewer tokens are economically useful only when caching, retries, trajectory length, and task success still produce a lower final bill.
arXiv ↗Phrase of the Day
“Tokenmaxxing”
Tokenmaxxing is the organizational practice of encouraging or rewarding maximum AI token consumption as a proxy for AI adoption, experimentation, or productivity.
- AI adoption
- Tokenmaxxing
- Token shock
- Tokenminimizing
- Modelmaxxing
- Token discipline
- Token efficiency
- Token yield
The likely winners are organizations that keep the experimentation tokenmaxxing encouraged while replacing raw consumption targets with routing, caching, budgets, selective context, and outcome measurement.
- AI FinOps teams
- model routers
- AI gateways
- agent budget controls
- cache-aware inference systems
- retrieval-based tool loading
- outcome-linked observability
Tokenmaxxing may have taught companies to use the machine. The invoice is teaching them how to use it well.
IBM ↗The jCodeMunch read
Today's cache and tool-surface findings reinforce a useful distinction between making context unavailable and making it available only when needed. jCodeMunch reduces code-reading tokens through tree-sitter symbol retrieval and byte-precise context, keeping relevant code evidence accessible without making repository-scale context the default.
See how the 95%+ cut is measured → ← All editions