Unverified50% confidenceSolutionExact time
Modifying the system prompt to adjust effort invalidates the prompt cache; the official recommendation is to control effort via API parameters rather than prompt text in order to maintain cache validity.
1
Sources
50%
Confidence
Medium-term (~90 days)
Relevance
10/7/2026
First Seen
Valid until: 1/5/2027
Sources
Related Entities
Related Claims
UnverifiedWhen the API is unavailable, applications should implement graceful degradation by returning cached results, prompting users to retry, or switching to a fallback solution, rather than crashing directly70% similarUnverifiedPrefix caching is extremely sensitive to input stability; as long as any single token in the prefix is modified or inserted, the cache is invalidated and all subsequent content must be recomputed.67% similarUnverifiedIn the cache reuse mechanism, once the request prefix is modified, the cache for all content after it becomes invalid; modifying tools or other parts of the request will still affect reuse.67% similarUnverifiedSwitching the tokenizer causes existing Prompt Caching caches to become completely invalid, reducing the cache hit rate to zero.66% similarUnverifiedAPI Keys are designed with no concept of expiration and remain valid long-term once generated; whereas tokens have an expiration time and require re-login to obtain after expiry.65% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/984220API
curl https://kongchang.com/api/v1/knowledge/claims/984220MCP
get_claim(id=984220)