A Swiss service boundary
Work with RouterLab as the gateway and product layer for account, access, catalog and usage operations.
Swiss-operated control layer
A Swiss AI API layer for European teams
RouterLab gives applications and agents a Swiss-operated access and control layer for published AI model routes. It centralizes the customer relationship, keys, usage view and model catalog while upstream processing remains route-specific and transparent.
Request route200 · route ready
Your client
App, agent or workflow
RouterLab API
Swiss control layer, route-specific processing
Applications
Coding agents
Model providers
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.
Clear responsibility split
RouterLab documents the control layer separately from the upstream provider used by an individual model route.
One European operating context
Consolidate multi-model access around a Swiss-operated product instead of managing each integration in isolation.
Swiss-operated does not mean every model is hosted in Switzerland
Data processing depends on the selected route and upstream provider. RouterLab’s trust and data-protection pages explain the service boundary; teams with residency requirements should validate the route that they plan to use.
The same stable API endpoint for European workloads
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.
European product teams
Adopt a closer operational and contractual control layer for applications that use several AI providers.
Procurement clarity
Review one product catalog, pricing surface and trust section before selecting model routes.
Governed experimentation
Let teams evaluate published models through centralized keys and usage visibility.
Get started
- 01
Review the service boundary
Read the trust and data-protection pages before selecting a route for regulated or sensitive workloads.
- 02
Choose a published route
Check the model origin, API format and capability data in the live catalog.
- 03
Apply your own data policy
Send only workloads that match the selected route, provider and organizational requirements.
Common questions
Use the live catalog and API documentation as the final source for route availability.
Is RouterLab a Swiss AI API?
RouterLab is a Swiss-operated AI API gateway and control product. The actual model and upstream processing location depend on the selected route.
Does every request stay in Switzerland?
No blanket residency claim is made. Review the published route and trust information for the upstream processing relevant to your workload.
Why use a European control layer?
It can simplify the account, access, catalog and usage relationship for teams that otherwise manage several provider integrations independently.