Conversation
tigent
bot
added
ai/provider
Collaborator
Author
This stack of pull requests is managed by Graphite. Learn more about stacking. |
gr2m
approved these changes
Apr 10, 2026
gr2m
added
the
backport
shaper
deleted the
04-10-feat_provider_anthropic_add_support_for_inference_geo_provider_option
branch
vercel-ai-sdk bot
pushed a commit
that referenced
this pull request
Apr 11, 2026
…ion (#14339) ## Background Anthropic supports data residency controls through an `inference_geo` parameter that allows developers to specify where model inference should run for compliance and data governance requirements. See https://platform.claude.com/docs/en/build-with-claude/data-residency ## Changes Added support for the `inferenceGeo` provider option to the Anthropic provider, allowing users to control where model inference runs by specifying either `'us'` (US-only infrastructure) or `'global'` (any available geography, default). The implementation includes: - New `inferenceGeo` option in `AnthropicLanguageModelOptions` with proper validation - Request body mapping to Anthropic's `inference_geo` parameter - Documentation with usage examples - Test coverage for the new functionality - Example implementation demonstrating the feature ## Manual Verification Tested the feature by running the provided example with `inferenceGeo: 'us'` and verified that the parameter is correctly passed to Anthropic's API in the request body as `inference_geo`. ## Checklist - [x] Tests have been added / updated (for bug fixes / features) - [x] Documentation has been added / updated (for bug fixes / features) - [x] A _patch_ changeset for relevant packages has been added (for bug fixes / features - run `pnpm changeset` in the project root) - [x] I have reviewed this pull request (self-review)
vercel-ai-sdk
bot
removed
the
backport
Contributor
|
✅ Backport PR created: #14344 |
Contributor
|
🚀 Published in:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Background
Anthropic supports data residency controls through an
inference_geoparameter that allows developers to specify where model inference should run for compliance and data governance requirements. See https://platform.claude.com/docs/en/build-with-claude/data-residencyChanges
Added support for the
inferenceGeoprovider option to the Anthropic provider, allowing users to control where model inference runs by specifying either'us'(US-only infrastructure) or'global'(any available geography, default).The implementation includes:
inferenceGeooption inAnthropicLanguageModelOptionswith proper validationinference_geoparameterManual Verification
Tested the feature by running the provided example with
inferenceGeo: 'us'and verified that the parameter is correctly passed to Anthropic's API in the request body asinference_geo.Checklist
pnpm changesetin the project root)