Create or repoint an alias
Point a stable name at a model — and repoint it whenever you like, with no change to your code.
Your application keeps calling support-bot; the next request after a repoint already routes to the new model. This is what makes an eval result actionable: prove a cheaper model holds up, then repoint.
Upsert by name, so CI can repoint idempotently without a lookup first. Owner/admin key required — repointing silently redirects live production traffic, so it’s audited with the before/after.
You are always billed for the model that RAN. An alias is a routing decision, never a pricing one.
Authorizations
Your workspace API key, e.g. sk_sovereign_..., sent as Authorization: Bearer <key>.
Body
3–64 chars (letters, numbers, dots, dashes, underscores). Scoped to your workspace — a name that isn't an alias is treated as a normal model id, so aliases never shadow the catalog.
"support-bot"
The model requests route to. Validated against the live catalog.
"Qwen/Qwen3-32B"
Optional. A share of requests route here instead — for a gradual cutover.
0 = no split. 100 = full cutover. The split is per REQUEST, not per user.
0 <= x <= 100200"switched after eval ev_123 (90% win, -88% cost)"
Turn the canary split into a supervised rollout: the online scorer judges BOTH arms with this criterion and the gate decides on corrected-rate CI bounds. The criterion must have been aligned against your labels.
recommend: verdicts surface on GET /v1/aliases (gate_verdict) and via alert notifications — you click the button. auto: the gate may repoint the alias itself (promote) or zero the canary (roll back), always audited with the numbers. Auto requires an ALIGNED criterion (TPR and TNR ≥ 90%): a judge may recommend with a weaker signal, but it doesn't get the keys.
recommend, auto No verdict of any kind until BOTH arms have this many scored requests.
10 <= x <= 1000Roll back only when even the canary's OPTIMISTIC bound (CI upper) sits below this — confidently bad, not unluckily sampled.
0 <= x <= 1Scores older than this don't count toward the verdict.
1 <= x <= 720Omitted = leave the alias's existing policy alone (a plain repoint can't quietly switch the policy off); false on create. With it on, a PUT that routes traffic to a model it isn't already reaching must be backed by a finished comparison in this workspace, within the last 30 days, whose candidate win-rate CI lower bound clears 50% against the model traffic is leaving. Refusals are 412.
The audited escape hatch for an evidence refusal: a written justification of at least 10 characters lets the repoint through and writes an audit event naming the actor, both models, and the reason. Omitted or blank is not an override.
Response
The alias.
The name you put in model.
"support-bot"
The model this resolves to today.
0–100. Share of requests routed to canaryModel.
recommend, auto The last gate evaluation: {decision: promote|rollback|hold, reason, canary: {model, rate, ci, judged}, incumbent: {...}, acted}.
No gate verdict until both canary arms have this many scored samples in the window.
Roll back only when even the canary's optimistic bound (CI upper) sits below this corrected pass rate.
Scores older than this do not count toward the verdict.
The model version this alias currently serves, when it points at a trained version (null for raw catalog models). Repoint to an older version to roll back.
Evidence policy: with this on, a repoint that would send traffic to an unproven model is refused with 412 unless a passing, in-window comparison exists (or an audited override_reason is given).
The eval run that authorized the current routing. Null when the routing predates the policy or went through as an audited override.