By default, Gatelit routes requests through shared provider keys managed by Gatelit. With BYOK (Bring Your Own Key), your organization supplies its own provider API keys. All requests from your org are then routed through your accounts — giving you full control over rate limits, spend visibility, and provider billing.
Supported providers
Adding a provider key
- In the Gatelit dashboard, navigate to Settings → Provider Keys.
- Select the provider you want to configure.
- Paste your API key into the input field and click Save.
Once saved, all requests from your organization automatically use your key for that provider. No code changes are required on the client or gateway side.
You can add a key for some providers and rely on Gatelit’s shared keys for others. For example, you might supply your own OpenAI key while continuing to use the shared Anthropic key.
Embedding your org ID in signed tokens
When you issue signed tokens from your backend, include your organization’s orgId so the gateway can look up your org’s provider keys for every request:
The orgId is embedded in the signed token payload. The gateway reads it on every request to resolve which provider keys to use for your organization. Without orgId, the gateway falls back to Gatelit’s shared keys.
Security
Provider keys are encrypted at rest and are never exposed in plain text after storage. You cannot retrieve a stored key from the dashboard — if you need to rotate it, delete the existing entry and add the new key.
Deleting a provider key
To remove a key, navigate to Settings → Provider Keys, find the provider entry, and click Delete. After deletion, requests for that provider automatically fall back to Gatelit’s shared key.