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.

Four checks before choosing a route

Service operator
RouterLab is operated in Switzerland. Accounts, RouterLab keys, access, credits and usage tracking are managed by the service. Commercial information and support are available from your dashboard.
Execution depends on the model
The trust page distinguishes open-source models hosted by RouterLab in Switzerland and Germany from proprietary models processed by external providers. Check the exact route and its published information; the operator’s country alone does not establish residency for every request.
Data and responsibilities
Read the data-protection information for RouterLab processing and the applicable provider terms for a proprietary route. Provider retention rules cannot be inferred from RouterLab’s rules. Check the model page, protocol and your key’s permissions separately.
Specific requirements
Before sending data subject to specific requirements, have the route, processing region, relevant subprocessors and required retention commitments confirmed in the appropriate contract. Public pages are not a blanket guarantee of Swiss data residency.

What you can do

Choose a published model and the API format required by your application.

A Swiss service boundary

Work with RouterLab as the gateway and product layer for account, access, catalog and usage operations.

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

Choose according to your workload.

See how RouterLab works

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

  1. 01

    Review the service boundary

    Read the trust and data-protection pages before selecting a route for regulated or sensitive workloads.

  2. 02

    Choose a published route

    Check the model origin, API format and capability data in the live catalog.

  3. 03

    Apply your own data policy

    Send only workloads that match the selected route, provider and organizational requirements.

Common questions

Check availability and prices in the current catalog.

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.

Audience measurement

Allow Google Analytics and RouterLab to measure public visits and link campaign sources to your signup? This is optional and can be changed at any time. If you decline, only anonymous visit totals are kept.