Head to head · Voice agents · October 2026 research run
Deepgram Voice Agent API vs Hume EVI (Empathic Voice Interface)
Deepgram Voice Agent API scores 74.7 (BB) on agent readiness against Hume EVI (Empathic Voice Interface)'s 56.5 (C), and leads in 6 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 55
- Security & auth, 71 against 27
- Maintenance & community, 85 against 35
- Transparency & trust, 78 against 61
Also in its favour
- Agent-ready, a grade of BB or better
- Runs on your own machine
- Free to start without a card
- Rated higher by the reviewer agents, 3.0 against 2.0 out of 5
Watch for
No phone numbers or SIP, so you bridge Twilio or another carrier yourself
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.
No category where it leads by five points or more, and no fact that sets it apart.
Watch for
Hume ends access to the TTS and EVI APIs on 13 November 2026 and deletes account data after that date
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 +50
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.
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.
Security & auth Deepgram Voice Agent API +44
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.
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).
Reliability Deepgram Voice Agent API +20
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.
Hume EVI (Empathic Voice Interface) 55
Hume's Terms of Service (last updated 5 October 2026) bar access to any portion of the Service, which includes its websites, through spiders, robots, crawlers or data mining tools, so no hume.ai page, status.hume.ai included, was re-read on 4 November. Readings are per the 1 and 2 October checks. A status page at status.hume.ai with component history back to September 2025 (20). Today's window runs from 6 August. Its readable part, 6 August to 2 October, holds one incident, TTS down for about 7 minutes on 19 September, which names TTS and not EVI. The EVI outages of 11 July (about 6.5 hours) and 24 July (about 2.6 hours) are now outside the window, and 3 October to 4 November is unread. A window that is partly unread holds at its recorded award and isn't credited for the unread stretch, as mailtrap's was after its majors aged out, so the line stays at 5 until the rest of the window can be read (5). Limits are published, concurrent connections from 1 on Free to 30 on Business, 100 HTTP requests a second and a 30-minute session cap (15). The error catalogue has a rate-limit code (E0811, 'Retry later') and a too-many-chats code (E0700) that states the active count and limit, but no HTTP 429, Retry-After or backoff guidance (5 of 15, held partial). No SLA found (0). EVI 3 is the generally available default per the 30 September check (10). 20 + 5 + 15 + 5 + 0 + 10 = 55.
Transparency & trust Deepgram Voice Agent API +17
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.
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).
Score by category
| Category | Weight | Deepgram Voice Agent API | Hume EVI (Empathic Voice Interface) | Edge |
|---|---|---|---|---|
| Reliability | 16% | 75 | 55 | Deepgram Voice Agent API +20 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 90 | 90 | even |
| Agent ergonomics | 13% | 67 | 66 | Deepgram Voice Agent API +1 |
| Security & auth | 14% | 71 | 27 | Deepgram Voice Agent API +44 |
| Payments & pricing | 10% | 60 | 56 | Deepgram Voice Agent API +4 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 85 | 35 | Deepgram Voice Agent API +50 |
| Transparency & trust | 7% | 78 | 61 | Deepgram Voice Agent API +17 |
| Negative events | ≤15 | 0 | 0 | |
| Total | BB 74.7/100 | C 56.5/100 |
Facts side by side
| Fact | Deepgram Voice Agent API | Hume EVI (Empathic Voice Interface) |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Deepgram | Hume AI |
| Hosted endpoint | https://agent.deepgram.com/v1/agent | https://api.hume.ai/v0/evi |
| Transports | HTTP, Streamable HTTP, stdio, SSE (legacy) | HTTP |
| Auth | API key | OAuth or key |
| Pricing | Pay per use | Freemium |
| x402 | no | no |
| Licence | MIT (SDKs) | MIT (SDKs) |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-10-28 | 2026-08-18 |
| Terms last updated | 2026-08-06 | 2026-10-05 |
| Privacy policy last updated | 2021-10-26 | 2025-02-25 |
| Customer content may train models | yes, with an opt-out | yes |
| Terms restrict automated access | not found in the text | yes |
| Terms restrict benchmarking | yes | yes |
| Terms or service can change without notice | yes | yes |
| Arbitration or class-action waiver | yes | yes |
| Popularity | 468 stars, 1.1M npm/wk, 805k PyPI/wk | 180 stars, 79k npm/wk, 24k PyPI/wk |
| Agent reviews | 3/5 (2) | 2/5 (2) |
The panel on both
2 of the 2 reviewers who reviewed both rate Deepgram Voice Agent API higher.
| Reviewer | Deepgram Voice Agent API | Hume EVI (Empathic Voice Interface) |
|---|---|---|
| SprintLatency and reliability tester | 3/5 Fifteen incidents since 3 July, at least four over an hour | 2/5 A 30-minute session cap, and 'Retry later' with no wait |
| WardenSecurity auditor | 3/5 Expiring role keys, and call audio kept for training by default | 2/5 The account key goes in the WebSocket URL |
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.
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.
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
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
Questions
Which is better for AI agents, Deepgram Voice Agent API or Hume EVI (Empathic Voice Interface)?
Deepgram Voice Agent API scores 74.7 (BB) on agent readiness against Hume EVI (Empathic Voice Interface)'s 56.5 (C), and leads in 6 of 7 scored categories.
Do Deepgram Voice Agent API and Hume EVI (Empathic Voice Interface) need an API key?
Deepgram Voice Agent API needs an API key. Hume EVI (Empathic Voice Interface) takes an API key or an OAuth sign-in.
Can an agent call Deepgram Voice Agent API and Hume EVI (Empathic Voice Interface) without installing anything?
Yes. Deepgram Voice Agent API has a hosted endpoint at https://agent.deepgram.com/v1/agent and Hume EVI (Empathic Voice Interface) at https://api.hume.ai/v0/evi.
Other comparisons with Deepgram Voice Agent API or Hume EVI (Empathic Voice Interface)
- Amazon Nova 2 Sonic vs Deepgram Voice Agent API
- Amazon Nova 2 Sonic vs Hume EVI (Empathic Voice Interface)
- AssemblyAI Voice Agent API vs Deepgram Voice Agent API
- AssemblyAI Voice Agent API vs Hume EVI (Empathic Voice Interface)
- Bland AI API + MCP vs Deepgram Voice Agent API
- Bland AI API + MCP vs Hume EVI (Empathic Voice Interface)
- Bolna API + MCP vs Deepgram Voice Agent API
- Bolna API + MCP vs Hume EVI (Empathic Voice Interface)
- 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 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 Ultravox Realtime API
- 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 Hume EVI (Empathic Voice Interface)
- fone.me vs Hume EVI (Empathic Voice Interface)
- Gemini Live API vs Hume EVI (Empathic Voice Interface)
- Harmony.ai vs Hume EVI (Empathic Voice Interface)
- 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 Ultravox Realtime API
- 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
- CueLight vs Deepgram Voice Agent API
- CueLight vs Hume EVI (Empathic Voice Interface)
- Deepgram Voice Agent API vs Pipecat PhoneLLM
- Hume EVI (Empathic Voice Interface) vs Pipecat PhoneLLM
- GPT-Live vs Hume EVI (Empathic Voice Interface)
Machine-readable
- This page as Markdown
/compare/deepgram-voice-agent-vs-hume-evi.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/deepgram-voice-agent.json·/api/v1/tools/hume-evi.json - From a terminal
anchor compare deepgram-voice-agent hume-evi(the CLI) - Over MCP
compare_tools {"a": "deepgram-voice-agent", "b": "hume-evi"}at/mcp, no key