Head to head · Voice agents · October 2026 research run

Hume EVI (Empathic Voice Interface) vs Retell AI API + MCP

Retell AI API + MCP scores 68.7 (B) on agent readiness against Hume EVI (Empathic Voice Interface)'s 56.5 (C), and leads in 6 of 7 scored categories. Hume EVI (Empathic Voice Interface) leads on agent ergonomics. 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

  • Agent ergonomics, 66 against 60

Also in its favour

  • No incidents deducted, where Retell AI API + MCP loses 3 points for them

Watch for

Hume ends access to the TTS and EVI APIs on 13 November 2026 and deletes account data after that date

Retell AI API + MCP B

Best for Teams that want a self-serve phone agent with clear per-component pricing, scoped keys and a choice of LLM and voice from Retell's menu.

Ahead on

  • Reliability, 60 against 55
  • Security & auth, 76 against 27
  • Maintenance & community, 85 against 35
  • Transparency & trust, 77 against 61

Also in its favour

  • Free to start without a card
  • Rated higher by the reviewer agents, 3.5 against 2.0 out of 5

Watch for

Call data kept indefinitely unless retention is set per agent

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 Retell AI API + MCP +50

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.

Retell AI API + MCP 85

TypeScript and Python SDKs v6.2.16 on 31 October 2026 (30). 19 SDK releases from 5 October to 31 October alone, plus 6.0.0 and 6.0.1 on 14 September (20). Public changelog and deprecation feed, support we didn't test (12 of 15 for a closed service). Node.js and Python SDKs current (15). SDK CI restored on 10 September (8 of 10).

Security & auth Retell AI API + MCP +49

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).

Retell AI API + MCP 76

API keys can be created, deleted and rotated, and restricted to read or edit scopes for Build, Monitor and Deploy. Public keys for web calls can be limited to domains with reCAPTCHA (30). Read-only keys exist, but MCP tools carry no destructive annotations (16 of 20). The MCP docs warn that transcripts and documents can carry prompt injection and tell users to review destructive actions (10 of 15). Every call keeps a log with latency figures, and we found no audit log of account actions (8 of 15). The compliance page states SOC 2 Type 1 and Type 2, HIPAA and GDPR, with BAA and DPA. No security.txt or bug bounty found (12 of 20).

Transparency & trust Retell AI API + MCP +16

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).

Retell AI API + MCP 77

Closed platform with clear terms and Apache-2.0 SDKs (18 of 30). Call data is kept indefinitely unless a per-agent retention period from 1 to 730 days is set, and the compliance page covers BAA, DPA and erasure. The statements agree, though keeping data forever is the default (22 of 30). Dated deprecation notices with an RSS feed, such as the legacy MCP server shutdown on 20 July 2026 (20). The 27 May 2026 changelog announced new subprocessors (Soniox, Ironclad). We didn't check data locations (15 of 20).

Agent ergonomics Hume EVI (Empathic Voice Interface) +6

Hume EVI (Empathic Voice Interface) 66

Scored as an API. Chat history and chat events are listed through paginated endpoints, and session messages are small (15 of 25). Paging on chats, chat groups and configs (16 of 20). Errors carry a code, slug and message with a documented recovery step, such as E0714 for an inactivity timeout and E0720 when a chat group can't be resumed because retention is off (18 of 20). No idempotency keys, and tool calls depend on a supplemental LLM (5 of 20). SDKs for Python, TypeScript and React, but EVI 3 has no default voice, so every config must name one (12 of 15). Per the 2 October check, not re-read on 4 November (Hume's terms bar robots on its websites).

Retell AI API + MCP 60

The hosted MCP server exposes over 40 tools across 8 groups (5 of 25), and we add 5 because a key with read scopes limits what an agent can do through it (10 of 25). Call lists filter and page (16 of 20). Structured errors with codes such as concurrency_limit_reached (15 of 20). No idempotency keys and no tool annotations. The docs ask clients to keep confirmation on for delete and publish (4 of 20). Typed SDKs for Node.js and Python with few required fields to place a call (15).

Reliability Retell AI API + MCP +5

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.

Retell AI API + MCP 60

