For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
WebsiteStatusSupportDashboard
DocumentationAPI ReferenceMCPSDKsCLI (new)What's New?
DocumentationAPI ReferenceMCPSDKsCLI (new)What's New?
  • Get started
    • Introduction
    • Phone calls
    • Web calls
    • Vapi Guides
    • Composer
    • CLI quickstart
  • Assistants
    • Quickstart
      • Speech configuration
      • Voice pipeline configuration
      • Voice fallback configuration
      • Transcriber fallback configuration
      • OpenAI realtime speech-to-speech
      • Provider keys
    • Tools
    • Custom keywords
    • Custom voices
    • Custom transcriber
    • Custom TTS
  • Observability
    • Boards
  • Squads
    • Quickstart
    • Overview
    • Handoff tool
    • Passing data between assistants
  • Best practices
    • Prompting guide
    • Debugging voice agents
    • Enterprise environments (DEV/UAT/PROD)
    • IVR navigation
  • Phone numbers
    • Free Vapi number
    • Inbound SMS
    • Phone Number Hooks
  • Calls
    • Call end reasons
    • Troubleshoot call errors
  • Outbound Campaigns
    • Quickstart
    • Overview
  • Chat
    • Quickstart
    • Streaming
    • Non-streaming
    • OpenAI compatibility
    • Session management
    • Variable substitution
    • SMS chat
    • Web widget
    • Webhooks
  • Workflows
    • Quickstart
    • Overview
LogoLogo
WebsiteStatusSupportDashboard
On this page
  • Transcription Providers
  • Model Providers
  • Voice Providers
  • Cloud Providers
AssistantsModel configurations

Provider Keys

Bring your own API keys to Vapi.
Was this page helpful?
Edit this page
Previous

Introduction to Tools

Extend your assistant's capabilities with powerful function calling tools.
Next
Built with

Have a custom model or voice with one of the providers? Or an enterprise account with volume pricing?

No problem! You can bring your own API keys to Vapi. You can add them in the Dashboard under the Integrations tab. Once your API key is validated, you won’t be charged when using that provider through Vapi. Instead, you’ll be charged directly by the provider.

Transcription Providers

Currently, the only available transcription provider is deepgram. To use a custom model, you can specify the deepgram model ID in the transcriber.model parameter of the Assistant.

Model Providers

We are currently have support for any OpenAI-compatible endpoint. This includes services like OpenRouter, AnyScale, Together AI, or your own server.

To use one of these providers, you can specify the provider and model in the model parameter of the Assistant.

You can find more details in the Custom LLMs section of the documentation.

Voice Providers

All voice providers are supported. Once you’ve validated your API through the Dashboard, any voice ID from your provider can be used in the voice.voiceId field of the Assistant.

Cloud Providers

Vapi stores recordings of conversations with assistants in the cloud. By default, Vapi stores these recordings in its own bucket in Cloudflare R2. You can configure Vapi to store recordings in your own bucket in AWS S3, GCP, or Cloudflare R2.

You can find more details on how to configure your Cloud Provider keys here:

  • AWS S3
  • GCP Cloud Storage
  • Cloudflare R2