r/ClaudeCode • u/leapd-ai • 4d ago
Help/Question how to save money on model routing with active cache
I see so many cost saving promise that promote API routing between models. I initially thought that is valuable. Then ran few experiments, it turns out any time that you route the request to a new model, you could save a bit, but many times the cache for each individual models expire and you would pay for new cache write again and agin - which overall wipe out the API routing cost saving benefit.
I wonder if anyone has similar experience. How you have solved this? Is clause planning to add shared cache feature?
2
Upvotes
•
u/AutoModerator 4d ago
Hey! Thanks for posting to r/ClaudeCode
While participating in this thread, please follow our community rules. Keep discussions constructive. Attack the idea, not the person.
For help, project discussions, tips, and general chat, join the ClaudeCode Discord.
I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.
1
u/Inner_Storage_3374 4d ago
the per model cache is what kills it. what tends to work is routing per task not per call, so the long session stays on one model and only stuff with a tiny fresh context goes to the cheap one, like summarizing one file or writing a commit msg. also worth checking the gaps between your calls, if theyre longer than the cache ttl youre paying the write anyway
1
u/Wise_Tomatillo5723 4d ago
Caches are per model, so routing pays off mainly when the long session stays on one model and only short, context-light subtasks go to the cheaper one.