Skip to main content
This guide is for the operator running the gateway. By the end you’ll have a provider connected and an API key you can hand to an app or a teammate.
You’ll need the admin portal URL and an admin key. You get both when we set up your gateway. Don’t have one yet? Reach out to us and we’ll get one running for your team.
1

Sign in to the admin portal

Open https://your-gateway.example.com/admin and enter your admin key.
2

Connect a provider

Go to Config and add a provider under Providers:
  • Name: a label you choose, such as openai.
  • Base URL: the provider’s API root, such as https://api.openai.com.
  • Format: one of openai, anthropic, or azure_openai.
  • API key env var: the name of the environment variable that holds the provider’s key, such as OPENAI_API_KEY.
The provider’s secret lives in an environment variable on the gateway host, not in the portal. We set these during deployment, so coordinate with us if you need a new one. For every option, including Azure and routing between providers, see Connect providers.Save your changes. The gateway picks up the new config right away, with no restart.Connecting a provider on the Config page
3

Create an API key

Go to API keys and create a key. You can give it a name, and attach a user or a team so you can track and govern it later.Copy the key when it appears. It’s shown only once and starts with sk-olga-. Store it somewhere safe.Creating an API key

​
Hand it off

Give the developer two things:
  • The gateway base URL, such as https://your-gateway.example.com/v1.
  • The API key you just created.
That’s everything they need to send traffic. Point them at Make your first request.

​
Next steps

Now that traffic can flow, decide what the gateway should enforce on it.

Set usage limits

Cap spend, requests, or tokens per key or team.

Add guardrails

Block or redact PII and stop prompt injection.