Integration routes
Choose a model, then configure your client
Select your model in Runmux Console and inspect its current integration configuration. The URL, key type, request model ID and example must belong to the same configuration.
| Access method | What to verify |
|---|---|
| Unified API | Unified base URL, public request model ID, required key and protocol |
| Direct gateway | Gateway URL, request model ID for that route, key type and protocol |
A matching model name does not make configurations interchangeable. Do not use internal supply identifiers as public request model IDs.
Prepare four things
- Model: your task and its verified capabilities.
- URL: the complete Base URL provided in Console; check whether your SDK appends paths to avoid duplicating
/v1. - Credential: the key type required by that model and route. Keep keys in local environment variables, never in shared URLs.
- Protocol: synchronous, streaming or asynchronous requests, with matching parameters and responses.
Video and other special protocols require their own entrypoint and Video Key checks. Ordinary keys and Video Keys are not interchangeable. Upstream direct access does not establish the default customer route.
Next steps
Model-specific minimal examples will be published after test review. Use the matching configuration already provided in Console; this page does not supply unverified model requests.