Deepgram Flux (English)
Up to 30%Transcribe speech with Deepgram Flux (English) on LLM.API—batch or streaming audio to text with the same developer surface as your other models.
What is Deepgram Flux (English)?
With Deepgram Flux (English), LLM.API turns audio into text for product voice features. Streaming speech-to-text model by Deepgram. The model id `flux` keeps STT alongside your other endpoints.
Providers
LLM.API routes Deepgram Flux (English) to the providers below, with discounted effective rates versus list price.
| Provider | Pricing | Context | Capabilities |
|---|---|---|---|
| in $0.0077; out — per minute of audio | — | — |
Prices and availability from the LLMAPI catalogue, updated nightly. Last updated 21 Sept 2026.
Try this model
Test Deepgram Flux (English) right here — free to start.
Suggestions for your first prompt
Code snippet
Call Deepgram Flux (English) through the OpenAI-compatible API — STT via LLM.API (see docs for audio endpoints).
from openai import OpenAI
client = OpenAI(
api_key="YOUR_LLMAP_KEY",
base_url="https://api.llmapi.ai/v1",
)
resp = client.chat.completions.create(
model="flux",
messages=[
{"role": "system", "content": "You are a precise product assistant."},
{"role": "user", "content": "Give me three crisp launch checklist items."},
],
)
print(resp.choices[0].message.content){
"model": "flux",
"messages": [
{"role": "system", "content": "You are a precise product assistant."},
{"role": "user", "content": "Give me three crisp launch checklist items."}
]
}5 Core Capabilities
Streaming recognition
Supports low-latency partial transcripts when the provider offers streaming STT. Reflects streaming speech-to-text positioning for this endpoint.
Downstream LLM prep
Feeds transcripts into summarization and action-item extractors. Tuned to how teams typically call Deepgram Flux (English).
Speech transcription
Converts spoken audio into text for captions, notes, and search. Tuned to how teams typically call Deepgram Flux (English).
Caption generation
Produces base transcripts for subtitle workflows.
Compliance archives
Creates text records of spoken interactions for audit trails. Grounded in the model's stt role rather than generic chat claims.
6 Most Valuable Use Cases
- Compliance recording text archives with Deepgram Flux (English)
- Feeding voice input into LLM agents
- Podcast and video caption drafts with Deepgram Flux (English)
- Live captioning prototypes
- Clinical or field note dictation workflows with Deepgram Flux (English)
- Call-center transcription and QA
Why Build on LLM.API?
One unified API. Every major model. Built-in reliability, cost control, and observability.
-
Intelligent AI Routing
Automatically route each request to the best model across providers based on latency, cost, and quality—without changing your integration or redeploying code.
One endpoint, every model. -
Cost-Aware Execution
Control spend with per-request cost estimation, smart model selection, and centralized quotas so teams can experiment fast without runaway bills or manual tracking.
More performance, less spend. -
Resilient Fallback Flows
Define automatic, provider-agnostic fallbacks to keep your app up during outages, rate limits, or timeouts—no brittle failover logic scattered through your codebase.
Never go dark on users. -
Deep LLM Observability
Trace every call across providers with logs, metrics, and request replay so you can debug, tune prompts, and optimize model choices from one unified dashboard.
See every token, everywhere. -
Task-Level Orchestration
Describe tasks, not models. LLM.API maps them to the right tools, models, and prompts so you ship complex AI workflows with minimal glue code.
Think tasks, not models. -
High-Throughput Batch APIs
Process millions of inferences efficiently with optimized batch pipelines, concurrency controls, and retry logic—all behind the same simple interface you use for single calls.
Scale from 1 to millions.
Why run Deepgram Flux (English) on LLM.API?
Unified AI Routing
Reach Deepgram Flux (English) and sibling models through one OpenAI-compatible endpoint.
Cost Control
Compare provider price points and keep spend visible as you scale Deepgram Flux (English).
Reliability Layer
Production: Retry and route across configured providers when a single upstream blips.
Observability
Production: Trace prompts, tokens, and errors for Deepgram Flux (English) alongside the rest of your stack.
Drop-in SDKs
Practical: Keep using familiar OpenAI client patterns with base URL https://api.llmapi.ai/v1.
Model Breadth
Swap Deepgram Flux (English) for chat, media, or embedding alternatives without rewriting auth.
When to Use — When NOT to Use
Use it if...
- You will pipe transcripts into search or LLM summarization (Deepgram Flux (English))
- You need speech-to-text for batch or streaming audio (Deepgram Flux (English))
- Voice is a primary input modality in your product (Deepgram Flux (English))
Avoid if...
- Your audio cannot leave your compliance boundary and you lack an approved provider path
- You require guaranteed perfect transcripts for every accent without evaluation
- You need text-to-speech or chat generation instead of transcription
COMMUNITY
What developers say about speech-to-text models
Summarised from publicly published developer and community reviews of this model family. Opinions are the sources’, not LLM.API’s, and may not be specific to Deepgram Flux (English).
- Head-to-head tests of the leading APIs land within a point or two of each other; the choice usually comes down to language coverage, streaming latency and batch pricing.
- Voice-agent developers report streaming latency and endpointing quality matter more in production than headline word-error rates.
- Whisper-family models remain the default open baseline, with hosted providers winning on real-time features and diarization.
SOURCES
Frequently Asked Questions
Which providers serve Deepgram Flux (English)?
LLM.API currently lists: deepgram. Availability can vary by region and account.
How do I call Deepgram Flux (English) via API?
Send OpenAI-compatible requests to https://api.llmapi.ai/v1 with model "flux" and your LLM.API key. See the code snippet on this page.
Does Deepgram Flux (English) translate speech?
Primary behavior is transcription to text. Translation—if needed—should be a separate step with a chat model unless the provider explicitly offers it.
What are limitations of Deepgram Flux (English)?
Like other API models, Deepgram Flux (English) can be wrong, incomplete, or uneven on edge cases. Validate outputs for high-stakes use. Media/OCR/STT models additionally depend on input quality.
Is Deepgram Flux (English) a chat model?
No—Deepgram Flux (English) is categorized as a stt model. Use the matching API surface rather than assuming chat completions.
What is Deepgram Flux (English)?
Streaming speech-to-text model by Deepgram. On LLM.API it is addressed as `flux`.
Where is the canonical page for Deepgram Flux (English)?
https://llmapi.ai/models/black-forest-labs-flux/
What modalities does Deepgram Flux (English) support?
Deepgram Flux (English) accepts audio and produces text according to its architecture metadata on LLM.API.
How is Deepgram Flux (English) priced on LLM.API?
Listed pricing metadata shows: In $7.7 / 1M tokens. LLM.API may offer discounted effective rates (illustrative ~30% callout vs list when available).. Confirm live rates in the LLM.API dashboard or docs before production budgeting.
When should I choose Deepgram Flux (English)?
Voice is a primary input modality in your product — especially when you specifically need Deepgram Flux (English).
What is the context length for Deepgram Flux (English)?
Reported context for Deepgram Flux (English) is See provider specs. Always verify the active provider row if multiple providers are listed.
Does Deepgram Flux (English) support streaming?
Streaming depends on the active provider; check the providers table on this page for flags.
COMPARE
Competitive Models
Get one key to every model
Swap your API key. Keep your code.