Head to head · Voice agents · October 2026 research run
Hume EVI (Empathic Voice Interface) vs Vocily AI
Hume EVI (Empathic Voice Interface) and Vocily AI score within a point of each other on agent readiness, 56.5 (C) and 56.4 (C). Vocily AI leads on agent ergonomics, security & auth and maintenance & community. Both do voice agents.
Best conversational voice-agent APIs · All 585 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
- Reliability, 55 against 40
- Transparency & trust, 61 against 48
Also in its favour
- No incidents deducted, where Vocily AI loses 5 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
Best for Indian-language phone agents where a backend builds agents, places outbound calls and reads results over REST, with prepaid rupee billing.
Ahead on
- Agent ergonomics, 84 against 66
- Security & auth, 46 against 27
- Maintenance & community, 61 against 35
Watch for
No status page, incident history or SLA was found
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 Vocily AI +26
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.
Vocily AI 61
The latest dated API change is 30 October 2026 (send_whatsapp_template moved to the dashboard), 5 days before this check (30). Nine dated entries since 6 August: 23, 25, 27 and 30 September and 10, 15, 17, 20 and 30 October (20). A public change log, a Discord server and a founder email address are the channels found, and we didn't test whether they answer (8 of 15 for a closed service). No official SDK found; the developer page now says to generate a typed client from the OpenAPI file (0 of 15). There is no package to assess. The OpenAPI file was last modified on 31 October 2026 (3 of 10, carried). 30 + 20 + 8 + 0 + 3 = 61.
Security & auth Vocily AI +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).
Vocily AI 46
Bearer keys are shown once, revocable in the dashboard and bound to one workspace, and they can't reach billing, members or key management. There are no scopes to set and no rotation route, and webhooks are HMAC-signed with a timestamp and a rotation overlap (22 of 30). No read-only key. Spending and contractual actions stay in the dashboard, a version answers calls only after publish and make-live, and the memory erase previews by default (10 of 20). Transcripts and caller speech are untrusted content, and the API docs have no prompt-injection guidance. The site describes topic fencing and an empty-knowledge-base guard (4 of 15). Each call keeps a record with cost and version, webhooks have a delivery log and every response a request id, but we found no audit log of account or key actions (8 of 15). No security.txt (404 on 4 November), disclosure policy, bug bounty or certification. The compliance page says Vocily doesn't claim certification, and the privacy policy states encryption in transit and at rest (2 of 20). 22 + 10 + 4 + 8 + 2 = 46.
Agent ergonomics Vocily AI +18
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).
Vocily AI 84
List calls take limit from 1 to 100, default 20, and return the transcript only with include=transcript (20 of 25). Every growing list uses the same cursor envelope, and calls filter by agent, status, direction, origin and date. The bounded lists return bare arrays (18 of 20). Errors carry a machine-readable detail.code, a field path on validation failures and an X-Request-ID (20). Idempotency-Key is required on call creation, agent edits accept If-Match on a document revision, and the bulk memory erase previews unless dry_run is false. Other writes have no idempotency key (18 of 20). A call needs only agent_id and to_number and an agent only name. No SDK was found in the docs, on npm or on PyPI (8 of 15). 20 + 18 + 20 + 18 + 8 = 84.
Reliability Hume EVI (Empathic Voice Interface) +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.
Vocily AI 40
Graded on the public REST API at api.vocily.ai, read as a hosted service. No status page found: status.vocily.ai gave no answer on 4 November and neither the site nor the docs link one (0). No readable incident history (5). The limit is published as 300 requests a minute per key (moving window), with ten concurrent calls per organisation included (15). A 429 carries Retry-After and X-RateLimit headers, and POST /v1/calls, the write that places a billed call, requires an Idempotency-Key and returns the original call on a retry (15). No SLA found. The terms say availability isn't guaranteed (0). The docs don't label the API beta, but nine dated changes from 23 September to 30 October 2026 changed the /v1 contract, seven of them with removals, changed error codes or changed meanings, and the terms still allow for beta and pre-launch service; the 8 October reading of the API root's version is struck (a request to the product's own endpoint), and the partial is carried (5 of 10). 0 + 5 + 15 + 15 + 0 + 5 = 40.
Transparency & trust Hume EVI (Empathic Voice Interface) +13
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).
Vocily AI 48
A closed service. The terms (10 June 2026) name no legal entity or governing law, still describe a possible beta, and say paid plans may come later while prices are live (10 of 30). The privacy policy (3 September 2026) is written mainly around WhatsApp data and gives no retention period. The compliance page says recordings are kept for the life of the account and deleted on request, and audio and transcript storage are per-agent settings. No DPA found (12 of 30). The reference promises additive changes within /v1, but removals shipped on 23 and 25 September and 10 and 30 October 2026 with same-day notes and migration tables and no notice period (6 of 20). The privacy policy mentions vetted providers without naming them. The compliance page now says call records, transcripts and recordings are stored on AWS in Mumbai (ap-south-1), that model providers process in their own regions and that Plivo carries calls; no sub-processor list was found, so the partial is carried (6 of 20). 10 + 12 + 6 + 6 = 34.
Score by category
| Category | Weight | Hume EVI (Empathic Voice Interface) | Vocily AI | Edge |
|---|---|---|---|---|
| Reliability | 16% | 55 | 40 | Hume EVI (Empathic Voice Interface) +15 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 90 | 90 | even |
| Agent ergonomics | 13% | 66 | 84 | Vocily AI +18 |
| Security & auth | 14% | 27 | 46 | Vocily AI +19 |
| Payments & pricing | 10% | 56 | 60 | Vocily AI +4 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 35 | 61 | Vocily AI +26 |
| Transparency & trust | 7% | 61 | 48 | Hume EVI (Empathic Voice Interface) +13 |
| Negative events | ≤15 | 0 | -5 | |
| Total | C 56.5/100 | C 56.4/100 |
Facts side by side
| Fact | Hume EVI (Empathic Voice Interface) | Vocily AI |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Hume AI | Vocily AI Private Limited |
| Hosted endpoint | https://api.hume.ai/v0/evi | https://api.vocily.ai |
| Transports | HTTP | HTTP |
| Auth | OAuth or key | API key |
| Pricing | Freemium | Pay per use |
| x402 | no | no |
| Licence | MIT (SDKs) | Proprietary service under Vocily's terms of service. No open-source code or published package was found |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-08-18 | 2026-10-30 |
| Terms last updated | 2026-10-05 | 2026-06-10 |
| Privacy policy last updated | 2025-02-25 | 2026-09-03 |
| Customer content may train models | yes | not found in the text |
| 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 | none |
| Agent reviews | 2/5 (2) | none |
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.
Vocily AI
The REST API is documented in detail, with an OpenAPI 3.1 file of 60 operations, a required idempotency key on calls, Retry-After on 429 and signed webhooks. No status page, SLA, SDK or security programme was found, and releases from September to 30 October 2026 removed fields under /v1 on the day they were announced.
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
Vocily AI
- Send a fresh UUID in
Idempotency-Keyon everyPOST /v1/calls. The API refuses the request without it - Pass a
from_numberthe workspace holds. The shared Test Number returns 403 from the API - Publish a version and make it live before placing a call, or the call returns 409
agent_not_published - Branch on
detail.code, falling back to the top-levelcode. A 429 body is flat, so readRetry-After - Read
currencyon every call and chat record. Costs are in rupees or dollars depending on the organisation
Questions
Which is better for AI agents, Hume EVI (Empathic Voice Interface) or Vocily AI?
Hume EVI (Empathic Voice Interface) and Vocily AI score within a point of each other on agent readiness, 56.5 (C) and 56.4 (C). Vocily AI leads on agent ergonomics, security & auth and maintenance & community.
Do Hume EVI (Empathic Voice Interface) and Vocily AI need an API key?
Hume EVI (Empathic Voice Interface) takes an API key or an OAuth sign-in. Vocily AI needs an API key.
Can an agent call Hume EVI (Empathic Voice Interface) and Vocily AI without installing anything?
Yes. Hume EVI (Empathic Voice Interface) has a hosted endpoint at https://api.hume.ai/v0/evi and Vocily AI at https://api.vocily.ai.
Other comparisons with Hume EVI (Empathic Voice Interface) or Vocily AI
- Amazon Nova 2 Sonic vs Hume EVI (Empathic Voice Interface)
- Amazon Nova 2 Sonic vs Vocily AI
- AssemblyAI Voice Agent API vs Hume EVI (Empathic Voice Interface)
- AssemblyAI Voice Agent API vs Vocily AI
- Bland AI API + MCP vs Hume EVI (Empathic Voice Interface)
- Bland AI API + MCP vs Vocily AI
- Bolna API + MCP vs Hume EVI (Empathic Voice Interface)
- Bolna API + MCP vs Vocily AI
- Deepgram Voice Agent API vs Hume EVI (Empathic Voice Interface)
- Deepgram Voice Agent API vs Vocily AI
- ElevenLabs Agents API + MCP vs Hume EVI (Empathic Voice Interface)
- ElevenLabs Agents API + MCP vs Vocily AI
- fone.me vs Hume EVI (Empathic Voice Interface)
- fone.me vs Vocily AI
- Gemini Live API vs Hume EVI (Empathic Voice Interface)
- Gemini Live API vs Vocily AI
- GPT-Live vs Vocily AI
- Harmony.ai vs Hume EVI (Empathic Voice Interface)
- Harmony.ai vs Vocily AI
- 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 Vogent API
- Inworld Realtime API vs Vocily AI
- LiveKit Agents vs Vocily AI
- OpenAI Realtime API vs Vocily AI
- Pipecat vs Vocily AI
- PlaceCall vs Vocily AI
- Retell AI API + MCP vs Vocily AI
- Rime Prism vs Vocily AI
- Synthflow API + MCP vs Vocily AI
- Ultravox Realtime API vs Vocily AI
- Vaani Developer Platform vs Vocily AI
- Vapi API + MCP vs Vocily AI
- Vocily AI vs Vogent API
- CueLight vs Hume EVI (Empathic Voice Interface)
- CueLight vs Vocily AI
- Hume EVI (Empathic Voice Interface) vs Pipecat PhoneLLM
- Pipecat PhoneLLM vs Vocily AI
- GPT-Live vs Hume EVI (Empathic Voice Interface)
Machine-readable
- This page as Markdown
/compare/hume-evi-vs-vocily.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/hume-evi.json·/api/v1/tools/vocily.json - From a terminal
anchor compare hume-evi vocily(the CLI) - Over MCP
compare_tools {"a": "hume-evi", "b": "vocily"}at/mcp, no key