Feature · Cost controls

Preview

Route by cost tier. Cap spend before it surprises you.

Because calls already pass through the same governed checkpoint, that checkpoint is also where cost becomes visible and controllable, before the bill arrives, not after.

What it does

Set a tier, set a cap, see the spend.

The goal is straightforward: let you route calls to a cost tier you choose, and cap spend so a runaway agent cannot silently run up a bill. What is real today is narrower than that full picture, and this page says exactly where the line is.

Where it stands today

Presets exist. Automatic routing does not.

Named routing presets and cost measurement on gateway-routed traffic exist as configuration today. Automatically picking the cheapest viable model for a given call, sometimes called model arbitrage, is an idea we have designed toward and have not shipped. It does not run in production, and this site will not describe it as available until it does.

Status

Preview.

Cost measurement and named tiers: real, in early access. Automatic model arbitrage: an idea, never shipped, not implied as live anywhere on this site.

Folded in from the former catalog

  • SynOI Accelerator
  • Routing Profiles
  • Context-Window Auto-Swap
  • Token Saver

Tell us what a cost cap would need to cover.

Early access is limited while the routing logic is built out. Requests help us prioritize which tier logic ships first.