Skip to main content

BYOK — bring your own API keys

SimplAI lets you bring your own API key (BYOK) for any LLM, STT, or TTS provider used in a voice agent. The key selector is a unified component used everywhere a provider appears.

How the selector works​

Each provider appears once in the provider dropdown. After you pick a provider, an API key selector appears below it. The selector shows:

  • SimplAI API key — the platform-managed option. A small cost label (+ $0.00X / min) is shown next to it to indicate the additional per-minute platform cost when using this key.
  • Your saved keys for this provider — listed by the name you gave each one. No cost label is shown for user-owned keys (they bill against your account with the provider directly).
  • + Add new key — open an inline form to add a new key without leaving the configuration screen.

Default selection​

  • If you have one or more user-owned keys saved for the selected provider, the most recently added key is selected by default.
  • If you have no user keys for that provider, SimplAI API key is selected by default.

This default is just a starting point — change it anytime via the selector.

Adding a new key inline​

Click + Add new key. An inline form (or small drawer) opens with:

  • Name — a label you'll see in the selector later (e.g., "Prod ElevenLabs").
  • API key — the secret value. It is stored encrypted and never shown again after this step.

The key is saved encrypted and becomes immediately available in the selector. The flow works the same way whether you currently have SimplAI key or a user-owned key selected.

Cost implications​

The cost label is the cleanest way to know which side pays for usage:

  • SimplAI API key (+ $0.00X / min): the provider's usage is included in the per-second voice rate. Your SimplAI credits cover it.
  • Your own key (no label): the provider's usage bills against your account with that provider directly. The per-second SimplAI rate still applies for the platform layer.

The workspace usage dashboard reports voice usage split into platform-managed vs. BYOK so you can see how much went through each path. See Pricing.

Failed BYOK keys​

If a BYOK key fails or is rate-limited at runtime:

  • The call fails gracefully — the user hears a fallback response, not silence.
  • The failure is recorded in Run history with the error.
  • If you've configured fallback STT or TTS providers (see Transcriber and Voice), the platform tries them in order before failing.

Rotate keys frequently and keep at least one fallback provider configured for production voice agents.