Gateways
Route your connections' calls through a proxy for monitoring and policy.
A gateway connection is an optional proxy that other connections' calls are routed through. Instead of calling the service directly, the call goes through the gateway first — giving you a central place for monitoring, rate limiting, and access policy across a project's traffic.
Available gateways
Apigee
Route requests through Google's Apigee API gateway.
How a gateway fits in
A gateway sits between Compass and the service it's calling:
Agent ──▶ Gateway (Apigee) ──▶ Provider (OpenAI / Anthropic / …) ──▶ ModelGateways apply to connections that talk to an HTTP API at a base URL: the Anthropic, OpenAI, and LM Studio providers, and custom OpenAPI integrations. The Gateway step appears on every connection form, but only takes effect for those. Once a connection is routed through a gateway, its calls at run time go through the proxy (the checks made while you save it go direct). Agents and workflows don't change — they still point at the same connection.
Connecting a gateway
Start a new gateway connection
Under Studio → Connections, click Apigee, then New connection.
Configure it
Give it a Connection name, then fill in Configuration: the Proxy base
url and the Api key Apigee expects. If the key goes in a header other than
x-apikey, set Api key header under Advanced. The gateway's Api key is a
configuration value, not a credential: it's stored as plain config and shown when
you edit the gateway.
Save, then attach it
Click Create connection. Then edit each connection whose traffic should flow through it and pick the gateway under Gateway → Route through gateway.
To stop routing a connection through the gateway, edit that connection and change its Gateway choice. A gateway can't be deleted while any connection is routed through it; the delete dialog lists them.