Skip to main content

Routing Rules

Custom routing rules select an eligible same-provider model using supported conditions and priority. Configure rules in Routing Rules. Conditions and target capabilities are validated by the application; test with representative input before relying on a rule.

Routing stays within the provider selected by the proxy path. It evaluates applicable customer rules before global defaults, with lower priority numbers evaluated first. The global low-confidence guard can preserve the requested model. Capabilities, request shape and STICKY conversation continuity can prevent a change. A successful request can have Makas-Was-Routed: false and zero savings.

GroupDefault behavior
COST_DOWN_CHEAPESTOn: simple mechanical tasks to cheapest capable models
COST_DOWN_BUDGETOn: light routine tasks to budget models
COST_DOWN_MIDOn: economical models for eligible everyday and selected complex tasks
CODE_SPECIALIZATIONOn: eligible code tasks to purpose-built models at the same price
MODERNIZEOn when the plan includes automatic model upgrades: same or lower cost
RETIRE_DEPRECATEDOff: may raise cost; current opt-out API cannot enable it
QUALITY_UPGRADEOff: raises cost; current opt-out API cannot enable it

Default-on groups can be opted out in Routing Rules. Removing a cost-raising group from an opt-out list does not turn it on; there is no current customer enable API for those groups. MODERNIZE requires Growth+ in the planned paid tier system and is included in Founding.

Custom rules require Growth+ when billing is enabled; Founding includes up to 10. Adding a rule beyond the limit returns 403 with type: urn:makas:error:limit-exceeded. Per-key routing opt-outs require Scale+ in the planned paid tiers and are included in Founding. Do not assume all rules apply to every request.

Compare model requested/used and the optional rule in Request Logs. Conditional response headers can also help for buffered inference.