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.
The Deepgram CLI brings transcription, speech synthesis, text analysis, account management, and MCP tooling to your terminal through a single dg command.
What you can do
Use the dg CLI to work with Deepgram from your terminal:
Transcribe files, URLs, microphone input, and piped audio
Generate speech with Deepgram Aura voices
Run text analysis workflows such as summarization, sentiment, and topic detection
Flux Multilingual: Conversational STT, Now in 10 Languages
The same model that solved turn detection for English voice agents now works everywhere your customers speak — no language routing, no model-per-language infrastructure, no accuracy tradeoff.
Deepgram is proud to announce the general availability of Flux Multilingual (flux-general-multi), a single model supporting 10 languages with the same turn-aware, interruption-aware conversational intelligence as flux-general-en.
Key Features:
10 languages, one model — English, Spanish, French, German, Hindi, Russian, Portuguese, Japanese, Italian, and Dutch. No language routing or model-per-language infrastructure required.
Language prompting — The optional language_hint parameter biases the model toward specific languages, delivering accuracy on par with dedicated monolingual models. Without hints, the model auto-detects the spoken language.
Native code-switching — Handles mid-sentence language switches without configuration changes or reconnections.
Language detection on every turn — All TurnInfo events include a languages field reporting detected languages sorted by word count, and a languages_hinted field reflecting the active hints.
Mid-stream reconfiguration — Update language hints during a stream using the Configure control message without disconnecting. Supports patterns like detect-then-lock for optimal accuracy.
Same Flux architecture — All turn detection, eager end-of-turn, and configuration parameters from flux-general-en work identically.
Use Cases:
Designed for non-English monolingual voice agents, multilingual voice agents, global contact centers, bilingual support lines, and any real-time conversational application where callers may speak different languages. For English-only workloads, continue using flux-general-en.
Getting Started:
Connect to Flux Multilingual by setting model=flux-general-multi on the /v2/listen endpoint — no new credentials or endpoints required. Pricing is the same as flux-general-en.
