Deepgram Enhanced Phone Call API: Endpoint & Pricing
Deepgram Enhanced Phone Call brings speech-to-text speech-to-text to LLM.API for voice notes, calls, and caption pipelines.
What is Deepgram Enhanced Phone Call?
With Deepgram Enhanced Phone Call, LLM.API turns audio into text for product voice features. Speech-to-text model by Deepgram. The model id `enhanced-phonecall` keeps STT alongside your other endpoints.
Can you self-host Deepgram Enhanced Phone Call?
No. We found no public weights for Deepgram Enhanced Phone Call on Hugging Face, so there is nothing to download, quantize or serve on your own GPUs: no VRAM budget, no vLLM or GGUF build to plan for. The only way to run it is over an API.
Skip the deploy — use LLM.API as your endpoint
No GPUs, no quantization trade-offs. Same model, OpenAI-compatible, up to 30% below list price.
Providers
LLM.API routes Deepgram Enhanced Phone Call to the providers below, with discounted effective rates versus list price.
List price by provider
InputOutputProvider list prices; the LLM.API discount applies on top.
| Provider | Pricing | Context | Capabilities |
|---|---|---|---|
| in $0; out — per minute of audio | — | — |
Prices and availability from the LLMAPI catalogue, updated nightly. Last updated 8 Oct 2026.
Try this model
Test Deepgram Enhanced Phone Call right here — free to start.
Suggestions for your first prompt
Code snippet
Call Deepgram Enhanced Phone Call through the OpenAI-compatible API — STT via LLM.API (see docs for audio endpoints).
Switching from OpenAI? Change 2 lines.
- base_url="https://api.openai.com/v1"
- api_key="YOUR_OPENAI_KEY"
+ base_url="https://api.llmapi.ai/v1"
+ api_key="YOUR_LLMAPI_KEY"Everything else stays the same — SDK, message format, tools, streaming. Set model to enhanced-phonecall and the call runs unchanged.
curl https://api.llmapi.ai/v1/chat/completions \
-H "Authorization: Bearer $LLMAPI_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "enhanced-phonecall",
"messages": [
{"role": "user", "content": "Give me three crisp launch checklist items."}
]
}'from openai import OpenAI
client = OpenAI(
api_key="YOUR_LLMAPI_KEY",
base_url="https://api.llmapi.ai/v1",
)
resp = client.chat.completions.create(
model="enhanced-phonecall",
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)import OpenAI from "openai";
const client = new OpenAI({
apiKey: process.env.LLMAPI_KEY,
baseURL: "https://api.llmapi.ai/v1",
});
const resp = await client.chat.completions.create({
model: "enhanced-phonecall",
messages: [
{ role: "user", content: "Give me three crisp launch checklist items." },
],
});
console.log(resp.choices[0].message.content);stream = client.chat.completions.create(
model="enhanced-phonecall",
messages=[{"role": "user", "content": "Write a haiku about latency."}],
stream=True,
)
for chunk in stream:
delta = chunk.choices[0].delta.content
if delta:
print(delta, end="", flush=True){
"model": "enhanced-phonecall",
"messages": [
{"role": "system", "content": "You are a precise product assistant."},
{"role": "user", "content": "Give me three crisp launch checklist items."}
]
}ENDPOINTS
Supported endpoints & features
Base URL https://api.llmapi.ai/v1 · model ID enhanced-phonecall · OpenAI-compatible.
POST /v1/chat/completionsChat Completions — supported
| Feature | Status | How to set it |
|---|---|---|
| Function calling (tools) | Not supported | tools, tool_choice |
| Parallel tool calls | Not supported | parallel_tool_calls |
| JSON mode | Not supported | response_format: {"type": "json_object"} |
| Structured outputs | Not supported | response_format: {"type": "json_schema", …} |
| Streaming | Not supported | stream: true |
| Vision (image input) | Not supported | image_url content parts |
| Web search | Not supported | web_search |
ERRORS
Errors & fallback routing
| Code | What it means | What to do |
|---|---|---|
401 | Missing or invalid API key. | Send Authorization: Bearer YOUR_LLMAPI_KEY and check the key is active. |
429 | Rate limited, or the upstream provider is throttling the request. | Back off and retry with jitter; the gateway also retries the request on another provider where one is available. |
5xx | Upstream provider error or timeout. | Retry; fallback routing sends the retry to the next healthy provider for this model. |
When a provider fails or throttles, the request is routed to the next provider serving this model — the ones listed in the providers table above.
Deepgram Enhanced Phone Call in production
What the model is good at.
Meeting capture
Fits voice notes, calls, and meeting recording pipelines. Tuned to how teams typically call Deepgram Enhanced Phone Call.
Caption generation
Produces base transcripts for subtitle workflows.
Multilingual audio
Handles diverse accents and languages depending on the model. Reflects speech-to-text positioning for this endpoint.
Downstream LLM prep
Feeds transcripts into summarization and action-item extractors. Relevant for `enhanced-phonecall` workloads on LLM.API.
Streaming recognition
Supports low-latency partial transcripts when the provider offers streaming STT. Relevant for `enhanced-phonecall` workloads on LLM.API.
What you get when you call Deepgram Enhanced Phone Call through LLM.API.
Unified AI Routing
Reach Deepgram Enhanced Phone Call and sibling models through one OpenAI-compatible endpoint.
One endpoint, every model.Cost Control
Production: Compare provider price points and keep spend visible as you scale Deepgram Enhanced Phone Call.
More performance, less spend.Reliability Layer
Retry and route across configured providers when a single upstream blips.
Never go dark on users.Observability
Practical: Trace prompts, tokens, and errors for Deepgram Enhanced Phone Call alongside the rest of your stack.
See every token, everywhere.Drop-in SDKs
Practical: Keep using familiar OpenAI client patterns with base URL https://api.llmapi.ai/v1.
Think tasks, not models.Model Breadth
Production: Swap Deepgram Enhanced Phone Call for chat, media, or embedding alternatives without rewriting auth.
Scale from 1 to millions.
When to Use — When NOT to Use
Use it if...
- You will pipe transcripts into search or LLM summarization (Deepgram Enhanced Phone Call)
- Voice is a primary input modality in your product (Deepgram Enhanced Phone Call)
- You need speech-to-text for batch or streaming audio (Deepgram Enhanced Phone Call)
Avoid if...
- You require guaranteed perfect transcripts for every accent without evaluation
- You need text-to-speech or chat generation instead of transcription
- Your audio cannot leave your compliance boundary and you lack an approved provider path
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 Enhanced Phone Call.
- 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
Does Deepgram Enhanced Phone Call 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.
When should I choose Deepgram Enhanced Phone Call?
You will pipe transcripts into search or LLM summarization — especially when you specifically need Deepgram Enhanced Phone Call.
What modalities does Deepgram Enhanced Phone Call support?
Deepgram Enhanced Phone Call accepts audio and produces text according to its architecture metadata on LLM.API.
Where is the canonical page for Deepgram Enhanced Phone Call?
https://llmapi.ai/models/enhanced-phonecall/
What are limitations of Deepgram Enhanced Phone Call?
Like other API models, Deepgram Enhanced Phone Call can be wrong, incomplete, or uneven on edge cases. Validate outputs for high-stakes use. Media/OCR/STT models additionally depend on input quality.
Does Deepgram Enhanced Phone Call support streaming?
Streaming depends on the active provider; check the providers table on this page for flags.
What is Deepgram Enhanced Phone Call?
Speech-to-text model by Deepgram. On LLM.API it is addressed as `enhanced-phonecall`.
How do I call Deepgram Enhanced Phone Call via API?
Send OpenAI-compatible requests to https://api.llmapi.ai/v1 with model "enhanced-phonecall" and your LLM.API key. See the code snippet on this page.
Which providers serve Deepgram Enhanced Phone Call?
LLM.API currently lists: deepgram. Availability can vary by region and account.
Is Deepgram Enhanced Phone Call a chat model?
No—Deepgram Enhanced Phone Call is categorized as a stt model. Use the matching API surface rather than assuming chat completions.
Can I use tools or structured outputs with Deepgram Enhanced Phone Call?
Tooling support varies; for pure stt models, prefer the modalities listed rather than assuming chat tools.
COMPARE
Competitive Models
Deepgram Enhanced Finance
Input$0.0145 / minuteList price per minute of audio.
$0.0145 in / — out per minute of audio, context varies — the closest current alternative to Deepgram Enhanced Phone Call.
Cartesia Ink 2 (Streaming)
Input$0.013 / minuteList price per minute of audio.
$0.013 in / — out per minute of audio, context varies — the closest current alternative to Deepgram Enhanced Phone Call.
Deepgram Base Meeting
Input$0.0125 / minuteList price per minute of audio.
$0.0125 in / — out per minute of audio, context varies — the closest current alternative to Deepgram Enhanced Phone Call.
Get one key to every model
Swap your API key. Keep your code.