inferenceProvider to anthropic and supply an API key as described below. This is the first-party path: inference goes straight to Anthropic rather than to a Claude deployment on Google Cloud’s Agent Platform, Amazon Bedrock, or Microsoft Foundry.
When
inferenceProvider is anthropic, inference traffic goes to Anthropic’s API endpoints rather than staying within your cloud provider. The data-residency and compliance statements on these pages do not apply to this option.Choose an authentication approach
There are three options. With neither a static key nor a credential helper configured, each user sees Sign in with Claude Console on first launch: the app opens the browser, the user signs in and selects a Claude Console (API) organization, and the app creates a personal API key for them and stores it encrypted on the device until it is revoked in Console; usage is billed to that Console organization. Alternatively, place a static API key in the managed configuration asinferenceAnthropicApiKey, or, where static keys aren’t permitted, set inferenceCredentialHelper to an executable that fetches a short-lived credential at runtime; see Write a credential helper. Browser sign-in reaches platform.claude.com in addition to api.anthropic.com.