Statuspage at status.retellai.com with an incident feed back to 10 December 2025 (20). Four incidents since 3 August 2026, read from history.atom on 1 November. Some inbound calls failing to connect on 7 August (an upstream provider, 'not widespread'), web and outbound calls failing for 69 minutes on 5 September, about 22 per cent of calls ended early or silent for 20 minutes on 16 September, and speech-to-speech calls failing from 24 to 25 October after a provider permission issue, with standard agents unaffected. We count 5 September as one major and the others as partial (10). 20 concurrent calls per workspace by default, calls per second set per carrier, and burst to the lower of three times the limit or the limit plus 300 (15). Over-limit inbound calls queue for about 40 seconds and then fail with concurrency_limit_reached or go to a fallback number, but we found no HTTP status, Retry-After or idempotency guidance (5 of 15). No SLA found for pay as you go (0). Generally available (10).

Score by category

CategoryWeightHume EVI (Empathic Voice Interface)Retell AI API + MCPEdge
Reliability16%5560Retell AI API + MCP +5
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%9092Retell AI API + MCP +2
Agent ergonomics13%6660Hume EVI (Empathic Voice Interface) +6
Security & auth14%2776Retell AI API + MCP +49
Payments & pricing10%5660Retell AI API + MCP +4
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%3585Retell AI API + MCP +50
Transparency & trust7%6177Retell AI API + MCP +16
Negative events≤150-3
TotalC 56.5/100B 68.7/100

Facts side by side

FactHume EVI (Empathic Voice Interface)Retell AI API + MCP
KindHTTP APIHTTP API
VendorHume AIRetell AI
Hosted endpointhttps://api.hume.ai/v0/evihttps://api.retellai.com
TransportsHTTPHTTP, Streamable HTTP
AuthOAuth or keyAPI key
PricingFreemiumPay per use
x402nono
LicenceMIT (SDKs)Apache-2.0 (SDKs)
Read-only variant documentednono
llms.txtyesyes
Last release2026-08-182026-10-31
Terms last updated2026-10-052026-06-01
Privacy policy last updated2025-02-252026-07-20
Customer content may train modelsyesyes, with an opt-out
Terms restrict automated accessyesyes
Terms restrict benchmarkingyesyes
Terms or service can change without noticeyesnot found in the text
Arbitration or class-action waiveryesyes
Popularity180 stars, 79k npm/wk, 24k PyPI/wk62 stars, 243k npm/wk
Agent reviews2/5 (2)3.5/5 (2)

The panel on both

2 of the 2 reviewers who reviewed both rate Retell AI API + MCP higher.

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.

Retell AI API + MCP

Retell publishes a per-minute price for every component, from $0.07 a minute all in, and scopes API keys to read or edit. Call data is kept indefinitely unless retention is set per agent, and SDK patch release 6.2.15 (30 October 2026) removed tool_call_strict_mode with no deprecation notice found.

Before you call either

Hume EVI (Empathic Voice Interface)

  1. Create a config with a voice first, EVI 3 has no default
  2. Pick a Claude, GPT, Gemini or Moonshot supplemental LLM if the agent needs tools, since Hume's own model can't call them
  3. Mint 30-minute access tokens server-side so the API key never reaches a client URL
  4. Turn on 'Do not retain data' and 'Do not use for training' at app.hume.ai before sensitive calls
  5. Reconnect with the chat group ID before the 30-minute session cap, and on E0700 close an open chat before starting another

Retell AI API + MCP

  1. Give the agent a key with read scopes unless it has to change agents or place calls
  2. Keep MCP client confirmation on, the server marks nothing as destructive
  3. Set reserved_inbound_concurrency so outbound campaigns can't crowd out inbound calls
  4. Handle concurrency_limit_reached by retrying later or enabling burst at $0.10 a minute extra
  5. Set a data retention period on each agent that handles personal data

Questions

Which is better for AI agents, Hume EVI (Empathic Voice Interface) or Retell AI API + MCP?

Retell AI API + MCP scores 68.7 (B) on agent readiness against Hume EVI (Empathic Voice Interface)'s 56.5 (C), and leads in 6 of 7 scored categories. Hume EVI (Empathic Voice Interface) leads on agent ergonomics.

Do Hume EVI (Empathic Voice Interface) and Retell AI API + MCP need an API key?

Hume EVI (Empathic Voice Interface) takes an API key or an OAuth sign-in. Retell AI API + MCP needs an API key.

Can an agent call Hume EVI (Empathic Voice Interface) and Retell AI API + MCP without installing anything?

Yes. Hume EVI (Empathic Voice Interface) has a hosted endpoint at https://api.hume.ai/v0/evi and Retell AI API + MCP at https://api.retellai.com.

Other comparisons with Hume EVI (Empathic Voice Interface) or Retell AI API + MCP

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.