
Anthropic's automatic caching billed us $0.022 per turn for the same 8,400 tokens that cost $0.003 once we placed the cache marker by hand Automatic caching means one switch, and the system decides what to save. Manual caching means you mark the exact block yourself, so nothing varying ever poisons the entry. That single difference explains the whole gap, and our meter confirmed it across every repeat. So we wrote down every trick that moved the bill, and each one ships with code you can paste. Every figure below comes from our own runs > Mark the stable prefix > Buy minutes, not hours > Read the usage meter > Batch the night shift Then come the two that need explaining. Split planner from executor across two sessions. Cap thinking before it eats its own output. Our mid-thread model switch billed $0.197 with zero hits. The two-session version read its cache for $0.011, which means the second prefix never charged twice. Anthropic's docs describe all six features. Our meter readings show what each one actually saves. The full tutorial walks through every trick with Python and cURL. Full breakdown ↓↓

Argues manual cache-breakpoint placement and splitting planner from executor across sessions can cut prompt-caching cost roughly 7x versus relying on Claude's automatic caching alone, a concrete lever for repeated-large- workloads.
“Anthropic's automatic caching billed us $0.022 per turn for the same 8,400 tokens that cost $0.003 once we placed the cache marker by hand”
“Automatic caching means one switch, and the system decides what to save.”
“Our mid-thread model switch billed $0.197 with zero hits.”
“The two-session version read its cache for $0.011, which means the second prefix never charged twice.”
Checking sign-in…
Loading comments…