Skip to main content

BYOK

What Is BYOK?

BYOK (Bring Your Own Key) is an optional capability module that lets you connect your own AI provider to Enia. Once connected, all AI operations — including Signal detection, Chat, and Task execution — are powered by your own provider account instead of consuming Enia's Request quota.

How It Works

BYOK is available at every subscription tier, from Free to Ultra.

  • After BYOK is activated, your Enia subscription tier, billing cycle, and quota remain unchanged. BYOK only determines where AI compute is sourced.
  • Enia automatically selects the best-fit model from your connected providers. No manual configuration is needed.
  • When no providers remain connected, Enia reverts to your subscription plan.

Setting Up a Provider

  1. Click your avatar in the top navigation bar, then select Connect Provider.
  2. Choose the provider you want to configure, then click Use API Key.
  3. Enter your API Key and click Submit. Enia validates the key immediately.

After validation, the provider is enabled by default. All subsequent AI calls will use your key automatically.

Managing Providers

You can connect multiple providers at the same time. To manage connections:

  • Enable/Disable: Toggle whether the provider is included in BYOK usage. Changes take effect instantly, and your API Key is preserved for future use.
  • Edit: Click Edit on a connected provider card to update your API Key.
  • Disconnect: Click the x button to remove the key entirely. This permanently deletes it from your local storage, and Enia will no longer use it.

Supported Providers

ProviderConnection Method
AnthropicAPI Key
OpenAIAPI Key
GoogleAPI Key

Provider Status

StatusMeaning
AvailableConnected and working normally.
UnavailableA problem was detected (e.g., key invalid, insufficient balance).
DisabledYou manually turned this provider off. Connection is preserved and can be re-enabled at any time.
Not connectedNo API Key configured yet.

Security

All provider credentials are stored locally on your device and are never uploaded to Enia servers. Credentials are displayed in masked form throughout the interface.