Unverified50% confidenceFactExact time
For agents continuously operating on the same codebase, cache reads can account for 70%–90% of total token consumption, making them the decisive factor in real costs.
1
Sources
50%
Confidence
Long-term
Relevance
10/2/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedFor applications that heavily rely on context reuse, the $0.10 cached read price is the primary source of cost savings.74% similarUnverifiedUnder the cache-hit billing mechanism, the portion that hits the cache is billed at a lower price; in Agent scenarios the cache hit rate is often as high as 90% or above, and the cache price has a far greater impact on the actual costs of heavy Agent users than the nominal input unit price.73% similarUnverifiedContext caching mechanisms can reduce API costs by 60%–80% for enterprise applications that repeatedly query the same knowledge base, with some providers offering cache-hit token discounts as high as 90%.72% similarUnverifiedThe Prompt Caching mechanism can typically save 50%–90% of input costs.71% similarUnverifiedIn agentic coding work, the proportion of cache reads in total cost is under 5% in Fable, close to 20% in Opus, and potentially over 50% in Sonnet 5.5.71% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/967371API
curl https://kongchang.com/api/v1/knowledge/claims/967371MCP
get_claim(id=967371)