Documentation
README
LLM Caching
Cut LLM costs and latency with exact match, semantic, and provider-side caching layers.
When to Use This Skill
Use this skill when:
- The same or similar queries are asked repeatedly (FAQ bots, support tools)
- LLM API costs are growing and you need immediate savings
- Serving high request volumes where repeated queries cause bottlenecks
- Implementing prompt caching for long system prompts (Anthropic/OpenAI)
- Building offline-capable AI features that need response persistence
Caching Layers
Request โ Exact Cache โ Semantic Cache โ Provider Cache โ LLM API
โ hit โ hit โ hit
instant ~5ms 50-80% cheaper
Layer 1: Exact Match Cache (Redis)
This is the opening of the README. Read the full README on GitHub.