Caching & Dedup

Caching & Deduplication

Identical content verified within a 5-minute window returns the cached result instantly, no LLM call, no latency, no cost.

Info

Cached responses include "cached": true in the response body so you can distinguish them from fresh verifications.

How It Works

1. Content is hashed with SHA-256 on arrival
2. The hash is checked against a per-workspace Redis cache
3. If a match is found within the 5-minute TTL, the cached result is returned with a fresh verification_id
4. If no match, the full verification pipeline runs and the result is cached