2 · Bypass to a concrete model
Name a real model and routing is skipped entirely.
What it is
A request whose model field names a catalog entry directly (gpt-strong, devin/opus, dynamic-1, a worker queue name, ...) instead of "auto". routsi never runs the classifier — it's a hard bypass, not a hint.
Why
For callers that already know exactly which model or agent they want — testing a specific upstream, pinning a feature to a specific provider, or letting a power user override the router. It's also how every non-auto scenario on this site works under the hood: dynamic groups and agents are still just named catalog entries.
Configure
Nothing special — any entry under models: in models.yaml is addressable by its name (or provider/variant for expanded variants). No tiers: or auth config is required for bypass to work.
curl -i localhost:8080/v1/chat/completions \
-d '{"model":"gpt-strong","messages":[{"role":"user","content":"hi"}]}'
# → X-Selected-Model: gpt-strong (no classification ran)How to adapt
Just send the exact name: (or provider/variant) from your models.yaml catalog — check GET /v1/models for the full live list, including discovered/variant-expanded names. Unknown names return an error rather than silently falling back to routing.