Skip to main content
The Provider Hub lets admins register their own API keys for supported LLM providers. When a BYOK (Bring Your Own Key) key is active, AI traffic for your organization routes through your key instead of the platform’s shared keys, giving you direct billing control and access to your provider’s usage dashboard. The Provider Hub has two tabs: API Keys for BYOK keys, and Advanced for custom LLM endpoints.

​
How It Works

RelayHub resolves which API key to use in this order:
  1. Custom Provider — If you have configured a custom LLM endpoint, it takes priority
  2. BYOK Key — Your own API key registered in the Provider Hub
  3. Platform Key — RelayHub’s default shared key (usage counted against your subscription)

​
Supported Providers

See Supported Models for the full catalog with capabilities.

​
Adding an API Key

1

Open Provider Hub

Navigate to Provider Hub in the left sidebar (Admin only) and stay on the API Keys tab.
2

Select a provider

Click Add Key on the card for the provider you want to configure (e.g., OpenAI).
3

Enter your API key

Paste your API key. It is encrypted before being stored and is never saved or displayed in plaintext.
4

Validate and save

Click Validate & Save. RelayHub makes a lightweight test call to the provider’s API to confirm authentication before storing the key.
Once saved, the key is active and your organization’s traffic to that provider routes through it.

​
Platform Fallback

Each key has an Allow platform fallback on failure toggle (on by default). It controls what happens when your key starts failing with authentication or quota errors (401/429):
  • Toggle on: failed requests retry on RelayHub’s platform key, so chat keeps working while you fix the key. After three consecutive failures the key shows a Degraded badge with the failure count and last error; calls route to the platform key until you update or revalidate the key, at which point the status clears automatically.
  • Toggle off: failures surface as errors with no fallback. Choose this if your compliance posture requires that traffic never touch platform keys.
Fallback events and key state changes are recorded in the Audit Hub, so you have a record of exactly when platform keys were used.

​
Managing Keys

Each configured provider card shows its status (Active, Paused, Degraded, or No Key), a masked key hint (e.g., ...7xQ2), and when the key was last validated. Actions:
  • Toggle: pause a key without deleting it; paused keys are skipped and traffic uses the platform key
  • Revalidate: re-test the key against the provider (also clears a Degraded state if the key works again)
  • Update Key: replace the key with a new one
  • Remove: delete the key; that provider reverts to the platform key

​
Key Security

API keys are encrypted at rest. Once stored, the full key is never displayed again — only a hint is shown for identification.
  • Keys are scoped to your organization and cannot be viewed by other customers
  • The Provider Hub UI never returns the raw key after initial submission
Use BYOK keys when you need direct visibility into your AI usage costs, want your own rate limits, or have compliance requirements around API key ownership.