Routing
Claude Proxy
The router that serves Claude Code and Claude Desktop: its routes, regions, credentials, models, settings and errors.
A Claude Proxy is a router that serves Claude Code, Claude Desktop and other clients of Anthropic's APIs. It receives requests in the native Anthropic, AWS Bedrock or Google Vertex format, forwards the request body to the provider its route names, and returns the provider's response unchanged, so every feature of those APIs is available. A Claude Proxy has a route, which sets the provider and variant, a region, a credential source and the models it serves, and it records usage for each person in Traffic. How Claude Code and Claude Desktop are configured to use a Claude Proxy is described in Agents & Editors.
Endpoints
The endpoints of a Claude Proxy are the API paths that accept requests in each provider's native format. A request selects the proxy with the X-MR-Router header, which names the proxy's id or an alias that points to it and is required on the Bedrock and Vertex endpoints. Each endpoint serves the routes of its own provider:
| Endpoint | Format | Serves |
|---|---|---|
POST /v1/messages | Anthropic Messages | The Anthropic API route. |
POST /v1/messages/count_tokens | Anthropic token counting | The Anthropic API route. |
POST /bedrock/model/{model}/invoke | AWS Bedrock | The Bedrock routes. |
POST /bedrock/model/{model}/invoke-with-response-stream | AWS Bedrock streaming | The Bedrock routes. |
POST /vertex/projects/{p}/locations/{l}/publishers/anthropic/models/{m}:rawPredict | Google Vertex | The Vertex AI route, including token counting with the model count-tokens. |
…:streamRawPredict | Google Vertex streaming | The Vertex AI route. |
GET /v1/models | Anthropic model list | The models the proxy serves, answered from the catalog. |
On the Vertex endpoint, Multi-Router uses the project of the provider key and the region of the route, whatever project and location the client's URL names. The Bedrock endpoint accepts any model name the proxy recognizes in the URL, including a URL-encoded inference profile ARN.
Routes
A route is the provider and variant a Claude Proxy sends requests to. The dashboard lists the following routes:
| Route | Route id | Provider and variant | Description |
|---|---|---|---|
| Anthropic API | anthropic | Anthropic, standard | Forwards to api.anthropic.com in the global or us region. |
| Bedrock (Global) | bedrock-global | AWS Bedrock, global | Cross-region inference profiles. Inference can run in any AWS region, with no residency guarantee. |
| Bedrock (Geo) | bedrock-geo | AWS Bedrock, geo | Geography inference profiles. Inference stays inside one geography, such as the US, EU, Japan or Australia. |
| Bedrock (In-region) | bedrock-in-region | AWS Bedrock, in_region | Bare foundation-model ids. Inference stays in the single region called, and fewer models are offered. |
| Vertex AI | vertex | Google Vertex, standard | Vertex AI in the project of the provider key and the region of the route. |
| Custom | custom | Set for each model | Routes each model through a model group, whose members name their own provider, variant and region. See Custom route. |
Every route except Custom requires a region, chosen from the regions the route serves. A model with no offering in the chosen region is Not Available there, and Multi-Router does not fall back to another region. The dashboard shows how many of the route's models each region serves. See Regions & Variants.
Credentials
The credential source decides whose provider account pays for requests:
| Credential source | Dashboard label | Routes | Behavior |
|---|---|---|---|
organization | Organization Key | Every route | Multi-Router removes the client's credential and sends the provider key set on the proxy. Usage is billed to the organization's Anthropic, AWS or Google Cloud account. |
developer | Developer Credentials | Anthropic API | The client's own Anthropic credential is forwarded unchanged, and usage is billed to that person's account. |
The Multi-Router API key travels in the X-MR-Api-Token: Bearer <key> header. With Organization Key, the client can send it in Authorization or x-api-key instead, because Multi-Router replaces that credential with the provider key; with Developer Credentials, a Multi-Router API key in those headers returns 400.
An organization key must be an enabled key of the route's provider. A Bedrock API key must have been created for the proxy's region, while AWS access keys and Vertex keys work in any region. When a proxy's key is later disabled or deleted, its requests return 503 until the proxy uses another key. See Provider Key.
Models
The models a Claude Proxy serves are the current Claude models listed in the catalog's Claude Proxy section, such as Claude Opus 5.5, Claude Sonnet 5 and Claude Haiku 4.5. A proxy can turn off individual models, and at least one model must stay served. Each model has one of three states on a proxy:
| State | API value | Meaning |
|---|---|---|
| Served | served | The route offers the model in the proxy's region, and the proxy serves it. |
| Disabled | disabled | The proxy has turned the model off. The dashboard shows a Disabled badge. |
| Not available | not_available | The route does not offer the model in the proxy's region. The dashboard shows Not available in the region. |
Clients name models in their own format, and Multi-Router maps each name to the catalog model and then to the model id of the proxy's route and region. For example, every one of these names resolves to Claude Sonnet 4.6:
| Name the client sends | Model id sent to the provider |
|---|---|
claude-sonnet-4-6 | claude-sonnet-4-6 on the Anthropic API and Vertex AI routes |
us.anthropic.claude-sonnet-4-6 | global.anthropic.claude-sonnet-4-6 on Bedrock (Global) |
anthropic/claude-sonnet-4.6 | jp.anthropic.claude-sonnet-4-6 on Bedrock (Geo) in ap-northeast-1 |
anthropic.claude-sonnet-4-6 | anthropic.claude-sonnet-4-6 on Bedrock (In-region) |
Because the route and region decide where inference runs, a client's Bedrock inference profile prefix or Vertex location does not change it. GET /v1/models with the proxy's X-MR-Router header lists the served models with the model ids of the proxy's route.
Custom route
The Custom route serves the members of a model group, each on the provider, variant and region the member names, so one Claude Proxy can serve one model on Anthropic and another on AWS Bedrock in the EU. Every member must be a Claude model the Claude Proxy serves, appear once, and name a variant and a region. The Custom route uses organization credentials with one provider key for each member, set in routing.model_keys, and has no region of its own. A request for a model outside the group is refused. Each endpoint serves only its own provider, so a client reaches the group members on the provider of the endpoint it calls: a Claude Code client set up for Bedrock reaches the members on AWS Bedrock. The model group is set with routing.model_group when the proxy is created, or with PATCH /v1/routers/{id}. See Model Group.
Request handling
Multi-Router forwards the client's request body unchanged, with two exceptions: it replaces the model name with the model id of the route when they differ, and on the Anthropic API route in the us region it adds "inference_geo": "us" when the request omits it. It forwards the client's headers, and removes cookies, forwarding headers and every x-mr- header; with Organization Key it also replaces the client's credential headers and adds an anthropic-version header when the client sends none. The query string is forwarded as sent, except one that carries a Multi-Router API key or a reserved provider parameter, which returns 400. Requests are sent to the provider once, without retries, and the provider's status and error body are returned to the client.
| Limit | Value |
|---|---|
| Request body | 32 MB |
| Time to the provider's response headers | 300 seconds |
Settings
A Claude Proxy's settings are its routing configuration (route, region, credential source, provider key and disabled models), its request logging, and its name, description and tags. Request logging records each inference request in Traffic according to the proxy's Request Logging settings; see Router Settings and Observability. Budgets apply to a Claude Proxy and its models. Prompt bindings, parameter defaults and model source apply to static routers and have no effect on a Claude Proxy.
Creating a Claude Proxy
To create a Claude Proxy in the dashboard:
- On the Routers page, select New router, and under Proxies choose Claude Proxy.
- Under Details, enter a Name, and optionally a Description and Tags.
- Under Routing, choose a Route and a Region, turn off any models the proxy should not serve, and choose Developer Credentials or Organization Key with a provider key.
- Under Review & create, check the Route, Region (or Model group on the Custom route), Models and Credentials, and create the proxy.
The Routing card shows the models the proxy serves with their model ids and prices, the client endpoint for the route, and the Claude Code setup. To create a Claude Proxy with the API, send POST /v1/routers with kind claude_proxy and its routing: route, region, credential_source, provider_key_id, model_group, model_keys and disabled_models. Static router fields, such as prompt and parameter_defaults, are refused:
A Claude Proxy created without routing uses the Anthropic API route in the global region with developer credentials. Its routing is read and changed with the following endpoints:
| Method | Path | Description | Scope |
|---|---|---|---|
| GET | /v1/routers/{id} | The proxy, with its routing: route, region, credential source, provider key, model group, model keys and disabled models. | routers:read |
| GET | /v1/routers/{id}/routes | Every model the proxy serves, with its provider, variant, region and provider key. | routers:read |
| PATCH | /v1/routers/{id} | Changes the routing fields sent. A route switch sends the fields the new route needs in the same request. | routers:write |
Policy-managed Claude Proxies
A policy-managed Claude Proxy is one Multi-Router creates when a person assigned to a tools policy sets up Claude Code or Claude Desktop in the Portal, one for each tool, with routing taken from the policy. These proxies carry the reserved person: and policy: tags and are managed through the policy: changing, enabling, disabling or deleting one directly returns 409 policy_managed. See Self-Service Provisioning.
Traffic and pricing
Traffic records one row for each inference request through a Claude Proxy, with the name the client sent, the model and model id that served it, the provider, variant and region, and the cost. Token counting requests are not recorded. Cost is computed from the catalog price of the route and region; on the Anthropic API route it follows the region Anthropic reports the request ran in.
Errors
Creating or changing a Claude Proxy returns the following errors, each with status 400:
| Error | Cause |
|---|---|
route_not_found | The route is not in the catalog, or the routing settings are missing. |
region_not_on_route | The route requires a region, the route does not serve the region, or the Custom route names a region. |
credential_not_allowed | Developer credentials are used on a route other than Anthropic API, or the Custom route names a single key or developer credentials. |
key_not_found | Organization credentials name no key, a key not in the organization, or a disabled key, or a Custom member has no key. |
key_vendor_mismatch | The key belongs to a different provider than the route or member. |
key_region_mismatch | A Bedrock API key was created for a region other than the proxy's region, or a Bedrock or Vertex key has invalid settings. |
group_not_found | The Custom route names no model group or a model group not in the organization, or a model group is set on another route. |
group_member_not_served | The model group has no members, a member is not a served Claude model, appears twice, lacks a variant or region, or is not served at its provider, variant and region, or member keys are set on another route or name a model the proxy does not serve. |
all_models_disabled | Every model the route serves in the region, or every group member, is disabled. |
disabled_not_in_models | The disabled list names a model the proxy does not serve, or names one twice. |
catalog_section_missing | The catalog has no Claude Proxy section. |
Requests through a Claude Proxy return the following errors, in the format of the endpoint:
| Status | Cause |
|---|---|
| 404 | The model is unknown, retired or deprecated, disabled on the proxy, not available on the route in its region, outside the Custom route's model group, or served by another endpoint's provider. |
| 403 | The Claude Proxy is disabled. |
| 503 | The proxy's provider key is missing or disabled, its route or the catalog's Claude Proxy section is missing, its model group is missing, a Custom member has no key, or a Vertex access token is not ready. |
| 502 | The provider could not be reached or timed out. |
| 429 | The API key's rate limit or a budget refused the request. |
| 413 | The request body is over 32 MB. |
| 405 | A method other than POST was used on the Bedrock or Vertex endpoint. |
| 400 | The X-MR-Router header is missing on the Bedrock or Vertex endpoint, the Multi-Router API key was sent in a forwarded header, the query string carries a Multi-Router API key or reserved parameter, or an inference_geo conflicts with the proxy's region. |