Glossary · term193 of 202
TTL
The time a cached prompt stays valid before it expires and must be rewritten at full cost. Shortening it turns yesterday's cheap cache reads into today's expensive cache writes.
also written as cache lifetime · time to live
Related terms
cache readA token served from a prior prompt's cached context instead of being processed fresh, billed at a fraction of the base input price. Most tokens in a long agent session are cache reads, not new context.view termcache writeThe cost of storing a prompt's context so later requests can read it from cache instead of reprocessing it. Billed above base input price, with the rate depending on how long the write stays valid.view term
At a glance
- cited by
- 6 posts
- categories
- 4
- first used
- apr 2026
Claude Code vs Codex Limits, Measured in the Same UnitClaude Code vs Codex limits, measured across 28 days and 56.8 billion tokens. Why token counts cannot predict quota burn, and what to read on each side instead.
Perplexity Isn't Shutting Down. Its Citation Corpus Might ShrinkNo, Perplexity is not down. The lawsuits threaten which sources it can read, so plan for a thinner citation set inside a healthy 200, and detect it in code.
Ways to Make the Most Out of Claude Fable 5 (2026)Get more from Claude Fable 5: pick the right effort level, plan with Fable while cheaper models implement, and claw back costs with caching and batching.
Stop Treating localStorage Like a Database (It Will Bite You in Production)localStorage has a 5-10MB limit, throws QuotaExceededError silently, and vanishes in Safari private browsing. Here are the five ways it breaks in production and what to use instead.
Next.js 16 Cache Components: The Feature Nobody Understands YetNext.js 16 cache components replace unstable_cache with the use cache directive, cacheLife, and cacheTag. A clear walkthrough of what changed, why it matters, and how to migrate.
Claude Usage Limits Are a Bigger Problem Than Anthropic AdmitsClaude usage limits burned $200 plans in 19 minutes. Zero published quotas, peak-hour rationing, and opacity are driving developers away from Anthropic.