# Geo-Aware Routing for Agentforce Coworker

Agentforce Coworker follows the same geo-aware routing rules as the broader Agentforce platform for AI inference - the process of running a query through an AI model to generate a response.

Two conditions can route Agentforce Coworker's inference to US-based infrastructure:

- Your region doesn't yet have a local deployment for a given model.
- A regional outage or capacity event triggers an automatic fallback.

To stop automatic rerouting to the US or other regions for supported models, see Enable In-Region Model Requests Only at the end of this page.

## Models and Their Geo-Aware Routing

Agentforce Coworker uses these model components when searching and generating answers. The Routing column shows where each model's requests go when no local deployment exists or when a fallback triggers. To stop automatic rerouting to the US or other regions, see Enable In-Region Model Requests Only.

| Model             | Model ID                       | Provider                 | Role in Coworker                                         | Routing                                                                                                                                                                                                                                       |
| :---------------- | :----------------------------- | :----------------------- | :------------------------------------------------------- | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Claude Haiku 4.5  | BedrockAnthropicClaude45Haiku  | Anthropic on AWS Bedrock | Classifies and routes queries internally within Coworker | See [Geo-Aware Routing for Anthropic](https://help.salesforce.com/s/articleView?id=ai.generative_ai_platform_geo_aware_routing_anthropic.htm&language=en_US&type=5)                                                                           |
| Claude Sonnet 4.6 | BedrockAnthropicClaude46Sonnet | Anthropic on AWS Bedrock | Synthesizes answers                                      | See [Geo-Aware Routing for Anthropic](https://help.salesforce.com/s/articleView?id=ai.generative_ai_platform_geo_aware_routing_anthropic.htm&language=en_US&type=5) (see Note 1)                                                              |
| Amazon Nova Micro | amazon.nova-micro-v1:0         | Anthropic on AWS Bedrock | Improves search ranking                                  | Only used in regions that have this model available locally. See [Geo-Aware Routing for Anthropic](https://help.salesforce.com/s/articleView?id=ai.generative_ai_platform_geo_aware_routing_anthropic.htm&language=en_US&type=5) (see Note 2) |

- **Note 1:** The [Geo-Aware Routing for Anthropic](https://help.salesforce.com/s/articleView?id=ai.generative_ai_platform_geo_aware_routing_anthropic.htm\&language=en_US\&type=5) doc only mentions Claude Haiku 4.5. Claude Sonnet 4.6 and Amazon Nova Micro are also Anthropic models on AWS Bedrock and route the same way as Claude Haiku 4.5.
- **Note 2:** For regions that do not have Amazon Nova Micro being served locally, this model isn't used.

## Enable In-Region Model Requests Only

When a request fails to process in your designated region, the default behavior for models is to automatically re-route the request to another region to avoid returning an error. You can change this behavior in your org for some models by turning on “Enable In-Region Model Requests Only” from Einstein Setup.

:::warning
Claude Haiku 4.5 and Sonnet 4.6 aren't available in-region on AWS in Brazil, Canada, India, Israel, Korea, Singapore, and Switzerland. Turning on the Enable In-Region Model Requests Only toggle causes Claude Haiku 4.5 and Sonnet 4.6 requests from those regions to fail. In any region, if in-region endpoints are overloaded, requests return an error instead of routing to a secondary region. For compliance questions, contact your Salesforce account executive.
:::

1. Make sure that Data 360 is turned on. Data 360 is automatically provisioned when a Data 360 license is added to your Salesforce org. See [Turn On Data 360](https://help.salesforce.com/s/articleView?id=data.c360\_a_setup_provision.htm\&language=en_US\&type=5).
2. From Setup, go to Einstein Setup.
3. Turn on **Enable In-Region Model Requests Only**.