Unverified50% confidenceFactExact time
In this audit sample, 66% of the cost came from cache reads, 99% of input-side tokens were cache hits, while output (including thinking) accounted for only 12%.
1
Sources
50%
Confidence
Long-term
Relevance
10/16/2026
First Seen
Sources
Related Entities
Related Claims
VerifiedThe cost of cache reads should, by industry convention, be approximately one-tenth that of regular input tokens.77% similarUnverifiedUnder the API billing model, about 65% of the equivalent bill comes from cache reads.76% similarUnverifiedThe author has a spending dashboard that can show that 63% of the context is bash output and that a single web search consumes 27,000 characters, but it never showed that one third of the spending went to buying back one's own mistakes.75% similarUnverifiedIn the session assumed by the article, a gateway labeled "50% off" but with cache reads at only a 20% discount and cache writes at full price actually gives a 28% discount, costing $12.13.75% similarUnverifiedIn a typical agentic coding session, cache pricing (cache reads + cache writes) together accounts for about 56% of the bill, while input and output account for only about 44%.74% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1047781API
curl https://kongchang.com/api/v1/knowledge/claims/1047781MCP
get_claim(id=1047781)