Agents & Editors
Overview
How coding agents, editors and chat apps connect to Multi-Router, which router each one uses, and what an organization controls once they do.
Agents and editors are the AI tools people use directly, such as a coding agent in a terminal, an editor's chat, or a chat app. Each tool connects to Multi-Router through a router that accepts its request format. Tools built for one provider's models use a proxy for that provider: a Claude Proxy, a Codex Proxy or a Gemini Proxy. Tools that work with many providers send OpenAI Chat Completions requests to an Adaptive Router, which serves any model in its model group. The organization decides which models each tool can use, which credentials pay for it, how much it can spend, and what Traffic records about it.
Supported tools
| Tool | Kind | Router | Format |
|---|---|---|---|
| Claude Code | Coding agent in the terminal | Claude Proxy | Anthropic Messages, Amazon Bedrock and Google Vertex |
| Codex CLI | Coding agent in the terminal | Codex Proxy | OpenAI Responses |
| Gemini CLI | Coding agent in the terminal | Gemini Proxy | Gemini generateContent |
| Pi.Dev | Coding agent in the terminal | Adaptive Router | OpenAI Chat Completions |
| Qwen Code | Coding agent in the terminal | Adaptive Router | OpenAI Chat Completions |
| OpenCode | Coding agent in the terminal | Adaptive Router | OpenAI Chat Completions |
| Amp | Coding agent | Adaptive Router | OpenAI Chat Completions |
| Goose | Agent, command-line version | Adaptive Router | OpenAI Chat Completions |
| Aider | Coding agent in the terminal | Adaptive Router | OpenAI Chat Completions |
| GitHub Copilot | Editor agent in VS Code | Adaptive Router | OpenAI Chat Completions |
| Zed | Editor | Adaptive Router | OpenAI Chat Completions |
| Cline | Editor agent | Adaptive Router | OpenAI Chat Completions |
| Kilo Code | Editor agent | Adaptive Router | OpenAI Chat Completions |
| Claude Desktop | Desktop chat app | Claude Proxy | Anthropic Messages |
| Claude for Office | Office add-in | Claude Proxy | Anthropic Messages |
| Open WebUI | Self-hosted chat app | Adaptive Router | OpenAI Chat Completions |
| LibreChat | Self-hosted chat app | Adaptive Router | OpenAI Chat Completions |
| OpenWork | Desktop agent app | Adaptive Router | OpenAI Chat Completions |
Routers for tools
| Router | Serves | Models | Credential |
|---|---|---|---|
| Claude Proxy | Anthropic Messages at https://api.multi-router.ai, and the Bedrock and Vertex formats | The models of the proxy's route | Organization key, or the developer's own Anthropic login |
| Codex Proxy | OpenAI Responses at https://api.multi-router.ai/v1/responses | OpenAI models only | Organization OpenAI key, or the developer's own OpenAI API key |
| Gemini Proxy | Gemini generateContent and streamGenerateContent under https://api.multi-router.ai/v1beta/models | Gemini models only | Organization Gemini key |
| Adaptive Router | OpenAI Chat Completions at https://api.multi-router.ai/v1/chat/completions | Any model switched on in the router's model group | Organization key for each provider |
How a tool connects
A tool connects to Multi-Router by sending its normal requests to the Multi-Router address, https://api.multi-router.ai, with two additions. The X-MR-Router header names the router that serves the tool, such as rt_XXXXXXXX, and the Multi-Router API key identifies the person or machine making the request. Each tool's page gives the exact settings. A request is handled in this order:
- The tool sends a request in its own format, such as an Anthropic Messages request from Claude Code or a Chat Completions request from OpenCode.
- Multi-Router checks the API key and selects the router named in
X-MR-Router. - The router checks the request against the organization's rules, such as the allowed models, budgets and rate limits.
- The router sends the request to the provider with the credential its settings call for, and streams the response back.
- Traffic records the request with its router, API key, model, tokens and cost.
Without X-MR-Router, a request is not served by the tool's router. Every tool on this list can send the header from its settings.
Credentials
The credential is the provider login that pays for each request:
| Credential source | Who pays | Routers |
|---|---|---|
| Organization | The organization's provider key, added in Provider Keys. The tool holds only the Multi-Router API key. | Claude Proxy, Codex Proxy, Gemini Proxy and Adaptive Router |
| Developer | Each developer's own provider login, passed through to the provider: an Anthropic login or Claude subscription on a Claude Proxy, or an OpenAI API key on a Codex Proxy. | Claude Proxy on the Anthropic route, and Codex Proxy |
With either source, the developer also holds a Multi-Router API key, which identifies them in Traffic and applies the organization's limits. See Provider Key.
What the organization controls
| Control | Applies to | Effect |
|---|---|---|
| Route and region | Claude Proxy | Which provider and region serve the tool, such as Anthropic, or Bedrock in the US. |
| Allowed models | Claude Proxy and Adaptive Router | The models the router serves: a Claude Proxy's route or model group, or an Adaptive Router's model group with each model switched on or off. |
| Disable | Every router | Disabling the router stops the tool for everyone using it, from the next request. |
| Budgets | Every router | Spending caps for the organization, chosen routers or router tags. When each person has their own router, a router budget caps one person. |
| Rate limits | Every API key | Requests per API key. |
| Request logging | Every router | Whether Traffic records request metadata and payloads. |
API keys
Each person or machine using a tool needs a Multi-Router API key with the scopes the tool calls for. A key can also be limited to the tool's router, so it reaches nothing else in the organization.
| Scope | Needed for |
|---|---|
inference | Every request a tool sends. |
models:read | Claude Desktop's model picker, and model discovery in Claude Code. |
Keep the key in an environment variable, a secret store or the tool's own key storage, never in a file that is committed to a repository. In organizations that use Self-Service Provisioning, people set up Claude Code and Claude Desktop themselves from the Portal. See Self-Service Provisioning.
Usage in Traffic
Traffic shows each request a tool sends, with the router in the Router column and the API key in the request detail, so usage and cost are visible per person and per tool. Each tool's page ends with a first request to send and find in Traffic. See Observability.
Related topics
| Page | Covers |
|---|---|
| Troubleshooting | Errors each tool can return, with their causes and fixes. |
| Claude Proxy | Routes, credentials, regions and models of a Claude Proxy. |
| Model Group | The model sets an Adaptive Router or a Claude Proxy serves. |
| API Key | Creating keys, scopes and router limits. |