Skip to main content

Stop Paying Twice

Every time a user asks “What’s the capital of France?” you pay for a new API call. With Raptor’s semantic cache, you pay once.

How It Works

Unlike traditional caches, we don’t require exact text matches: All return the same cached response. That’s 75% fewer API calls just from query variations.

Typical Savings

Response Headers

Check cache status in every response:

Streaming Support

Cache hits work with streaming too. We replay cached responses with realistic timing (~15ms between words) so users still see the “typing” effect.

Cache Behavior

Best Practices

  1. Normalize inputs - Remove extra whitespace, lowercase when possible
  2. Use specific system prompts - Helps cache recognize similar queries
  3. Monitor hit rates - Check your dashboard for optimization opportunities
Your first request is always a cache miss. Test with realistic query patterns to see actual savings.