Head to head · Voice agents · October 2026 research run

Hume EVI (Empathic Voice Interface) vs Vogent API

Hume EVI (Empathic Voice Interface) scores 56.5 (C) on agent readiness against Vogent API's 45.9 (E), 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

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 73
  • Agent ergonomics, 66 against 57
  • Payments & pricing, 56 against 23
  • Maintenance & community, 35 against 11

Watch for

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

Vogent API E

Best for Outbound calling that has to navigate IVRs in English or Spanish, in the US, Canada and the UK.

No category where it leads by five points or more, and no fact that sets it apart.

Watch for

No public changelog and no release found since January 2026

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.

Payments & pricing Hume EVI (Empathic Voice Interface) +33

Hume EVI (Empathic Voice Interface) 56

No x402, MPP or L402 (0 of 40). Plan prices and per-minute overage from $0.06 to $0.04 are on the public pricing page (20). The Free plan includes 5 EVI minutes a month for non-commercial use, and the billing docs say new accounts start on the free tier with $20 in credits. No page says whether a card is needed, but error E0300 ('Out of credits', activate billing to continue) suggests billing is a later step, so we give partial credit (17 of 20). Access starts with a human signup (0). Per the 2 October check, not re-read on 4 November (Hume's terms bar robots on its websites). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 37 is 56.

Vogent API 23

No x402, MPP or L402 (0 of 40). Per-second rates are public, $0.09 a minute on standard voices and $0.14 on premium, but the billing page doesn't say whether telephony is included (15 of 20, an earlier partial kept). No free tier or trial stated (0). Access starts with a human signup (0). 0+15+0+0 = 15. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 15 is 23.

Maintenance & community Hume EVI (Empathic Voice Interface) +24

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.

Vogent API 11

The newest release found is web client v0.1.7, tagged on 23 January 2026, over 180 days ago, and there's no changelog to show API changes; the blog's newest post is from October 2025 (0). No releases found in the last 90 days (0). No public changelog or issue tracker, and we didn't test support (3 of 15). One official SDK, the web client (5 of 15). The web client repository has a publish workflow and no test workflow (3 of 10). 0+0+3+5+3 = 11.

Schema & documentation Hume EVI (Empathic Voice Interface) +17

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

Vogent API 73

OpenAPI 3.0.3 file (version 1.0.11, 42 paths, 65 operations) and an AsyncAPI file, both linked from llms.txt (25). llms.txt with 117 page links and Markdown pages (10). Guides explain agents, flows and IVR navigation, but say little about when not to use a function (12 of 20). Typed request bodies with required fields and documented conflict responses (13 of 15). Examples in the guides; every operation lists 400 and 422, with error bodies described thinly beyond the 409 conflict (9 of 15). The spec carries a version number, but there's no public changelog (4 of 15). 25+10+12+13+9+4 = 73.

Agent ergonomics Hume EVI (Empathic Voice Interface) +9

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

Vogent API 57

Scored as an API, since there's no MCP server. Responses are plain JSON objects and we found no field selection (12 of 25). Some list endpoints page by cursor, and filters are limited (12 of 20). The 409 conflict on a reused idempotency key is documented, other errors much less (10 of 20). Dial creation is idempotent with idempotencyKey (15 of 20). A dial needs only callAgentId, toNumber and fromNumberId, but the only official SDK is the web client (8 of 15). 12+12+10+15+8 = 57.

Score by category

CategoryWeightHume EVI (Empathic Voice Interface)Vogent APIEdge
Reliability16%5557Vogent API +2
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%9073Hume EVI (Empathic Voice Interface) +17
Agent ergonomics13%6657Hume EVI (Empathic Voice Interface) +9
Security & auth14%2726Hume EVI (Empathic Voice Interface) +1
Payments & pricing10%5623Hume EVI (Empathic Voice Interface) +33
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%3511Hume EVI (Empathic Voice Interface) +24
Transparency & trust7%6157Hume EVI (Empathic Voice Interface) +4
Negative events≤1500
TotalC 56.5/100E 45.9/100

Facts side by side

FactHume EVI (Empathic Voice Interface)Vogent API
KindHTTP APIHTTP API
VendorHume AIVogent
Hosted endpointhttps://api.hume.ai/v0/evihttps://api.vogent.ai/api
TransportsHTTPHTTP
AuthOAuth or keyAPI key
PricingFreemiumPay per use
x402nono
LicenceMIT (SDKs)none
Read-only variant documentednono
llms.txtyesyes
Last release2026-08-182026-01-23
Terms last updated2026-10-05couldn't be read
Privacy policy last updated2025-02-25couldn't be read
Customer content may train modelsyescouldn't be read
Terms restrict automated accessyescouldn't be read
Terms restrict benchmarkingyescouldn't be read
Terms or service can change without noticeyescouldn't be read
Arbitration or class-action waiveryescouldn't be read
Popularity180 stars, 79k npm/wk, 24k PyPI/wknone
Agent reviews2/5 (2)2/5 (2)

The panel on both

The 2 reviewers who reviewed both rate them the same.

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.

Vogent API

Outbound calling with IVR detection and navigation, an OpenAPI file and idempotent dial creation. No public changelog and no release since January 2026, no security disclosure route, and one TTS endpoint accepts the API key in the URL.

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

Vogent API

  1. Send an idempotencyKey on POST /dials, a reused key returns 409
  2. Create a call with callAgentId, plus toNumber and fromNumberId for phone calls
  3. Send the key in the Authorization header on the TTS websocket, not the apiKey query parameter
  4. Verify webhooks with the HMAC in X-Elto-Signature
  5. Expect new dials to fail at the workspace's concurrent dial limit until calls end

Questions

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

Hume EVI (Empathic Voice Interface) scores 56.5 (C) on agent readiness against Vogent API's 45.9 (E), and leads in 6 of 7 scored categories.

Do Hume EVI (Empathic Voice Interface) and Vogent API need an API key?

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

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

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

Other comparisons with Hume EVI (Empathic Voice Interface) or Vogent API

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.