switchboard-100.pages.dev

list_traffic_classes

List the traffic classes this workload is split into, with the constraints each must satisfy, and how many models are currently eligible for each. Read this before proposing any routing change — the constraints are the whole point and several are not about money. Per class: monthlyCalls and average token counts, which are OPERATOR-DECLARED estimates and not measured (you cannot change them; only the human can, in the UI). Then the constraints: maxP95Ms, minSuccessRate (judged against the chain-level delivery rate, not one model's success rate), requireQualityGates, maxDataRetentionDays (null here means UNCONSTRAINED — the opposite of null on a model, where it means undocumented and therefore not clearable), allowTrainingOnData (false means never route to a model that trains on submitted data, in any chain position, including fallbacks), requireMeasured. You cannot write these constraints — but the operator can, under 'relax constraints' on each class in the UI. So when a class has zero eligible models, the useful move is to name precisely which constraint is emptying the set and what it would cost to relax each one, then let them choose. Do not route around a constraint you were not given permission to relax.

Input schema

No input properties (empty object).

{
  "type": "object",
  "properties": {}
}