OpenAI-compatible migration

If your application already speaks the OpenAI SDK, route-switch is the lowest-friction way to add a gateway: it is an OpenAI-compatible endpoint. Migration is a base-URL change, and everything the gateway offers becomes available afterward without a rewrite.

Step one: the swap

const client = new OpenAI({
  baseURL: "http://localhost:8080/v1", // route-switch
  apiKey: process.env.RS_KEY,
});

That’s the migration. The drop-in OpenAI base_url swap guide covers streaming and edge cases.

Step two: unlock the gateway

Now that traffic flows through route-switch, layer on capability at your own pace:

• Routing across combinations and providers — choose a strategy.
• Analytics — per-prompt cost, latency, and success in DuckDB.
• Failover — automatic fallback when a combination degrades.
• Optimization — MIPROv2 on your traces.

The trade to weigh

You take on running a self-hosted binary and keeping its SQLite and DuckDB files. In exchange, your prompt, routing, analytics, and optimizer live in one process you control, and your traffic never leaves your infrastructure. If zero-ops access to a wide model catalogue matters more, a hosted aggregator like OpenRouter is the other shape.