{ "data": { "a": { "slug": "hume-evi", "name": "Hume EVI (Empathic Voice Interface)", "vendor": "Hume AI", "vendorUrl": "https://www.hume.ai", "kind": "http-api", "category": "voice-agents", "summary": "Hume's hosted voice-agent service, accessed through a WebSocket API.", "url": "https://www.anchorterminal.com/tools/hume-evi", "markdownUrl": "https://www.anchorterminal.com/tools/hume-evi.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/hume-evi.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/hume-evi.json", "repo": "https://github.com/HumeAI/hume-python-sdk", "license": "MIT (SDKs)", "transports": [ "http" ], "remoteUrl": "https://api.hume.ai/v0/evi", "packages": [ { "registry": "npm", "name": "hume" }, { "registry": "pypi", "name": "hume" }, { "registry": "npm", "name": "@humeai/voice-react" } ], "auth": "mixed", "authNotes": "`X-Hume-Api-Key` header for REST. The chat WebSocket takes `api_key` or a short-lived `access_token` in the query string. The Twilio webhook URL carries the API key as a query parameter.", "pricing": "freemium", "pricingNotes": "Free includes 5 EVI minutes a month and 1 concurrent connection. Starter $3 40 minutes, Creator $14 ($7 first month) 200 minutes, Pro $70 1,200 minutes then $0.06 a minute, Scale $200 5,000 then $0.05, Business $500 12,500 then $0.04. External LLM usage is billed on top. Free and Starter are non-commercial (https://www.hume.ai/pricing).", "priceSummary": "$14 / mo", "where": "hosted", "x402": { "level": "no", "evidence": "No x402 or machine payment in the docs or pricing (checked 2026-09-30).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": 180, "npmWeekly": 79177, "pypiWeekly": 23750, "asOf": "2026-09-30" }, "docsUrl": "https://dev.hume.ai/docs/speech-to-speech-evi/overview", "llmsTxt": "https://dev.hume.ai/llms.txt", "openapi": "https://dev.hume.ai/openapi/speech-to-speech-evi.json", "capabilities": [ "voice.agent", "voice.speech-to-speech", "voice.pipeline", "voice.tools", "voice.telephony" ], "tags": [ "hosted", "freemium", "free-tier", "closed-source", "python", "typescript", "llms-txt", "speech-to-speech", "pipeline", "streaming", "websocket", "webhooks", "enterprise", "status-page" ], "lastRelease": "2026-08-18", "graded": true, "anchor": { "graded": true, "score": 56.7, "grade": "C", "agentReady": false, "rank": 486, "ranked": true, "rankOf": 722, "categoryRank": 7, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 66, "maintenance": 65, "payments": 37, "reliability": 55, "schema": 90, "security": 27, "transparency": 61 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-01" }, "negative": 0, "verdict": "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.", "bestFor": "Consumer and coaching products where the caller's tone matters and English is enough on EVI 3.", "strengths": [ "Speech-language model that reads the caller's tone and answers with matching prosody", "4 to 7 cents a minute including Hume's own model", "External LLMs or a custom endpoint for tool calling", "AsyncAPI 2.6.0 file for the EVI WebSocket and an error catalogue with a recovery step for each code", "Dated end-of-support notices for older EVI versions" ], "weaknesses": [ "One account-wide key, sent in the WebSocket and Twilio webhook URLs", "Privacy page contradicts itself on training use of EVI data", "EVI down in a majority of cases for about 6.5 hours on 11 July 2026, posted to the status page three days later", "Public changelog ends at 15 May 2026", "No HTTP 429, Retry-After or backoff guidance, only 'retry later' error codes" ], "agentNotes": [ "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" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 2, "avgRating": 2, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 56.7 } ], "editorialScores": { "ergonomics": 66, "maintenance": 65, "payments": 37, "reliability": 55, "schema": 90, "security": 27, "transparency": 48 }, "provenanceScore": 73 }, "connect": { "http": "curl https://api.hume.ai/v0/evi/configs -H \"X-Hume-Api-Key: $HUME_API_KEY\"" }, "letme": { "capability": "https://letme.dev/voice.agent", "tool": "https://letme.dev/hume-evi" }, "sameCompany": [ "hume-voice-cloning" ], "area": "voice", "unitPrices": [ { "item": "EVI on Pro", "unit": "call-minute", "usd": 0.06, "note": "overage after 1,200 included minutes, Hume model included, external LLM extra" }, { "item": "EVI on Scale", "unit": "call-minute", "usd": 0.05, "note": "overage after 5,000 included minutes" }, { "item": "EVI on Business", "unit": "call-minute", "usd": 0.04, "note": "overage after 12,500 included minutes" }, { "item": "Creator plan", "unit": "month", "usd": 14, "note": "200 EVI minutes, 5 concurrent, $7 first month" }, { "item": "Pro plan", "unit": "month", "usd": 70, "note": "1,200 EVI minutes, 10 concurrent" } ], "provenance": { "legalEntity": "Hume AI, Inc.", "domain": "hume.ai", "domainRegistered": "2020-04-06", "endpointOnVendorDomain": true, "terms": "https://www.hume.ai/terms-of-use", "privacy": "https://www.hume.ai/privacy-policy", "statusPage": "https://status.hume.ai", "changelog": "https://dev.hume.ai/changelog", "securityTxt": "none", "checked": "2026-09-30", "score": 73 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/hume-evi.json", "live": { "slug": "hume-evi", "probe": { "target": "https://api.hume.ai/v0/evi", "method": "get", "lastAt": "2026-10-08T20:09:47.581345314Z", "lastOk": true, "lastStatus": 404, "lastMs": 213, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 181, "p95ms24h": 269, "samples24h": 272, "samples30d": 2146, "days": [ { "date": "2026-09-30", "probes": 35, "ok": 35 }, { "date": "2026-10-01", "probes": 276, "ok": 276 }, { "date": "2026-10-02", "probes": 248, "ok": 248 }, { "date": "2026-10-03", "probes": 271, "ok": 271 }, { "date": "2026-10-04", "probes": 272, "ok": 272 }, { "date": "2026-10-05", "probes": 272, "ok": 272 }, { "date": "2026-10-06", "probes": 272, "ok": 272 }, { "date": "2026-10-07", "probes": 272, "ok": 272 }, { "date": "2026-10-08", "probes": 228, "ok": 228 } ] }, "vendorStatus": { "page": "https://status.hume.ai", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-08T20:01:05.137659469Z" }, "versions": [ { "registry": "github", "name": "HumeAI/hume-python-sdk", "version": "v0.14.0", "released": "2026-06-17", "seenAt": "2026-10-08T16:16:19.139438596Z" }, { "registry": "npm", "name": "@humeai/voice-react", "version": "0.3.0-beta.6", "seenAt": "2026-10-08T16:16:18.914229577Z" }, { "registry": "npm", "name": "hume", "version": "0.16.1", "seenAt": "2026-10-08T16:16:13.575758324Z" }, { "registry": "pypi", "name": "hume", "version": "0.14.1", "released": "2026-08-17", "seenAt": "2026-10-08T16:16:18.723171327Z" } ], "githubStars": 181, "npmWeekly": 82525, "pypiWeekly": 19565, "securityTxt": { "url": "https://hume.ai/.well-known/security.txt", "state": "none", "checkedAt": "2026-10-08T15:39:08.10154338Z" }, "llmsTxt": { "url": "https://dev.hume.ai/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-10-08T14:00:31.616139606Z" }, "domain": { "domain": "hume.ai", "registered": "2020-04-06", "source": "https://rdap.identitydigital.services/rdap/domain/hume.ai", "checkedAt": "2026-10-04T13:04:35.90510371Z" }, "pages": [ { "url": "https://dev.hume.ai/changelog", "kind": "changelog", "status": 200, "checkedAt": "2026-10-08T18:16:57.75925123Z", "changedAt": "2026-10-07T18:03:50.996699372Z", "fingerprint": "835f41512f87" }, { "url": "https://dev.hume.ai/docs/speech-to-speech-evi/configuration/evi-version", "kind": "deprecations", "status": 200, "checkedAt": "2026-10-08T18:17:01.36706317Z", "changedAt": "2026-10-08T18:17:01.36706317Z", "fingerprint": "4e0a06676652" }, { "url": "https://www.hume.ai/pricing", "kind": "pricing", "status": 304, "checkedAt": "2026-10-08T18:28:21.159396124Z", "changedAt": "2026-10-07T18:12:20.387954598Z", "fingerprint": "4cb5d5bdce6c" }, { "url": "https://www.hume.ai/privacy-policy", "kind": "privacy", "status": 304, "checkedAt": "2026-10-08T18:28:23.34725682Z", "changedAt": "2026-10-07T18:12:22.545753584Z", "fingerprint": "2ea7655d6bc1" }, { "url": "https://www.hume.ai/terms-of-use", "kind": "terms", "status": 304, "checkedAt": "2026-10-08T18:28:25.310869642Z", "changedAt": "2026-10-07T18:12:24.556500594Z", "fingerprint": "7e3429fcec08" } ], "updatedAt": "2026-10-08T20:09:47.581345314Z" } }, "answer": "Hume EVI (Empathic Voice Interface) scores 56.7 (C) on agent readiness against Vocily AI's 53.8 (D), and leads in 3 of 7 scored categories. Vocily AI leads on agent ergonomics and security \u0026 auth.", "b": { "slug": "vocily", "name": "Vocily AI", "vendor": "Vocily AI Private Limited", "vendorUrl": "https://vocily.ai", "kind": "http-api", "category": "voice-agents", "summary": "Vocily AI is a hosted voice-agent platform from Bengaluru for phone calls, WhatsApp and website voice and chat, aimed at Indian languages. Its REST API builds and publishes agents, places outbound calls and reads back transcripts, recordings and costs.", "url": "https://www.anchorterminal.com/tools/vocily", "markdownUrl": "https://www.anchorterminal.com/tools/vocily.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/vocily.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/vocily.json", "license": "Proprietary service under Vocily's terms of service. No open-source code or published package was found", "transports": [ "http" ], "remoteUrl": "https://api.vocily.ai", "packages": [], "auth": "api-key", "authNotes": "A Bearer API key (`vk_...`) created in the dashboard under Developers, API Keys, shown once and revocable there. A key is bound to one workspace and reaches the whole public API for it. Billing, team members, account settings and key management answer 403 to any key. Keys have no scopes to configure, although the error table names an `agents:publish` permission for making a version live. Webhooks are signed with HMAC-SHA256 and a timestamp, with two signatures sent during a secret rotation. Access is self-serve after an email-verified signup.", "pricing": "usage", "pricingNotes": "Prepaid wallet with no monthly fee, billed in rupees or US dollars as chosen at signup, each with its own price list. Voice starts at ₹3.10 or $0.041 a connected minute (speech-to-text, model, voice and a $0.03 platform fee), and telephony is free on your own Plivo or VoBiz account or $0.004 a minute in 30-second pulses on a rented number. Chat is charged per model reply from $0.001. A new organisation gets ₹200 or $2 of credit with no card. Ten concurrent calls are included and a pack of two more is $8 a month (https://vocily.ai/pricing).", "priceSummary": "$8 / mo", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the docs, the OpenAPI file or the pricing page (checked 2026-10-08).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-08" }, "docsUrl": "https://docs.vocily.ai", "llmsTxt": "https://docs.vocily.ai/llms.txt", "openapi": "https://docs.vocily.ai/developers/openapi.json", "capabilities": [ "voice.agent", "voice.pipeline", "voice.tools", "voice.telephony" ], "tags": [ "hosted", "india", "openapi", "llms-txt", "webhooks", "pipeline", "telephony", "whatsapp", "prepaid", "new" ], "lastRelease": "2026-09-30", "graded": true, "anchor": { "graded": true, "score": 53.8, "grade": "D", "agentReady": false, "rank": 540, "ranked": true, "rankOf": 722, "categoryRank": 8, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 84, "maintenance": 61, "payments": 40, "reliability": 40, "schema": 90, "security": 46, "transparency": 47 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-08" }, "negative": -5, "negativeNotes": [ "2026-09-23 and 2026-09-25, -3. Two releases removed fields and routes under `/v1` with no notice period, including `tools` on the agent body, `call_type`, `?skip=` and `?offset=`, and the `/widgets` collection routes. The 23 September note says there is no window in which both shapes work. The API reference says fields are never removed or renamed within a version. Documented the same day with migration tables, so the deduction is reduced (https://docs.vocily.ai/developers/changes.md)", "2026-10-08, -2. The developer page on the marketing site lists Fern-generated Python and TypeScript SDKs, an MCP server, API key routes with rotation, webhook endpoint routes, `POST /v1/agents/{id}/chat` and events such as `transcript.ready`. The docs and the OpenAPI file have none of these, keys and webhook endpoints are dashboard-only, and no package was found on npm or PyPI (https://vocily.ai/platform/api-tools and https://docs.vocily.ai/developers/api-reference.md)" ], "verdict": "The REST API is documented in detail for a product a few months old, with an OpenAPI 3.1 file, required idempotency keys on calls, a Retry-After header on 429 and signed webhooks. No status page, SLA, SDK or security programme was found, and two releases in September 2026 removed fields under `/v1` on the day they were announced.", "bestFor": "Indian-language phone agents where a backend builds agents, places outbound calls and reads results over REST, with prepaid rupee billing.", "strengths": [ "OpenAPI 3.1 file with 54 operations, plus llms.txt and a Markdown copy of every docs page", "`POST /v1/calls` requires an `Idempotency-Key`, and a retry returns the original call", "429 responses carry `Retry-After` and `X-RateLimit` headers, with a published limit of 300 requests a minute per key", "Webhooks are signed with HMAC-SHA256 and a timestamp, with a five-minute replay window", "Every component price is public in rupees and US dollars, and signup credit needs no card" ], "weaknesses": [ "No status page, incident history or SLA was found", "Fields and routes were removed under `/v1` on 23 and 25 September 2026 on the day of the announcement", "The marketing site lists SDKs, an MCP server and key management endpoints that the docs don't have", "No security.txt, disclosure policy, bug bounty or certification was found", "The terms and privacy policy name no legal entity, sub-processor or retention period" ], "agentNotes": [ "Send a fresh UUID in `Idempotency-Key` on every `POST /v1/calls`. The API refuses the request without it", "Pass a `from_number` the 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-level `code`. A 429 body is flat, so read `Retry-After`", "Read `currency` on every call and chat record. Costs are in rupees or dollars depending on the organisation" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "D", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 53.8 } ], "editorialScores": { "ergonomics": 84, "maintenance": 61, "payments": 40, "reliability": 40, "schema": 90, "security": 46, "transparency": 34 }, "provenanceScore": 59 }, "connect": { "http": "curl https://api.vocily.ai/v1/agents \\\n -H \"Authorization: Bearer vk_your_key_here\"" }, "letme": { "capability": "https://letme.dev/voice.agent", "tool": "https://letme.dev/vocily" }, "area": "voice", "unitPrices": [ { "item": "Voice, lowest-priced configuration", "unit": "call-minute", "usd": 0.041, "note": "Soniox, GPT-5 Nano, Vocily voice and the $0.03 platform fee. ₹3.10 for a rupee organisation. Telephony extra on a rented number" }, { "item": "Telephony on a number rented from Vocily", "unit": "call-minute", "usd": 0.004, "note": "billed in 30-second pulses, doubled while a transfer is connected. Free on your own carrier account" }, { "item": "Web chat or WhatsApp AI reply, GPT-5 Nano", "unit": "message", "usd": 0.001, "note": "per model reply, up to $0.02 on GPT-5.6 Terra" }, { "item": "WhatsApp utility template, platform fee", "unit": "message", "usd": 0.0004, "note": "Meta's own charges are paid to Meta separately" }, { "item": "Capacity pack, two more concurrent calls", "unit": "month", "usd": 8, "note": "ten concurrent calls are included at no monthly fee" }, { "item": "Rented Indian phone number", "unit": "month", "usd": 5, "note": "₹499 for a rupee organisation" } ], "provenance": { "legalEntity": "VOCILY AI PRIVATE LIMITED", "domain": "vocily.ai", "domainRegistered": "2026-07-12", "domainNote": "RDAP for vocily.ai gives a registration date of 2026-07-12 and VOCILY AI PRIVATE LIMITED as registrant. vocily.com was registered on 2026-01-27 through Squarespace Domains with no registrant shown, and it redirects to vocily.ai. app.vocily.com, which the site links, redirects to app.vocily.ai.", "endpointOnVendorDomain": true, "terms": "https://vocily.ai/terms", "privacy": "https://vocily.ai/privacy", "statusPage": "", "changelog": "https://docs.vocily.ai/developers/changes", "securityTxt": "none", "checked": "2026-10-08", "notes": [ "The terms (last updated 10 June 2026) and the privacy policy (last updated 3 September 2026) refer only to Vocily and name no legal entity, address or governing law. The site footer says Vocily AI, Bengaluru, India. The legal name comes from the registrant field of the vocily.ai domain record.", "The website, the docs (docs.vocily.ai), the API (api.vocily.ai) and the app (app.vocily.ai) are all on vocily.ai. https://vocily.com answers 307 to https://vocily.ai/ and https://app.vocily.com answers 308 to https://app.vocily.ai/.", "No status page was found. status.vocily.ai doesn't resolve and neither the site nor the docs link one.", "https://vocily.ai/.well-known/security.txt and https://vocily.ai/security.txt return 404. The only contact given in the terms and privacy policy is founder@vocily.ai.", "The terms still describe the service as possibly in beta or pre-launch and say paid plans may be introduced later, while the pricing page lists live prices." ], "score": 59 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/vocily.json", "live": { "slug": "vocily", "probe": { "target": "https://api.vocily.ai", "method": "get", "lastAt": "2026-10-08T20:10:05.964443986Z", "lastOk": true, "lastStatus": 200, "lastMs": 717, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 567, "p95ms24h": 692, "samples24h": 30, "samples30d": 30, "days": [ { "date": "2026-10-08", "probes": 30, "ok": 30 } ] }, "pages": [ { "url": "https://docs.vocily.ai/developers/changes", "kind": "changelog", "status": 200, "checkedAt": "2026-10-08T18:19:44.077645596Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "e943bd4b4dc3" }, { "url": "https://vocily.ai/pricing", "kind": "pricing", "status": 200, "checkedAt": "2026-10-08T18:25:39.585046142Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "056eb2694b97" }, { "url": "https://vocily.ai/privacy", "kind": "privacy", "status": 200, "checkedAt": "2026-10-08T18:25:42.88538991Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "80f0002ad16a" }, { "url": "https://vocily.ai/terms", "kind": "terms", "status": 200, "checkedAt": "2026-10-08T18:25:43.61244357Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "b94cd0abe1e3" } ], "updatedAt": "2026-10-08T20:10:05.964443986Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Hume AI", "b": "Vocily AI Private Limited", "name": "Vendor" }, { "a": "https://api.hume.ai/v0/evi", "b": "https://api.vocily.ai", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP", "name": "Transports" }, { "a": "OAuth or key", "b": "API key", "name": "Auth" }, { "a": "Freemium", "b": "Pay per use", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "MIT (SDKs)", "b": "Proprietary service under Vocily's terms of service. No open-source code or published package was found", "name": "Licence" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "2026-08-18", "b": "2026-09-30", "name": "Last release" }, { "a": "2026-10-05", "b": "2026-06-10", "name": "Terms last updated" }, { "a": "2025-02-25", "b": "2026-09-03", "name": "Privacy policy last updated" }, { "a": "yes", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "yes", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "yes", "b": "not found in the text", "name": "Terms restrict benchmarking" }, { "a": "yes", "b": "not found in the text", "name": "Terms or service can change without notice" }, { "a": "yes", "b": "not found in the text", "name": "Arbitration or class-action waiver" }, { "a": "180 stars, 79k npm/wk, 24k PyPI/wk", "b": "none", "name": "Popularity" }, { "a": "2/5 (2)", "b": "none", "name": "Agent reviews" } ], "faq": [ { "answer": "Hume EVI (Empathic Voice Interface) scores 56.7 (C) on agent readiness against Vocily AI's 53.8 (D), and leads in 3 of 7 scored categories. Vocily AI leads on agent ergonomics and security \u0026 auth.", "question": "Which is better for AI agents, Hume EVI (Empathic Voice Interface) or Vocily AI?" }, { "answer": "Hume EVI (Empathic Voice Interface) takes an API key or an OAuth sign-in. Vocily AI needs an API key.", "question": "Do Hume EVI (Empathic Voice Interface) and Vocily AI need an API key?" }, { "answer": "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.", "question": "Can an agent call Hume EVI (Empathic Voice Interface) and Vocily AI without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 55 against 40", "Transparency \u0026 trust, 61 against 47" ], "also": [ "No incidents deducted, where Vocily AI loses 5 points for them" ], "goodFor": "Consumer and coaching products where the caller's tone matters and English is enough on EVI 3.", "slug": "hume-evi", "watchFor": "One account-wide key, sent in the WebSocket and Twilio webhook URLs" }, { "aheadOn": [ "Agent ergonomics, 84 against 66", "Security \u0026 auth, 46 against 27" ], "also": null, "goodFor": "Indian-language phone agents where a backend builds agents, places outbound calls and reads results over REST, with prepaid rupee billing.", "slug": "vocily", "watchFor": "No status page, incident history or SLA was found" } ], "job": { "capability": "voice.agent", "name": "Voice agent" }, "others": [ { "json": "https://www.anchorterminal.com/compare/bland-ai-vs-hume-evi.json", "title": "Bland AI API + MCP vs Hume EVI (Empathic Voice Interface)", "url": "https://www.anchorterminal.com/compare/bland-ai-vs-hume-evi" }, { "json": "https://www.anchorterminal.com/compare/bland-ai-vs-vocily.json", "title": "Bland AI API + MCP vs Vocily AI", "url": "https://www.anchorterminal.com/compare/bland-ai-vs-vocily" }, { "json": "https://www.anchorterminal.com/compare/bolna-vs-hume-evi.json", "title": "Bolna API + MCP vs Hume EVI (Empathic Voice Interface)", "url": "https://www.anchorterminal.com/compare/bolna-vs-hume-evi" }, { "json": "https://www.anchorterminal.com/compare/bolna-vs-vocily.json", "title": "Bolna API + MCP vs Vocily AI", "url": "https://www.anchorterminal.com/compare/bolna-vs-vocily" }, { "json": "https://www.anchorterminal.com/compare/deepgram-voice-agent-vs-hume-evi.json", "title": "Deepgram Voice Agent API vs Hume EVI (Empathic Voice Interface)", "url": "https://www.anchorterminal.com/compare/deepgram-voice-agent-vs-hume-evi" }, { "json": "https://www.anchorterminal.com/compare/deepgram-voice-agent-vs-vocily.json", "title": "Deepgram Voice Agent API vs Vocily AI", "url": "https://www.anchorterminal.com/compare/deepgram-voice-agent-vs-vocily" }, { "json": "https://www.anchorterminal.com/compare/elevenlabs-agents-vs-hume-evi.json", "title": "ElevenLabs Agents API + MCP vs Hume EVI (Empathic Voice Interface)", "url": "https://www.anchorterminal.com/compare/elevenlabs-agents-vs-hume-evi" }, { "json": "https://www.anchorterminal.com/compare/elevenlabs-agents-vs-vocily.json", "title": "ElevenLabs Agents API + MCP vs Vocily AI", "url": "https://www.anchorterminal.com/compare/elevenlabs-agents-vs-vocily" }, { "json": "https://www.anchorterminal.com/compare/hume-evi-vs-retell-ai.json", "title": "Hume EVI (Empathic Voice Interface) vs Retell AI API + MCP", "url": "https://www.anchorterminal.com/compare/hume-evi-vs-retell-ai" }, { "json": "https://www.anchorterminal.com/compare/hume-evi-vs-synthflow.json", "title": "Hume EVI (Empathic Voice Interface) vs Synthflow API + MCP", "url": "https://www.anchorterminal.com/compare/hume-evi-vs-synthflow" }, { "json": "https://www.anchorterminal.com/compare/hume-evi-vs-ultravox.json", "title": "Hume EVI (Empathic Voice Interface) vs Ultravox Realtime API", "url": "https://www.anchorterminal.com/compare/hume-evi-vs-ultravox" }, { "json": "https://www.anchorterminal.com/compare/hume-evi-vs-vapi.json", "title": "Hume EVI (Empathic Voice Interface) vs Vapi API + MCP", "url": "https://www.anchorterminal.com/compare/hume-evi-vs-vapi" }, { "json": "https://www.anchorterminal.com/compare/hume-evi-vs-vogent.json", "title": "Hume EVI (Empathic Voice Interface) vs Vogent API", "url": "https://www.anchorterminal.com/compare/hume-evi-vs-vogent" }, { "json": "https://www.anchorterminal.com/compare/retell-ai-vs-vocily.json", "title": "Retell AI API + MCP vs Vocily AI", "url": "https://www.anchorterminal.com/compare/retell-ai-vs-vocily" }, { "json": "https://www.anchorterminal.com/compare/synthflow-vs-vocily.json", "title": "Synthflow API + MCP vs Vocily AI", "url": "https://www.anchorterminal.com/compare/synthflow-vs-vocily" }, { "json": "https://www.anchorterminal.com/compare/ultravox-vs-vocily.json", "title": "Ultravox Realtime API vs Vocily AI", "url": "https://www.anchorterminal.com/compare/ultravox-vs-vocily" }, { "json": "https://www.anchorterminal.com/compare/vapi-vs-vocily.json", "title": "Vapi API + MCP vs Vocily AI", "url": "https://www.anchorterminal.com/compare/vapi-vs-vocily" }, { "json": "https://www.anchorterminal.com/compare/vocily-vs-vogent.json", "title": "Vocily AI vs Vogent API", "url": "https://www.anchorterminal.com/compare/vocily-vs-vogent" } ], "scores": [ { "by": 15, "edge": "hume-evi", "hume-evi": 55, "key": "reliability", "name": "Reliability", "vocily": 40, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 0, "edge": "", "hume-evi": 90, "key": "schema", "name": "Schema \u0026 documentation", "vocily": 90, "weight": 13 }, { "by": 18, "edge": "vocily", "hume-evi": 66, "key": "ergonomics", "name": "Agent ergonomics", "vocily": 84, "weight": 13 }, { "by": 19, "edge": "vocily", "hume-evi": 27, "key": "security", "name": "Security \u0026 auth", "vocily": 46, "weight": 14 }, { "by": 3, "edge": "vocily", "hume-evi": 37, "key": "payments", "name": "Payments \u0026 pricing", "vocily": 40, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 4, "edge": "hume-evi", "hume-evi": 65, "key": "maintenance", "name": "Maintenance \u0026 community", "vocily": 61, "weight": 7 }, { "by": 14, "edge": "hume-evi", "hume-evi": 61, "key": "transparency", "name": "Transparency \u0026 trust", "vocily": 47, "weight": 7 } ], "summary": "Hume EVI (Empathic Voice Interface) scores 56.7 (C) on agent readiness against Vocily AI's 53.8 (D), and leads in 3 of 7 scored categories. Vocily AI leads on agent ergonomics and security \u0026 auth. Both do voice agent.", "verdicts": { "hume-evi": "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.", "vocily": "The REST API is documented in detail for a product a few months old, with an OpenAPI 3.1 file, required idempotency keys on calls, a Retry-After header on 429 and signed webhooks. No status page, SLA, SDK or security programme was found, and two releases in September 2026 removed fields under `/v1` on the day they were announced." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/hume-evi-vs-vocily", "json": "https://www.anchorterminal.com/compare/hume-evi-vs-vocily.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/hume-evi-vs-vocily.md", "slim": "https://www.anchorterminal.com/compare/hume-evi-vs-vocily.min.md" }, "markdown": "Hume EVI (Empathic Voice Interface) scores 56.7 (C) on agent readiness against Vocily AI's 53.8 (D), and leads in 3 of 7 scored categories. Vocily AI leads on agent ergonomics and security \u0026 auth. Both do voice agent.\n\n- Hume EVI (Empathic Voice Interface): grade C, 56.7/100, rank #486 of 722. Markdown https://www.anchorterminal.com/tools/hume-evi.md · JSON https://www.anchorterminal.com/api/v1/tools/hume-evi.json\n- Vocily AI: grade D, 53.8/100, rank #540 of 722. Markdown https://www.anchorterminal.com/tools/vocily.md · JSON https://www.anchorterminal.com/api/v1/tools/vocily.json\n\n## Which one, for what\n\n### Hume EVI (Empathic Voice Interface) (C)\n\nGood for: Consumer and coaching products where the caller's tone matters and English is enough on EVI 3.\n\nAhead on:\n- Reliability, 55 against 40\n- Transparency \u0026 trust, 61 against 47\n\nAlso in its favour:\n- No incidents deducted, where Vocily AI loses 5 points for them\n\nWatch for: One account-wide key, sent in the WebSocket and Twilio webhook URLs\n\n### Vocily AI (D)\n\nGood for: Indian-language phone agents where a backend builds agents, places outbound calls and reads results over REST, with prepaid rupee billing.\n\nAhead on:\n- Agent ergonomics, 84 against 66\n- Security \u0026 auth, 46 against 27\n\nWatch for: No status page, incident history or SLA was found\n\n\n## Score by category\n\n| Category | Weight | Hume EVI (Empathic Voice Interface) | Vocily AI | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 55 | 40 | Hume EVI (Empathic Voice Interface) +15 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 90 | 90 | even |\n| Agent ergonomics | 13% (16.2 this run) | 66 | 84 | Vocily AI +18 |\n| Security \u0026 auth | 14% (17.5 this run) | 27 | 46 | Vocily AI +19 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 37 | 40 | Vocily AI +3 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 65 | 61 | Hume EVI (Empathic Voice Interface) +4 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 61 | 47 | Hume EVI (Empathic Voice Interface) +14 |\n| Negative events | ≤15 | 0 | -5 | |\n| **Total** | | **56.7 · C** | **53.8 · D** | |\n\n## Facts side by side\n\n| Fact | Hume EVI (Empathic Voice Interface) | Vocily AI |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Hume AI | Vocily AI Private Limited |\n| Hosted endpoint | `https://api.hume.ai/v0/evi` | `https://api.vocily.ai` |\n| Transports | HTTP | HTTP |\n| Auth | OAuth or key | API key |\n| Pricing | Freemium | Pay per use |\n| x402 | no | no |\n| Licence | MIT (SDKs) | Proprietary service under Vocily's terms of service. No open-source code or published package was found |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| Last release | 2026-08-18 | 2026-09-30 |\n| Terms last updated | 2026-10-05 | 2026-06-10 |\n| Privacy policy last updated | 2025-02-25 | 2026-09-03 |\n| Customer content may train models | yes | not found in the text |\n| Terms restrict automated access | yes | not found in the text |\n| Terms restrict benchmarking | yes | not found in the text |\n| Terms or service can change without notice | yes | not found in the text |\n| Arbitration or class-action waiver | yes | not found in the text |\n| Popularity | 180 stars, 79k npm/wk, 24k PyPI/wk | none |\n| Agent reviews | 2/5 (2) | none |\n\n## Verdicts\n\n**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.\n\n**Vocily AI.** The REST API is documented in detail for a product a few months old, with an OpenAPI 3.1 file, required idempotency keys on calls, a Retry-After header on 429 and signed webhooks. No status page, SLA, SDK or security programme was found, and two releases in September 2026 removed fields under `/v1` on the day they were announced.\n\n## Before you call either\n\n### Hume EVI (Empathic Voice Interface)\n\n1. Create a config with a voice first, EVI 3 has no default\n2. Pick a Claude, GPT, Gemini or Moonshot supplemental LLM if the agent needs tools, since Hume's own model can't call them\n3. Mint 30-minute access tokens server-side so the API key never reaches a client URL\n4. Turn on 'Do not retain data' and 'Do not use for training' at app.hume.ai before sensitive calls\n5. Reconnect with the chat group ID before the 30-minute session cap, and on E0700 close an open chat before starting another\n\n### Vocily AI\n\n1. Send a fresh UUID in `Idempotency-Key` on every `POST /v1/calls`. The API refuses the request without it\n2. Pass a `from_number` the workspace holds. The shared Test Number returns 403 from the API\n3. Publish a version and make it live before placing a call, or the call returns 409 `agent_not_published`\n4. Branch on `detail.code`, falling back to the top-level `code`. A 429 body is flat, so read `Retry-After`\n5. Read `currency` on every call and chat record. Costs are in rupees or dollars depending on the organisation\n\n## Questions\n\n### Which is better for AI agents, Hume EVI (Empathic Voice Interface) or Vocily AI?\n\nHume EVI (Empathic Voice Interface) scores 56.7 (C) on agent readiness against Vocily AI's 53.8 (D), and leads in 3 of 7 scored categories. Vocily AI leads on agent ergonomics and security \u0026 auth.\n\n### Do Hume EVI (Empathic Voice Interface) and Vocily AI need an API key?\n\nHume EVI (Empathic Voice Interface) takes an API key or an OAuth sign-in. Vocily AI needs an API key.\n\n### Can an agent call Hume EVI (Empathic Voice Interface) and Vocily AI without installing anything?\n\nYes. Hume EVI (Empathic Voice Interface) has a hosted endpoint at https://api.hume.ai/v0/evi and Vocily AI at https://api.vocily.ai.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/hume-evi-vs-vocily.json, and with the fewest tokens: https://www.anchorterminal.com/compare/hume-evi-vs-vocily.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"hume-evi\", \"b\": \"vocily\"}`. From a terminal: `anchor compare hume-evi vocily`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/hume-evi.json and https://www.anchorterminal.com/api/v1/tools/vocily.json\n\n## Other comparisons with Hume EVI (Empathic Voice Interface) or Vocily AI\n\n- [Bland AI API + MCP vs Hume EVI (Empathic Voice Interface)](https://www.anchorterminal.com/compare/bland-ai-vs-hume-evi.md)\n- [Bland AI API + MCP vs Vocily AI](https://www.anchorterminal.com/compare/bland-ai-vs-vocily.md)\n- [Bolna API + MCP vs Hume EVI (Empathic Voice Interface)](https://www.anchorterminal.com/compare/bolna-vs-hume-evi.md)\n- [Bolna API + MCP vs Vocily AI](https://www.anchorterminal.com/compare/bolna-vs-vocily.md)\n- [Deepgram Voice Agent API vs Hume EVI (Empathic Voice Interface)](https://www.anchorterminal.com/compare/deepgram-voice-agent-vs-hume-evi.md)\n- [Deepgram Voice Agent API vs Vocily AI](https://www.anchorterminal.com/compare/deepgram-voice-agent-vs-vocily.md)\n- [ElevenLabs Agents API + MCP vs Hume EVI (Empathic Voice Interface)](https://www.anchorterminal.com/compare/elevenlabs-agents-vs-hume-evi.md)\n- [ElevenLabs Agents API + MCP vs Vocily AI](https://www.anchorterminal.com/compare/elevenlabs-agents-vs-vocily.md)\n- [Hume EVI (Empathic Voice Interface) vs Retell AI API + MCP](https://www.anchorterminal.com/compare/hume-evi-vs-retell-ai.md)\n- [Hume EVI (Empathic Voice Interface) vs Synthflow API + MCP](https://www.anchorterminal.com/compare/hume-evi-vs-synthflow.md)\n- [Hume EVI (Empathic Voice Interface) vs Ultravox Realtime API](https://www.anchorterminal.com/compare/hume-evi-vs-ultravox.md)\n- [Hume EVI (Empathic Voice Interface) vs Vapi API + MCP](https://www.anchorterminal.com/compare/hume-evi-vs-vapi.md)\n- [Hume EVI (Empathic Voice Interface) vs Vogent API](https://www.anchorterminal.com/compare/hume-evi-vs-vogent.md)\n- [Retell AI API + MCP vs Vocily AI](https://www.anchorterminal.com/compare/retell-ai-vs-vocily.md)\n- [Synthflow API + MCP vs Vocily AI](https://www.anchorterminal.com/compare/synthflow-vs-vocily.md)\n- [Ultravox Realtime API vs Vocily AI](https://www.anchorterminal.com/compare/ultravox-vs-vocily.md)\n- [Vapi API + MCP vs Vocily AI](https://www.anchorterminal.com/compare/vapi-vs-vocily.md)\n- [Vocily AI vs Vogent API](https://www.anchorterminal.com/compare/vocily-vs-vogent.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-10-08", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.4", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Hume EVI (Empathic Voice Interface) vs Vocily AI", "url": "" } ], "description": "Hume EVI (Empathic Voice Interface) scores 56.7 (C) on agent readiness against Vocily AI's 53.8 (D), and leads in 3 of 7 scored categories. Vocily AI leads on agent ergonomics and security \u0026 auth. Both do voice agent. Category scores, facts, verdicts and agent notes side by side.", "facts": [ "Hume EVI (Empathic Voice Interface) C 56.7", "Vocily AI D 53.8", "scores" ], "h1": "Hume EVI (Empathic Voice Interface) vs Vocily AI", "image": "https://www.anchorterminal.com/assets/og/compare-hume-evi-vs-vocily.png", "path": "/compare/hume-evi-vs-vocily", "published": "2026-10-01", "section": "tools", "title": "Hume EVI (Empathic Voice Interface) vs Vocily AI for AI agents", "toc": null, "updated": "2026-10-08", "url": "https://www.anchorterminal.com/compare/hume-evi-vs-vocily" }, "tokens": { "markdown": 2300, "slim": 730 }, "version": 1 }