Loading benchmark data…
EyesInAI·Loading live benchmark data
Switchyard sits between your chatbot and the models. For every request it picks the least-expensive model that still passes the task — measured against a live benchmark, not a hand-written rule. Model-agnostic, provider-agnostic, and fast enough to sit right in the request path. You change one line: your base URL.
client = OpenAI(
base_url="https://gateway.eyesinai.com/v1", # ← the one line
api_key=YOUR_SWITCHYARD_KEY,
)
client.chat.completions.create(
model="auto", # ← let Switchyard choose
messages=[...],
)Keep model="auto" to let Switchyard route, or name a model any time to pass straight through. It speaks the API you already use.
One line changes in your existing OpenAI-compatible client. Send model:"auto" and Switchyard chooses; send a specific model and it passes straight through. No rewrite, no SDK lock-in.
Each request is matched to the task it belongs to and sent to the least-expensive model that still clears your quality bar — read from a live benchmark of the candidates, not a static rule.
Switchyard shadow-tests alternatives in the background and re-routes as models change. Every real request it sees makes the next routing decision sharper. You watch the savings, not the plumbing.
Switchyard only ever picks a model that clears the quality bar you set for a task. If nothing beats what you run today, it tells you — and routes nothing. Savings that cost you accuracy are worth nothing, so we never make that trade.
For a request it has seen the shape of before, the routing decision is an in-memory lookup — not another model call added to your latency. It is built to be invisible.
Provider keys are passed through per request and never stored. Prompt data is held only if you want it held — for tuning — and can live in your own database. What we learn is which models are better, never your content.
The routing engine behind Switchyard already runs on a real support chatbot, where a per-action routing table cut model cost 31% with no measurable accuracy loss. Switchyard is that engine, made a product. Read the case study →
Not sure routing would help you yet? Start with a one-time benchmark of your use case — we measure the savings first, honestly, before you wire anything in. Switchyard is what implements that routing table live once you're ready.
Tell us what you're running. We'll set up a gateway scoped to your workload and show you the measured savings before you commit.