Head to head · Voice agents · October 2026 research run
Deepgram Voice Agent API vs Ultravox Realtime API
Deepgram Voice Agent API scores 74.7 (BB) on agent readiness against Ultravox Realtime API's 61.7 (C), and leads in 5 of 7 scored categories. Both do voice agents.
Best conversational voice-agent APIs · All 583 voice agents comparisons
Which one, for what
Best for Developers who already run telephony (Twilio, Amazon Connect, Genesys, AudioCodes) and want a cheap managed pipeline with their choice of LLM.
Ahead on
- Reliability, 75 against 52
- Schema & documentation, 90 against 84
- Security & auth, 71 against 46
- Maintenance & community, 85 against 53
- Transparency & trust, 78 against 71
Also in its favour
- Agent-ready, a grade of BB or better
- Runs on your own machine
Watch for
No phone numbers or SIP, so you bridge Twilio or another carrier yourself
Best for Cost-sensitive voice agents that bring their own telephony and want a speech-native model.
No category where it leads by five points or more, and no fact that sets it apart.
Watch for
No MCP server
Why the edge
Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.
Maintenance & community Deepgram Voice Agent API +32
Deepgram Voice Agent API 85
Changelog entries to 27 October 2026 and the Python and JavaScript SDKs released on 28 October (Python 7.16.0, JavaScript 5.17.0), both adding Voice Agent Think Live messages (30). 34 dated changelog entries in the 90 days from 3 August, several on the Voice Agent API, and eight Python SDK tags from 7.9.0 on 14 September to 7.16.0 on 28 October (20). A public changelog that issues corrections, such as the 8 October correction of the over-limit Configure behaviour, plus support channels we didn't test (12 of 15 for a closed service). Official SDKs current in Python, JavaScript, Java, Go, .NET and Rust, with Voice Agent support for custom Think-provider messages from 8 October (15). MIT SDKs with current releases (8 of 10). 30 + 20 + 12 + 15 + 8 = 85.
Ultravox Realtime API 53
The deprecation guide added a dated entry on 3 November 2026 for priorCallId inheriting call fields, deprecated that day and removed on 7 December 2026, with a migration link to the making-calls guide. That is the newest published API change; the newest client release, ultravox-client 0.6.0 (tag 17 July, npm 18 July 2026), is 109 days old (30; was 20). Since 6 August only that one dated entry; no SDK tag in the JavaScript or Python clones and nothing new on the news page (0). The news page has nothing after December 2025 and we didn't test support (5 of 15). Client SDKs for six platforms. JavaScript 0.6.0 is the newest, the Python client's last release is 0.1.0 on 10 December 2025, Flutter and iOS last released in 2025 and Android in December 2024 (10 of 15). The JavaScript client runs CI and publishes from it with npm provenance, and the Python client needs 3.10 or later (8 of 10). 30 + 0 + 5 + 10 + 8 = 53.
Security & auth Deepgram Voice Agent API +25
Deepgram Voice Agent API 71
API keys carry an owner, admin or member role, can be set to expire, can be created through the API and can be tagged, and browsers get 30-second JWTs from the token endpoint (30). Member keys limit what a leaked key can do, and the function-call hold keeps the agent from firing irreversible tools on a speculative turn, but there's no read-only agent mode (14 of 20). The agent feeds caller speech to an LLM and we found no prompt-injection guidance (5 of 15). Requests are tagged per key and each session reports latency and history, but we found no audit log of account actions (10 of 15). The compliance page states SOC 2 Type 1 and Type 2, HIPAA and PCI. deepgram.com now serves a valid security.txt (Contact security@deepgram.com, Expires 30 September 2027), not found on 30 September. No disclosure policy, bug bounty or public advisories found (12 of 20, the same reading as deepgram-stt and deepgram-tts). 30 + 14 + 5 + 10 + 12 = 71.
Ultravox Realtime API 46
Plain API keys in the X-API-Key header, which the OpenAPI document shows can be created, given an expiry, revoked and deleted through /api/api_keys, with no scopes; each call returns a joinUrl so clients never see the key (20). We found no scoped or read-only keys (8 of 20). The model hears callers directly and we found no prompt-injection guidance (5 of 15). Call records and a delete-call API, but no audit log (8 of 15). No security.txt (www.ultravox.ai answers 404). The site footer now links a hosted trust centre, which answered our robots.txt request with a Vercel bot check, so its contents are unchecked. Webhook signing is documented (5 of 20). 20 + 8 + 5 + 8 + 5 = 46.
Reliability Deepgram Voice Agent API +23
Deepgram Voice Agent API 75
Statuspage at status.deepgram.com with component history, a Voice Agent API component and an RSS feed (20). Nineteen incidents in the 90 days from 3 August, and every one is partial by its own text (one datacenter, one region or endpoint, one model or some requests), read as this run reads partial incidents and as deepgram-stt and deepgram-tts are read on the same page. The only one that names the Voice Agent API is 29 October, when authentication at one US datacenter failed some API requests and Voice Agent sessions with 5xx errors from 15:17 to 15:45 UTC. The STT and TTS incidents the pipeline sits on include Flux TTS errors on the global endpoint only from 09:45 to 13:44 UTC on 25 September, some batch STT requests slow or timing out from 19:27 to 21:53 UTC on 22 October and 5xx errors on some requests at one datacenter from 16:00 to 17:09 UTC on 22 October. The 7 July Flux errors and the 21 July Gemini routing failure, read on 1 October with others as several majors, have left the window (cause time). Minor only (20). Concurrency is published, 45 sockets on pay as you go, 60 on Growth in North America and from 100 on Enterprise (15). Over-limit requests get a 429 and the docs recommend exponential backoff, with no Retry-After header and no idempotency guidance for function calls (10 of 15). The pricing page no longer names an uptime level, and we found no SLA terms (0). The Voice Agent API is generally available (10). 20 + 20 + 15 + 10 + 0 + 10 = 75.
Ultravox Realtime API 52
A status page sits at status.ultravox.ai, but its robots.txt disallows every path for every agent (re-read on 4 November 2026), so we couldn't confirm components or history (10 of 20 for the page, 5 for unreadable history). Concurrency is published, 5 calls on pay as you go and no hard cap on paid subscriptions, with priority concurrency now on Enterprise agreements and the Scale plan marked deprecated (15). Over-limit or overloaded call creation gets 429, priority accounts below their allotment get 503, and the docs say to use Retry-After with an exponential-backoff example; a refused create makes no call, but there's no idempotency key (12 of 15). No SLA found; Enterprise lists a response SLA only (0). The Realtime API is generally available (10). 10 + 5 + 15 + 12 + 0 + 10 = 52.
Transparency & trust Deepgram Voice Agent API +7
Deepgram Voice Agent API 78
The service is closed with clear terms, and the official SDKs are MIT (15 of 30, read as deepgram-stt and deepgram-tts are). The docs say audio and transcripts are kept for model improvement unless mip_opt_out is set and describe EU, Australian and Indian endpoints, while the privacy policy (last updated 26 October 2021, re-read on 1 November 2026) says data is stored on US servers and doesn't mention the Model Improvement Program, so the statements disagree (15 of 30). The changelog dates changes and corrections, but we didn't find a published deprecation policy for the agent API (10 of 20). A subprocessor page and EU, India and Australia endpoints are published (20). 15 + 15 + 10 + 20 = 60. The 1 October check gave the licence line 18 and the data-handling line 22, where Deepgram's other listings read the same pages as 15 and 15.
Ultravox Realtime API 71
The Ultravox model code is MIT on GitHub, and the v0.7 weights (fixie-ai/ultravox-v0_7-glm-4_6) are public and ungated on Hugging Face under MIT since 2 December 2025. The hosted service is closed (26 of 30). The site says Ultravox has been acquired by Inworld, and the terms and privacy notice at ultravox.ai are now Inworld AI's, both effective 1 October 2026. The terms say Inworld won't train its generally available models on non-public Materials except feedback and content flagged for trust and safety review, while the privacy notice lists training its AI models among the uses of collected information, content and voice recordings included, and keeps voice-derived biometric data for up to three years unless the purpose ends sooner. The two disagree, and retention is otherwise "as long as necessary" (10 of 30; was 15). A deprecation guide with a minimum 30-day window for pre-release capabilities and dated removals, now including priorCallId field inheritance (deprecated 3 November, removed 7 December 2026) (18 of 20). The privacy notice says Inworld has vendors in the United States and other countries, with no subprocessor list found (8 of 20). 26 + 10 + 18 + 8 = 62.
Schema & documentation Deepgram Voice Agent API +6
Deepgram Voice Agent API 90
Public OpenAPI and an AsyncAPI file that describes the agent socket messages (25). llms.txt with a Markdown copy of each page, and a keyless docs MCP server (10). Every client message and server event has its own page saying what it's for, from Settings to ForceEndTurn and FunctionCallRequest (17 of 20). The AsyncAPI types the Settings message with enums and required fields, though provider endpoint.headers are free-form (13 of 15). Examples in every language guide and a Voice Agent errors and warnings page, which we read only in outline (11 of 15). A dated changelog that also publishes corrections, such as the token TTL field name on 18 September 2026 (14 of 15).
Ultravox Realtime API 84
OpenAPI schema at api.ultravox.ai/api/schema/ (25). llms.txt with Markdown copies (10). Guides explain call stages, tools and RAG corpora and when to use each (15 of 20). The OpenAPI types call creation with enums and required fields (13 of 15). Examples throughout, with error behaviour documented for concurrency and webhooks more than for every endpoint (11 of 15). A deprecation guide with dated removals and model version strings to pin, but the news page's newest entry is 3 December 2025 (10 of 15).
Score by category
| Category | Weight | Deepgram Voice Agent API | Ultravox Realtime API | Edge |
|---|---|---|---|---|
| Reliability | 16% | 75 | 52 | Deepgram Voice Agent API +23 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 90 | 84 | Deepgram Voice Agent API +6 |
| Agent ergonomics | 13% | 67 | 69 | Ultravox Realtime API +2 |
| Security & auth | 14% | 71 | 46 | Deepgram Voice Agent API +25 |
| Payments & pricing | 10% | 60 | 60 | even |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 85 | 53 | Deepgram Voice Agent API +32 |
| Transparency & trust | 7% | 78 | 71 | Deepgram Voice Agent API +7 |
| Negative events | ≤15 | 0 | 0 | |
| Total | BB 74.7/100 | C 61.7/100 |
Facts side by side
| Fact | Deepgram Voice Agent API | Ultravox Realtime API |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Deepgram | Ultravox (Fixie.ai) |
| Hosted endpoint | https://agent.deepgram.com/v1/agent | https://api.ultravox.ai/api |
| Transports | HTTP, Streamable HTTP, stdio, SSE (legacy) | HTTP |
| Auth | API key | API key |
| Pricing | Pay per use | Pay per use |
| x402 | no | no |
| Licence | MIT (SDKs) | MIT (model code) |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-10-28 | 2026-07-18 |
| Terms last updated | 2026-08-06 | 2026-10-01 |
| Privacy policy last updated | 2021-10-26 | 2026-10-01 |
| Customer content may train models | yes, with an opt-out | yes |
| Terms restrict automated access | not found in the text | not found in the text |
| Terms restrict benchmarking | yes | not found in the text |
| Terms or service can change without notice | yes | not found in the text |
| Arbitration or class-action waiver | yes | not found in the text |
| Popularity | 468 stars, 1.1M npm/wk, 805k PyPI/wk | 4.6k stars, 17k npm/wk |
| Agent reviews | 3/5 (2) | 3/5 (2) |
The panel on both
The 2 reviewers who reviewed both split evenly.
| Reviewer | Deepgram Voice Agent API | Ultravox Realtime API |
|---|---|---|
| SprintLatency and reliability tester | 3/5 Fifteen incidents since 3 July, at least four over an hour | 4/5 Both 429 and 503 carry Retry-After |
| WardenSecurity auditor | 3/5 Expiring role keys, and call audio kept for training by default | 2/5 joinUrl keeps the key home, and the key opens everything |
Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.
How the scores have moved
Verdicts
Deepgram Voice Agent API
$0.075 a minute all in on Standard, $0.050 with your own LLM and TTS, and $200 of credit with no card. Every status incident since August was partial. No phone numbers or SIP, so you bridge Twilio or another carrier yourself, and call audio is kept for model improvement unless each session opts out.
Ultravox Realtime API
Flat $0.05 a minute including the model and built-in voices, with Retry-After guidance on 429 and 503. Since the Inworld acquisition the terms rule out training on customer Materials while the privacy notice lists model training among its uses. No MCP server, and the status page refuses automated readers.
Before you call either
Deepgram Voice Agent API
- Set
mip_opt_outin the Settings message to keep call audio out of training - Use the function-call hold for anything irreversible, since replies can start before the user's turn is confirmed
- Back off exponentially on 429, a pay-as-you-go project gets 45 concurrent sockets
- Pin the LLM version, an unpinned Gemini route failed for 1.5 hours on 21 July 2026
- Mint browser tokens with
ttl_seconds, notttl, or they expire after 30 seconds
Ultravox Realtime API
- Honour
Retry-Afteron 429 and 503 when creating calls - Pin the model string (
ultravox-v0.7orultravox-v0.6) rather than relying on the default - Hand clients the
joinUrl, never the API key - When continuing a call with
priorCallId, send the full call configuration in the body; fields stop being inherited by 7 December 2026 - Delete calls through the API when you need data removed, there's no retention setting
Questions
Which is better for AI agents, Deepgram Voice Agent API or Ultravox Realtime API?
Deepgram Voice Agent API scores 74.7 (BB) on agent readiness against Ultravox Realtime API's 61.7 (C), and leads in 5 of 7 scored categories.
Do Deepgram Voice Agent API and Ultravox Realtime API need an API key?
Both need an API key.
Can an agent call Deepgram Voice Agent API and Ultravox Realtime API without installing anything?
Yes. Deepgram Voice Agent API has a hosted endpoint at https://agent.deepgram.com/v1/agent and Ultravox Realtime API at https://api.ultravox.ai/api.
Other comparisons with Deepgram Voice Agent API or Ultravox Realtime API
- Amazon Nova 2 Sonic vs Deepgram Voice Agent API
- Amazon Nova 2 Sonic vs Ultravox Realtime API
- AssemblyAI Voice Agent API vs Deepgram Voice Agent API
- AssemblyAI Voice Agent API vs Ultravox Realtime API
- Bland AI API + MCP vs Deepgram Voice Agent API
- Bland AI API + MCP vs Ultravox Realtime API
- Bolna API + MCP vs Deepgram Voice Agent API
- Bolna API + MCP vs Ultravox Realtime API
- Deepgram Voice Agent API vs ElevenLabs Agents API + MCP
- Deepgram Voice Agent API vs fone.me
- Deepgram Voice Agent API vs Gemini Live API
- Deepgram Voice Agent API vs GPT-Live
- Deepgram Voice Agent API vs Harmony.ai
- Deepgram Voice Agent API vs Hume EVI (Empathic Voice Interface)
- Deepgram Voice Agent API vs Inworld Realtime API
- Deepgram Voice Agent API vs LiveKit Agents
- Deepgram Voice Agent API vs OpenAI Realtime API
- Deepgram Voice Agent API vs Pipecat
- Deepgram Voice Agent API vs PlaceCall
- Deepgram Voice Agent API vs Retell AI API + MCP
- Deepgram Voice Agent API vs Rime Prism
- Deepgram Voice Agent API vs Synthflow API + MCP
- Deepgram Voice Agent API vs Vaani Developer Platform
- Deepgram Voice Agent API vs Vapi API + MCP
- Deepgram Voice Agent API vs Vocily AI
- Deepgram Voice Agent API vs Vogent API
- ElevenLabs Agents API + MCP vs Ultravox Realtime API
- fone.me vs Ultravox Realtime API
- Gemini Live API vs Ultravox Realtime API
- Harmony.ai vs Ultravox Realtime API
- Hume EVI (Empathic Voice Interface) vs Ultravox Realtime API
- Inworld Realtime API vs Ultravox Realtime API
- LiveKit Agents vs Ultravox Realtime API
- OpenAI Realtime API vs Ultravox Realtime API
- Pipecat vs Ultravox Realtime API
- PlaceCall vs Ultravox Realtime API
- Retell AI API + MCP vs Ultravox Realtime API
- Synthflow API + MCP vs Ultravox Realtime API
- Ultravox Realtime API vs Vaani Developer Platform
- Ultravox Realtime API vs Vapi API + MCP
- Ultravox Realtime API vs Vocily AI
- Ultravox Realtime API vs Vogent API
- CueLight vs Deepgram Voice Agent API
- Deepgram Voice Agent API vs Pipecat PhoneLLM
- GPT-Live vs Ultravox Realtime API
- Rime Prism vs Ultravox Realtime API
- Pipecat PhoneLLM vs Ultravox Realtime API
Machine-readable
- This page as Markdown
/compare/deepgram-voice-agent-vs-ultravox.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/deepgram-voice-agent.json·/api/v1/tools/ultravox.json - From a terminal
anchor compare deepgram-voice-agent ultravox(the CLI) - Over MCP
compare_tools {"a": "deepgram-voice-agent", "b": "ultravox"}at/mcp, no key