Your Cut List Is Now Your Roadmap — But Naive Routing Will Eat the Savings
The Cache Trap Nobody Priced In
Routing easy calls to cheap models backfires in production. Prompt caching gives ~90% discounts on previously-seen input, but caches are model-specific: route call #3 of a five-step agent task to a different model and you re-bill the full context at cold rates. Result: a cache-hot expensive model can cost less than a cache-cold cheap one. Optimize at the session level, not the call level.
The converging production pattern: a guardrail filter, a 1.5B-parameter router (Arch-Router, trained on human preference data), a cost/speed policy, and session pinning that locks the winning model to the whole task. Open-source Plano (Katanemo) cut costs 2x on the Hermes agent benchmark with zero agent code changes, via YAML config. At $50K/mo inference spend, that's $25K back without engineering cycles.
Where the Sources Converge
Three independent analyses agree: OpenAI's Sol/Terra/Luna tiering is an explicit routing blueprint — Terra delivers GPT-5.5-level performance at $2.50/$15, half the cost, and without routing you overpay 3-5x on ~80% of calls. A second analysis warns per-call routing raises costs via cache misses. Synthesis: routing is table stakes; only session-pinned routing captures the savings. And quality no longer trades off against efficiency — GPT-5.6 Sol scores 80.0 on the Coding Agent Index vs Claude Fable 5's 77.2, using under half the tokens at a third the cost.
Caveat: the window is symmetric — your competitors' cut lists just became viable too. Advantage goes to whoever re-runs unit economics and ships first.
A cache-hot expensive model can cost less than a cache-cold cheap one — optimize AI costs per session, not per call.
What to do
Rescore every backlog feature previously cut for unit economics using cost-per-completed-task at Luna/Terra/Grok pricing by end of week
Prototype session-pinned model routing this sprint — evaluate Plano against your current single-provider integration and instrument per-request cost visibility