Skip to main content
On the Providers screen, an administrator adds the company API keys for the supported LLM providers. When your own key is active, the AI traffic of your organization goes through your key and not through the shared platform key. You then see the usage and the cost in the dashboard of your provider. To open the screen, go to the Admin group in the sidebar and click Providers. Only administrators see it. The screen has two tabs. API Keys holds your own keys. Advanced holds the custom LLM endpoints.

​
Key order

RelayHub uses the first key that applies, in this order:
  1. Custom provider: a custom LLM endpoint that is set as the default.
  2. Your own key: the key that you added on the API Keys tab.
  3. Platform key: the shared RelayHub key.

​
Supported providers

The API Keys tab has one row for each provider: OpenAI, Anthropic, Google and xAI. See Supported Models for the full list of models.

​
Add an API key

1

Open the API Keys tab

In the Admin group, click Providers. Stay on the API Keys tab.
2

Select a provider

On the row of the provider, click Add Key.
3

Enter the key

Paste the key into the API Key field. RelayHub encrypts the key before it stores it.
4

Validate and save

Click Validate & Save. RelayHub sends a small test call to the provider. It stores the key only when the provider accepts it.
After you save the key, it is active. The traffic of your organization to that provider goes through your key.

​
Platform fallback

Each key has the setting Allow platform fallback on failure. It is on by default. It controls what RelayHub does when your key fails with an authentication error or a quota error (401 or 429).
  • On: RelayHub sends the failed request again with the platform key, and the chat continues. After three failures in a row, the row shows the Degraded status and the message Key over quota, with the failure count and the last error. Calls go to the platform key until you update or revalidate the key.
  • Off: RelayHub shows the error and does not use the platform key. Use this setting if your policy does not let traffic go through the platform keys.
RelayHub records each fallback and each change of key status in the Audit Log.

​
Manage keys

Each row shows a status: Active, Paused, Degraded or No Key. A row with a key also shows the last characters of the key and the time of the last validation. The row has these controls:
  • Pause provider or Activate provider: stop a key and keep it. When a key is paused, the traffic uses the platform key.
  • Revalidate key: test the key again. If the key works, the Degraded status clears.
  • Update key: replace the key with a new key. The old key is deleted.
  • Remove key: delete the key. The provider then uses the platform key.

​
Key security

RelayHub encrypts the keys at rest. After you save a key, RelayHub never shows the full key again. It shows only the last characters.
  • The keys belong to your organization. Other organizations cannot see them.
  • The screen never shows the full key after you save it.
Use your own keys when you must see the AI cost directly, when you want your own rate limits, or when your policy requires that you own the API keys.