multi-router.aidocs

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

ToolKindRouterFormat
Claude CodeCoding agent in the terminalClaude ProxyAnthropic Messages, Amazon Bedrock and Google Vertex
Codex CLICoding agent in the terminalCodex ProxyOpenAI Responses
Gemini CLICoding agent in the terminalGemini ProxyGemini generateContent
Pi.DevCoding agent in the terminalAdaptive RouterOpenAI Chat Completions
Qwen CodeCoding agent in the terminalAdaptive RouterOpenAI Chat Completions
OpenCodeCoding agent in the terminalAdaptive RouterOpenAI Chat Completions
AmpCoding agentAdaptive RouterOpenAI Chat Completions
GooseAgent, command-line versionAdaptive RouterOpenAI Chat Completions
AiderCoding agent in the terminalAdaptive RouterOpenAI Chat Completions
GitHub CopilotEditor agent in VS CodeAdaptive RouterOpenAI Chat Completions
ZedEditorAdaptive RouterOpenAI Chat Completions
ClineEditor agentAdaptive RouterOpenAI Chat Completions
Kilo CodeEditor agentAdaptive RouterOpenAI Chat Completions
Claude DesktopDesktop chat appClaude ProxyAnthropic Messages
Claude for OfficeOffice add-inClaude ProxyAnthropic Messages
Open WebUISelf-hosted chat appAdaptive RouterOpenAI Chat Completions
LibreChatSelf-hosted chat appAdaptive RouterOpenAI Chat Completions
OpenWorkDesktop agent appAdaptive RouterOpenAI Chat Completions

Routers for tools

RouterServesModelsCredential
Claude ProxyAnthropic Messages at https://api.multi-router.ai, and the Bedrock and Vertex formatsThe models of the proxy's routeOrganization key, or the developer's own Anthropic login
Codex ProxyOpenAI Responses at https://api.multi-router.ai/v1/responsesOpenAI models onlyOrganization OpenAI key, or the developer's own OpenAI API key
Gemini ProxyGemini generateContent and streamGenerateContent under https://api.multi-router.ai/v1beta/modelsGemini models onlyOrganization Gemini key
Adaptive RouterOpenAI Chat Completions at https://api.multi-router.ai/v1/chat/completionsAny model switched on in the router's model groupOrganization 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:

  1. 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.
  2. Multi-Router checks the API key and selects the router named in X-MR-Router.
  3. The router checks the request against the organization's rules, such as the allowed models, budgets and rate limits.
  4. The router sends the request to the provider with the credential its settings call for, and streams the response back.
  5. 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 sourceWho paysRouters
OrganizationThe 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
DeveloperEach 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

ControlApplies toEffect
Route and regionClaude ProxyWhich provider and region serve the tool, such as Anthropic, or Bedrock in the US.
Allowed modelsClaude Proxy and Adaptive RouterThe 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.
DisableEvery routerDisabling the router stops the tool for everyone using it, from the next request.
BudgetsEvery routerSpending caps for the organization, chosen routers or router tags. When each person has their own router, a router budget caps one person.
Rate limitsEvery API keyRequests per API key.
Request loggingEvery routerWhether 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.

ScopeNeeded for
inferenceEvery request a tool sends.
models:readClaude 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.

PageCovers
TroubleshootingErrors each tool can return, with their causes and fixes.
Claude ProxyRoutes, credentials, regions and models of a Claude Proxy.
Model GroupThe model sets an Adaptive Router or a Claude Proxy serves.
API KeyCreating keys, scopes and router limits.
Managing PromptsClaude Code
Was this helpful?