Unverified50% confidenceFactExact time
According to DeepSeek's data, 96% of all input tokens hit the cache.
1
Sources
50%
Confidence
Medium-term (~90 days)
Relevance
10/21/2026
First Seen
Valid until: 1/19/2027
Sources
Related Entities
Related Claims
UnverifiedDeepSeek's cache-hit price is about one-fiftieth of the cache-miss price, and a cache hit depends on whether the beginning of the request is token-for-token identical to the previous request.70% similarUnverifiedCalculated at DeepSeek's list prices for the single-day traffic of October 16, output tokens account for only about 2% of the total but about 47% of the bill, uncached input accounts for about 42% of the bill, and cache reads, which make up 93% of input tokens, account for only about 11% of the cost.69% similarUnverifiedThe tester noted: Cursor did not report cache-write tokens, so its true token consumption is very likely higher than 92,000.67% similarUnverifiedAccording to an analysis based on real API traffic, out of about 411,000 requests over 7 days, 99.3% of processed tokens were input tokens; the median request had 3,782 input tokens and returned only 147 tokens.66% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1082055API
curl https://kongchang.com/api/v1/knowledge/claims/1082055MCP
get_claim(id=1082055)