> ## Documentation Index
> Fetch the complete documentation index at: https://docs.gatelit.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Providers

> Configure provider API keys. Org-scoped BYOK with fallback to gateway defaults.

The dashboard stores provider API keys at the organisation level. When the gateway receives a request, it uses the org's key for the requested provider.

## Adding a provider key

Go to **Settings → Providers**, pick a provider, and enter your API key.

| Provider  | Key format                | Where to get it                                                      |
| --------- | ------------------------- | -------------------------------------------------------------------- |
| OpenAI    | `sk-proj-...` or `sk-...` | [platform.openai.com/api-keys](https://platform.openai.com/api-keys) |
| Anthropic | `sk-ant-api03-...`        | [console.anthropic.com](https://console.anthropic.com)               |
| Google    | `AIza...`                 | [aistudio.google.com/apikey](https://aistudio.google.com/apikey)     |
| Mistral   | `...`                     | [console.mistral.ai/api-keys](https://console.mistral.ai/api-keys)   |

Keys are encrypted at rest.

## Rotating keys

1. Get a new key from the provider's console
2. Update it in the dashboard
3. The old key stops working immediately

No deploy needed. No restart needed.

## Custom providers

For OpenAI-compatible providers not in the built-in catalog, add a custom provider under **Org Settings → Custom Providers**. You specify:

* A name (appears in model pickers as `custom-provider/model-id`)
* A base URL (the provider's API root)
* An API key
* Optional: custom auth header name (defaults to `Authorization: Bearer <key>`)

Custom providers are org-scoped and don't affect other orgs.

<Frame>
  <img src="https://mintlify.s3.us-west-1.amazonaws.com/gatelit/images/dashboard/providers.png" alt="Provider settings" />
</Frame>