{"version":"2.1.285","anchor":"provider-auth-probes-and-clients-unify-headers-x-api-key-fo","canonical_anchor":"provider-auth-probes-and-clients-unify-headers-x-api-key-fo","heading":"Bedrock, Mantle and Vertex connections share headers and can send your API key","tier":"notice","area":"Third-Party Providers","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285\/e\/provider-auth-probes-and-clients-unify-headers-x-api-key-fo","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285","markdown":"### Bedrock, Mantle and Vertex connections share headers and can send your API key\n\nBedrock, Mantle and Vertex clients now share one set of headers and add an `X-Api-Key` header from `ANTHROPIC_API_KEY` unless one is set\n\n**Unclear.** Whether `CLAUDE_CODE_SKIP_AWS_CRED_CACHE` still has any effect, and how the new credential lookup caches credentials, is not clear.\n\n**What**\n\nClaude Code can talk to Claude through third-party providers such as Amazon Bedrock, Mantle and Google Vertex. How it connects to them changed:\n\n- The Bedrock, Mantle and Vertex connections now add a shared set of headers (extra labels sent with each request).\n\n- If `ANTHROPIC_API_KEY` is set, its value is sent as an `X-Api-Key` header, unless a header of that name is already present. This is useful when a gateway sits between Claude Code and the provider.\n\n- The checks that test whether Bedrock and Mantle are reachable now report what went wrong, not only yes or no.\n\n- The special handling for `CLAUDE_CODE_SKIP_AWS_CRED_CACHE`, which used to skip the cached AWS credentials, has been replaced by one shared way of looking up AWS credentials.\n\n**Why**\n\nIf you use a third-party provider, how Claude Code authenticates may behave differently. This matters most if you have `ANTHROPIC_API_KEY` set or rely on `CLAUDE_CODE_SKIP_AWS_CRED_CACHE`.\n\n- Area: Third-Party Providers\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}