Skip to main content
Claude Tag is in public beta. Features and behavior described here may change before general availability.
If a service you want to connect (a data warehouse, an internal API, a GitHub organization with an IP allow list) restricts access by source IP, add Anthropic’s egress range to its allowlist. Hand this page to the team that manages it.

​
Add Anthropic’s egress range to your allowlist

Requests from Claude to your services originate from Anthropic’s network. To let them through, add Anthropic’s published egress range to the service’s allowlist:
The authoritative list is Anthropic’s published IP addresses; check it when you create the rule. The range is shared across Anthropic services, and dedicated per-organization egress addresses aren’t available, so the allowlist entry admits Anthropic’s infrastructure as a whole. Your credential’s allowed websites are what scope which of your systems Claude can call. For GitHub, the repositories you granted to the channel do that scoping instead, except that git may still be able to clone public repositories you didn’t grant; see Network egress.
If your Google Cloud project uses VPC Service Controls, an IP-based access level doesn’t admit Claude’s queries through the BigQuery connection. See Allow the connection through a VPC Service Controls perimeter on the BigQuery page.

​
Internet reachability

A connected service must accept traffic from the internet (restricted by IP allowlist if you like). A service reachable only inside your private network can’t be connected; private networking such as PrivateLink or VPC peering is not supported.
In an Anthropic-hosted environment, every request from a channel’s sandbox to your service passes through Agent Proxy, which carries HTTP and HTTPS only. A service reachable only over another protocol, such as SSH or a database’s native wire protocol, can’t be connected; put an HTTP API in front of it instead.

​
IP allowlist vs. allowed websites

The IP allowlist on your service and the allowed websites on a connection are opposite sides of the same boundary:

​
Events and webhooks

Events from connected services, like GitHub activity, are delivered directly to Anthropic, so there is no inbound listener to configure on your side.