Unverified50% confidenceDecision RuleExact time
If cached tokens are always zero, first check and fix the prompt prefix, because any dynamic content in the prefix invalidates implicit caching; one tester saw a broken prefix inflate costs more than sixfold.
1
Sources
50%
Confidence
Long-term
Relevance
10/18/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedWhen the Vary header references a high-cardinality field such as User-Agent, cache effectiveness can be completely destroyed, with the cache hit rate approaching zero.71% similarUnverifiedIn bias mode, reskSecure applies a negative penalty value (such as -5.0) to tokens matching violating phrases, reducing but not eliminating the probability of the violating phrase appearing.71% similarUnverifiedPrompt caching requires an exact token sequence match as a prerequisite; any change at any position in the prefix invalidates the cache, and all tokens from that changed position onward must be recomputed.70% similarUnverifiedPrefix caching is highly sensitive to the order of context concatenation; if dynamic content is inserted at the head of the message list with every request, the cache hit rate will plummet to zero.70% similarUnverifiedThe cached input mechanism skips repeated inference computation by reusing the KV cache for identical prefix content, with cache-hit tokens billed at a lower price.69% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1059530API
curl https://kongchang.com/api/v1/knowledge/claims/1059530MCP
get_claim(id=1059530)