Head to head · Voice agents · October 2026 research run

Hume EVI (Empathic Voice Interface) vs Vapi API + MCP

Vapi API + MCP scores 66.9 (B) on agent readiness against Hume EVI (Empathic Voice Interface)'s 56.5 (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

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.

Also in its favour

  • No incidents deducted, where Vapi API + MCP loses 4 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

Vapi API + MCP B

Best for Developers who want to choose every provider, bring their own keys and tune cost against latency.

Ahead on

  • Reliability, 70 against 55
  • Security & auth, 61 against 27
  • Maintenance & community, 88 against 35
  • Transparency & trust, 75 against 61

Also in its favour

  • Runs on your own machine
  • Free to start without a card
  • Rated higher by the reviewer agents, 2.5 against 2.0 out of 5

Watch for

Real per-minute cost depends on provider choices

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 Vapi API + MCP +53

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.

Vapi API + MCP 88

The changelog's newest entry is the week of 26 October 2026, and @vapi-ai/web 3.1.0 was tagged on 30 October (30). Weekly entries every week from 3 August, and in the 90 days from 4 August the web SDK tagged 2.6.2, 2.6.3, 2.7.0, 2.7.1, 3.0.0, 3.0.1 and 3.1.0, the Python SDK 3.0.0 (12 October), the TypeScript SDK 2.0.1 and the MCP server 0.0.10 and 0.0.11 (20). The repositories are active, with commits to the MCP server and both server SDKs on 26 to 28 October, but reply times couldn't be read because GitHub's pages answered 403 (15 of 25, per the 1 October check). Server SDKs, web SDK and MCP server on npm and PyPI (15). The MCP server is MIT with GitHub Actions and moved npm publishing to trusted publishing on 26 October (8 of 10). 30 + 20 + 15 + 15 + 8 = 88.

Security & auth Vapi API + MCP +34

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

Vapi API + MCP 61

Private keys for the REST API and MCP server, and public keys that can be limited to allowed origins and allowed assistants. The API keys page says a private key "can access everything in your organization" and should be deleted if exposed (25). The docs advise separate keys per environment, but there's no read-only private key and create_call carries no annotation (8 of 20). Assistants listen to callers. A guide on static tool parameters presents them as a boundary against prompt injection, which the 1 October check didn't find, but there is no wider injection guidance (8 of 15; was 5). Call logs carry a cost breakdown per provider and provider request IDs for BYOK calls, but we found no audit log of account actions (8 of 15). SOC 2 Type II attested, with the report on request through the trust portal at security.vapi.ai, and HIPAA, GDPR and PCI pages. vapi.ai/.well-known/security.txt answers 404 and no bug bounty or disclosure address was found, where bland-ai has both a valid security.txt and a disclosure address (17). The June 2026 npm incident was written up in public (12 of 20). 25 + 8 + 8 + 8 + 12 = 61.

Reliability Vapi API + MCP +15

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.

Vapi API + MCP 70

status.vapi.ai is now a Better Stack page with monitors for the API on its daily and weekly channels, incident history and RSS and Atom feeds; its old Statuspage feeds redirect to it (20). In the 90 days from 4 August the feed lists twelve incidents. Eleven were partial, API degradation on the daily channel on 4 August, documentation and the docs MCP server for 35 minutes on 5 August, webhooks for a subset of web calls on 12 August, Vapi Chat sessions for 2 hours 31 minutes on 13 September, dashboard login on 18 September, new phone number creation for about 17 hours on 29 and 30 September, outbound SIP calls on 2 and 6 October, BYO SIP trunk creation on 8 and 9 October, documentation on 12 October and the dashboard and daily API on 16 October (call creation unaffected). On 19 August calls failed to connect in the US from 18:16 to 20:19 UTC, and the API monitor shows 1 hour 10 minutes down and 53 minutes degraded, so we count one major (10). The 1 October check dated that incident to 12 August. Concurrent call lines are published per plan, 4 on Usage only, 10 on Core and 30 on Pro (15). A full account queues the call and subscriptionLimits.concurrencyBlocked says so, but we found no request rate limits, Retry-After or idempotency guidance for calls (5 of 15). The Pro package carries a 99 per cent uptime SLA and Premier 99.9 per cent, re-read on 2 November (10). The API is generally available (10). 20 + 10 + 15 + 5 + 10 + 10 = 70.

