{ "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", "dns": "hume-evi.grade.anchorterminal.com", "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": 54.1, "grade": "C", "agentReady": false, "rank": 914, "ranked": true, "rankOf": 1486, "categoryRank": 16, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 66, "maintenance": 35, "payments": 37, "reliability": 55, "schema": 90, "security": 27, "transparency": 61 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-04" }, "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. Hume ends API access on 13 November 2026.", "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": [ "Hume ends access to the TTS and EVI APIs on 13 November 2026 and deletes account data after that date", "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 (outside today's 90-day window)", "Public changelog ends at 15 May 2026, and no SDK release since 17 June 2026 changes EVI code", "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.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 54.1 } ], "editorialScores": { "ergonomics": 66, "maintenance": 35, "payments": 37, "reliability": 55, "schema": 90, "security": 27, "transparency": 48 }, "provenanceScore": 74, "checked": { "categories": { "ergonomics": "2026-11-04", "maintenance": "2026-11-04", "payments": "2026-11-04", "reliability": "2026-11-04", "schema": "2026-11-04", "security": "2026-11-04", "transparency": "2026-11-04" }, "last": "2026-11-04", "lastMoved": "2026-11-04", "oldest": "2026-11-04", "stale": false, "staleAfterDays": 90 } }, "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": 74 }, "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-11-07T18:20:31.171944254Z", "lastOk": true, "lastStatus": 404, "lastMs": 592, "authRequired": false, "uptime24h": 100, "uptime30d": 99.97, "p50ms24h": 186, "p95ms24h": 325, "samples24h": 239, "samples30d": 7910, "days": [ { "date": "2026-10-07", "probes": 272, "ok": 272 }, { "date": "2026-10-08", "probes": 268, "ok": 268 }, { "date": "2026-10-09", "probes": 250, "ok": 250 }, { "date": "2026-10-10", "probes": 247, "ok": 247 }, { "date": "2026-10-11", "probes": 247, "ok": 247 }, { "date": "2026-10-12", "probes": 247, "ok": 247 }, { "date": "2026-10-13", "probes": 248, "ok": 248 }, { "date": "2026-10-14", "probes": 249, "ok": 249 }, { "date": "2026-10-15", "probes": 253, "ok": 253 }, { "date": "2026-10-16", "probes": 252, "ok": 252 }, { "date": "2026-10-17", "probes": 253, "ok": 252 }, { "date": "2026-10-18", "probes": 256, "ok": 256 }, { "date": "2026-10-19", "probes": 255, "ok": 255 }, { "date": "2026-10-20", "probes": 252, "ok": 252 }, { "date": "2026-10-21", "probes": 253, "ok": 253 }, { "date": "2026-10-22", "probes": 253, "ok": 253 }, { "date": "2026-10-23", "probes": 248, "ok": 248 }, { "date": "2026-10-24", "probes": 251, "ok": 251 }, { "date": "2026-10-25", "probes": 250, "ok": 250 }, { "date": "2026-10-26", "probes": 252, "ok": 252 }, { "date": "2026-10-27", "probes": 249, "ok": 249 }, { "date": "2026-10-28", "probes": 251, "ok": 250 }, { "date": "2026-10-29", "probes": 248, "ok": 248 }, { "date": "2026-10-30", "probes": 249, "ok": 249 }, { "date": "2026-10-31", "probes": 251, "ok": 251 }, { "date": "2026-11-01", "probes": 249, "ok": 249 }, { "date": "2026-11-02", "probes": 250, "ok": 250 }, { "date": "2026-11-03", "probes": 248, "ok": 248 }, { "date": "2026-11-04", "probes": 246, "ok": 246 }, { "date": "2026-11-05", "probes": 185, "ok": 185 }, { "date": "2026-11-06", "probes": 241, "ok": 241 }, { "date": "2026-11-07", "probes": 187, "ok": 187 } ] }, "vendorStatus": { "page": "https://status.hume.ai", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-11-07T18:21:16.218886709Z" }, "versions": [ { "registry": "github", "name": "HumeAI/hume-python-sdk", "version": "v0.14.0", "released": "2026-06-17", "seenAt": "2026-11-06T23:33:33.281405535Z" }, { "registry": "npm", "name": "@humeai/voice-react", "version": "0.3.0-beta.6", "seenAt": "2026-11-06T23:33:31.348799046Z" }, { "registry": "npm", "name": "hume", "version": "0.16.1", "seenAt": "2026-11-06T23:33:30.882415583Z" }, { "registry": "pypi", "name": "hume", "version": "0.14.1", "released": "2026-08-17", "seenAt": "2026-11-06T23:33:31.137751759Z" } ], "githubStars": 182, "npmWeekly": 112038, "pypiWeekly": 35235, "securityTxt": { "url": "https://hume.ai/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-07T16:00:06.21640031Z" }, "llmsTxt": { "url": "https://dev.hume.ai/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:32:43.099335004Z" }, "domain": { "domain": "hume.ai", "registered": "2020-04-06", "source": "https://rdap.identitydigital.services/rdap/domain/hume.ai", "checkedAt": "2026-11-01T14:15:47.929579773Z" }, "pages": [ { "url": "https://dev.hume.ai/changelog", "kind": "changelog", "status": 200, "checkedAt": "2026-11-07T14:02:42.258079855Z", "changedAt": "2026-11-07T14:02:42.258079855Z", "fingerprint": "5270e0220952" }, { "url": "https://dev.hume.ai/docs/speech-to-speech-evi/configuration/evi-version", "kind": "deprecations", "status": 200, "checkedAt": "2026-11-07T14:02:44.785277903Z", "changedAt": "2026-11-03T07:44:22.849107211Z", "fingerprint": "f455cbe5ada8" }, { "url": "https://dev.hume.ai/voice/changelog", "kind": "deprecations", "status": 200, "checkedAt": "2026-11-07T14:02:47.263426439Z", "changedAt": "2026-11-03T07:44:24.928972119Z", "fingerprint": "f455cbe5ada8" }, { "url": "https://www.hume.ai/pricing", "kind": "pricing", "status": 200, "checkedAt": "2026-11-07T14:29:57.573825036Z", "changedAt": "2026-11-05T13:13:37.427346866Z", "fingerprint": "50fd1569271e" }, { "url": "https://www.hume.ai/privacy-policy", "kind": "privacy", "status": 200, "checkedAt": "2026-11-07T14:29:59.946480788Z", "changedAt": "2026-11-03T08:07:04.335803675Z", "fingerprint": "21dfc9509149" }, { "url": "https://www.hume.ai/terms-of-use", "kind": "terms", "status": 200, "checkedAt": "2026-11-07T14:30:01.908784241Z", "changedAt": "2026-11-03T08:07:06.305319602Z", "fingerprint": "b63621d6a65b" } ], "github": { "repo": "humeai/hume-python-sdk", "checkedAt": "2026-11-02T08:55:18.175954656Z", "stars": 181, "archived": false, "issuesEnabled": true, "pushedAt": "2026-08-17T21:04:05Z", "openIssues": 2, "openPRs": 3, "issuesOpened90d": 2, "issuesClosed90d": 0, "prsMerged90d": 0, "ci": { "branch": "main", "runs": 39, "success": 34, "failure": 4, "other": 1, "latest": "success", "latestAt": "2026-06-17T16:43:53Z" }, "replies": { "sampled": 25, "unanswered": 2, "medianDays": 62.1 } }, "updatedAt": "2026-11-07T18:21:16.218886709Z" } }, "answer": "Inworld Realtime API scores 60.1 (C) on agent readiness against Hume EVI (Empathic Voice Interface)'s 54.1 (C), and leads in 6 of 7 scored categories. Hume EVI (Empathic Voice Interface) leads on schema \u0026 documentation.", "b": { "slug": "inworld-realtime", "name": "Inworld Realtime API", "vendor": "Inworld AI", "vendorUrl": "https://inworld.ai", "kind": "http-api", "category": "voice-agents", "summary": "Inworld's Realtime API runs spoken conversations over WebSocket or WebRTC, chaining Inworld STT, an LLM chosen by the developer and Inworld TTS, with turn detection, interruptions and tool calling. It follows OpenAI's Realtime protocol.", "url": "https://www.anchorterminal.com/tools/inworld-realtime", "markdownUrl": "https://www.anchorterminal.com/tools/inworld-realtime.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/inworld-realtime.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/inworld-realtime.json", "dns": "inworld-realtime.grade.anchorterminal.com", "transports": [ "websocket", "http" ], "packages": [ { "registry": "npm", "name": "@inworld/cli" } ], "auth": "api-key", "authNotes": "Servers send `Authorization: Basic` with the Base64 `key_id:secret` credential. Browsers send `Authorization: Bearer` with a session token minted server side. The `key` query parameter in the WebSocket URL is a session ID, not a secret.", "pricing": "usage", "pricingNotes": "No per-minute or per-session price. A session is billed as its STT ($0.10 to $0.15 an hour), its LLM tokens at the model's rate and its TTS characters (TTS-2 from $25 per million on the free plan). Segments already sent to TTS are billed after an interruption.", "priceSummary": "Pay per use", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the docs, llms.txt or pricing page (checked 2026-11-06). Plans and credits are bought in the Portal.", "endpoints": [] }, "toolCount": 0, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-06" }, "docsUrl": "https://docs.inworld.ai/realtime/overview", "llmsTxt": "https://docs.inworld.ai/llms.txt", "capabilities": [ "voice.agent", "voice.pipeline", "voice.tools", "voice.telephony" ], "tags": [ "hosted", "usage", "free-tier", "closed-source", "llms-txt", "streaming", "websocket", "webrtc", "openai-compatible", "enterprise" ], "lastRelease": "2026-10-16", "graded": true, "anchor": { "graded": true, "score": 60.1, "grade": "C", "agentReady": false, "rank": 668, "ranked": true, "rankOf": 1486, "categoryRank": 12, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 68, "maintenance": 71, "payments": 40, "reliability": 62, "schema": 60, "security": 58, "transparency": 63 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-06" }, "negative": 0, "verdict": "Inworld's Realtime API speaks OpenAI's Realtime protocol over WebSocket or WebRTC, with a choice of LLM, client-side tools and dated release notes. Cost is the sum of STT, LLM and TTS usage with no per-minute price, there is no machine-readable event schema, and status history couldn't be read.", "bestFor": "Teams moving off OpenAI's Realtime API who want a choice of LLM and Inworld voices.", "strengths": [ "Follows OpenAI's Realtime events, with a migration guide that changes only the URL, key and a few defaults", "Dated release notes name affected clients and required actions for each compatibility change", "A choice of LLM through Inworld's router, with prompt caching on Anthropic models", "Concurrent sessions from 10 on the free plan to 1,000 on Growth", "Zero data retention covers session content from the Developer plan up" ], "weaknesses": [ "No per-minute price. A session's cost depends on STT, LLM tokens and TTS characters, and interrupted segments are still billed", "No AsyncAPI or other machine-readable schema for the socket events", "Status history couldn't be read, and an SLA exists only for Enterprise", "The 21 July 2026 release changed response and item shapes for existing clients", "Zero data retention doesn't cover requests routed to third-party LLM providers" ], "agentNotes": [ "Set the auto follow-up off if your client sends its own `response.create` after a tool result, or replies double", "Read `response.done` usage as an estimate and mute input audio when nobody speaks, since STT bills every second sent", "Use `response.speak` for fixed greetings, which skips the LLM", "Treat `unsupported_field` errors as warnings and keep the session open", "Mint browser session tokens on your server and never ship the Basic credential to a client" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 60.1 } ], "editorialScores": { "ergonomics": 68, "maintenance": 71, "payments": 40, "reliability": 62, "schema": 60, "security": 58, "transparency": 51 }, "provenanceScore": 75, "checked": { "categories": { "ergonomics": "2026-11-06", "maintenance": "2026-11-06", "payments": "2026-11-06", "reliability": "2026-11-06", "schema": "2026-11-06", "security": "2026-11-06", "transparency": "2026-11-06" }, "last": "2026-11-06", "oldest": "2026-11-06", "stale": false, "staleAfterDays": 90 } }, "connect": { "install": "npm install -g @inworld/cli" }, "letme": { "capability": "https://letme.dev/voice.agent", "tool": "https://letme.dev/inworld-realtime" }, "sameCompany": [ "inworld-stt", "inworld-tts", "inworld-voice-cloning" ], "area": "voice", "unitPrices": [ { "item": "Speech recognition in a session", "unit": "audio-minute", "usd": 0.0025, "note": "STT-1 at $0.15 an hour On-Demand, $0.10 on paid plans" }, { "item": "Agent speech, TTS-2", "unit": "1m-chars", "usd": 25, "note": "free On-Demand plan; lower on paid plans" } ], "provenance": { "legalEntity": "Theai, Inc. dba Inworld AI", "domain": "inworld.ai", "domainRegistered": "", "endpointOnVendorDomain": true, "terms": "https://inworld.ai/terms", "privacy": "https://inworld.ai/privacy", "statusPage": "https://status.inworld.ai", "changelog": "https://docs.inworld.ai/release-notes/realtime", "securityTxt": "none", "checked": "2026-11-06", "notes": [ "The Terms of Service (effective 11 June 2025) are an agreement with Theai, Inc. dba Inworld AI under California law, with courts in Santa Clara. The Privacy Notice (last updated 18 January 2026) names Theai, Inc.", "inworld.ai/.well-known/security.txt returns 404. The security page links a vulnerability report form.", "status.inworld.ai runs the open-source issue-status app, which draws incidents from GitHub issues in inworld-ai/inworld-issue-status. Its history wasn't read, because GitHub's robots.txt couldn't be read from our environment.", "inworld.ai's robots.txt allows Claude agents on the paths read and sets `Content-Signal: ai-train=no, search=yes, ai-input=no`. docs.inworld.ai has no such signal.", "The domain's registration date wasn't established, because the RDAP lookup failed.", "firstReleased is left empty. The public Realtime release notes start on 21 July 2026 and no launch date was found." ], "score": 75 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/inworld-realtime.json", "live": { "slug": "inworld-realtime", "vendorStatus": { "page": "https://status.inworld.ai", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-11-07T04:47:57.03709454Z" }, "versions": [ { "registry": "npm", "name": "@inworld/cli", "version": "1.5.0", "seenAt": "2026-11-06T23:35:04.551623033Z" } ], "npmWeekly": 290, "securityTxt": { "url": "https://inworld.ai/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-07T16:01:11.794771951Z" }, "llmsTxt": { "url": "https://docs.inworld.ai/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:32:46.028273902Z" }, "pages": [ { "url": "https://docs.inworld.ai/release-notes/realtime", "kind": "changelog", "status": 200, "checkedAt": "2026-11-07T14:06:42.218731652Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "9ae0f1f05b69" }, { "url": "https://inworld.ai/privacy", "kind": "privacy", "status": 304, "checkedAt": "2026-11-07T14:11:39.031139211Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "99dc39a9de92" }, { "url": "https://inworld.ai/terms", "kind": "terms", "status": 304, "checkedAt": "2026-11-07T14:11:41.181276356Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "777d881cbf9b" } ], "updatedAt": "2026-11-07T16:01:11.794771951Z" } }, "edges": [ { "by": 36, "category": "maintenance", "leads": "inworld-realtime", "name": "Maintenance \u0026 community", "reasons": { "a": "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.", "b": "Release note of 16 October 2026 (`cache_transcript`), 21 days ago (30). Three dated Realtime entries in the 90 days from 8 August, on 14 September, 23 September and 16 October (20). Discord and support@inworld.ai, with no evidence of answers read (8 of 15). Works with OpenAI's Realtime clients and the CLI is current at 1.5.0, but there is no Inworld Realtime SDK (8 of 15). CLI on npm under MIT, CI not read (5 of 10). Total 71." }, "scores": { "a": 35, "b": 71 } }, { "by": 31, "category": "security", "leads": "inworld-realtime", "name": "Security \u0026 auth", "reasons": { "a": "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).", "b": "Workspace API keys sent as Basic credentials, deleted to revoke, with separate keys per environment advised. The CLI mints read-only keys unless `--write` is given, but write toggles cover only the Voice and Router APIs, so no key is limited to one product. Browsers use short-lived tokens minted server side. Session IDs, not secrets, go in the URL (25 of 30). Tools run in the client, so the developer approves side effects, with no approval step in the API (10 of 20). The agent listens to callers and passes their speech to an LLM, and no prompt-injection guidance was found (5 of 15). Usage per key and a Performance page with errors and throttling (8 of 15). SOC 2 Type II and HIPAA claimed and a vulnerability report form, with no security.txt or bug bounty, per the 4 November reading (10 of 20). Total 58. Zero data retention covers session content from the Developer plan up, but not requests routed to third-party LLM providers." }, "scores": { "a": 27, "b": 58 } }, { "by": 30, "category": "schema", "leads": "hume-evi", "name": "Schema \u0026 documentation", "reasons": { "a": "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).", "b": "No AsyncAPI or other machine-readable file for the socket, and the spec paths redirect (0). llms.txt, Markdown twins and a docs MCP server (10). The overview, OpenAI migration guide, `providerData` reference and the billing page's account of how a session is counted say what to use when (16 of 20). The reference lists every client and server event with field types and required marks, as text rather than a schema (12 of 15). JavaScript and Python example projects and an error event with `type`, `code` and `param`, without a list of codes (9 of 15). Dated release notes with affected clients and required actions, but no API version beyond `/v1` (13 of 15). Total 60." }, "scores": { "a": 90, "b": 60 } }, { "by": 7, "category": "reliability", "leads": "inworld-realtime", "name": "Reliability", "reasons": { "a": "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.", "b": "Hosted reading of the checklist. status.inworld.ai is a public status page (20), with history we couldn't read, as on inworld-tts (5). Concurrent sessions are published per plan, 10 on On-Demand up to 1,000 on Growth (15). The rate limits page gives exponential backoff with jitter and Retry-After on longer windows, and sessions emit `rate_limits.updated`, with nothing on reconnecting a dropped session (12 of 15). An SLA appears only in the Enterprise column, with no terms (0). No preview or beta label on the Realtime API (10). 20 + 5 + 15 + 12 + 0 + 10 = 62." }, "scores": { "a": 55, "b": 62 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Hume AI", "b": "Inworld AI", "name": "Vendor" }, { "a": "https://api.hume.ai/v0/evi", "b": "no (local only)", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "websocket, HTTP", "name": "Transports" }, { "a": "OAuth or key", "b": "API key", "name": "Auth" }, { "a": "Freemium", "b": "Pay per use", "name": "Pricing" }, { "a": "not published", "b": "$25 per 1M characters", "name": "Price for voice agents" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "MIT (SDKs)", "b": "none", "name": "Licence" }, { "a": "none", "b": "0", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "2026-08-18", "b": "2026-10-16", "name": "Last release" }, { "a": "2026-10-05", "b": "2025-06-11", "name": "Terms last updated" }, { "a": "2025-02-25", "b": "2026-01-18", "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": "Inworld Realtime API scores 60.1 (C) on agent readiness against Hume EVI (Empathic Voice Interface)'s 54.1 (C), and leads in 6 of 7 scored categories. Hume EVI (Empathic Voice Interface) leads on schema \u0026 documentation.", "question": "Which is better for AI agents, Hume EVI (Empathic Voice Interface) or Inworld Realtime API?" }, { "answer": "Hume EVI (Empathic Voice Interface) takes an API key or an OAuth sign-in. Inworld Realtime API needs an API key.", "question": "Do Hume EVI (Empathic Voice Interface) and Inworld Realtime API need an API key?" }, { "answer": "Hume EVI (Empathic Voice Interface) has a hosted endpoint at https://api.hume.ai/v0/evi. No hosted endpoint is listed for Inworld Realtime API.", "question": "Can an agent call Hume EVI (Empathic Voice Interface) and Inworld Realtime API without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Schema \u0026 documentation, 90 against 60" ], "also": [ "A hosted endpoint, with nothing to install" ], "goodFor": "Consumer and coaching products where the caller's tone matters and English is enough on EVI 3.", "slug": "hume-evi", "watchFor": "Hume ends access to the TTS and EVI APIs on 13 November 2026 and deletes account data after that date" }, { "aheadOn": [ "Reliability, 62 against 55", "Security \u0026 auth, 58 against 27", "Maintenance \u0026 community, 71 against 35" ], "also": null, "goodFor": "Teams moving off OpenAI's Realtime API who want a choice of LLM and Inworld voices.", "slug": "inworld-realtime", "watchFor": "No per-minute price. A session's cost depends on STT, LLM tokens and TTS characters, and interrupted segments are still billed" } ], "history": { "hume-evi": [ { "causes": [ "time" ], "date": "2026-11-04", "delta": -2.6, "from": 56.7, "fromGrade": "C", "to": 54.1, "toGrade": "C" }, { "causes": [ "method" ], "date": "2026-10-08", "delta": -0.6, "from": 57.3, "fromGrade": "C", "to": 56.7, "toGrade": "C" } ], "inworld-realtime": null }, "job": { "capability": "voice.agent", "name": "Voice agents" }, "others": [ { "json": "https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-hume-evi.json", "title": "Amazon Nova 2 Sonic vs Hume EVI (Empathic Voice Interface)", "url": "https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-hume-evi" }, { "json": "https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-inworld-realtime.json", "title": "Amazon Nova 2 Sonic vs Inworld Realtime API", "url": "https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-inworld-realtime" }, { "json": "https://www.anchorterminal.com/compare/assemblyai-voice-agent-vs-hume-evi.json", "title": "AssemblyAI Voice Agent API vs Hume EVI (Empathic Voice Interface)", "url": "https://www.anchorterminal.com/compare/assemblyai-voice-agent-vs-hume-evi" }, { "json": "https://www.anchorterminal.com/compare/assemblyai-voice-agent-vs-inworld-realtime.json", "title": "AssemblyAI Voice Agent API vs Inworld Realtime API", "url": "https://www.anchorterminal.com/compare/assemblyai-voice-agent-vs-inworld-realtime" }, { "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-inworld-realtime.json", "title": "Bland AI API + MCP vs Inworld Realtime API", "url": "https://www.anchorterminal.com/compare/bland-ai-vs-inworld-realtime" }, { "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-inworld-realtime.json", "title": "Bolna API + MCP vs Inworld Realtime API", "url": "https://www.anchorterminal.com/compare/bolna-vs-inworld-realtime" }, { "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-inworld-realtime.json", "title": "Deepgram Voice Agent API vs Inworld Realtime API", "url": "https://www.anchorterminal.com/compare/deepgram-voice-agent-vs-inworld-realtime" }, { "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-inworld-realtime.json", "title": "ElevenLabs Agents API + MCP vs Inworld Realtime API", "url": "https://www.anchorterminal.com/compare/elevenlabs-agents-vs-inworld-realtime" }, { "json": "https://www.anchorterminal.com/compare/fone-me-vs-hume-evi.json", "title": "fone.me vs Hume EVI (Empathic Voice Interface)", "url": "https://www.anchorterminal.com/compare/fone-me-vs-hume-evi" }, { "json": "https://www.anchorterminal.com/compare/fone-me-vs-inworld-realtime.json", "title": "fone.me vs Inworld Realtime API", "url": "https://www.anchorterminal.com/compare/fone-me-vs-inworld-realtime" }, { "json": "https://www.anchorterminal.com/compare/gemini-live-vs-hume-evi.json", "title": "Gemini Live API vs Hume EVI (Empathic Voice Interface)", "url": "https://www.anchorterminal.com/compare/gemini-live-vs-hume-evi" }, { "json": "https://www.anchorterminal.com/compare/gemini-live-vs-inworld-realtime.json", "title": "Gemini Live API vs Inworld Realtime API", "url": "https://www.anchorterminal.com/compare/gemini-live-vs-inworld-realtime" }, { "json": "https://www.anchorterminal.com/compare/gpt-live-vs-inworld-realtime.json", "title": "GPT-Live vs Inworld Realtime API", "url": "https://www.anchorterminal.com/compare/gpt-live-vs-inworld-realtime" }, { "json": "https://www.anchorterminal.com/compare/harmony-ai-vs-hume-evi.json", "title": "Harmony.ai vs Hume EVI (Empathic Voice Interface)", "url": "https://www.anchorterminal.com/compare/harmony-ai-vs-hume-evi" }, { "json": "https://www.anchorterminal.com/compare/harmony-ai-vs-inworld-realtime.json", "title": "Harmony.ai vs Inworld Realtime API", "url": "https://www.anchorterminal.com/compare/harmony-ai-vs-inworld-realtime" }, { "json": "https://www.anchorterminal.com/compare/hume-evi-vs-livekit-agents.json", "title": "Hume EVI (Empathic Voice Interface) vs LiveKit Agents", "url": "https://www.anchorterminal.com/compare/hume-evi-vs-livekit-agents" }, { "json": "https://www.anchorterminal.com/compare/hume-evi-vs-openai-realtime.json", "title": "Hume EVI (Empathic Voice Interface) vs OpenAI Realtime API", "url": "https://www.anchorterminal.com/compare/hume-evi-vs-openai-realtime" }, { "json": "https://www.anchorterminal.com/compare/hume-evi-vs-pipecat.json", "title": "Hume EVI (Empathic Voice Interface) vs Pipecat", "url": "https://www.anchorterminal.com/compare/hume-evi-vs-pipecat" }, { "json": "https://www.anchorterminal.com/compare/hume-evi-vs-placecall.json", "title": "Hume EVI (Empathic Voice Interface) vs PlaceCall", "url": "https://www.anchorterminal.com/compare/hume-evi-vs-placecall" }, { "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-rime-prism.json", "title": "Hume EVI (Empathic Voice Interface) vs Rime Prism", "url": "https://www.anchorterminal.com/compare/hume-evi-vs-rime-prism" }, { "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-vaani-voice.json", "title": "Hume EVI (Empathic Voice Interface) vs Vaani Developer Platform", "url": "https://www.anchorterminal.com/compare/hume-evi-vs-vaani-voice" }, { "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-vocily.json", "title": "Hume EVI (Empathic Voice Interface) vs Vocily AI", "url": "https://www.anchorterminal.com/compare/hume-evi-vs-vocily" }, { "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/inworld-realtime-vs-livekit-agents.json", "title": "Inworld Realtime API vs LiveKit Agents", "url": "https://www.anchorterminal.com/compare/inworld-realtime-vs-livekit-agents" }, { "json": "https://www.anchorterminal.com/compare/inworld-realtime-vs-openai-realtime.json", "title": "Inworld Realtime API vs OpenAI Realtime API", "url": "https://www.anchorterminal.com/compare/inworld-realtime-vs-openai-realtime" }, { "json": "https://www.anchorterminal.com/compare/inworld-realtime-vs-pipecat.json", "title": "Inworld Realtime API vs Pipecat", "url": "https://www.anchorterminal.com/compare/inworld-realtime-vs-pipecat" }, { "json": "https://www.anchorterminal.com/compare/inworld-realtime-vs-placecall.json", "title": "Inworld Realtime API vs PlaceCall", "url": "https://www.anchorterminal.com/compare/inworld-realtime-vs-placecall" }, { "json": "https://www.anchorterminal.com/compare/inworld-realtime-vs-retell-ai.json", "title": "Inworld Realtime API vs Retell AI API + MCP", "url": "https://www.anchorterminal.com/compare/inworld-realtime-vs-retell-ai" }, { "json": "https://www.anchorterminal.com/compare/inworld-realtime-vs-rime-prism.json", "title": "Inworld Realtime API vs Rime Prism", "url": "https://www.anchorterminal.com/compare/inworld-realtime-vs-rime-prism" }, { "json": "https://www.anchorterminal.com/compare/inworld-realtime-vs-synthflow.json", "title": "Inworld Realtime API vs Synthflow API + MCP", "url": "https://www.anchorterminal.com/compare/inworld-realtime-vs-synthflow" }, { "json": "https://www.anchorterminal.com/compare/inworld-realtime-vs-ultravox.json", "title": "Inworld Realtime API vs Ultravox Realtime API", "url": "https://www.anchorterminal.com/compare/inworld-realtime-vs-ultravox" }, { "json": "https://www.anchorterminal.com/compare/inworld-realtime-vs-vaani-voice.json", "title": "Inworld Realtime API vs Vaani Developer Platform", "url": "https://www.anchorterminal.com/compare/inworld-realtime-vs-vaani-voice" }, { "json": "https://www.anchorterminal.com/compare/inworld-realtime-vs-vapi.json", "title": "Inworld Realtime API vs Vapi API + MCP", "url": "https://www.anchorterminal.com/compare/inworld-realtime-vs-vapi" }, { "json": "https://www.anchorterminal.com/compare/inworld-realtime-vs-vocily.json", "title": "Inworld Realtime API vs Vocily AI", "url": "https://www.anchorterminal.com/compare/inworld-realtime-vs-vocily" }, { "json": "https://www.anchorterminal.com/compare/inworld-realtime-vs-vogent.json", "title": "Inworld Realtime API vs Vogent API", "url": "https://www.anchorterminal.com/compare/inworld-realtime-vs-vogent" }, { "json": "https://www.anchorterminal.com/compare/cuelight-vs-hume-evi.json", "title": "CueLight vs Hume EVI (Empathic Voice Interface)", "url": "https://www.anchorterminal.com/compare/cuelight-vs-hume-evi" }, { "json": "https://www.anchorterminal.com/compare/cuelight-vs-inworld-realtime.json", "title": "CueLight vs Inworld Realtime API", "url": "https://www.anchorterminal.com/compare/cuelight-vs-inworld-realtime" }, { "json": "https://www.anchorterminal.com/compare/hume-evi-vs-pipecat-phonellm.json", "title": "Hume EVI (Empathic Voice Interface) vs Pipecat PhoneLLM", "url": "https://www.anchorterminal.com/compare/hume-evi-vs-pipecat-phonellm" }, { "json": "https://www.anchorterminal.com/compare/inworld-realtime-vs-pipecat-phonellm.json", "title": "Inworld Realtime API vs Pipecat PhoneLLM", "url": "https://www.anchorterminal.com/compare/inworld-realtime-vs-pipecat-phonellm" }, { "json": "https://www.anchorterminal.com/compare/gpt-live-vs-hume-evi.json", "title": "GPT-Live vs Hume EVI (Empathic Voice Interface)", "url": "https://www.anchorterminal.com/compare/gpt-live-vs-hume-evi" } ], "panel": null, "scores": [ { "by": 7, "edge": "inworld-realtime", "hume-evi": 55, "inworld-realtime": 62, "key": "reliability", "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 30, "edge": "hume-evi", "hume-evi": 90, "inworld-realtime": 60, "key": "schema", "name": "Schema \u0026 documentation", "weight": 13 }, { "by": 2, "edge": "inworld-realtime", "hume-evi": 66, "inworld-realtime": 68, "key": "ergonomics", "name": "Agent ergonomics", "weight": 13 }, { "by": 31, "edge": "inworld-realtime", "hume-evi": 27, "inworld-realtime": 58, "key": "security", "name": "Security \u0026 auth", "weight": 14 }, { "by": 3, "edge": "inworld-realtime", "hume-evi": 37, "inworld-realtime": 40, "key": "payments", "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 36, "edge": "inworld-realtime", "hume-evi": 35, "inworld-realtime": 71, "key": "maintenance", "name": "Maintenance \u0026 community", "weight": 7 }, { "by": 2, "edge": "inworld-realtime", "hume-evi": 61, "inworld-realtime": 63, "key": "transparency", "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "Inworld Realtime API scores 60.1 (C) on agent readiness against Hume EVI (Empathic Voice Interface)'s 54.1 (C), and leads in 6 of 7 scored categories. Hume EVI (Empathic Voice Interface) leads on schema \u0026 documentation. Both do voice agents.", "tasks": null, "tutorials": [], "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. Hume ends API access on 13 November 2026.", "inworld-realtime": "Inworld's Realtime API speaks OpenAI's Realtime protocol over WebSocket or WebRTC, with a choice of LLM, client-side tools and dated release notes. Cost is the sum of STT, LLM and TTS usage with no per-minute price, there is no machine-readable event schema, and status history couldn't be read." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/hume-evi-vs-inworld-realtime", "json": "https://www.anchorterminal.com/compare/hume-evi-vs-inworld-realtime.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/hume-evi-vs-inworld-realtime.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/hume-evi-vs-inworld-realtime.min.md" }, "markdown": "Inworld Realtime API scores 60.1 (C) on agent readiness against Hume EVI (Empathic Voice Interface)'s 54.1 (C), and leads in 6 of 7 scored categories. Hume EVI (Empathic Voice Interface) leads on schema \u0026 documentation. Both do voice agents.\n\n- Hume EVI (Empathic Voice Interface): grade C, 54.1/100, rank #914 of 1486. Markdown https://www.anchorterminal.com/tools/hume-evi.md · JSON https://www.anchorterminal.com/api/v1/tools/hume-evi.json\n- Inworld Realtime API: grade C, 60.1/100, rank #668 of 1486. Markdown https://www.anchorterminal.com/tools/inworld-realtime.md · JSON https://www.anchorterminal.com/api/v1/tools/inworld-realtime.json\n- Best conversational voice-agent APIs: https://www.anchorterminal.com/best/voice-agents/index.md\n- All 518 voice agents comparisons: https://www.anchorterminal.com/compare/voice-agents/index.md\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- Schema \u0026 documentation, 90 against 60\n\nAlso in its favour:\n- A hosted endpoint, with nothing to install\n\nWatch for: Hume ends access to the TTS and EVI APIs on 13 November 2026 and deletes account data after that date\n\n### Inworld Realtime API (C)\n\nGood for: Teams moving off OpenAI's Realtime API who want a choice of LLM and Inworld voices.\n\nAhead on:\n- Reliability, 62 against 55\n- Security \u0026 auth, 58 against 27\n- Maintenance \u0026 community, 71 against 35\n\nWatch for: No per-minute price. A session's cost depends on STT, LLM tokens and TTS characters, and interrupted segments are still billed\n\n\n## Why the edge\n\n### Maintenance \u0026 community: Inworld Realtime API +36\n\n- 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.\n- Inworld Realtime API (71): Release note of 16 October 2026 (`cache_transcript`), 21 days ago (30). Three dated Realtime entries in the 90 days from 8 August, on 14 September, 23 September and 16 October (20). Discord and support@inworld.ai, with no evidence of answers read (8 of 15). Works with OpenAI's Realtime clients and the CLI is current at 1.5.0, but there is no Inworld Realtime SDK (8 of 15). CLI on npm under MIT, CI not read (5 of 10). Total 71.\n\n### Security \u0026 auth: Inworld Realtime API +31\n\n- 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).\n- Inworld Realtime API (58): Workspace API keys sent as Basic credentials, deleted to revoke, with separate keys per environment advised. The CLI mints read-only keys unless `--write` is given, but write toggles cover only the Voice and Router APIs, so no key is limited to one product. Browsers use short-lived tokens minted server side. Session IDs, not secrets, go in the URL (25 of 30). Tools run in the client, so the developer approves side effects, with no approval step in the API (10 of 20). The agent listens to callers and passes their speech to an LLM, and no prompt-injection guidance was found (5 of 15). Usage per key and a Performance page with errors and throttling (8 of 15). SOC 2 Type II and HIPAA claimed and a vulnerability report form, with no security.txt or bug bounty, per the 4 November reading (10 of 20). Total 58. Zero data retention covers session content from the Developer plan up, but not requests routed to third-party LLM providers.\n\n### Schema \u0026 documentation: Hume EVI (Empathic Voice Interface) +30\n\n- 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).\n- Inworld Realtime API (60): No AsyncAPI or other machine-readable file for the socket, and the spec paths redirect (0). llms.txt, Markdown twins and a docs MCP server (10). The overview, OpenAI migration guide, `providerData` reference and the billing page's account of how a session is counted say what to use when (16 of 20). The reference lists every client and server event with field types and required marks, as text rather than a schema (12 of 15). JavaScript and Python example projects and an error event with `type`, `code` and `param`, without a list of codes (9 of 15). Dated release notes with affected clients and required actions, but no API version beyond `/v1` (13 of 15). Total 60.\n\n### Reliability: Inworld Realtime API +7\n\n- 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.\n- Inworld Realtime API (62): Hosted reading of the checklist. status.inworld.ai is a public status page (20), with history we couldn't read, as on inworld-tts (5). Concurrent sessions are published per plan, 10 on On-Demand up to 1,000 on Growth (15). The rate limits page gives exponential backoff with jitter and Retry-After on longer windows, and sessions emit `rate_limits.updated`, with nothing on reconnecting a dropped session (12 of 15). An SLA appears only in the Enterprise column, with no terms (0). No preview or beta label on the Realtime API (10). 20 + 5 + 15 + 12 + 0 + 10 = 62.\n\n## Score by category\n\n| Category | Weight | Hume EVI (Empathic Voice Interface) | Inworld Realtime API | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 55 | 62 | Inworld Realtime API +7 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 90 | 60 | Hume EVI (Empathic Voice Interface) +30 |\n| Agent ergonomics | 13% (16.2 this run) | 66 | 68 | Inworld Realtime API +2 |\n| Security \u0026 auth | 14% (17.5 this run) | 27 | 58 | Inworld Realtime API +31 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 37 | 40 | Inworld Realtime API +3 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 35 | 71 | Inworld Realtime API +36 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 61 | 63 | Inworld Realtime API +2 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **54.1 · C** | **60.1 · C** | |\n\n## Facts side by side\n\n| Fact | Hume EVI (Empathic Voice Interface) | Inworld Realtime API |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Hume AI | Inworld AI |\n| Hosted endpoint | `https://api.hume.ai/v0/evi` | no (local only) |\n| Transports | HTTP | websocket, HTTP |\n| Auth | OAuth or key | API key |\n| Pricing | Freemium | Pay per use |\n| Price for voice agents | not published | $25 per 1M characters |\n| x402 | no | no |\n| Licence | MIT (SDKs) | none |\n| Tools exposed | none | 0 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| Last release | 2026-08-18 | 2026-10-16 |\n| Terms last updated | 2026-10-05 | 2025-06-11 |\n| Privacy policy last updated | 2025-02-25 | 2026-01-18 |\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## How the scores have moved\n\n### Hume EVI (Empathic Voice Interface)\n\n- -2.6 on 4 November 2026: time\n- -0.6 on 8 October 2026: checklist\n\n### Inworld Realtime API\n\nNo score change since it was listed.\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. Hume ends API access on 13 November 2026.\n\n**Inworld Realtime API.** Inworld's Realtime API speaks OpenAI's Realtime protocol over WebSocket or WebRTC, with a choice of LLM, client-side tools and dated release notes. Cost is the sum of STT, LLM and TTS usage with no per-minute price, there is no machine-readable event schema, and status history couldn't be read.\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### Inworld Realtime API\n\n1. Set the auto follow-up off if your client sends its own `response.create` after a tool result, or replies double\n2. Read `response.done` usage as an estimate and mute input audio when nobody speaks, since STT bills every second sent\n3. Use `response.speak` for fixed greetings, which skips the LLM\n4. Treat `unsupported_field` errors as warnings and keep the session open\n5. Mint browser session tokens on your server and never ship the Basic credential to a client\n\n## Questions\n\n### Which is better for AI agents, Hume EVI (Empathic Voice Interface) or Inworld Realtime API?\n\nInworld Realtime API scores 60.1 (C) on agent readiness against Hume EVI (Empathic Voice Interface)'s 54.1 (C), and leads in 6 of 7 scored categories. Hume EVI (Empathic Voice Interface) leads on schema \u0026 documentation.\n\n### Do Hume EVI (Empathic Voice Interface) and Inworld Realtime API need an API key?\n\nHume EVI (Empathic Voice Interface) takes an API key or an OAuth sign-in. Inworld Realtime API needs an API key.\n\n### Can an agent call Hume EVI (Empathic Voice Interface) and Inworld Realtime API without installing anything?\n\nHume EVI (Empathic Voice Interface) has a hosted endpoint at https://api.hume.ai/v0/evi. No hosted endpoint is listed for Inworld Realtime API.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/hume-evi-vs-inworld-realtime.json, and with the fewest tokens: https://www.anchorterminal.com/compare/hume-evi-vs-inworld-realtime.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"hume-evi\", \"b\": \"inworld-realtime\"}`. From a terminal: `anchor compare hume-evi inworld-realtime`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/hume-evi.json and https://www.anchorterminal.com/api/v1/tools/inworld-realtime.json\n\n## Other comparisons with Hume EVI (Empathic Voice Interface) or Inworld Realtime API\n\n- [Amazon Nova 2 Sonic vs Hume EVI (Empathic Voice Interface)](https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-hume-evi.md)\n- [Amazon Nova 2 Sonic vs Inworld Realtime API](https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-inworld-realtime.md)\n- [AssemblyAI Voice Agent API vs Hume EVI (Empathic Voice Interface)](https://www.anchorterminal.com/compare/assemblyai-voice-agent-vs-hume-evi.md)\n- [AssemblyAI Voice Agent API vs Inworld Realtime API](https://www.anchorterminal.com/compare/assemblyai-voice-agent-vs-inworld-realtime.md)\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 Inworld Realtime API](https://www.anchorterminal.com/compare/bland-ai-vs-inworld-realtime.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 Inworld Realtime API](https://www.anchorterminal.com/compare/bolna-vs-inworld-realtime.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 Inworld Realtime API](https://www.anchorterminal.com/compare/deepgram-voice-agent-vs-inworld-realtime.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 Inworld Realtime API](https://www.anchorterminal.com/compare/elevenlabs-agents-vs-inworld-realtime.md)\n- [fone.me vs Hume EVI (Empathic Voice Interface)](https://www.anchorterminal.com/compare/fone-me-vs-hume-evi.md)\n- [fone.me vs Inworld Realtime API](https://www.anchorterminal.com/compare/fone-me-vs-inworld-realtime.md)\n- [Gemini Live API vs Hume EVI (Empathic Voice Interface)](https://www.anchorterminal.com/compare/gemini-live-vs-hume-evi.md)\n- [Gemini Live API vs Inworld Realtime API](https://www.anchorterminal.com/compare/gemini-live-vs-inworld-realtime.md)\n- [GPT-Live vs Inworld Realtime API](https://www.anchorterminal.com/compare/gpt-live-vs-inworld-realtime.md)\n- [Harmony.ai vs Hume EVI (Empathic Voice Interface)](https://www.anchorterminal.com/compare/harmony-ai-vs-hume-evi.md)\n- [Harmony.ai vs Inworld Realtime API](https://www.anchorterminal.com/compare/harmony-ai-vs-inworld-realtime.md)\n- [Hume EVI (Empathic Voice Interface) vs LiveKit Agents](https://www.anchorterminal.com/compare/hume-evi-vs-livekit-agents.md)\n- [Hume EVI (Empathic Voice Interface) vs OpenAI Realtime API](https://www.anchorterminal.com/compare/hume-evi-vs-openai-realtime.md)\n- [Hume EVI (Empathic Voice Interface) vs Pipecat](https://www.anchorterminal.com/compare/hume-evi-vs-pipecat.md)\n- [Hume EVI (Empathic Voice Interface) vs PlaceCall](https://www.anchorterminal.com/compare/hume-evi-vs-placecall.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 Rime Prism](https://www.anchorterminal.com/compare/hume-evi-vs-rime-prism.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 Vaani Developer Platform](https://www.anchorterminal.com/compare/hume-evi-vs-vaani-voice.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 Vocily AI](https://www.anchorterminal.com/compare/hume-evi-vs-vocily.md)\n- [Hume EVI (Empathic Voice Interface) vs Vogent API](https://www.anchorterminal.com/compare/hume-evi-vs-vogent.md)\n- [Inworld Realtime API vs LiveKit Agents](https://www.anchorterminal.com/compare/inworld-realtime-vs-livekit-agents.md)\n- [Inworld Realtime API vs OpenAI Realtime API](https://www.anchorterminal.com/compare/inworld-realtime-vs-openai-realtime.md)\n- [Inworld Realtime API vs Pipecat](https://www.anchorterminal.com/compare/inworld-realtime-vs-pipecat.md)\n- [Inworld Realtime API vs PlaceCall](https://www.anchorterminal.com/compare/inworld-realtime-vs-placecall.md)\n- [Inworld Realtime API vs Retell AI API + MCP](https://www.anchorterminal.com/compare/inworld-realtime-vs-retell-ai.md)\n- [Inworld Realtime API vs Rime Prism](https://www.anchorterminal.com/compare/inworld-realtime-vs-rime-prism.md)\n- [Inworld Realtime API vs Synthflow API + MCP](https://www.anchorterminal.com/compare/inworld-realtime-vs-synthflow.md)\n- [Inworld Realtime API vs Ultravox Realtime API](https://www.anchorterminal.com/compare/inworld-realtime-vs-ultravox.md)\n- [Inworld Realtime API vs Vaani Developer Platform](https://www.anchorterminal.com/compare/inworld-realtime-vs-vaani-voice.md)\n- [Inworld Realtime API vs Vapi API + MCP](https://www.anchorterminal.com/compare/inworld-realtime-vs-vapi.md)\n- [Inworld Realtime API vs Vocily AI](https://www.anchorterminal.com/compare/inworld-realtime-vs-vocily.md)\n- [Inworld Realtime API vs Vogent API](https://www.anchorterminal.com/compare/inworld-realtime-vs-vogent.md)\n- [CueLight vs Hume EVI (Empathic Voice Interface)](https://www.anchorterminal.com/compare/cuelight-vs-hume-evi.md)\n- [CueLight vs Inworld Realtime API](https://www.anchorterminal.com/compare/cuelight-vs-inworld-realtime.md)\n- [Hume EVI (Empathic Voice Interface) vs Pipecat PhoneLLM](https://www.anchorterminal.com/compare/hume-evi-vs-pipecat-phonellm.md)\n- [Inworld Realtime API vs Pipecat PhoneLLM](https://www.anchorterminal.com/compare/inworld-realtime-vs-pipecat-phonellm.md)\n- [GPT-Live vs Hume EVI (Empathic Voice Interface)](https://www.anchorterminal.com/compare/gpt-live-vs-hume-evi.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "attributionRequired": true, "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-11-07", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.7", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run", "terms": "https://www.anchorterminal.com/terms/#data" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Hume EVI (Empathic Voice Interface) vs Inworld Realtime API", "url": "" } ], "description": "Inworld Realtime scores 60.1 (C) to Hume EVI's 54.1 (C) for voice agents. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Hume EVI (Empathic Voice Interface) C 54.1", "Inworld Realtime API C 60.1", "scores" ], "h1": "Hume EVI (Empathic Voice Interface) vs Inworld Realtime API", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/hume-evi-vs-inworld-realtime", "published": "2026-10-01", "section": "tools", "title": "Hume EVI vs Inworld Realtime for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/hume-evi-vs-inworld-realtime" }, "tokens": { "markdown": 5200, "slim": 2530 }, "version": 1 }