Deepgram Base Voicemail
Up to 30%Transcribe speech with Deepgram Base Voicemail on LLM.API—batch or streaming audio to text with the same developer surface as your other models.
What is Deepgram Base Voicemail?
With Deepgram Base Voicemail, LLM.API turns audio into text for product voice features. Speech-to-text model by Deepgram. The model id `base-voicemail` keeps STT alongside your other endpoints.
Providers
LLM.API routes Deepgram Base Voicemail to the providers below, with discounted effective rates versus list price.
| Provider | Pricing | Context | Capabilities |
|---|---|---|---|
| in $0.0125; out — per minute of audio | — | — |
Prices and availability from the LLMAPI catalogue, updated nightly. Last updated 21 Sept 2026.
Try this model
Test Deepgram Base Voicemail right here — free to start.
Suggestions for your first prompt
Code snippet
Call Deepgram Base Voicemail 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="base-voicemail",
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": "base-voicemail",
"messages": [
{"role": "system", "content": "You are a precise product assistant."},
{"role": "user", "content": "Give me three crisp launch checklist items."}
]
}5 Core Capabilities
Compliance archives
Creates text records of spoken interactions for audit trails. Relevant for `base-voicemail` workloads on LLM.API.
Streaming recognition
Supports low-latency partial transcripts when the provider offers streaming STT. Relevant for `base-voicemail` workloads on LLM.API.
Multilingual audio
Handles diverse accents and languages depending on the model.
Meeting capture
Fits voice notes, calls, and meeting recording pipelines. Tuned to how teams typically call Deepgram Base Voicemail.
Voice UX input
Powers voice-driven product interfaces and IVR handoffs. Tuned to how teams typically call Deepgram Base Voicemail.
6 Most Valuable Use Cases
- Live captioning prototypes with Deepgram Base Voicemail
- Clinical or field note dictation workflows
- Compliance recording text archives with Deepgram Base Voicemail
- Feeding voice input into LLM agents
- Meeting notes and searchable recordings with Deepgram Base Voicemail
- 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 Base Voicemail on LLM.API?
Unified AI Routing
Reach Deepgram Base Voicemail and sibling models through one OpenAI-compatible endpoint.
Cost Control
Production: Compare provider price points and keep spend visible as you scale Deepgram Base Voicemail.
Reliability Layer
Retry and route across configured providers when a single upstream blips.
Observability
Practical: Trace prompts, tokens, and errors for Deepgram Base Voicemail alongside the rest of your stack.
Drop-in SDKs
Production: Keep using familiar OpenAI client patterns with base URL https://api.llmapi.ai/v1.
Model Breadth
Swap Deepgram Base Voicemail for chat, media, or embedding alternatives without rewriting auth.
When to Use — When NOT to Use
Use it if...
- Voice is a primary input modality in your product (Deepgram Base Voicemail)
- You will pipe transcripts into search or LLM summarization (Deepgram Base Voicemail)
- You need speech-to-text for batch or streaming audio (Deepgram Base Voicemail)
Avoid if...
- Your audio cannot leave your compliance boundary and you lack an approved provider path
- You need text-to-speech or chat generation instead of transcription
- You require guaranteed perfect transcripts for every accent without evaluation
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 Base Voicemail.
- 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
Can I use tools or structured outputs with Deepgram Base Voicemail?
Tooling support varies; for pure stt models, prefer the modalities listed rather than assuming chat tools.
Does Deepgram Base Voicemail support streaming?
Streaming depends on the active provider; check the providers table on this page for flags.
What is the context length for Deepgram Base Voicemail?
Reported context for Deepgram Base Voicemail is See provider specs. Always verify the active provider row if multiple providers are listed.
Which providers serve Deepgram Base Voicemail?
LLM.API currently lists: deepgram. Availability can vary by region and account.
Where is the canonical page for Deepgram Base Voicemail?
https://llmapi.ai/models/base-voicemail/
What modalities does Deepgram Base Voicemail support?
Deepgram Base Voicemail accepts audio and produces text according to its architecture metadata on LLM.API.
When should I choose Deepgram Base Voicemail?
You need speech-to-text for batch or streaming audio — especially when you specifically need Deepgram Base Voicemail.
Is Deepgram Base Voicemail a chat model?
No—Deepgram Base Voicemail is categorized as a stt model. Use the matching API surface rather than assuming chat completions.
Does Deepgram Base Voicemail 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 Base Voicemail?
Like other API models, Deepgram Base Voicemail can be wrong, incomplete, or uneven on edge cases. Validate outputs for high-stakes use. Media/OCR/STT models additionally depend on input quality.
How is Deepgram Base Voicemail priced on LLM.API?
Listed pricing metadata shows: In $12.5 / 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.
What is Deepgram Base Voicemail?
Speech-to-text model by Deepgram. On LLM.API it is addressed as `base-voicemail`.
COMPARE
Competitive Models
Get one key to every model
Swap your API key. Keep your code.