Configure a custom client
Configure iRouter endpoints, protocols, models, and keys in custom-provider clients.
Requirements
The client must support custom endpoints, keys, model IDs, and the intended protocol. This field guide is not certification of every chat client, configuration manager, or agent version.
Complete a curl request in a separate terminal before client setup to distinguish connection issues from client configuration.
Fill in fields
Field | Value |
|---|---|
Provider name | iRouter |
Protocol | Match the selected model and line |
OpenAI-compatible base URL | |
Anthropic base URL | |
API key | The complete account key, without the word Bearer |
Model ID | Copy from the available model list |
Some endpoint fields accept only an origin and append /v1; others accept a versioned base URL. Inspect the actual request path for duplicate prefixes. Fields requiring a complete endpoint use operation paths from the API overview.
Verify
Save and restart the affected client. Confirm the active provider, model, and authentication method. Send short text and inspect iRouter usage before testing streaming, tools, and images. A connection check does not validate model access or optional capabilities.
Configuration managers may rewrite other clients' settings, so preserve existing configuration. iRouter documentation does not require third-party presets, installation scripts, or changes to client approval permissions.
Client guides
See Claude Code and Codex CLI. For other tools, consult their official documentation if custom model endpoints are unavailable. Do not use an account password as an API key.