Update Routing Policy
Update the fields you send. The policy is updated in place, so its id
stays the same. To change the routing, send strategy with its fields.
Needs a management key.
Authentication
A management key (mgmt_...), sent as Authorization: Bearer <key>. Reading /v1/routing-policies also accepts the organization’s gateway API keys; writing there needs a management key.
Path parameters
The policy’s id.
Request
INTELLIGENT only, optional. Not stored: responses rebuild it from allowed_models. If sent non-empty, it must name the same providers as allowed_models (order and repeats don’t matter), or the request fails with 422. Checked only when strategy is sent.
INTELLIGENT only. What the router optimizes for: COST, PERFORMANCE or CAPABILITY. Omitted or null means COST. Used only when strategy is sent.
PRIORITY only. The priority values are kept as sent; responses list the entries sorted by priority. A model listed twice is a 422. Used only when strategy is sent.
Send with its fields to replace the routing. Omitted or null leaves the routing as it is, and allowed_providers, allowed_models, priority_order and axis are ignored.
Response
INTELLIGENT only. The providers of allowed_models, sorted. Always rebuilt from allowed_models; never stored.
INTELLIGENT only, else null. What the router optimizes for: COST, PERFORMANCE or CAPABILITY.
The ready-to-send model string for this policy, like “@alias/fast-experiment”. Send it as the model in any gateway request to route with this policy.
The policy’s model alias as a bare name, like “fast-experiment”. Null only when no alias could be made, such as an organization at its alias limit.
PRIORITY tries priority_order in turn; INTELLIGENT picks among allowed_models per request, optimizing for axis.