What
The gateway's configuration schema for upstream providers (Bedrock, AnthropicAws, Vertex, and Foundry) now supports a headers field, letting an administrator attach custom HTTP headers to a specific upstream provider's requests alongside its existing authentication settings.
Why
This gives self-hosted gateway operators more control over outgoing requests to each provider, for example to satisfy provider- or network-specific header requirements.
Names in the bundleheaders
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Confirmed since
Anthropic's documentation has since written up headers, on overview.
| **Beta** | Preview features used for gathering feedback and iterating on a less mature use case. Availability may be limited, including through sign-up requirements or waitlists, and may not be publicly announced. Features may change sig…build-with-claude/overview see the edit
Added since
A small documentation edit on computer-use-tool touched a line naming headers after this was published.
Existing `computer_20251124` integrations keep working on the models listed for it under [Earlier tool versions](https://platform.claude.com/docs/en/agents-and-tools/tool-use/computer-use-tool#earlier-tool-versions), and earlier tool versi…agents-and-tools/tool-use/computer-use-tool see the edit
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agrees
A small documentation edit on computer-use-tool touched a line naming headers after this was published.