Deepgram Flux TTS for Developers: What Ships at General Availability
Blog post from Deepgram
Deepgram has made Flux TTS generally available through its /v2/speak endpoint, offering turn-based text-to-speech for voice agents via streaming WebSocket and batch REST interfaces while leaving existing Aura /v1/speak implementations unchanged. The WebSocket service streams audio as LLM tokens arrive and supports turn controls such as Flush, Interrupt, and mid-session speed changes, allowing applications to avoid sentence chunking, reconnect workarounds, local character billing estimates, and client-side calculations of what users heard after an interruption. Flux launches with 36 English voices across seven accents, uses flux-{voice}-{language} model names, and includes beta expressivity controls, markup stripping, and shared model and media settings across batch and streaming modes, although compressed formats are batch-only. It is now the default speech provider in Deepgram’s Voice Agent API, creating a compatibility issue for sessions that omit an explicit provider while requesting compressed output, which must instead specify an Aura model. Flux is supported by Deepgram SDKs, LiveKit, Pipecat, and starter applications, with pricing based on synthesized characters and regional concurrency limits that vary significantly by plan and service type.
No tracked trend matches for this post yet.
Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.