Unverified50% confidenceFactExact time
Setting a TTL counts as one Advanced Operation per started 60 days, on top of the write operation; a 7-day TTL counts once, and the 730-day cap counts as 13.
1
Sources
50%
Confidence
Medium-term (~90 days)
Relevance
11/17/2026
First Seen
Valid until: 2/15/2027
Sources
Related Entities
Related Claims
UnverifiedVercel Blob added a TTL feature, allowing an expiration period (1 to 730 days) to be specified at write time via the ttlDays parameter, after which the system deletes it automatically.76% similarVerifiedThe cache is not permanently valid; providers usually have a TTL of a few minutes to an hour, and the hit rate fluctuates with user behavior.75% similarUnverifiedIdempotency records typically set a TTL of 24 hours to 7 days to align with the bank reconciliation window; a retry after the key expires will execute the payment again, and the mitigation is dual-layer storage (hot storage in Redis + cold storage in an immutable ledger).75% similarUnverifiedThe article recommends setting the TTL of the idempotency key to 2–3 times the duration of a single complete agent execution.73% similarUnverifiedAnthropic's prompt caching lives for about five minutes by default (TTL), each hit refreshes the timer, and the cache expires if there is no request beyond its lifetime.73% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1181361API
curl https://kongchang.com/api/v1/knowledge/claims/1181361MCP
get_claim(id=1181361)