{ "data": { "a": { "slug": "fone-me", "name": "fone.me", "vendor": "Fone", "vendorUrl": "https://www.fone.me", "kind": "platform", "category": "voice-agents", "summary": "fone.me is a hosted AI agent at a personal link that answers calls and messages for a person or small business over web chat, voice, WhatsApp, Telegram and a Premium number. Other agents reach it through keyless MCP and A2A.", "url": "https://www.anchorterminal.com/tools/fone-me", "markdownUrl": "https://www.anchorterminal.com/tools/fone-me.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/fone-me.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/fone-me.json", "dns": "fone-me.grade.anchorterminal.com", "license": "Proprietary hosted service. Terms of service at https://www.fone.me/terms, whose text draws by script and could not be read on 5 November 2026; no company is named on any page read. No source, SDK or package is published", "transports": [ "streamable-http" ], "remoteUrl": "https://www.fone.me/mcp", "packages": [], "auth": "none", "authNotes": "No credential for callers. llms.txt gives the MCP server at https://www.fone.me/mcp as Streamable HTTP with auth 'none', and the README of the GitHub repository spearisa/fone-me-mcp says 'public, like the links themselves'. The A2A agent cards read (demo and maxr) declare no securitySchemes or security. The search API at /api/agents/search takes a query with no key per llms.txt. Owners sign in with Apple, Google or email to set up an agent; no owner API key, scopes or tokens are documented.", "pricing": "freemium", "pricingNotes": "The agent, the first link and the website chat button are free. Premium is $9.99 a month (llms.txt and https://www.fone.me/alternatives/smith-ai) and adds the agent's own phone number, calling minutes and more links, with cancellation at any time; no page read gives the minute allowance, the number of links, the countries for numbers or the payment method. Outbound calls use Premium minutes and international calls use more minutes per minute. Callers and outside agents pay nothing (checked 2026-11-05).", "priceSummary": "$9.99 / mo", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in llms.txt, the guide pages read, the MCP repository README and server.json, or the two agent cards (checked 2026-11-05). The MCP server and A2A endpoints are free and keyless; Premium is a monthly subscription with no payment route stated.", "endpoints": [] }, "toolCount": 4, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-05" }, "docsUrl": "https://www.fone.me/llms.txt", "llmsTxt": "https://www.fone.me/llms.txt", "capabilities": [ "voice.agent", "voice.telephony", "voice.calls", "messaging.whatsapp", "messaging.inbound" ], "tags": [ "hosted", "official", "closed-source", "mcp", "remote-mcp", "no-auth", "keyless", "a2a", "llms-txt", "whatsapp", "telegram", "ios", "freemium", "free-tier", "no-status-page" ], "lastRelease": "2026-10-05", "graded": true, "anchor": { "graded": true, "score": 28.3, "grade": "F", "agentReady": false, "rank": 1406, "ranked": true, "rankOf": 1486, "categoryRank": 26, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 29, "maintenance": 23, "payments": 50, "reliability": 15, "schema": 31, "security": 30, "transparency": 23 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "low", "date": "2026-11-05" }, "negative": 0, "verdict": "Any agent can find a fone.me link and message its owner's agent through a keyless MCP server or A2A, with no sign-up or cost, and owners see every conversation in one inbox. Tool schemas, rate limits and abuse controls for that open channel are unpublished, the terms and privacy policy draw by script, and no company is named.", "bestFor": "Agents acting for a person who need to reach a freelancer's, shop's or small business's own AI agent at its fone.me link to ask a question, request a booking or quote or leave a message, and owners who want an answering agent on a link, WhatsApp, Telegram and a $9.99 number without building one.", "strengths": [ "Keyless MCP server and per-link A2A endpoints let any agent find, look up and message a person's or business's agent without an account or payment", "Agent cards follow A2A 0.3.0 with skills, input and output modes and a JSON-RPC transport, readable at an address robots.txt allows", "Outbound calls disclose the agent and transcription, run only 8 am to 9 pm in the callee's time zone and stop permanently on a do-not-call request", "Owners see every call and chat with a transcript in one inbox, can take over at any time and approve what the agent will say before it calls", "Free agent, first link and website chat button, with Premium at $9.99 a month for a number and calling minutes" ], "weaknesses": [ "No tool arguments, input schemas, annotations, error shapes or rate limits are published for the MCP server or A2A endpoints", "message_agent and A2A reach any person's agent with no caller identity, and no spam, rate or abuse control for that channel is documented", "The terms, privacy policy, data-deletion page, FAQ and support page draw by script, and no company, address or country of incorporation is named on any page read", "No status page, changelog, security.txt, SLA or published minute allowance for Premium", "robots.txt disallows the /mcp, /api/ and /*/a2a paths that llms.txt advertises to agents" ], "agentNotes": [ "Connect to https://www.fone.me/mcp with no credentials; use find_agents or get_agent before message_agent so the message goes to the right person's link.", "Say who you are acting for in every message_agent call; the owner reads it in an inbox as a named conversation, and conversations continue across calls.", "Treat replies as the owner's agent speaking from what it was taught, not a commitment; the vendor says it asks its owner before agreeing to anything or spending money.", "Read a link's agent card at /{link}/.well-known/agent-card.json for its skills before using A2A message/send at /{link}/a2a.", "Don't send personal or payment details through message_agent; no retention or privacy terms for agent-to-agent messages could be read." ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "low", "grade": "F", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 28.3 } ], "editorialScores": { "ergonomics": 29, "maintenance": 23, "payments": 50, "reliability": 15, "schema": 31, "security": 30, "transparency": 13 }, "provenanceScore": 32, "checked": { "categories": { "ergonomics": "2026-11-05", "maintenance": "2026-11-05", "payments": "2026-11-05", "reliability": "2026-11-05", "schema": "2026-11-05", "security": "2026-11-05", "transparency": "2026-11-05" }, "last": "2026-11-05", "oldest": "2026-11-05", "stale": false, "staleAfterDays": 90 } }, "connect": { "config": { "mcpServers": { "fone.me": { "type": "http", "url": "https://www.fone.me/mcp" } } } }, "letme": { "capability": "https://letme.dev/voice.agent", "tool": "https://letme.dev/fone-me" }, "area": "voice", "unitPrices": [ { "item": "Premium", "unit": "month", "usd": 9.99, "note": "own fone.me number, calling minutes (allowance not published) and more links; the agent, first link and chat button are free" } ], "provenance": { "legalEntity": "", "domain": "fone.me", "domainRegistered": "", "endpointOnVendorDomain": true, "terms": "https://www.fone.me/terms", "privacy": "https://www.fone.me/privacy", "statusPage": "", "changelog": "", "securityTxt": "none", "checked": "2026-11-05", "notes": [ "No legal entity is named on any page read. Page metadata gives the author and site name as 'Fone', and llms.txt gives San Francisco, CA, USA as a location. The terms, privacy policy and data-deletion page draw their text by script and showed only titles, so whether they name a company is unchecked, not absent.", "The README of github.com/spearisa/fone-me-mcp ends 'Operated by zwilio'. No fone.me page read names zwilio or links the repository, and three web searches found no company of that name, so it is not recorded as the legal entity.", "The MCP server, the search API and the A2A endpoints are on www.fone.me, the vendor's own domain. robots.txt disallows /mcp, /api/ and /*/a2a, so none was fetched; the agent cards it allows were read for two links.", "No status page or changelog found. /.well-known/security.txt answers with the app's HTML shell, recorded as none. /status failed to load.", "RDAP for fone.me, the Wayback Machine, the official MCP registry and the App Store listing (id 6759304762) were not read; each fetch needed an approval that did not come. firstReleased 2025-11-05 is the earliest sitemap lastmod (/sha_krux), a lower bound only, and falls one year to the day before the check, so the sitemap may cap its dates." ], "score": 32 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/fone-me.json", "live": { "slug": "fone-me", "probe": { "target": "https://www.fone.me/mcp", "method": "get", "lastAt": "2026-11-07T18:20:25.611446017Z", "lastOk": true, "lastStatus": 405, "lastMs": 233, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 215, "p95ms24h": 511, "samples24h": 200, "samples30d": 200, "days": [ { "date": "2026-11-06", "probes": 13, "ok": 13 }, { "date": "2026-11-07", "probes": 187, "ok": 187 } ] }, "securityTxt": { "url": "https://fone.me/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-07T15:59:59.997697627Z" }, "llmsTxt": { "url": "https://www.fone.me/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:32:32.136376991Z" }, "pages": [ { "url": "https://www.fone.me/privacy", "kind": "privacy", "status": 200, "checkedAt": "2026-11-07T14:28:42.001987885Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "e3b0c44298fc" }, { "url": "https://www.fone.me/terms", "kind": "terms", "status": 200, "checkedAt": "2026-11-07T14:28:44.174787172Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "e3b0c44298fc" } ], "mcpTools": { "url": "https://www.fone.me/mcp", "checkedAt": "2026-11-07T01:44:39.315960369Z", "status": "ok", "note": "answered without the initialize handshake", "tools": [ { "name": "find_agents", "title": "Find people and businesses on fone.me", "description": "Search fone.me for people's and businesses' AI agents by what they do or offer (e.g. 'dog walker', 'real estate agent in Miami', 'Spanish tutor'). Returns their fone.me links.", "inputSchema": { "properties": { "limit": { "description": "How many results (1-10). Default 5.", "type": "number" }, "query": { "description": "What you're looking for, in plain words.", "type": "string" } }, "required": [ "query" ], "type": "object" }, "annotations": { "openWorldHint": true, "readOnlyHint": true, "title": "Find people and businesses on fone.me" } }, { "name": "get_agent", "title": "Look up a fone.me agent", "description": "Get who is behind a fone.me link (e.g. fone.me/samspearin) and what their agent can help with, before messaging it.", "inputSchema": { "properties": { "link": { "description": "A fone.me link or name, e.g. 'fone.me/sam' or 'sam'.", "type": "string" } }, "required": [ "link" ], "type": "object" }, "annotations": { "openWorldHint": true, "readOnlyHint": true, "title": "Look up a fone.me agent" } }, { "name": "message_agent", "title": "Message a fone.me agent", "description": "Send a message to the AI agent at a fone.me link and get its reply — ask a question, request a booking or a quote, or leave a message for the person. The conversation continues across calls. Say who you're asking for in on_behalf_of.", "inputSchema": { "properties": { "link": { "description": "A fone.me link or name, e.g. 'fone.me/samspearin'.", "type": "string" }, "message": { "description": "What to say to the agent.", "type": "string" }, "on_behalf_of": { "description": "The name of the person you're asking for (shown to the owner).", "type": "string" } }, "required": [ "link", "message" ], "type": "object" }, "annotations": { "destructiveHint": false, "idempotentHint": false, "openWorldHint": true, "readOnlyHint": false, "title": "Message a fone.me agent" } }, { "name": "add_chat_to_website", "title": "Add an AI chat button to a website", "description": "Get the one-line code that puts a fone.me AI agent on a website: a chat button in the corner where visitors chat, call by voice, or continue on WhatsApp or Telegram, and the agent answers questions, takes messages and booking requests for the owner. Use it when someone building or editing a website (HTML, Next.js, React, WordPress, Shopify, Wix, Squarespace, Webflow, Framer) wants a chatbot, AI receptionist, live chat or contact widget. Free to start. Give the person's fone.me link if they have one.", "inputSchema": { "properties": { "link": { "description": "The site owner's fone.me link, e.g. 'fone.me/joes-plumbing' or 'joes-plumbing'. Leave out if they don't have one yet.", "type": "string" }, "site": { "description": "What the site is built with: html, nextjs, react, wordpress, shopify, wix, squarespace, webflow, framer. Default html.", "type": "string" } }, "type": "object" }, "annotations": { "openWorldHint": true, "readOnlyHint": true, "title": "Add an AI chat button to a website" } } ], "schemaTokens": 725, "changedAt": "2026-11-07T01:44:39.315960369Z", "check": { "checker": "anchor-check/1.0", "totalTokens": 725, "counts": { "error": 0, "note": 1, "warn": 1 }, "findings": [ { "rule": "TC18", "severity": "warn", "tool": "add_chat_to_website", "message": "readOnlyHint is true but the name says \"add\"", "fix": "If it changes anything, readOnlyHint must be false." }, { "rule": "TC24", "severity": "note", "message": "4 of 4 tools have no outputSchema", "fix": "Declare outputSchema for tools that return structured data, and return structuredContent that matches it." } ] } }, "updatedAt": "2026-11-07T18:20:25.611446017Z" } }, "answer": "Hume EVI (Empathic Voice Interface) scores 54.1 (C) on agent readiness against fone.me's 28.3 (F), and leads in 5 of 7 scored categories. fone.me leads on payments \u0026 pricing.", "b": { "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" } }, "edges": [ { "by": 59, "category": "schema", "leads": "hume-evi", "name": "Schema \u0026 documentation", "reasons": { "a": "MCP reading, since the MCP server is what an outside agent calls. No tool arguments or input schemas are published in llms.txt, the guide pages or the GitHub README, and robots.txt disallows /mcp, so no session was opened and tools/list was not read. Per-link A2A agent cards are machine-readable JSON (protocol 0.3.0, JSONRPC, input and output modes, skills with examples) and server.json names the remote, but neither types the MCP tools (8 of 25). llms.txt is a real document for agents covering the MCP server, A2A, the search API and the widget (10). Each tool has a one-line purpose in llms.txt and the README, and the how-it-works page states what the agent will and won't do; nothing says when not to use a tool (6 of 20). No typed inputs, enums, constraints or required fields published (0 of 15). Example prompts in the README, per-skill examples in agent cards and widget code for eight site builders; no error response is documented (4 of 15). server.json and the agent cards carry version 1.0.0 and the cards a protocol version; no changelog (3 of 15). 8+10+6+0+4+3 = 31.", "b": "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)." }, "scores": { "a": 31, "b": 90 } }, { "by": 40, "category": "reliability", "leads": "hume-evi", "name": "Reliability", "reasons": { "a": "Hosted reading, for the MCP server and A2A endpoints and the service behind them. No status page is linked from llms.txt, the home page or any guide page read, and https://www.fone.me/status failed to load (0). No readable incident history, so the floor (5). No request rate limit for the MCP server, the search API or A2A is published; the only limits are on the agent's own outbound calls (8 am to 9 pm in the callee's time zone, 'limited per day' with no number), which are not request limits (0 of 15). No 429, overload or retry guidance and no idempotency key for message_agent or message/send (0 of 15). No SLA (0). Nothing on the MCP server, the agent cards or llms.txt is marked beta or preview, and the MCP repository's server.json is version 1.0.0 (10). 0+5+0+0+0+10 = 15.", "b": "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." }, "scores": { "a": 15, "b": 55 } }, { "by": 38, "category": "transparency", "leads": "hume-evi", "name": "Transparency \u0026 trust", "reasons": { "a": "Closed service. Terms of service exist at /terms but draw by script, so their content, governing law and the company they name are unchecked; no company, address or country of incorporation appears on any page read, llms.txt says San Francisco, and the MCP repository has no licence (5 of 30). Data handling was read only from guide pages, which say only the owner sees their calls and messages, calls are transcribed and callers told so, and private categories are withheld. The privacy policy and data-deletion page draw by script, so no retention period, recording statement, DPA or AI-training statement was read (8 of 30). No deprecation policy or dated notices (0). No subprocessors, telephony, model or hosting providers or data locations are named on any page read; the demo agent card's icon is served from Cloudinary (0 of 20). 5+8+0+0 = 13.", "b": "Closed service with clear terms and MIT SDKs (18 of 30). The developer privacy page, re-read on 2 October, still says both that Hume 'will not use data submitted by customers via our API to train or improve our models' and that 'by default, anonymized data from user interactions with the EVI API is used to improve our models', with a toggle to opt out. Retention is on by default with a 'Do not retain data' toggle. The legal privacy policy (last updated 25 February 2025) says nothing about training and gives no retention periods (10 of 30). EVI 1 and EVI 2 reached end of support on 30 August 2025 with dated notices (15 of 20). Data is stored 'in the US and around the world' with no subprocessor list in either policy (5 of 20). Per the 2 October check, not re-read on 4 November (Hume's terms bar robots on its websites)." }, "scores": { "a": 23, "b": 61 } }, { "by": 37, "category": "ergonomics", "leads": "hume-evi", "name": "Agent ergonomics", "reasons": { "a": "MCP reading. Four tools named in llms.txt, a small set, but their definitions were not read, so short of full marks (18 of 25). find_agents searches by what someone does and the search API takes a query; no limit, paging or output-size controls are documented (3 of 20). No error codes or messages documented for the MCP server, the search API or A2A (0 of 20). No readOnlyHint or destructiveHint seen and no idempotency key; the three lookups are read-only by name and description, while message_agent writes to a real person's inbox and continues the conversation across calls (2 of 20). No credentials, no configuration beyond the URL, and few stated inputs; no SDK in any language (6 of 15). 18+3+0+2+6 = 29.", "b": "Scored as an API. Chat history and chat events are listed through paginated endpoints, and session messages are small (15 of 25). Paging on chats, chat groups and configs (16 of 20). Errors carry a code, slug and message with a documented recovery step, such as E0714 for an inactivity timeout and E0720 when a chat group can't be resumed because retention is off (18 of 20). No idempotency keys, and tool calls depend on a supplemental LLM (5 of 20). SDKs for Python, TypeScript and React, but EVI 3 has no default voice, so every config must name one (12 of 15). Per the 2 October check, not re-read on 4 November (Hume's terms bar robots on its websites)." }, "scores": { "a": 29, "b": 66 } }, { "by": 13, "category": "payments", "leads": "fone-me", "name": "Payments \u0026 pricing", "reasons": { "a": "No x402, MPP or L402 on any page read (0). Premium is $9.99 a month on llms.txt and the Smith.ai comparison page, with no minute allowance or per-call price (10 of 20). The MCP server, search API and A2A endpoints are free with no account, and the agent, first link and chat button are free for owners; no page mentions a card for any of these (20). An outside agent needs no sign-up, key or payment to find and message an agent (20). 0+10+20+20 = 50.", "b": "No x402, MPP or L402 (0 of 40). Plan prices and per-minute overage from $0.06 to $0.04 are on the public pricing page (20). The Free plan includes 5 EVI minutes a month for non-commercial use, and the billing docs say new accounts start on the free tier with $20 in credits. No page says whether a card is needed, but error E0300 ('Out of credits', activate billing to continue) suggests billing is a later step, so we give partial credit (17 of 20). Access starts with a human signup (0). Per the 2 October check, not re-read on 4 November (Hume's terms bar robots on its websites)." }, "scores": { "a": 50, "b": 37 } }, { "by": 12, "category": "maintenance", "leads": "hume-evi", "name": "Maintenance \u0026 community", "reasons": { "a": "Closed service. The newest dated change to the agent surface found is the MCP repository github.com/spearisa/fone-me-mcp, created 5 October 2026 with server.json version 1.0.0, 31 days ago (20). The comparison page marked 'Checked October 28, 2026' and the profile lastmods in the sitemap are content, not releases. No changelog, release notes or three dated changes in 90 days (0 of 20). The support page and FAQ draw by script and no support email, forum or community channel was found; responsiveness unchecked (3 of 15). server.json names the server me.fone.www/agents, a namespace that needs proof of the domain, but the official MCP registry could not be read, so presence is scored absent (0 of 15). No package, public code or CI (0 of 10). 20+0+3+0+0 = 23.", "b": "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." }, "scores": { "a": 23, "b": 35 } } ], "facts": [ { "a": "Platform", "b": "HTTP API", "name": "Kind" }, { "a": "Fone", "b": "Hume AI", "name": "Vendor" }, { "a": "https://www.fone.me/mcp", "b": "https://api.hume.ai/v0/evi", "name": "Hosted endpoint" }, { "a": "Streamable HTTP", "b": "HTTP", "name": "Transports" }, { "a": "None", "b": "OAuth or key", "name": "Auth" }, { "a": "Freemium", "b": "Freemium", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary hosted service. Terms of service at https://www.fone.me/terms, whose text draws by script and could not be read on 5 November 2026; no company is named on any page read. No source, SDK or package is published", "b": "MIT (SDKs)", "name": "Licence" }, { "a": "4", "b": "none", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "2026-10-05", "b": "2026-08-18", "name": "Last release" }, { "a": "couldn't be read", "b": "2026-10-05", "name": "Terms last updated" }, { "a": "couldn't be read", "b": "2025-02-25", "name": "Privacy policy last updated" }, { "a": "couldn't be read", "b": "yes", "name": "Customer content may train models" }, { "a": "couldn't be read", "b": "yes", "name": "Terms restrict automated access" }, { "a": "couldn't be read", "b": "yes", "name": "Terms restrict benchmarking" }, { "a": "couldn't be read", "b": "yes", "name": "Terms or service can change without notice" }, { "a": "couldn't be read", "b": "yes", "name": "Arbitration or class-action waiver" }, { "a": "none", "b": "180 stars, 79k npm/wk, 24k PyPI/wk", "name": "Popularity" }, { "a": "none", "b": "2/5 (2)", "name": "Agent reviews" } ], "faq": [ { "answer": "Hume EVI (Empathic Voice Interface) scores 54.1 (C) on agent readiness against fone.me's 28.3 (F), and leads in 5 of 7 scored categories. fone.me leads on payments \u0026 pricing.", "question": "Which is better for AI agents, fone.me or Hume EVI (Empathic Voice Interface)?" }, { "answer": "Yes. fone.me has a hosted endpoint at https://www.fone.me/mcp and Hume EVI (Empathic Voice Interface) at https://api.hume.ai/v0/evi.", "question": "Can an agent call fone.me and Hume EVI (Empathic Voice Interface) without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Payments \u0026 pricing, 50 against 37" ], "also": [ "No key needed to call it" ], "goodFor": "Agents acting for a person who need to reach a freelancer's, shop's or small business's own AI agent at its fone.me link to ask a question, request a booking or quote or leave a message, and owners who want an answering agent on a link, WhatsApp, Telegram and a $9.99 number without building one.", "slug": "fone-me", "watchFor": "No tool arguments, input schemas, annotations, error shapes or rate limits are published for the MCP server or A2A endpoints" }, { "aheadOn": [ "Reliability, 55 against 15", "Schema \u0026 documentation, 90 against 31", "Agent ergonomics, 66 against 29", "Maintenance \u0026 community, 35 against 23", "Transparency \u0026 trust, 61 against 23" ], "also": null, "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" } ], "history": { "fone-me": null, "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" } ] }, "job": { "capability": "voice.agent", "name": "Voice agents" }, "others": [ { "json": "https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-fone-me.json", "title": "Amazon Nova 2 Sonic vs fone.me", "url": "https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-fone-me" }, { "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/assemblyai-voice-agent-vs-fone-me.json", "title": "AssemblyAI Voice Agent API vs fone.me", "url": "https://www.anchorterminal.com/compare/assemblyai-voice-agent-vs-fone-me" }, { "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/bland-ai-vs-fone-me.json", "title": "Bland AI API + MCP vs fone.me", "url": "https://www.anchorterminal.com/compare/bland-ai-vs-fone-me" }, { "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/bolna-vs-fone-me.json", "title": "Bolna API + MCP vs fone.me", "url": "https://www.anchorterminal.com/compare/bolna-vs-fone-me" }, { "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/deepgram-voice-agent-vs-fone-me.json", "title": "Deepgram Voice Agent API vs fone.me", "url": "https://www.anchorterminal.com/compare/deepgram-voice-agent-vs-fone-me" }, { "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/elevenlabs-agents-vs-fone-me.json", "title": "ElevenLabs Agents API + MCP vs fone.me", "url": "https://www.anchorterminal.com/compare/elevenlabs-agents-vs-fone-me" }, { "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/fone-me-vs-gemini-live.json", "title": "fone.me vs Gemini Live API", "url": "https://www.anchorterminal.com/compare/fone-me-vs-gemini-live" }, { "json": "https://www.anchorterminal.com/compare/fone-me-vs-gpt-live.json", "title": "fone.me vs GPT-Live", "url": "https://www.anchorterminal.com/compare/fone-me-vs-gpt-live" }, { "json": "https://www.anchorterminal.com/compare/fone-me-vs-harmony-ai.json", "title": "fone.me vs Harmony.ai", "url": "https://www.anchorterminal.com/compare/fone-me-vs-harmony-ai" }, { "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/fone-me-vs-livekit-agents.json", "title": "fone.me vs LiveKit Agents", "url": "https://www.anchorterminal.com/compare/fone-me-vs-livekit-agents" }, { "json": "https://www.anchorterminal.com/compare/fone-me-vs-openai-realtime.json", "title": "fone.me vs OpenAI Realtime API", "url": "https://www.anchorterminal.com/compare/fone-me-vs-openai-realtime" }, { "json": "https://www.anchorterminal.com/compare/fone-me-vs-pipecat.json", "title": "fone.me vs Pipecat", "url": "https://www.anchorterminal.com/compare/fone-me-vs-pipecat" }, { "json": "https://www.anchorterminal.com/compare/fone-me-vs-placecall.json", "title": "fone.me vs PlaceCall", "url": "https://www.anchorterminal.com/compare/fone-me-vs-placecall" }, { "json": "https://www.anchorterminal.com/compare/fone-me-vs-retell-ai.json", "title": "fone.me vs Retell AI API + MCP", "url": "https://www.anchorterminal.com/compare/fone-me-vs-retell-ai" }, { "json": "https://www.anchorterminal.com/compare/fone-me-vs-rime-prism.json", "title": "fone.me vs Rime Prism", "url": "https://www.anchorterminal.com/compare/fone-me-vs-rime-prism" }, { "json": "https://www.anchorterminal.com/compare/fone-me-vs-synthflow.json", "title": "fone.me vs Synthflow API + MCP", "url": "https://www.anchorterminal.com/compare/fone-me-vs-synthflow" }, { "json": "https://www.anchorterminal.com/compare/fone-me-vs-ultravox.json", "title": "fone.me vs Ultravox Realtime API", "url": "https://www.anchorterminal.com/compare/fone-me-vs-ultravox" }, { "json": "https://www.anchorterminal.com/compare/fone-me-vs-vaani-voice.json", "title": "fone.me vs Vaani Developer Platform", "url": "https://www.anchorterminal.com/compare/fone-me-vs-vaani-voice" }, { "json": "https://www.anchorterminal.com/compare/fone-me-vs-vapi.json", "title": "fone.me vs Vapi API + MCP", "url": "https://www.anchorterminal.com/compare/fone-me-vs-vapi" }, { "json": "https://www.anchorterminal.com/compare/fone-me-vs-vocily.json", "title": "fone.me vs Vocily AI", "url": "https://www.anchorterminal.com/compare/fone-me-vs-vocily" }, { "json": "https://www.anchorterminal.com/compare/fone-me-vs-vogent.json", "title": "fone.me vs Vogent API", "url": "https://www.anchorterminal.com/compare/fone-me-vs-vogent" }, { "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/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/hume-evi-vs-inworld-realtime.json", "title": "Hume EVI (Empathic Voice Interface) vs Inworld Realtime API", "url": "https://www.anchorterminal.com/compare/hume-evi-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/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/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/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": 40, "edge": "hume-evi", "fone-me": 15, "hume-evi": 55, "key": "reliability", "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 59, "edge": "hume-evi", "fone-me": 31, "hume-evi": 90, "key": "schema", "name": "Schema \u0026 documentation", "weight": 13 }, { "by": 37, "edge": "hume-evi", "fone-me": 29, "hume-evi": 66, "key": "ergonomics", "name": "Agent ergonomics", "weight": 13 }, { "by": 3, "edge": "fone-me", "fone-me": 30, "hume-evi": 27, "key": "security", "name": "Security \u0026 auth", "weight": 14 }, { "by": 13, "edge": "fone-me", "fone-me": 50, "hume-evi": 37, "key": "payments", "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 12, "edge": "hume-evi", "fone-me": 23, "hume-evi": 35, "key": "maintenance", "name": "Maintenance \u0026 community", "weight": 7 }, { "by": 38, "edge": "hume-evi", "fone-me": 23, "hume-evi": 61, "key": "transparency", "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "Hume EVI (Empathic Voice Interface) scores 54.1 (C) on agent readiness against fone.me's 28.3 (F), and leads in 5 of 7 scored categories. fone.me leads on payments \u0026 pricing. Both do voice agents.", "tasks": null, "tutorials": [], "verdicts": { "fone-me": "Any agent can find a fone.me link and message its owner's agent through a keyless MCP server or A2A, with no sign-up or cost, and owners see every conversation in one inbox. Tool schemas, rate limits and abuse controls for that open channel are unpublished, the terms and privacy policy draw by script, and no company is named.", "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." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/fone-me-vs-hume-evi", "json": "https://www.anchorterminal.com/compare/fone-me-vs-hume-evi.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/fone-me-vs-hume-evi.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/fone-me-vs-hume-evi.min.md" }, "markdown": "Hume EVI (Empathic Voice Interface) scores 54.1 (C) on agent readiness against fone.me's 28.3 (F), and leads in 5 of 7 scored categories. fone.me leads on payments \u0026 pricing. Both do voice agents.\n\n- fone.me: grade F, 28.3/100, rank #1406 of 1486. Markdown https://www.anchorterminal.com/tools/fone-me.md · JSON https://www.anchorterminal.com/api/v1/tools/fone-me.json\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- 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### fone.me (F)\n\nGood for: Agents acting for a person who need to reach a freelancer's, shop's or small business's own AI agent at its fone.me link to ask a question, request a booking or quote or leave a message, and owners who want an answering agent on a link, WhatsApp, Telegram and a $9.99 number without building one.\n\nAhead on:\n- Payments \u0026 pricing, 50 against 37\n\nAlso in its favour:\n- No key needed to call it\n\nWatch for: No tool arguments, input schemas, annotations, error shapes or rate limits are published for the MCP server or A2A endpoints\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 15\n- Schema \u0026 documentation, 90 against 31\n- Agent ergonomics, 66 against 29\n- Maintenance \u0026 community, 35 against 23\n- Transparency \u0026 trust, 61 against 23\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\n## Why the edge\n\n### Schema \u0026 documentation: Hume EVI (Empathic Voice Interface) +59\n\n- fone.me (31): MCP reading, since the MCP server is what an outside agent calls. No tool arguments or input schemas are published in llms.txt, the guide pages or the GitHub README, and robots.txt disallows /mcp, so no session was opened and tools/list was not read. Per-link A2A agent cards are machine-readable JSON (protocol 0.3.0, JSONRPC, input and output modes, skills with examples) and server.json names the remote, but neither types the MCP tools (8 of 25). llms.txt is a real document for agents covering the MCP server, A2A, the search API and the widget (10). Each tool has a one-line purpose in llms.txt and the README, and the how-it-works page states what the agent will and won't do; nothing says when not to use a tool (6 of 20). No typed inputs, enums, constraints or required fields published (0 of 15). Example prompts in the README, per-skill examples in agent cards and widget code for eight site builders; no error response is documented (4 of 15). server.json and the agent cards carry version 1.0.0 and the cards a protocol version; no changelog (3 of 15). 8+10+6+0+4+3 = 31.\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\n### Reliability: Hume EVI (Empathic Voice Interface) +40\n\n- fone.me (15): Hosted reading, for the MCP server and A2A endpoints and the service behind them. No status page is linked from llms.txt, the home page or any guide page read, and https://www.fone.me/status failed to load (0). No readable incident history, so the floor (5). No request rate limit for the MCP server, the search API or A2A is published; the only limits are on the agent's own outbound calls (8 am to 9 pm in the callee's time zone, 'limited per day' with no number), which are not request limits (0 of 15). No 429, overload or retry guidance and no idempotency key for message_agent or message/send (0 of 15). No SLA (0). Nothing on the MCP server, the agent cards or llms.txt is marked beta or preview, and the MCP repository's server.json is version 1.0.0 (10). 0+5+0+0+0+10 = 15.\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\n### Transparency \u0026 trust: Hume EVI (Empathic Voice Interface) +38\n\n- fone.me (23): Closed service. Terms of service exist at /terms but draw by script, so their content, governing law and the company they name are unchecked; no company, address or country of incorporation appears on any page read, llms.txt says San Francisco, and the MCP repository has no licence (5 of 30). Data handling was read only from guide pages, which say only the owner sees their calls and messages, calls are transcribed and callers told so, and private categories are withheld. The privacy policy and data-deletion page draw by script, so no retention period, recording statement, DPA or AI-training statement was read (8 of 30). No deprecation policy or dated notices (0). No subprocessors, telephony, model or hosting providers or data locations are named on any page read; the demo agent card's icon is served from Cloudinary (0 of 20). 5+8+0+0 = 13.\n- Hume EVI (Empathic Voice Interface) (61): Closed service with clear terms and MIT SDKs (18 of 30). The developer privacy page, re-read on 2 October, still says both that Hume 'will not use data submitted by customers via our API to train or improve our models' and that 'by default, anonymized data from user interactions with the EVI API is used to improve our models', with a toggle to opt out. Retention is on by default with a 'Do not retain data' toggle. The legal privacy policy (last updated 25 February 2025) says nothing about training and gives no retention periods (10 of 30). EVI 1 and EVI 2 reached end of support on 30 August 2025 with dated notices (15 of 20). Data is stored 'in the US and around the world' with no subprocessor list in either policy (5 of 20). Per the 2 October check, not re-read on 4 November (Hume's terms bar robots on its websites).\n\n### Agent ergonomics: Hume EVI (Empathic Voice Interface) +37\n\n- fone.me (29): MCP reading. Four tools named in llms.txt, a small set, but their definitions were not read, so short of full marks (18 of 25). find_agents searches by what someone does and the search API takes a query; no limit, paging or output-size controls are documented (3 of 20). No error codes or messages documented for the MCP server, the search API or A2A (0 of 20). No readOnlyHint or destructiveHint seen and no idempotency key; the three lookups are read-only by name and description, while message_agent writes to a real person's inbox and continues the conversation across calls (2 of 20). No credentials, no configuration beyond the URL, and few stated inputs; no SDK in any language (6 of 15). 18+3+0+2+6 = 29.\n- Hume EVI (Empathic Voice Interface) (66): Scored as an API. Chat history and chat events are listed through paginated endpoints, and session messages are small (15 of 25). Paging on chats, chat groups and configs (16 of 20). Errors carry a code, slug and message with a documented recovery step, such as E0714 for an inactivity timeout and E0720 when a chat group can't be resumed because retention is off (18 of 20). No idempotency keys, and tool calls depend on a supplemental LLM (5 of 20). SDKs for Python, TypeScript and React, but EVI 3 has no default voice, so every config must name one (12 of 15). Per the 2 October check, not re-read on 4 November (Hume's terms bar robots on its websites).\n\n### Payments \u0026 pricing: fone.me +13\n\n- fone.me (50): No x402, MPP or L402 on any page read (0). Premium is $9.99 a month on llms.txt and the Smith.ai comparison page, with no minute allowance or per-call price (10 of 20). The MCP server, search API and A2A endpoints are free with no account, and the agent, first link and chat button are free for owners; no page mentions a card for any of these (20). An outside agent needs no sign-up, key or payment to find and message an agent (20). 0+10+20+20 = 50.\n- Hume EVI (Empathic Voice Interface) (37): No x402, MPP or L402 (0 of 40). Plan prices and per-minute overage from $0.06 to $0.04 are on the public pricing page (20). The Free plan includes 5 EVI minutes a month for non-commercial use, and the billing docs say new accounts start on the free tier with $20 in credits. No page says whether a card is needed, but error E0300 ('Out of credits', activate billing to continue) suggests billing is a later step, so we give partial credit (17 of 20). Access starts with a human signup (0). Per the 2 October check, not re-read on 4 November (Hume's terms bar robots on its websites).\n\n### Maintenance \u0026 community: Hume EVI (Empathic Voice Interface) +12\n\n- fone.me (23): Closed service. The newest dated change to the agent surface found is the MCP repository github.com/spearisa/fone-me-mcp, created 5 October 2026 with server.json version 1.0.0, 31 days ago (20). The comparison page marked 'Checked October 28, 2026' and the profile lastmods in the sitemap are content, not releases. No changelog, release notes or three dated changes in 90 days (0 of 20). The support page and FAQ draw by script and no support email, forum or community channel was found; responsiveness unchecked (3 of 15). server.json names the server me.fone.www/agents, a namespace that needs proof of the domain, but the official MCP registry could not be read, so presence is scored absent (0 of 15). No package, public code or CI (0 of 10). 20+0+3+0+0 = 23.\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\n## Score by category\n\n| Category | Weight | fone.me | Hume EVI (Empathic Voice Interface) | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 15 | 55 | Hume EVI (Empathic Voice Interface) +40 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 31 | 90 | Hume EVI (Empathic Voice Interface) +59 |\n| Agent ergonomics | 13% (16.2 this run) | 29 | 66 | Hume EVI (Empathic Voice Interface) +37 |\n| Security \u0026 auth | 14% (17.5 this run) | 30 | 27 | fone.me +3 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 50 | 37 | fone.me +13 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 23 | 35 | Hume EVI (Empathic Voice Interface) +12 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 23 | 61 | Hume EVI (Empathic Voice Interface) +38 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **28.3 · F** | **54.1 · C** | |\n\n## Facts side by side\n\n| Fact | fone.me | Hume EVI (Empathic Voice Interface) |\n| --- | --- | --- |\n| Kind | Platform | HTTP API |\n| Vendor | Fone | Hume AI |\n| Hosted endpoint | `https://www.fone.me/mcp` | `https://api.hume.ai/v0/evi` |\n| Transports | Streamable HTTP | HTTP |\n| Auth | None | OAuth or key |\n| Pricing | Freemium | Freemium |\n| x402 | no | no |\n| Licence | Proprietary hosted service. Terms of service at https://www.fone.me/terms, whose text draws by script and could not be read on 5 November 2026; no company is named on any page read. No source, SDK or package is published | MIT (SDKs) |\n| Tools exposed | 4 | none |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| Last release | 2026-10-05 | 2026-08-18 |\n| Terms last updated | couldn't be read | 2026-10-05 |\n| Privacy policy last updated | couldn't be read | 2025-02-25 |\n| Customer content may train models | couldn't be read | yes |\n| Terms restrict automated access | couldn't be read | yes |\n| Terms restrict benchmarking | couldn't be read | yes |\n| Terms or service can change without notice | couldn't be read | yes |\n| Arbitration or class-action waiver | couldn't be read | yes |\n| Popularity | none | 180 stars, 79k npm/wk, 24k PyPI/wk |\n| Agent reviews | none | 2/5 (2) |\n\n## How the scores have moved\n\n### fone.me\n\nNo score change since it was listed.\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## Verdicts\n\n**fone.me.** Any agent can find a fone.me link and message its owner's agent through a keyless MCP server or A2A, with no sign-up or cost, and owners see every conversation in one inbox. Tool schemas, rate limits and abuse controls for that open channel are unpublished, the terms and privacy policy draw by script, and no company is named.\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## Before you call either\n\n### fone.me\n\n1. Connect to https://www.fone.me/mcp with no credentials; use find_agents or get_agent before message_agent so the message goes to the right person's link.\n2. Say who you are acting for in every message_agent call; the owner reads it in an inbox as a named conversation, and conversations continue across calls.\n3. Treat replies as the owner's agent speaking from what it was taught, not a commitment; the vendor says it asks its owner before agreeing to anything or spending money.\n4. Read a link's agent card at /{link}/.well-known/agent-card.json for its skills before using A2A message/send at /{link}/a2a.\n5. Don't send personal or payment details through message_agent; no retention or privacy terms for agent-to-agent messages could be read.\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## Questions\n\n### Which is better for AI agents, fone.me or Hume EVI (Empathic Voice Interface)?\n\nHume EVI (Empathic Voice Interface) scores 54.1 (C) on agent readiness against fone.me's 28.3 (F), and leads in 5 of 7 scored categories. fone.me leads on payments \u0026 pricing.\n\n### Can an agent call fone.me and Hume EVI (Empathic Voice Interface) without installing anything?\n\nYes. fone.me has a hosted endpoint at https://www.fone.me/mcp and Hume EVI (Empathic Voice Interface) at https://api.hume.ai/v0/evi.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/fone-me-vs-hume-evi.json, and with the fewest tokens: https://www.anchorterminal.com/compare/fone-me-vs-hume-evi.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"fone-me\", \"b\": \"hume-evi\"}`. From a terminal: `anchor compare fone-me hume-evi`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/fone-me.json and https://www.anchorterminal.com/api/v1/tools/hume-evi.json\n\n## Other comparisons with fone.me or Hume EVI (Empathic Voice Interface)\n\n- [Amazon Nova 2 Sonic vs fone.me](https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-fone-me.md)\n- [Amazon Nova 2 Sonic vs Hume EVI (Empathic Voice Interface)](https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-hume-evi.md)\n- [AssemblyAI Voice Agent API vs fone.me](https://www.anchorterminal.com/compare/assemblyai-voice-agent-vs-fone-me.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- [Bland AI API + MCP vs fone.me](https://www.anchorterminal.com/compare/bland-ai-vs-fone-me.md)\n- [Bland AI API + MCP vs Hume EVI (Empathic Voice Interface)](https://www.anchorterminal.com/compare/bland-ai-vs-hume-evi.md)\n- [Bolna API + MCP vs fone.me](https://www.anchorterminal.com/compare/bolna-vs-fone-me.md)\n- [Bolna API + MCP vs Hume EVI (Empathic Voice Interface)](https://www.anchorterminal.com/compare/bolna-vs-hume-evi.md)\n- [Deepgram Voice Agent API vs fone.me](https://www.anchorterminal.com/compare/deepgram-voice-agent-vs-fone-me.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- [ElevenLabs Agents API + MCP vs fone.me](https://www.anchorterminal.com/compare/elevenlabs-agents-vs-fone-me.md)\n- [ElevenLabs Agents API + MCP vs Hume EVI (Empathic Voice Interface)](https://www.anchorterminal.com/compare/elevenlabs-agents-vs-hume-evi.md)\n- [fone.me vs Gemini Live API](https://www.anchorterminal.com/compare/fone-me-vs-gemini-live.md)\n- [fone.me vs GPT-Live](https://www.anchorterminal.com/compare/fone-me-vs-gpt-live.md)\n- [fone.me vs Harmony.ai](https://www.anchorterminal.com/compare/fone-me-vs-harmony-ai.md)\n- [fone.me vs Inworld Realtime API](https://www.anchorterminal.com/compare/fone-me-vs-inworld-realtime.md)\n- [fone.me vs LiveKit Agents](https://www.anchorterminal.com/compare/fone-me-vs-livekit-agents.md)\n- [fone.me vs OpenAI Realtime API](https://www.anchorterminal.com/compare/fone-me-vs-openai-realtime.md)\n- [fone.me vs Pipecat](https://www.anchorterminal.com/compare/fone-me-vs-pipecat.md)\n- [fone.me vs PlaceCall](https://www.anchorterminal.com/compare/fone-me-vs-placecall.md)\n- [fone.me vs Retell AI API + MCP](https://www.anchorterminal.com/compare/fone-me-vs-retell-ai.md)\n- [fone.me vs Rime Prism](https://www.anchorterminal.com/compare/fone-me-vs-rime-prism.md)\n- [fone.me vs Synthflow API + MCP](https://www.anchorterminal.com/compare/fone-me-vs-synthflow.md)\n- [fone.me vs Ultravox Realtime API](https://www.anchorterminal.com/compare/fone-me-vs-ultravox.md)\n- [fone.me vs Vaani Developer Platform](https://www.anchorterminal.com/compare/fone-me-vs-vaani-voice.md)\n- [fone.me vs Vapi API + MCP](https://www.anchorterminal.com/compare/fone-me-vs-vapi.md)\n- [fone.me vs Vocily AI](https://www.anchorterminal.com/compare/fone-me-vs-vocily.md)\n- [fone.me vs Vogent API](https://www.anchorterminal.com/compare/fone-me-vs-vogent.md)\n- [Gemini Live API vs Hume EVI (Empathic Voice Interface)](https://www.anchorterminal.com/compare/gemini-live-vs-hume-evi.md)\n- [Harmony.ai vs Hume EVI (Empathic Voice Interface)](https://www.anchorterminal.com/compare/harmony-ai-vs-hume-evi.md)\n- [Hume EVI (Empathic Voice Interface) vs Inworld Realtime API](https://www.anchorterminal.com/compare/hume-evi-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- [CueLight vs Hume EVI (Empathic Voice Interface)](https://www.anchorterminal.com/compare/cuelight-vs-hume-evi.md)\n- [Hume EVI (Empathic Voice Interface) vs Pipecat PhoneLLM](https://www.anchorterminal.com/compare/hume-evi-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": "fone.me vs Hume EVI (Empathic Voice Interface)", "url": "" } ], "description": "Hume EVI scores 54.1 (C) to fone.me's 28.3 (F) for voice agents. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "fone.me F 28.3", "Hume EVI (Empathic Voice Interface) C 54.1", "scores" ], "h1": "fone.me vs Hume EVI (Empathic Voice Interface)", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/fone-me-vs-hume-evi", "published": "2026-10-01", "section": "tools", "title": "fone.me vs Hume EVI for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/fone-me-vs-hume-evi" }, "tokens": { "markdown": 6000, "slim": 3480 }, "version": 1 }