API endpoints and connectivity
Choose the correct UniRoute API address and protocol path, and troubleshoot connection problems.
UniRoute's API root is https://api.uniroute.app. Use this address when configuring a client, with the path suffix required by its protocol.
Addresses by protocol
| Usage | Address or path |
|---|---|
Claude Code ANTHROPIC_BASE_URL | https://api.uniroute.app |
| Codex / OpenAI SDK API base URL | https://api.uniroute.app/v1 |
Gemini CLI GOOGLE_GEMINI_BASE_URL | https://api.uniroute.app |
| Anthropic Messages request path | /v1/messages |
| OpenAI Responses request path | /v1/responses |
| OpenAI Chat Completions request path | /v1/chat/completions |
| Gemini native API path prefix | /v1beta |
| Model catalog for the current API key | /v1/models |
SDKs and clients normally append the request path themselves. Do not add the complete endpoint path to a base URL that the client will extend. Provider adapters in clients such as OpenCode have their own base URL requirements; follow the relevant tutorial.
Pass your API key in an authentication header or the client's key setting. Do not place it in a URL path or query string, or send screenshots or configuration files containing the key to an AI conversation.
Use the configuration tool
The UniRoute configuration tool and Skill select addresses based on the client and model protocol, query the model catalog available to the current key, and back up configuration before changes.
You can also follow the Codex, Gemini CLI, OpenCode, OpenClaw, or Hermes tutorial directly.
Troubleshoot connections
- Check the domain, protocol, and path. Avoid duplicate
/v1or/v1betasegments. - For timeouts, check your local network, DNS, and existing proxy settings. Try another network or compare connectivity with your existing proxy enabled and disabled.
- For
401, check that the API key is complete and still valid. For403, check key permissions and account status. - After configuration, send a short request and inspect the console call record. Model requests are billed for actual usage.
Record the time, client version, and error message, then report the issue through the support entry point. Hide your API key.