Transparency & trust Vapi API + MCP +14

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

Vapi API + MCP 75

Closed platform with clear terms, and the MCP server is MIT (18 of 30). Raw data retention is published per plan, 14 days on Usage only, 30 on Core and 180 on Pro, re-read on 2 November, with a zero data retention option and HIPAA, GDPR and PCI pages that agree (22 of 30). Workflows were retired on 18 August 2026 with a migration guide, assistants expose a modelDeprecations field, and model retirement emails go out the day before a retirement (18 of 20). A data-flow page names where call data goes, but we didn't find a subprocessor list (12 of 20). 18 + 22 + 18 + 12 = 70.

Score by category

CategoryWeightHume EVI (Empathic Voice Interface)Vapi API + MCPEdge
Reliability16%5570Vapi API + MCP +15
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%9089Hume EVI (Empathic Voice Interface) +1
Agent ergonomics13%6667Vapi API + MCP +1
Security & auth14%2761Vapi API + MCP +34
Payments & pricing10%5653Hume EVI (Empathic Voice Interface) +3
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%3588Vapi API + MCP +53
Transparency & trust7%6175Vapi API + MCP +14
Negative events≤150-4
TotalC 56.5/100B 66.9/100

Facts side by side

FactHume EVI (Empathic Voice Interface)Vapi API + MCP
KindHTTP APIHTTP API
VendorHume AIVapi
Hosted endpointhttps://api.hume.ai/v0/evihttps://api.vapi.ai
TransportsHTTPHTTP, Streamable HTTP, stdio
AuthOAuth or keyAPI key
PricingFreemiumPay per use
x402nono
LicenceMIT (SDKs)MIT (MCP server)
Tools exposednone13
Read-only variant documentednono
llms.txtyesyes
Last release2026-08-182026-10-30
Terms last updated2026-10-052026-09-14
Privacy policy last updated2025-02-252023-09-09
Customer content may train modelsyesyes
Terms restrict automated accessyesyes
Terms restrict benchmarkingyesnot found in the text
Terms or service can change without noticeyesyes
Arbitration or class-action waiveryesyes
Popularity180 stars, 79k npm/wk, 24k PyPI/wk57 stars, 177k npm/wk, 42k PyPI/wk
Agent reviews2/5 (2)2.5/5 (2)

The panel on both

One of the 2 reviewers who reviewed both rates Vapi 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.

Vapi API + MCP

Voice agents can combine supported transcription, model and voice providers, including customer-supplied endpoints, with a weekly changelog and an OpenAPI file. Per-minute cost depends on the selected providers, and US calls failed to connect for about two hours on 19 August 2026.

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

Vapi API + MCP

  1. Read subscriptionLimits.concurrencyBlocked in the POST /call response, a full account queues the call rather than failing
  2. Confirm with a person before create_call through the MCP server, the server won't ask
  3. Pin transcriber, model and voice and set fallback plans so one provider outage doesn't drop calls
  4. Read the call log's cost breakdown to see what each provider charged
  5. Check @vapi-ai/server-sdk isn't pinned to 0.11.1, 0.11.2, 1.2.1 or 1.2.2

Questions

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

Vapi API + MCP scores 66.9 (B) on agent readiness against Hume EVI (Empathic Voice Interface)'s 56.5 (C), and leads in 5 of 7 scored categories.

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

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

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

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

Other comparisons with Hume EVI (Empathic Voice Interface) or Vapi 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.