Skip to main content
Bring Your Own Key (BYOK) lets your managed voice agents run on your own provider accounts. You register a model provider — an LLM endpoint, or a speech (STT/TTS) model — together with your API key, and your agents can then select those models like any other. Billing and rate limits for those models run against your provider account. Registered keys are scoped to your organization and stored encrypted. Keys are write-only: once saved, they can be replaced but never read back. Manage your keys at Bring your own key in the Dashboard.
Organization admins can add, edit, and delete BYOK models. Members can see which models are registered, but cannot manage keys.

​
LLM providers

The LLM providers tab registers a language-model endpoint. Each entry has:
  • Model — the model name, as it will appear in your agents’ model dropdowns (for example gpt-4o).
  • API key — your provider key, stored encrypted.
  • Endpoint URL — where requests are sent.
  • Provider (optional) — auto-detected by default, or set explicitly.
The provider type determines which extra fields apply: Credentials — the API key and the Vertex service-account JSON — are write-only. When editing an entry, leave the credential field blank to keep the current value.

​
Speech models

The Speech models tab registers your key for a speech model from the SLNG catalog:
  1. Pick the type — Speech to text or Text to speech.
  2. Pick a compatible model. The dropdown lists the catalog models available to your organization that support BYOK.
  3. Paste your provider API key.
Once saved, the key is used automatically whenever one of your agents runs with that model selected.

​
How agents use your models

Registered models appear in the agent editor’s model dropdowns alongside the SLNG catalog. Your own entries are labelled with a (BYOK) suffix — for example gpt-4o (openai-compat, BYOK) — and the editor shows a Bring your own key note under the selector when one is chosen. Which BYOK models are offered depends on the agent: entries can be limited to specific languages and regions, and the dropdown only shows models compatible with the agent’s current language and region settings. An entry with no restrictions is offered everywhere. If an agent’s saved model is no longer offered for its current settings, the selection is kept and shown as pinned rather than silently replaced.
Selecting a BYOK LLM automatically routes that agent’s LLM traffic through SLNG’s managed routing layer (llm_router_enabled). No extra configuration is needed — saving the agent with a BYOK model selected is enough.
Speech model keys need no per-agent setup at all: when an agent runs with a model you registered a key for, your key is used upstream.

​
Rotating a key

Edit the entry and paste the new key. Leaving the key field blank keeps the current one — there is no way to view a stored key, so rotation always means entering the replacement in full.

​
Relation to per-request TTS BYOK

This page covers org-level BYOK for managed voice agents: keys registered once in the Dashboard and used automatically by your agents. If you call the SLNG speech APIs directly (not through a managed agent), there is a separate per-request mechanism: passing your provider key on each TTS request with the X-Slng-Provider-Key header. See BYOK Voice Models.

​
Next steps

Vault

Store organization-wide variables and secrets for your agents.

Managed Agents

Create and operate voice agents in the Dashboard.