Skip to content
CortexDocs

Set up Gateway for your organization

Add your company's provider key, connect a client and verify your first request, then bring in your team.

Gateway is your organization's URL for model requests. Clients send requests to it with a personal Cortex key, and Gateway calls the enabled provider with your company's key. Gateway does not require Defender.

Gateway HomeOpen in Cortex

Before you begin

Required

  • Organization

    Create your organization if your company is not on Cortex yet.

  • Admin access

    An admin adds the provider key. Members only need a personal key.

  • Provider key

    Your company's API key for a model provider, such as Anthropic or OpenAI.

Set up Gateway

  1. Open Gateway. In the header, open View and select Gateway, or select Gateway in the left menu if your workspace shows it there.

  2. Add your provider key. Open Routing, then Providers, and select Add connection. Select Configure on the provider, enter your company's key for that provider in API key, make sure Enabled is on and select Save connection. See provider setup.

    Open Routing, then Providers, and select Add connectionOpen in Cortex
    Enter your company's key, keep Enabled on and save the connectionOpen in Cortex

  3. Choose your client. Open API Keys and select Connect a client. Choose Claude Code, Codex, Cursor, Anthropic SDK, OpenAI SDK or curl.

    Choose a client, add your API key and copy the client setupOpen in Cortex

  4. Add your API key. Under Add your API key, paste an existing key into Paste API key, or select Create a new key and store the key it shows in your approved secret manager.

  5. Send one request. Copy the client setup shown, then start the client or send the curl test request. Use an exact model ID that Gateway routes for your organization. See the model catalog.

Verify your first request

Open API Keys and find the key you used. Admins select My Keys. Last used shows when Gateway last accepted the key. If you used it in the previous few minutes, it can show that earlier time.

Last used shows when Gateway last accepted the keyOpen in Cortex

If you follow the Setup guide, its Gateway part has a First request check. It shows Received with the key's name after Gateway receives a request from a key you created during that part. A key that already existed does not count.

The First request check in the Setup guideOpen in Cortex

Done when the provider responds and Last used shows your request on API Keys. These confirm the request reached Gateway, not that it appears in Atlas or Usage. If the request fails, see Troubleshoot the first request and Troubleshoot refusals.

Bring in your team

Roll out Gateway. Ask each member to sign in, open their profile and select Settings, then select Create API key under Devices & API keys and follow the client setup.

On this page

Before you beginSet up GatewayVerify your first requestBring in your team