Explicit route formats
Catalog entries identify whether a model uses OpenAI-compatible, Claude Messages or embeddings routes.
A different multi-model operating model
An OpenRouter alternative built around control and clarity
RouterLab is a multi-model API option for teams that want a Swiss-operated product layer, an explicit public catalog, familiar API formats and a documented path for coding agents. Compare the operating model—not only the number of model names.
Request route200 · route ready
Your client
App, agent or workflow
RouterLab API
OpenAI-compatible + Claude Messages
Multi-model apps
Coding agents
European teams
ENTRY POINT
https://api.routerlab.ch/v1API guides
Start with the protocol. Choose a model family or a client integration only after that.
What you can do
Understand the connection path first, then choose a model from the live catalog.
Swiss-operated product layer
RouterLab provides the customer-facing gateway, catalog, key and usage experience from Switzerland.
Agent integration paths
Use direct custom endpoints for compatible agents or the ScioNos path for Claude Code and Codex CLI.
Compare gateway fit before comparing catalog size
The right alternative depends on the route formats your software needs, the models actually available to your account, pricing, support, operational location and how clearly upstream processing is documented. RouterLab is strongest when control and a focused product surface matter.
Test the RouterLab-compatible endpoint
import OpenAI from "openai";
const client = new OpenAI({
apiKey: process.env.ROUTERLAB_API_KEY,
baseURL: "https://api.routerlab.ch/v1",
});
const response = await client.chat.completions.create({
model: "model-id-from-/v1/models",
messages: [{ role: "user", content: "Hello RouterLab" }],
});Use a model ID returned by GET /v1/models.
Where it fits
Start from the workload and client contract, then choose the route.
Focused production catalog
Choose from routes that RouterLab actively publishes instead of integrating every upstream individually.
European operations
Place a Swiss-operated product layer between internal applications and multiple model providers.
Coding-agent access
Connect custom-endpoint agents directly and use ScioNos for supported terminal clients.
Get started
- 01
List your required capabilities
Write down the models, context, tools, route format, residency and support requirements that matter.
- 02
Check the live RouterLab catalog
Verify model IDs, capabilities and current pricing rather than relying on a static comparison table.
- 03
Test a representative workload
Run one real application or agent flow and compare reliability, output and total operating fit.
Common questions
Use the live catalog and API documentation as the final source for route availability.
Is RouterLab the same as OpenRouter?
No. Both can provide multi-model access, but the catalog, product layer, operational context, route design and supported workflows differ.
What should I compare?
Compare available models, API formats, feature support, pricing, upstream processing, account controls, support and the integration path for your actual clients.
Can I migrate an OpenAI-compatible application?
A compatible application can usually begin by changing the base URL, API key and model ID, then validating model-specific behavior with a real workload.