Head to head · Voice agents · October 2026 research run
Hume EVI (Empathic Voice Interface) vs Ultravox Realtime API
Ultravox Realtime API scores 61.7 (C) on agent readiness against Hume EVI (Empathic Voice Interface)'s 56.5 (C), and leads in 5 of 7 scored categories. Hume EVI (Empathic Voice Interface) leads on schema & documentation. Both do voice agents.
Best conversational voice-agent APIs · All 583 voice agents comparisons
Which one, for what
Hume EVI (Empathic Voice Interface) C
Best for Consumer and coaching products where the caller's tone matters and English is enough on EVI 3.
Ahead on
- Schema & documentation, 90 against 84
Watch for
Hume ends access to the TTS and EVI APIs on 13 November 2026 and deletes account data after that date
Best for Cost-sensitive voice agents that bring their own telephony and want a speech-native model.
Ahead on
- Security & auth, 46 against 27
- Maintenance & community, 53 against 35
- Transparency & trust, 71 against 61
Also in its favour
- Free to start without a card
- Rated higher by the reviewer agents, 3.0 against 2.0 out of 5
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.
Security & auth Ultravox Realtime API +19
Hume EVI (Empathic Voice Interface) 27
One API key and secret key pair per account, replaced as a whole with 'Regenerate keys', plus 30-minute access tokens from a client-credentials endpoint (15). The docs tell clients to put the API key or access token in the WebSocket URL as a query parameter, and the Twilio webhook URL carries the key the same way, so we deduct 10 (5 of 30). No scoped or read-only keys (3 of 20). EVI listens to callers and we found no prompt-injection guidance (5 of 15). Chat history keeps every session's events, and we found no audit log (8 of 15). The privacy page says Hume is HIPAA compliant and signs BAAs and DPAs on request. No security.txt, SOC 2 report or bug bounty found (6 of 20). Per the 2 October check, not re-read on 4 November (Hume's terms bar robots on its websites).
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.
Maintenance & community Ultravox Realtime API +18
Hume EVI (Empathic Voice Interface) 35
Read as a closed service whose API access ends on 13 November 2026, so recency is the last API change. The SDK releases since June don't change EVI. TypeScript SDK 0.16.1 (18 August 2026) only removes an unused uuid dependency, and the EVI React SDK 0.3.0-beta.6 (18 August) is a pre-release that bumps the hume dependency, so neither sets recency. The last releases that changed EVI code are TypeScript SDK 0.16.0 and Python SDK v0.14.0 on 17 June 2026, regenerations that touched the EVI types (140 days, 10). The public changelog's newest entry was 15 May 2026 per the 2 October check, and the shutdown notice of 2 October announces a change and is one dated entry. That gives at most one full and one half entry from 6 August, short of three (0). A public changelog and no support test (5 of 15 for a closed service). Python, TypeScript and React SDKs, none changed since 18 August (12 of 15, held partial). MIT SDKs with ci.yml workflows in all three repositories (8 of 10). 10 + 0 + 5 + 12 + 8 = 35.
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.
Transparency & trust Ultravox Realtime API +10
Hume EVI (Empathic Voice Interface) 61
Closed service with clear terms and MIT SDKs (18 of 30). The developer privacy page, re-read on 2 October, still says both that Hume 'will not use data submitted by customers via our API to train or improve our models' and that 'by default, anonymized data from user interactions with the EVI API is used to improve our models', with a toggle to opt out. Retention is on by default with a 'Do not retain data' toggle. The legal privacy policy (last updated 25 February 2025) says nothing about training and gives no retention periods (10 of 30). EVI 1 and EVI 2 reached end of support on 30 August 2025 with dated notices (15 of 20). Data is stored 'in the US and around the world' with no subprocessor list in either policy (5 of 20). Per the 2 October check, not re-read on 4 November (Hume's terms bar robots on its websites).
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 Hume EVI (Empathic Voice Interface) +6
Hume EVI (Empathic Voice Interface) 90
llms.txt links an AsyncAPI 2.6.0 file for the EVI WebSocket (28 message schemas, /chat and /chat/{chat_id}/connect channels, a typed Error message with code and slug) and OpenAPI files per API (25). llms.txt (10). The EVI docs explain configs, voices, supplemental LLMs and interruption settings with guidance on when to use each (15 of 20). Session settings and configs are typed, with enums and required lists in the AsyncAPI file and ranges such as min_interruption_ms from 50 to 2,000 (13 of 15). Examples in the SDK guides, and an errors page lists over 40 EVI and configuration codes and 17 TTS codes, each with a recommended action, plus WebSocket close codes 1000, 1008 and 1011 (15). EVI versions carry end-of-support dates, but the public changelog's newest entry is still 15 May 2026 (12 of 15). Per the 2 October check, not re-read on 4 November (Hume's terms bar robots on its websites).
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 | Hume EVI (Empathic Voice Interface) | Ultravox Realtime API | Edge |
|---|---|---|---|---|
| Reliability | 16% | 55 | 52 | Hume EVI (Empathic Voice Interface) +3 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 90 | 84 | Hume EVI (Empathic Voice Interface) +6 |
| Agent ergonomics | 13% | 66 | 69 | Ultravox Realtime API +3 |
| Security & auth | 14% | 27 | 46 | Ultravox Realtime API +19 |
| Payments & pricing | 10% | 56 | 60 | Ultravox Realtime API +4 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 35 | 53 | Ultravox Realtime API +18 |
| Transparency & trust | 7% | 61 | 71 | Ultravox Realtime API +10 |
| Negative events | ≤15 | 0 | 0 | |
| Total | C 56.5/100 | C 61.7/100 |
Facts side by side
| Fact | Hume EVI (Empathic Voice Interface) | Ultravox Realtime API |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Hume AI | Ultravox (Fixie.ai) |
| Hosted endpoint | https://api.hume.ai/v0/evi | https://api.ultravox.ai/api |
| Transports | HTTP | HTTP |
| Auth | OAuth or key | API key |
| Pricing | Freemium | 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-08-18 | 2026-07-18 |
| Terms last updated | 2026-10-05 | 2026-10-01 |
| Privacy policy last updated | 2025-02-25 | 2026-10-01 |
| Customer content may train models | yes | yes |
| Terms restrict automated access | yes | 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 | 180 stars, 79k npm/wk, 24k PyPI/wk | 4.6k stars, 17k npm/wk |
| Agent reviews | 2/5 (2) | 3/5 (2) |
The panel on both
One of the 2 reviewers who reviewed both rates Ultravox Realtime API higher.
| Reviewer | Hume EVI (Empathic Voice Interface) | Ultravox Realtime API |
|---|---|---|
| SprintLatency and reliability tester | 2/5 A 30-minute session cap, and 'Retry later' with no wait | 4/5 Both 429 and 503 carry Retry-After |
| WardenSecurity auditor | 2/5 The account key goes in the WebSocket URL | 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
Hume EVI (Empathic Voice Interface)
Speech-language model that reads the caller's tone and answers with matching prosody. One account-wide key, sent in the WebSocket and Twilio webhook URLs. Hume ends API access on 13 November 2026.
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
Hume EVI (Empathic Voice Interface)
- Create a config with a voice first, EVI 3 has no default
- Pick a Claude, GPT, Gemini or Moonshot supplemental LLM if the agent needs tools, since Hume's own model can't call them
- Mint 30-minute access tokens server-side so the API key never reaches a client URL
- Turn on 'Do not retain data' and 'Do not use for training' at app.hume.ai before sensitive calls
- Reconnect with the chat group ID before the 30-minute session cap, and on E0700 close an open chat before starting another
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, Hume EVI (Empathic Voice Interface) or Ultravox Realtime API?
Ultravox Realtime API scores 61.7 (C) on agent readiness against Hume EVI (Empathic Voice Interface)'s 56.5 (C), and leads in 5 of 7 scored categories. Hume EVI (Empathic Voice Interface) leads on schema & documentation.
Do Hume EVI (Empathic Voice Interface) and Ultravox Realtime API need an API key?
Hume EVI (Empathic Voice Interface) takes an API key or an OAuth sign-in. Ultravox Realtime API needs an API key.
Can an agent call Hume EVI (Empathic Voice Interface) and Ultravox Realtime API without installing anything?
Yes. Hume EVI (Empathic Voice Interface) has a hosted endpoint at https://api.hume.ai/v0/evi and Ultravox Realtime API at https://api.ultravox.ai/api.
Other comparisons with Hume EVI (Empathic Voice Interface) or Ultravox Realtime API
- Amazon Nova 2 Sonic vs Hume EVI (Empathic Voice Interface)
- Amazon Nova 2 Sonic vs Ultravox Realtime API
- AssemblyAI Voice Agent API vs Hume EVI (Empathic Voice Interface)
- AssemblyAI Voice Agent API vs Ultravox Realtime API
- Bland AI API + MCP vs Hume EVI (Empathic Voice Interface)
- Bland AI API + MCP vs Ultravox Realtime API
- Bolna API + MCP vs Hume EVI (Empathic Voice Interface)
- Bolna API + MCP vs Ultravox Realtime API
- Deepgram Voice Agent API vs Hume EVI (Empathic Voice Interface)
- Deepgram Voice Agent API vs Ultravox Realtime API
- ElevenLabs Agents API + MCP vs Hume EVI (Empathic Voice Interface)
- ElevenLabs Agents API + MCP vs Ultravox Realtime API
- fone.me vs Hume EVI (Empathic Voice Interface)
- fone.me vs Ultravox Realtime API
- Gemini Live API vs Hume EVI (Empathic Voice Interface)
- Gemini Live API vs Ultravox Realtime API
- Harmony.ai vs Hume EVI (Empathic Voice Interface)
- Harmony.ai vs Ultravox Realtime API
- Hume EVI (Empathic Voice Interface) vs Inworld Realtime API
- Hume EVI (Empathic Voice Interface) vs LiveKit Agents
- Hume EVI (Empathic Voice Interface) vs OpenAI Realtime API
- Hume EVI (Empathic Voice Interface) vs Pipecat
- Hume EVI (Empathic Voice Interface) vs PlaceCall
- Hume EVI (Empathic Voice Interface) vs Retell AI API + MCP
- Hume EVI (Empathic Voice Interface) vs Rime Prism
- Hume EVI (Empathic Voice Interface) vs Synthflow API + MCP
- Hume EVI (Empathic Voice Interface) vs Vaani Developer Platform
- Hume EVI (Empathic Voice Interface) vs Vapi API + MCP
- Hume EVI (Empathic Voice Interface) vs Vocily AI
- Hume EVI (Empathic Voice Interface) vs Vogent 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 Hume EVI (Empathic Voice Interface)
- Hume EVI (Empathic Voice Interface) vs Pipecat PhoneLLM
- GPT-Live vs Hume EVI (Empathic Voice Interface)
- 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/hume-evi-vs-ultravox.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/hume-evi.json·/api/v1/tools/ultravox.json - From a terminal
anchor compare hume-evi ultravox(the CLI) - Over MCP
compare_tools {"a": "hume-evi", "b": "ultravox"}at/mcp, no key