PointFive Research Finds Cutting AI Tokens Can Actually Increase Costs
Benchmarking across nearly 3,000 coding sessions, report finds ~80% of the AI bill is spent re-sending cached context, not generating answers
NEW YORK, Aug. 6, 2026 /PRNewswire/ -- New research from AI Efficiency OS company PointFive challenges a common assumption about AI cost management: that using fewer tokens automatically means spending less. An empirical study titled Token Reduction Is Not Cost Reduction charts the path toward more strategic AI budget allocation and use at scale. The study reviewed 2,908 paid coding sessions and found that reducing tool-output tokens by 38.4% actually increased billed costs by 6.8%, highlighting the disconnect between token consumption and the true cost of AI workloads.
Managing the cost of AI is the top forward-looking priority in the FinOps Foundation's 2026 State of FinOps survey. According to McKinsey's July 2026 Enterprise AI FinOps Survey, 93% of companies have exceeded their AI budgets while only 26% of companies have real-time visibility into the cost of running AI (KPMG). PointFive's report sheds light on what is happening between AI usage visibility and budget expenditure and why the most logical attempt at reducing AI costs – using fewer tokens – is failing.
"AI efficiency is a brand-new field, and most teams are making cost decisions without evidence," said Alon Arvatz, CEO of PointFive. "We did this research to understand how AI workloads actually behave, whether in the cloud or in the coding agent, and how we can bring those efficiencies to our customers. This is the first of many research reports we will publish. Research-backed evidence is how we build our product, and we look forward to sharing more discoveries."
Proper AI Measurement
PointFive's report spanned across 2,908 paid coding sessions, and incorporated 103 specific software tasks, using seven open-source repositories and tested against three models. The study produced surprising findings:
- About 80% of the actual AI bill was prompt-cache traffic – the instructions, tool definitions and context repeatedly sent to models – rather than newly generated AI responses. AI systems are spending far more money on feeding AI instructions and context rather than on producing the answers.
- Reducing tool-output tokens by 38.4% resulted in a 6.8% increase in billed costs, finding little correlation between token reduction and reduced spend. The reduction was achieved by keeping only task-relevant context, not by blind truncation, and it still cost more.
- Headroom, a widely used open-source third-party tool, increased AI costs by nearly 50% while showing no measurable improvement in task success.
Why Cutting Prompts Raises – Not Saves – the AI Bill
The study identifies two ways that efforts to reduce token use can backfire:
- AI is repeatedly paying to reread information it already has. First, AI coding agents repeatedly send instructions, tool definitions and context as they work, meaning a large share of billed input tokens can come from information that is not new. Across the sessions analyzed, only 1.3% of the bill was text the model was seeing for the first time, while nearly 80% was repeated instructions, tool definitions and contextual information. So even if you compress the text, you're only reducing a tiny portion of the overall bill.
- Aggressively removing context can force an agent to spend additional steps finding information it previously had available. The saving comes back as a larger bill.
The Path to Lower AI Costs: Visibility, Not Compression
The study points engineering leaders toward visibility and governance, not prompt compression, as the path to controlling AI costs. McKinsey research found that:
- 20% to 30% of AI spend is entirely unaccounted for, while
- Less than a quarter (20%-25%) of companies have mature AI cost-management practices
- Organizations that are thoughtful in their AI consumption effectively save 20% to 30% of their AI cost by improving visibility, tracking usage, setting accountability, and identifying waste
Costs are driven by how sessions unfold, the retries, re-reading and extra loops, and those stay invisible without per-team reporting, budgets and policy.
The benchmark is open source
The full paper, Token Reduction Is Not Cost Reduction, is a free download on arXiv (arxiv.org/abs/2607.12161), and the AI Efficiency Benchmark behind it is open source at github.com/PointFiveLabs/ai-efficiency-benchmark, so any savings claim, including PointFive's own, can be run through it. For more information, read the paper, download the field guide, or read the launch blog at pointfive.co. Further research in the series will follow, published the same way.
Methodology
The study was authored at PointFive and evaluates the company's own experimental build, an unmodified open-source compressor, alongside Headroom, a third-party tool. It is not independent research. Method, per-session data and limitations are published in full. Every cost figure was read from the actual provider bill rather than estimated from a token counter.
About PointFive
PointFive is the AI Efficiency OS, from the cloud to coding agents. It continuously improves efficiency across cloud infrastructure, data platforms, AI workloads, and coding agents, helping teams understand spend in plain language and ship optimizations at scale. Organizations like Fanatics, H&M, Hertz, Nubank, Citizens Bank and other Fortune 500 companies trust PointFive to create greater transparency into AI spend to uncover opportunities to maximize AI ROI. Learn more at https://pointfive.co.
Media contact:
+1 (339) 242-0393
SOURCE PointFive
Share this article