Provider Keys (BYOK)

Overview

Sulus supports bringing your own API keys (BYOK) for various providers, letting you use your own accounts, custom models, or negotiated enterprise pricing. You manage these through the Sulus dashboard under the Integrations tab. Once your API key is validated in the dashboard, you won't be charged by Sulus when using that provider — instead, you're billed directly by the provider.

The available transcription provider for BYOK is Deepgram. You can specify a custom Deepgram model ID in the transcriber.model parameter of your assistant.

Bring Your Own Key is also supported for these transcription providers: Deepgram, Gladia, AssemblyAI, Speechmatics, Google, and Azure.

Sulus supports any OpenAI-compatible endpoint, including: OpenAI, Anthropic, Azure OpenAI, Google Gemini, Groq, DeepSeek, OpenRouter, Together AI, Cerebras, DeepInfra, Perplexity, Anyscale, and xAI.

You specify the provider and model in the model parameter of your assistant configuration.

All voice providers are supported for BYOK. Once validated, any voice ID from your provider can be used in the voice.voiceId field of your assistant.

Supported voice providers: ElevenLabs, PlayHT, Cartesia, Deepgram, OpenAI TTS, Azure, LMNT, Rime AI, Smallest AI, Neuphonic, WellSaid, and Hume.

Sulus stores call recordings in the cloud. By default it uses its own storage bucket, but you can configure your own destination:

• AWS S3
• GCP Cloud Storage
• Cloudflare R2
• Supabase Storage
• Azure Blob Storage

When you validate a provider key in the dashboard, Sulus stops billing you for usage of that specific provider on your assistants — you're billed directly by the provider instead. Sulus platform usage (call minutes, concurrency, and any Sulus-native features) continues to bill normally through your Sulus subscription.

For securing your own webhook server endpoints (as opposed to provider API keys), see the separate Credentials & Auth guide, which covers Sulus's Custom Credentials system.