Skip to navigation

Integrations

Bring Speechify voices to the Vercel AI SDK, LiveKit, Pipecat, Vapi, Deepgram, and other frameworks and voice-agent platforms.

Voice-agent platforms handle transport, turn-taking, STT, and orchestration. Speechify handles the voice. These guides show how to slot Speechify TTS into each platform without inventing a new integration seam: either through the platform’s native plugin or service, or through the open-source tts-shims proxy when the platform expects a specific HTTP dialect.

Maintaining an integration?

Set the Speechify-Caller header so we can see your traffic, warn you before a change reaches your users, and credit the usage you drive. See Build an integration.

Supported platforms

LiveKit

Add speechify.TTS(...) to a LiveKit AgentSession with LiveKit’s official plugins for Python (livekit-plugins-speechify) and Node.js (@livekit/agents-plugin-speechify).

Pipecat

Use Pipecat’s built-in SpeechifyHttpTTSService as the TTS stage, with word timestamps (pipecat-ai 1.8.0 and later).

Vercel AI SDK

Call generateSpeech() with @speechify/ai-sdk-provider, speech marks included.

Vapi

Point Vapi custom voice at the tts-shims Vapi provider to serve raw PCM from Speechify.

Deepgram

Point Deepgram Voice Agent’s open_ai speak provider at the tts-shims OpenAI-compatible shim.

Puter

Call puter.ai.txt2speech() with provider: 'speechify', keyless on puter.com or with your key on your own instance.

Which integration should I pick?

PlatformLanguageIntegration shapeSpeechify key lives in
LiveKitPythonNative plugin (livekit-plugins-speechify)Agent process environment
LiveKitTypeScript (Node.js)Native plugin (@livekit/agents-plugin-speechify)Agent process environment
PipecatPythonNative service (SpeechifyHttpTTSService in pipecat-ai)Agent process environment
Vercel AI SDKTypeScriptSpeechify-maintained provider (@speechify/ai-sdk-provider)Server environment (SPEECHIFY_API_KEY)
VapiAny (HTTP)tts-shims Vapi providerShim process environment
DeepgramAny (HTTP)tts-shims OpenAI-compatible shimShim process environment
PuterJavaScriptNative puter.js provider (provider: 'speechify')None on puter.com; Puter instance config.json when self-hosted

Native plugins are the simplest path when the platform ships one. When it doesn’t, the tts-shims proxy translates the platform’s HTTP request into a Speechify call and returns audio in the format the platform expects, with no client change and no exposed Speechify key.

Why route TTS through Speechify?

Simba 3.2 is independently evaluated on Artificial Analysis’ TTS leaderboard. Every guide here defaults to a Simba 3.2 voice; swap voice_id and model together when you tune for your own use case.

Not seeing your platform?

The tts-shims repo is organized by inbound request dialect. If your platform sends an OpenAI-shaped speech request, the openai shim covers it (that’s the Deepgram integration). If it sends something else, adding a new provider is a small Go command under cmd/. Open an issue on tts-shims with the platform’s TTS webhook contract and we’ll look at it.