Skip to main content
Unlisted page
This page is unlisted. Search engines will not index it, and only users having a direct link can access it.
Version: 11.3.0

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​

  1. Open All Connectors → Add Connector → AI Providers → Anthropic.
  2. Optional: Enter the Admin API Key. Without it, the form warns that agent identity syncing is unavailable.
  3. Optional: Change the Base URL or API Version only if your Anthropic configuration requires different values.
  4. Click Next.
  5. Choose the onboarding mode.
  6. Click Create Connector. The connector opens.

What the Overview Tab Shows​

The connector's Overview tab has these fields.

FieldMeaning
Name, EnabledThe connector's name. Enabled turns traffic on or off
EndpointThe upstream host and port (api.anthropic.com:443). Click Change to point at a private or regional deployment
Allow Channel connectionsLets agents use this gateway as a channel for real-time supervisor messaging. On by default. See Having Conversations with Your Agent
Anthropic Admin APIThe 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 ModeWhat happens to an agent's first request. See Onboarding Mode
RoutesThe 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.