Gateways
Route your provider's model calls through a proxy for monitoring and policy.
A gateway connection is an optional proxy that your provider calls are routed through. Instead of an agent calling the model directly, the call goes through the gateway first — giving you a central place for monitoring, rate limiting, and access policy across all the model traffic in a project.
Available gateways
Apigee
Route model requests through Google's Apigee API gateway.
How a gateway fits in
A gateway sits between your agents and the model provider:
Agent ──▶ Gateway (Apigee) ──▶ Provider (OpenAI / Anthropic / …) ──▶ ModelYou attach a gateway when setting up a provider connection — see the optional gateway step in Connecting a provider. Once attached, every call that provider connection makes is proxied through the gateway automatically. Agents and workflows don't change; they still just point at the provider connection.
Connecting a gateway
Start a new gateway connection
Under Forge → Connections, choose the gateway and click New connection.
Name it and configure
Give it a name and provide its configuration — for Apigee, the proxy base URL and the API key it expects (and, if needed, the header that key is sent in).
Save, then attach it
Save the connection, then select it on the provider connections whose traffic you want routed through it.