Routing
Destination and format visible
Each published route shows the call format and whether the model is hosted by RouterLab or processed by a third-party provider, without exposing internal routing logic.
Trust & infrastructure
This page separates roles: RouterLab controls access, credits, and usage, and hosts all offered open-source models in Switzerland and Germany. Proprietary providers process requests sent to them.
TrustBoundaryMap
A request crosses several zones. RouterLab makes those zones readable.
Client source
ROUTERLAB CONTROL
Model processing
Visible
Published route + hosting
Measure
Usage + credits
Metadata
No prompt content
What RouterLab controls
RouterLab centralizes API access, applies account permissions, shows the published logical route, and ties each request to credits. Internal routing logic remains confidential.
Routing
Each published route shows the call format and whether the model is hosted by RouterLab or processed by a third-party provider, without exposing internal routing logic.
Credits
Each request feeds usage and the credit ledger so real cost can be tracked.
API keys
Your apps call RouterLab with a RouterLab key instead of storing provider keys everywhere.
Tracking
The dashboard shows the published logical route, consumption, and remaining credits, without displaying prompt and response content or internal routing logic.
Infrastructure and regions
RouterLab infrastructure and open-source models are hosted in Switzerland and Germany. Proprietary models are processed by their respective providers.
RouterLab infrastructure and open-source models run on our servers in Switzerland and Germany.
Proprietary routes use external providers, including OpenAI, Anthropic, Google, AWS Claude and xAI (Grok), depending on the selected model and route. Their processing and retention terms apply.
Published routes expose format, status, and hosting category. They do not describe internal routing logic.
TrustRoute
| Provider | Format | Role | What it means | Signal |
|---|---|---|---|---|
| OpenAI SDK | Third-party provider | Processes the request on OpenAI infrastructure under its own policies | Third-party provider | |
| Claude Messages API | Third-party provider | Processes Claude requests on infrastructure external to RouterLab | Third-party provider | |
| OpenAI-compatible | Third-party provider | Processes Gemini requests on Google infrastructure | Third-party provider | |
| Claude Messages API | Third-party provider | AWS Claude route: processing external to RouterLab, subject to the selected provider and route terms | Third-party provider | |
| OpenAI-compatible | Third-party provider | Grok route: processing external to RouterLab, subject to the selected provider and route terms | Third-party provider | |
| OpenAI-compatible | Hosted by RouterLab | Models run on RouterLab infrastructure in Switzerland and Germany | Hosted by RouterLab |
Data, keys, and limits
The right trust level is precise: state what is controlled, and do not promise what depends on a provider.
Your integrations call RouterLab with a RouterLab key. Provider keys are not distributed into your client apps.
RouterLab keeps only the events and metadata needed to track credits, costs, usage, and support.
RouterLab does not log or durably archive their content. A very short-lived technical cache may be used when strictly necessary to operate the service.
Customer and admin areas remain separated by authentication and application roles.
TransparencyBoundary
This page avoids unverified legal promises. It describes RouterLab's operational role.
Not a provider retention promise
Proprietary routes use external providers, including OpenAI, Anthropic, Google, AWS Claude and xAI (Grok), depending on the selected model and route. Their processing and retention terms apply.
Not a legal certificate
This page explains operational behavior. Legal commitments must remain in legal documents or contracts.
No provider hiding
When a route goes to a third-party provider, RouterLab should make it explicit instead of burying it.
Legal pages remain the source for terms, privacy, and data protection.
DataFlowDiagram
Tracking covers the operational metadata needed for permissions, the published destination, usage, and credits. It includes neither prompt and response content nor internal routing logic.
Request
POST /v1/chat/completions
Control
Key + permissions + plan
Destination
Hosting / provider
Credits
Ledger + usage
Verification
Test the endpoint, choose a model, and watch credits and usage return in the dashboard.
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.