Numbers make the case
The argument for caching becomes obvious as soon as you do the math on a real workflow. Take a 50K-token codebase review producing 8K tokens of feedback at illustrative Sonnet pricing ($3/M input, $15/M output, $0.30/M cached input).
Three scenarios
Scenario A — single shot: 50K input × $3/M + 8K output × $15/M = $0.27.
Scenario B — 10 follow-up turns, no caching: history grows each turn (~50K → ~100K), input dominates → ~$3.50 input + ~$1.20 output = ~$4.70.
Scenario C — 10 follow-up turns, with caching: stable prefix (~45K) cached, fresh input ~5K per turn → ~$0.40 input + ~$1.20 output = ~$1.60. Same conversation, 3x cheaper.
Where caching pays back fastest
Caching pays back fastest in workflows with: a large stable prefix (rules + tool schemas + corpus), many short follow-up turns, and short variable tail. Coding agents, customer-support bots, and long research chats are the canonical wins. Single-shot one-off prompts barely benefit.