Skip to content

See which routing rule wins

Purpose: rules set at the organisation, a team and a key can all name the same model. Vidai never asks you to type a priority: the order is fixed and readable, and for any key it shows which rule decides each model, and why the others step aside.

The order

  1. Compliance route (Enterprise): always first, no exemptions.
  2. Required rule, unless the key is exempt.
  3. A/B experiment.
  4. Default rule: the one closest to the key wins.

Region rules (Enterprise) and the organisation's list of models approved for use sit around all four: no rule can send a call outside them. Fallback chains act after the winner is chosen, when its provider is down.

Before you start

  • You're an organisation admin, organisation viewer, group admin or Compliance officer Enterprise. Anyone can read the routing that reaches their own key on the key's page.

Steps

  1. Open Models & routing › Routing and the Which rule wins tab.
  2. Under Explain a key, pick a key, for example campaign-copywriter production.
  3. For each model, read which rule decides its calls, or that its calls are refused. Region rules reaching the key are listed first.
  4. Under In the order they're weighed, each rule sits on the ladder: the winner is marked Decides, and every other rule says why it doesn't apply ("A required rule above it applies", "This key is exempt", "Paused").

Which rule wins for one key: the rule that decides each model, then every rule in the order it's weighed

The same view is in the Routing section of every key's page.

Worked examples

  • A default and an exception. The organisation sends gpt-4.1 to gpt-4.1-mini by default. Media buying sets its own rule to send gpt-4.1 to gpt-4.1-eu. Everyone else gets gpt-4.1-mini; Media buying's keys get gpt-4.1-eu.
  • A required rule and an exemption. Make the organisation's rule Required, and Media buying's rule says "A required rule above it applies". To let one key keep gpt-4.1 ("client SLA, until 31 March"), exempt it; when the exemption ends it follows the organisation's rule again.
  • A compliance route. Zuiderhoeve's compliance route sends gpt-4.1 to gpt-4.1-eu. Any routing rule or experiment for gpt-4.1 reaching Zuiderhoeve's keys reads Not acting here, naming the route.

Check it worked

Make a test call with the key and read it in Request logs: Why this happened names the rule that routed it, and the answer's x-vidai-routing-rule header carries its id.

Good to know

  • Rules on cards say what they really do for the working keys they reach: Acts for 9 of 12 keys, Not acting here, Already in place, Paused or No keys yet, each naming the rule that decides instead.
  • Home's Needs attention tells whoever may change a rule when it decides nothing or is already in place.