Providers & Models
Regions & Variants
Choose which build of a model serves a request and where it runs, and keep inference within a region or geography.
A variant is one way a provider offers a model, and a region is a location where that variant runs. The variant and region determine the model id sent to the provider, the price, and where inference takes place, which makes them the settings that control data residency, latency and cost. A static router names its variant and can name its region; when the router leaves the region unset, Multi-Router takes it from the provider key or the organization.
Variants
A variant distinguishes offerings of the same model on the same provider that differ in where inference runs, in serving speed, or in the build of the model. Each variant has an id, which routers and the API use, and a display name, which the dashboard shows.
| Variant | Display name | Offered by | Description |
|---|---|---|---|
standard | Standard | Most providers | The provider's ordinary endpoint for the model. |
in_region | In-region | AWS Bedrock | Inference runs only in the AWS region that receives the request. |
geo | Geo | AWS Bedrock | Inference runs within one geography, such as the United States or Europe. |
global | Global | AWS Bedrock | Inference can run in any AWS region, with no data residency guarantee. |
fast | Fast | Fireworks | A higher-throughput serving path, priced above the standard endpoint. |
fp8 | FP8 | Fireworks | An 8-bit quantized build. |
fp8-fast | FP8 Fast | Fireworks | An 8-bit quantized build on the higher-throughput serving path. |
fp4 | FP4 | Together | A 4-bit quantized build. Some Together models are offered only in this variant. |
Snapshots, such as 20251001 | Such as 1 Oct 2025 snapshot | Anthropic, AWS Bedrock, Fireworks, Together, xAI | A specific build of the model. See Snapshots below. |
Snapshots
A snapshot is a variant pinned to one dated build of a model, for applications that need the model's behavior to stay fixed. On Anthropic, the standard variant sends the undated model id, such as claude-haiku-4-5, which Anthropic points at its current build, and the snapshot variant 20251001 sends the dated id claude-haiku-4-5-20251001 at the same price. On AWS Bedrock the snapshot is combined with the inference scope, as in geo-20241022 (Geo, Snapshot 22 Oct 2024) and in_region-20240620, and some Bedrock models offer revisions such as in_region-v1-0. Fireworks, Together and xAI name snapshots by build number, such as 0813 and 0309.
Variant lifecycle
Each variant has its own lifecycle status, so a model can be retired in one variant or on one provider and remain available in another, such as a model retired on Anthropic whose AWS Bedrock geo variant is deprecated. A deprecated variant continues to serve requests, and its responses carry the x-mr-model-deprecated header. A router on a retired variant returns router_variant_retired, and the error message lists the variants of the model that the provider still serves. A router always uses the variant it names, and Multi-Router does not substitute another variant.
Regions
A region is a location where a variant is offered, and each region has its own model id and price. What the region controls depends on the provider:
| Provider | Region values | What the region controls |
|---|---|---|
| AWS Bedrock | AWS regions, such as us-east-1 and eu-central-1 | The AWS region that receives the request. The variant then sets where inference runs. See AWS Bedrock. |
| Google Vertex | global, us, eu and single Google Cloud regions, such as us-east5 | The Google Cloud location that runs the request, which is always the location set on the provider key. See Google Vertex. |
| OpenAI | global, us, eu, ae | us, eu and ae (UAE) send the request to OpenAI's data residency endpoint for that region. Some OpenAI models offer these regions. |
| Anthropic | global, us | us keeps inference in the United States. Some Anthropic models offer this region. |
| xAI | us-east-1, us-west-2, eu-west-1 | A label for the request. Every region of a model has the same price, and xAI serves every region from the same endpoint. |
| Other providers | global | The provider serves the model from a single endpoint. |
Google Vertex locations
Google Vertex offers three types of location, and the models available differ from one location to another:
| Location | Where inference runs |
|---|---|
global | In a location Google chooses. This is usually the lowest price, and some models are offered only here. |
us | Within the United States. |
eu | Within the European Union. |
A single region, such as us-east5, europe-west1 or asia-southeast1 | Only in that region. |
AWS Bedrock
AWS Bedrock offers each model in up to three inference scopes, and the AWS region that receives the request is the router's region or, when the router names none, the provider key's region. The inference scope then determines where the request runs:
| Variant | Where inference runs | Price |
|---|---|---|
in_region | Only in the AWS region that receives the request. | The same as geo in regions that offer both. |
geo | Anywhere within the geography of the receiving region. | The same as in_region in regions that offer both. |
global | In any AWS region. | Usually the lowest of the three. |
The geo variant covers the following geographies. Some regions belong to two geographies, and the model determines which applies: ap-northeast-1, for example, is in the Japan geography for Claude Haiku 4.5 and in the Asia Pacific geography for other models. The Models page shows the model id for each region.
| Geography | AWS regions |
|---|---|
| United States | us-east-1, us-east-2, us-west-1, us-west-2, ca-central-1, ca-west-1 |
| Europe | eu-central-1, eu-central-2, eu-north-1, eu-south-1, eu-south-2, eu-west-1, eu-west-2, eu-west-3, il-central-1 |
| Asia Pacific | ap-east-2, ap-northeast-1, ap-northeast-2, ap-northeast-3, ap-south-1, ap-south-2, ap-southeast-1, ap-southeast-2, ap-southeast-3, ap-southeast-4, ap-southeast-5, ap-southeast-7 |
| Japan | ap-northeast-1, ap-northeast-3 |
| Australia | ap-southeast-2, ap-southeast-4, ap-southeast-6 |
| India | ap-south-1 |
The global variant is also offered in regions outside these geographies, such as sa-east-1, af-south-1, me-central-1 and mx-central-1. The in_region variant is offered for the fewest models; Claude Haiku 4.5, for example, is offered on Bedrock in geo and global only. A Bedrock provider key's region is chosen from the AWS regions listed in the dashboard's key form, and a router can name any region the catalog lists for its variant. A Bedrock API key works only in the region it was created for, so a router that uses one must use that region.
Choosing a variant and region
The variant and region to choose depend on the residency, availability and price the application requires:
| Requirement | Variants and regions |
|---|---|
| Inference in a single region | AWS Bedrock in_region, or a single Google Vertex region. |
| Inference within one geography | AWS Bedrock geo, Google Vertex us or eu, Anthropic us, or OpenAI us, eu or ae. |
| Lowest price and widest availability | AWS Bedrock global, Google Vertex global, or the global region of any other provider. |
| A fixed model version | A snapshot variant. |
| Higher throughput | Fireworks fast or fp8-fast. |
How the region is selected
Multi-Router selects the region for each request from the router, the provider key and the organization, in the following order for each provider:
| Provider | Region used |
|---|---|
| AWS Bedrock | The router's region, otherwise the provider key's region. |
| Google Vertex | The location set on the provider key. |
| OpenAI | The router's region, otherwise global. The router's region, including global when it is unset, must match the region of its provider key. |
| Anthropic | The router's region, otherwise global. |
| xAI | The router's region, otherwise the organization's default region. |
| Other providers | global |
Multi-Router sends every request to the selected region and never switches it to another region. When the model is not offered in the selected region, the request returns region_not_served and the error message lists the regions where the model is available.
Organization default region
The organization default region is the region used by routers on providers whose provider keys carry no region, such as xAI, when the router names no region. Organization admins set it in the Default region card on the Organizations page, which opens from Manage Organizations in the profile menu.
Examples
| Router | Result |
|---|---|
Bedrock geo, model anthropic/claude-haiku-4.5, no region, key region us-west-2 | Sent to us-west-2 with the model id us.anthropic.claude-haiku-4-5-20251001-v1:0. Inference stays in the United States. |
The same router with region ap-northeast-1 | Sent to ap-northeast-1 with a jp. model id. Inference stays in Japan. |
The same router with key region sa-east-1 and no router region | Returns region_not_served, because Claude Haiku 4.5 has no geo offering in sa-east-1. Set a router region, or use global. |
xAI, no region, organization default us-west-2 | Served at us-west-2. With no organization default, returns region_not_served. |
OpenAI, no region, key region eu | Returns key_residency_mismatch, because an unset region means global. Set the router region to eu. |
| Anthropic, no region | Served at global, whatever region the key or the organization names. |
Configuring a router
A static router sets its variant in routing.variant and its region in routing.region. Through the API, both are required for every provider except custom endpoints; in the dashboard, the region can be left to inherit. Multi-Router checks both against the catalog when the router is created with POST /v1/routers or changed with PATCH /v1/routers/{id}, and rejects a variant the provider does not offer for the model and a region the variant does not offer. The offerings and regions of a model are read with GET /v1/catalog/models/{publisher}/{model}; see Catalog.
Dashboard region picker
The dashboard's model picker lists every variant of a model with its display name and description, and the region picker lists every region of the selected variant with its model id and price. The region picker's options depend on the provider:
| Option | Shown for | Meaning |
|---|---|---|
Default (global) | Providers with a default endpoint, such as Anthropic | The provider's ordinary endpoint. When the model is offered in one region only, the option shows that region instead of global. |
| Inherit from the key or org default | AWS Bedrock, Google Vertex and xAI | Leaves the router region unset, so the region is selected for each request as described above. |
| A named region | All regional providers | Sets the router region. For OpenAI, the picker lists only the region that matches the provider key. |
For AWS Bedrock, Google Vertex and xAI, the picker preselects the provider key's region, then the organization default region, then the first region the variant offers, and a note under the picker states which source it used. When neither the router, the key nor the organization supplies a region, the picker warns that requests will fail.
Custom endpoints
Routers on a custom endpoint take no variant. They can set a region only when the model is a custom model registered with regions, and a custom model offered in several regions requires one; see Custom Models & Pricing.
Claude Proxy routes
A Claude Proxy route is the provider and variant a Claude Proxy sends Claude Code and Claude Desktop traffic to, and each route except Custom requires a region that the route serves:
| Route | Provider and variant | Region |
|---|---|---|
| Anthropic API | Anthropic standard | global or us |
| Bedrock (Global) | AWS Bedrock global | An AWS region the route serves |
| Bedrock (Geo) | AWS Bedrock geo | An AWS region the route serves |
| Bedrock (In-region) | AWS Bedrock in_region | An AWS region the route serves |
| Vertex AI | Google Vertex standard | A Vertex location the route serves |
| Custom | The models in a model group | Set on each model in the group |
A Bedrock API key used by a Claude Proxy must have been created for the route's region. See Agents & Editors.
Traffic
Traffic records the variant and the region of every request. The Variant and Region columns are hidden by default and are turned on in the Columns picker, and the request detail view shows both. The Region column shows the region the request was billed at, and for Anthropic this is the region Anthropic reports the request ran in. The x-mr-region response header reports the region the request was sent to.
Errors
Router changes and requests return the following errors for variants and regions:
| Error | Cause | Resolution |
|---|---|---|
missing_variant | A static router is created without routing.variant. | Set a variant. |
missing_field | A static router is created or its routing changed without routing.region. | Set a region. |
invalid_variant | The router names a variant the provider does not offer for the model. The message lists the valid variants. | Set one of the listed variants. |
router_variant_missing | A router created before variants were required has no variant. | Set a variant on the router. |
router_variant_not_found | The catalog no longer offers the router's variant. | Set a variant the catalog offers. |
router_variant_retired | The router's variant is retired. The message lists the variants still served. | Set one of the listed variants. |
region_not_served | The model is not offered in the selected region, or no region is configured. The message lists the available regions. | Set a router region from the list, or change the key or organization default region. |
key_residency_mismatch | An OpenAI router's region differs from the region of its provider key. | Set the router region to the key region, or use a key with the matching region. |
region_not_applicable | A router on a custom endpoint sets routing.region for a model that is not a custom model. | Remove the region. |
region_not_offered | A router on a custom endpoint sets a region its custom model does not offer. | Set one of the custom model's regions. |
router_region_required | A custom model offered in several regions is used by a router with no region. | Set a router region. |
region_not_on_route | A Claude Proxy's region is missing or not served by its route. | Set a region the route serves. |
key_region_mismatch | A Claude Proxy uses a Bedrock API key created for a different region. | Use a key created for the route's region, or an access key (SigV4). |