Expired50% confidenceFactExact time
The optimization of reducing the cache from 1 hour to 5 minutes does not apply, because under the subscription model 1 hour is already the default.
1
Sources
50%
Confidence
Short-term (~14 days)
Relevance
10/13/2026
First Seen
This claim has expired. It is kept for the record and no longer describes the current state.
Valid until: 10/27/2026(expired)
Sources
Related Entities
Related Claims
UnverifiedCache entries have a validity period of approximately 5 minutes (default) to 1 hour (extendable), after which they are treated as cache misses.79% similarUnverifiedThe wrap-up quota cannot help users bypass the core five-hour limit, nor does it grant more time because a task is more complex.74% similarUnverifiedPrompt cache validity typically ranges from only a few minutes to several hours, and discount rates and cache windows may be adjusted at any time.73% similarUnverifiedThe cache TTL for the subscription version can stay warm for one hour, while the API call mode defaults to expiring after five minutes.72% similarUnverifiedMainstream large model API providers typically maintain prompt caches in units of 5 minutes to 1 hour, after which they expire.69% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1018424API
curl https://kongchang.com/api/v1/knowledge/claims/1018424MCP
get_claim(id=1018424)