Mission Control · API bay · §4.3
Cache Hit Rate Monitor
Live telemetry from the Anthropic Admin API. See your cache-hit rate per day, the dollars cached reads are saving, and whether your cache_control strategy is improving over time.
Free · bring your own key
Sign in to see your cache telemetry
This monitor reads your own org's usage report via your Anthropic key (BYOK) — your data, your key, never ours.
Sign inWhat you're looking at
Cache hit rate = cache_read / (cache_read + uncached_input). Above 60% means your cache_control strategy is paying off. Below 20% usually means you're writing caches that never get re-read.
Dollar savings assume a 90% discount on cache reads (Anthropic's standard cache_read multiplier of 0.10). At Sonnet 4.6 input rates that's ~$2.70 saved per million cached tokens.
Trend ratio compares the recent half of the window to the earlier half. > 1.0 = improving; < 1.0 = degrading. Drops past a 0.8 ratio are worth investigating — a downstream system probably changed its prompt prefix.
This view aggregates ALL traffic on the org key — your dev calls, your production calls, every team member sharing the org. If the org has multiple teams, the rate is mixed across them.