RouterLab API
Choose the API format your client needs.
RouterLab exposes multiple models behind two clear contracts. Start with your tool’s protocol, then choose a model from the catalog.
- Base URL
- https://api.routerlab.ch
- Key
- Bearer $ROUTERLAB_API_KEY
- Models
- GET /v1/models
Two protocols
Where should you start?
The model name does not decide the format. Its catalog route badge does.
OpenAI-compatible
For OpenAI SDKs and chat/completions
The standard path for applications, agents and tools that accept a custom base URL.
POST /v1/chat/completionsDeepSeek, GLM and other families
Claude Messages
For clients that speak Messages
The alternative HTTP contract for models whose catalog entry explicitly shows this route.
POST /v1/messagesRoute availability depends on the model
The important distinction
Protocol on one side. Model on the other.
DeepSeek and GLM are model families, not separate RouterLab APIs. Select their identifier in a request compatible with the listed route.
ScioNos wrapper
Claude Code and Codex CLI already have their integration.
These tools do not need two more API pages. The ScioNos wrapper centralizes installation, authentication and launch.