Gateway
The Gateway area of the console manages how agents reach language models and external tool servers.
The Gateway area of the console governs the two ways agents reach the outside world: language models (model routing) and external tools (MCP servers). Both are org-level concerns — they apply across workspaces.
The Model Routing and MCP Servers screens ship disabled by default and may not be enabled in your deployment. The underlying behavior they describe — platform-managed model endpoints, tools admitted through the org registry — applies either way. The accounts tools act with are managed separately, per workspace, under Build → Connected Accounts — see Connected Accounts.
In this section
Model routing
How agent model calls are routed: platform-managed model endpoints and the provider/model set agents can choose from.
MCP servers
External tool servers agents can use, and how tools become available to agents through registry admission.
Connected Accounts
The identities tools act with: named workspace service connections and each user's own connected accounts.
Usage and quotas
Token and execution metrics on the Usage screen, and windowed token quotas that gate agent invocations at admission time.
Model routing
How agent model calls are routed — platform-managed model endpoints, the providers and models offered at agent creation, and what the Gateway screen manages.