Anthropic
An Anthropic connector routes Claude requests through HYPR AgentPass™, from Claude Code, other local agents and cloud agents. Each request is attributed, evaluated by policy and recorded.
Before You Begin
- An Anthropic account with API access
- Optional: an Anthropic Admin API key. The gateway uses it to manage per-agent keys and synchronize agent identities. Without it, the connector still routes and observes traffic, and you can add the key later
- The gateway's public origin, which your agents point at
Create the Connector
- Open All Connectors → Add Connector → AI Providers → Anthropic.
- Optional: Enter the Admin API Key. Without it, the form warns that agent identity syncing is unavailable.
- Optional: Change the Base URL or API Version only if your Anthropic configuration requires different values.
- Click Next.
- Choose the onboarding mode.
- Click Create Connector. The connector opens.
What the Overview Tab Shows
The connector's Overview tab has these fields.
| Field | Meaning |
|---|---|
| Name, Enabled | The connector's name. Enabled turns traffic on or off |
| Endpoint | The upstream host and port (api.anthropic.com:443). Click Change to point at a private or regional deployment |
| Allow Channel connections | Lets agents use this gateway as a channel for real-time supervisor messaging. On by default. See Having Conversations with Your Agent |
| Anthropic Admin API | The base URL, API version and write-only admin API key. Click Update Key to replace the key. Used to sync the account's API keys into agent identities |
| Onboarding Mode | What happens to an agent's first request. See Onboarding Mode |
| Routes | The request paths the gateway forwards, such as POST /v1/messages.* (chat completions) and POST /channel-bootstrap/.* (channel session bootstrap) |
Agents Tab
Sync from Anthropic imports the account's API keys as agent identities, with a name, type, owner and status for each. Synced identities appear on the Agent identities page. See Agent identity.
Point an Agent at It
A local agent sets its Anthropic base URL to the gateway's public origin. The connector name is not part of the URL: the gateway matches the request path, such as /v1/messages, to the connector's routes. See Onboarding Your Agent.
On workstations under the Endpoint Guard, you can route agents here with no change on the agent side. See Routing and Observation.
Related
- Connectors — the tabs every connector shares
- Governing Inference Traffic — rules on what the model is asked and answers
- Anthropic Cloud Agents — agents Anthropic hosts, governed through a separate Cloud Agents connector