Integrations
Bring Speechify voices to LiveKit, Pipecat, Vapi, Deepgram, and other 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/service, or through the open-source tts-shims proxy when the platform expects a specific HTTP dialect.
SpeechifyAI ships its own voice-agents platform powered by Simba 3.2, independently evaluated on Artificial Analysis’ TTS leaderboard. See SpeechifyAI Agents if you want an end-to-end voice-agent stack instead of bringing a Speechify voice to a third-party platform.
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
Add speechify.TTS(...) to a LiveKit AgentSession via the official Python plugin (livekit-plugins-speechify).
Point Vapi custom voice at the tts-shims Vapi provider to serve raw PCM from Speechify.
Point Deepgram Voice Agent’s open_ai speak provider at the tts-shims OpenAI-compatible shim.
Call puter.ai.txt2speech() with provider: 'speechify' — your key configured once on the Puter instance.
Which integration should I pick?
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 — no client change, 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.