AI Gateway now shows where a session’s cache and spending went.
Inspect session-level routing and cache reuse before increasing the model budget.
Understand the changes. Choose the tools. Put AI to work.
NO FEED / Topics
Pricing, caching, usage and the cost of an accepted result.
22 results
Inspect session-level routing and cache reuse before increasing the model budget.
A developer chose cheaper models for delegated tasks and still saw most usage attributed to subagents. Measure the accepted result, including handoffs, retries and review.
5 min readKeep the current plan until the model-level budget and permanent account changes are clear.
Evaluate one narrow subagent role and measure completed-task cost on both sides of 100K.
Run it against your own task set before you move traffic. The price is verified; the capability claims are OpenAI's own runs.
Worth moving to, but read the migration notes before you change the model string. The three 400s are the whole of the work, and each has a named replacement.
Anyone running a long-lived agent loop on GPT-6 whose input bill is mostly re-sent context.
Anyone with a Sol or Luna line in a production bill, and anyone who priced an agent out at the old rate.
Copilot Business and Enterprise admins, whose default-enablement policy turns new models on unless they opted out.
A developer choosing an agent also chooses how that agent spends. A September comparison kept the model fixed and found a large cost gap. Its evidence is useful; its limits matter before a team switches tools.
5 min readThe design and the raw chart data are public and worth an hour. They will not settle a harness migration on thirty tasks — price your own rollouts before you move.
Join the waitlist and keep the pricing table. Hold the verdict until somebody outside the company has run it on their own workload.
A cheaper cache read helps only when the client actually reuses the context. Claude Code’s September rollout of Fable 5.1 shows how a working agent can finish its task while missing the economics used to justify it.
5 min readAnyone on Fable 5.1 in Claude Code after 2.1.257–259
Pin Claude Code ≥2.1.260 if you run Fable 5.1. On Copilot, enable Gemini 3.8 Flash and plan the 2 Oct model cutover.
Plus Codex/Work: plan around a 5h rolling window again, or move Pro / credits / another harness. Claude Code on Bedrock or a gateway: stay on latest ≥2.1.239 (ideally 2.1.246); stable still lacks those fixes.
If you already call Sol (or gpt-5.6), re-check invoices and budget alerts against $4/$20. Prefer Batch or Flex for offline work. Pin gpt-5.6-sol if you need the promo rate to stay attached to a snapshot name.
Meter DeepSeek by UTC hour. Prefer off-peak for batch and long loops; pin Pro-0813 or Flash-0731 so a silent version cell cannot surprise you.
anyone metering DeepSeek as a default agent model
goose hosts metering multi-turn runs
anyone whose agents default to Sonnet 5 and who had a 50% step-up in the September forecast
anyone with a high-volume batch job costed at last week's prices