Flux TTS Overview
Flux TTS is Deepgram’s voice-agent-first, streaming-first text-to-speech family, served on /v2/speak over both a real-time WebSocket and a batch REST transport.
Flux TTS brings the Flux promise to speech synthesis: a model and API built for the realities of a voice agent pipeline, not a one-shot text-to-audio pipe. It is served on the /v2/speak endpoint and shares one set of Flux voices across two transports. When a user barges in, Interrupt reports exactly what they heard (text_spoken) — the hard part of agent state reconciliation, answered by the API instead of reconstructed by hand.
Two transports, one voice family
Not sure which to use? See Batch vs Streaming.
Why Flux TTS
- Streaming-first — Stream LLM tokens straight into the socket; the server places flush boundaries internally.
- Turn-based lifecycle — Each agent response is a turn with a clean start/finish, reported per turn.
- Cross-turn voice consistency — Conversational state persists across turns, so tone carries forward. See Cross-Turn Context.
On barge-in, Interrupt reports exactly what the user heard, and mid-stream Configure adjusts speed without reconnecting.