Skip to main content

Roll out gateway clients

After you deploy the gateways, direct users to the setup instructions in the console. The console supplies the endpoints and client-specific configuration for your deployment.

Choose the gateway endpoints​

Clients can use either or both gateways:

  • Send OpenAI-compatible model traffic to the AI Gateway.
  • Send MCP tool calls to the Connector Gateway.

Users can open Setup in each gateway area of Your workspace for deployment-specific instructions. This keeps endpoint details out of rollout documentation and supports the clients listed in the console.

Choose an authentication method​

  • Use browser-based sign-in for interactive clients. The session identifies the caller through your corporate identity provider.
  • Use a virtual API key for scripts, scheduled jobs, continuous integration, and other clients without a browser flow. Requests remain attributed to the key owner.

Prepare access before rollout​

Before distributing the setup instructions:

  • Assign an AI Gateway budget to each user or group that will send model traffic.
  • Grant directory groups access to the required connectors.
  • Tell users that connectors requiring OAuth prompt them to authenticate through Your workspace or during their first client connection.

Next steps​