Unverified50% confidenceFactExact time
The cache-hit price is about fifty times different from the input price on a miss; in long-context, multi-turn Agent workflows, the vast majority of tokens can reuse the cache, greatly compressing costs.
1
Sources
50%
Confidence
Medium-term (~90 days)
Relevance
10/18/2026
First Seen
Valid until: 1/16/2027
Sources
Related Entities
Related Claims
UnverifiedThe higher the cache hit rate, the closer the actual billing is to the cache price rather than the full input price, which can reduce costs by an order of magnitude.78% 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.76% similarUnverifiedIn agentic scenarios where system prompts run to thousands of tokens, if more than 90% of requests hit the cache, the effective input cost per request may be only 5%–10% of the listed price.76% similarVerifiedToken billing is calculated based on the total volume of input and output; the longer a conversation, the more each call pays for an increasingly bloated history.75% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1061738API
curl https://kongchang.com/api/v1/knowledge/claims/1061738MCP
get_claim(id=1061738)