Data residency changed Anthropic, Jul 3, 2026
Anthropic · Jul 3, 2026 · 3 added, 3 removed · found in an Internet Archive capture
- Added: The inference_geo parameter is available on the Claude API (first-party) and Claude Platform on AWS . On Amazon Bedrock and Google Cloud, the inference region is determined by the endpoint URL or inference profile, so inference_geo is not applicable. On Claude in Microsoft Foundry , inference_geo is likewise not applicable: deployments hosted on Azure can instead use the US Data Zone Standard deployment type, which keeps inference within the United States. The inference_geo parameter is also not available through the OpenAI SDK compatibility endpoint .
- Removed: The inference_geo parameter is available on the Claude API (first-party) and Claude Platform on AWS . On Amazon Bedrock, Vertex AI, and Microsoft Foundry, the inference region is determined by the endpoint URL or inference profile, so inference_geo is not applicable. The inference_geo parameter is also not available through the OpenAI SDK compatibility endpoint .
- Added: This pricing applies to the Claude API (first-party) and Claude Platform on AWS. On Claude in Microsoft Foundry, the same 1.1x multiplier applies to deployments hosted on Azure that use the US Data Zone Standard deployment type. Partner-operated platforms (Bedrock and Google Cloud) have their own regional pricing. See Data residency pricing for details.
- Added: If you have a Priority Tier commitment, the 1.1x multiplier for US-only inference also affects how tokens are counted against your Priority Tier capacity. Each token consumed with inference_geo: "us" draws down 1.1 tokens from your committed TPM, consistent with how other pricing multipliers (such as prompt caching) affect burndown rates.
- Removed: This pricing applies to the Claude API (first-party) and Claude Platform on AWS. Partner-operated platforms (Bedrock and Vertex AI) have their own regional pricing. See Data residency pricing for details.
- Removed: If you use Priority Tier , the 1.1x multiplier for US-only inference also affects how tokens are counted against your Priority Tier capacity. Each token consumed with inference_geo: "us" draws down 1.1 tokens from your committed TPM, consistent with how other pricing multipliers (such as prompt caching) affect burndown rates.
About this change
- Page
- platform.claude.com/docs/en/manage-claude/data-residency
- Kind
- Documentation
- Text hash
- 897b0e0fd235 to a0009e3c95dd
- Dated by
- the first Internet Archive capture sampled that shows the new text; the change happened on or before this date