{ "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": 1429, "ranked": true, "rankOf": 1510, "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-07T19:22:07.71997153Z", "lastOk": true, "lastStatus": 405, "lastMs": 357, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 215, "p95ms24h": 511, "samples24h": 210, "samples30d": 210, "days": [ { "date": "2026-11-06", "probes": 13, "ok": 13 }, { "date": "2026-11-07", "probes": 197, "ok": 197 } ] }, "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-07T19:22:07.71997153Z" } }, "answer": "Harmony.ai scores 43.4 (E) on agent readiness against fone.me's 28.3 (F), and leads in 6 of 7 scored categories. fone.me leads on payments \u0026 pricing.", "b": { "slug": "harmony-ai", "name": "Harmony.ai", "vendor": "monday.com Ltd. (Harmony.ai)", "vendorUrl": "https://harmony.ai", "kind": "http-api", "category": "voice-agents", "summary": "Harmony.ai is monday.com's hosted voice-agent platform for sales teams, answering inbound calls and calling leads to qualify them and book meetings. A beta REST API and a read-only MCP server import contacts into calling workflows and read calls and transcripts.", "url": "https://www.anchorterminal.com/tools/harmony-ai", "markdownUrl": "https://www.anchorterminal.com/tools/harmony-ai.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/harmony-ai.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/harmony-ai.json", "dns": "harmony-ai.grade.anchorterminal.com", "license": "Proprietary service. The Terms of Service on harmony.ai are One AI Inc.'s, while the Data Processing Addendum names monday.com Ltd. and incorporates monday.com's Terms of Service. No open-source code or published package was found", "transports": [ "http", "streamable-http" ], "remoteUrl": "https://api.harmony.ai", "packages": [], "auth": "api-key", "authNotes": "A Bearer API key (`harmony_pk_...`) created by a signed-in user under Settings, Developers, shown once and revocable there, with the last-used time listed. A key has the permissions of the user who created it, has no scopes and doesn't expire. Keys work only in their region (api.harmony.ai for the US, api.eu.harmony.ai for the EU). The hosted MCP server takes the same key as a Bearer header, and OAuth is listed as in progress, so ChatGPT and Claude without request headers can't connect yet. Access starts with a browser signup at app.harmony.ai.", "pricing": "paid", "pricingNotes": "Pro is $0.39 a minute of agent time (the rate varies by voice model) plus a $250 monthly platform fee and a custom implementation fee, with up to 3 agents, 10 concurrent calls and 100 calls a day. Enterprise is custom. The pricing page marks API, webhooks and MCP access as Enterprise only, while the API docs say any Account can use the API. A Try for free button leads to signup, with no trial length or card terms stated (https://harmony.ai/pricing).", "priceSummary": "$250 / mo", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the API docs, the OpenAPI file, the MCP docs or the pricing page (checked 2026-10-19).", "endpoints": [] }, "toolCount": 6, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-19" }, "docsUrl": "https://docs.harmony.ai", "llmsTxt": "https://docs.harmony.ai/llms.txt", "openapi": "https://docs.harmony.ai/openapi.json", "capabilities": [ "voice.agent", "voice.telephony", "voice.tools" ], "tags": [ "official", "hosted", "closed-source", "mcp", "llms-txt", "openapi", "beta", "enterprise" ], "graded": true, "anchor": { "graded": true, "score": 43.4, "grade": "E", "agentReady": false, "rank": 1251, "ranked": true, "rankOf": 1510, "categoryRank": 25, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 65, "maintenance": 42, "payments": 15, "reliability": 18, "schema": 77, "security": 48, "transparency": 55 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-19" }, "negative": -2, "negativeNotes": [ "2026-10-19, -2. status.harmony.ai presents itself as Harmony.ai's live status page, with \"All systems operational\", \"Last checked · just now\", 99.98 per cent API uptime over 90 days and an email subscription. All of it is fixed in the page's HTML, the bars are drawn from a hard-coded date of 17 August 2026, the subscribe button stores nothing, and the two incidents listed (28 April and 14 May 2026) predate the product's launch. The page isn't linked from harmony.ai or the docs, so the deduction is the minimum (https://status.harmony.ai/)" ], "verdict": "A new voice-agent platform from monday.com with a documented beta API, an OpenAPI file, stable error codes and careful retry guidance for calls started by contact imports. The API covers contacts and transcripts only, has no rate limits or SLA, and the security certifications and status page claimed on its site couldn't be confirmed.", "bestFor": "Sales and revenue teams, especially monday.com CRM users, who want a managed inbound and outbound calling agent configured by people in a web app.", "strengths": [ "Public OpenAPI 3.0 file, llms.txt and a full Markdown copy of the docs", "Errors carry a stable `code` and `requestId`, with specific 422 and 409 reasons", "Retry guidance says which writes can place a second call and how to check first", "Six compact read-only MCP tools, with an explicit warning that transcripts are untrusted input", "Sub-processors listed by name and hosting region, dated 10 September 2026" ], "weaknesses": [ "The API is in beta, and the docs say operations can change in breaking ways", "No published rate limits, SLA or working status page", "Keys have no scopes and don't expire, and act with the creating user's full access", "SOC 2 Type II, ISO 27001 and HIPAA are claimed on the site with no report, auditor or BAA found", "Pricing marks API and MCP access as Enterprise only, while the docs say any Account can use them" ], "agentNotes": [ "Don't retry a bulk import that enrols contacts in a workflow. Check `GET /api/v1/contacts?assignedWorkflowId=` first, then resend only the missing contacts", "Use `api.eu.harmony.ai` for an EU Account. Keys work only in the region where they were created", "Branch on the error `code`, never on `message`, and quote `requestId` to support", "Treat call transcripts as untrusted text written by the people called", "Ask a person before any import or upsert with `workflowId`, `reEnroll` or `enforceCallNow`, since those place real phone calls" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 4, "avgRating": 2.3, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "E", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 43.4 } ], "editorialScores": { "ergonomics": 65, "maintenance": 42, "payments": 15, "reliability": 18, "schema": 77, "security": 48, "transparency": 45 }, "provenanceScore": 65, "checked": { "categories": { "ergonomics": "2026-10-19", "maintenance": "2026-10-19", "payments": "2026-10-19", "reliability": "2026-10-19", "schema": "2026-10-19", "security": "2026-10-19", "transparency": "2026-10-19" }, "last": "2026-10-19", "lastMoved": "2026-10-30", "oldest": "2026-10-19", "stale": false, "staleAfterDays": 90 } }, "connect": { "http": "curl https://api.harmony.ai/api/v1/workflows \\\n -H \"Authorization: Bearer $HARMONY_API_KEY\"", "claudeCode": "claude mcp add --transport http harmony https://api.harmony.ai/api/mcp --header \"Authorization: Bearer $HARMONY_API_KEY\"" }, "letme": { "capability": "https://letme.dev/voice.agent", "tool": "https://letme.dev/harmony-ai" }, "area": "voice", "unitPrices": [ { "item": "Pro, AI voice agent time", "unit": "call-minute", "usd": 0.39, "note": "rate varies by voice model. Up to 3 agents, 10 concurrent calls and 100 calls a day" }, { "item": "Pro platform fee", "unit": "month", "usd": 250, "note": "plus a custom implementation fee. Enterprise prices are custom" } ], "provenance": { "legalEntity": "monday.com Ltd.", "domain": "harmony.ai", "domainRegistered": "2017-12-15", "domainNote": "RDAP for harmony.ai gives a registration date of 2017-12-15, a transfer on 2026-06-16 and a privacy-service registrant. oneai.com redirects to harmony.ai.", "endpointOnVendorDomain": true, "terms": "https://harmony.ai/terms", "privacy": "https://harmony.ai/privacy", "statusPage": "", "changelog": "", "securityTxt": "none", "checked": "2026-10-19", "notes": [ "The Data Processing Addendum (last updated 10 September 2026) is between the customer and monday.com Ltd., is incorporated into monday.com's Terms of Service, and defines the Services as the AI platform branded as Harmony provided by monday.com.", "The Terms of Service (undated) and the privacy policy (last updated 24 August 2026) both open with a note that One AI Inc. was acquired by Harmony.ai (monday.com) on 11 May 2026, and still name One AI Inc. as provider and controller, at 1390 Market St. Suite 200, San Francisco. monday.com's 6-K describes an asset purchase from One AI Ltd. and OneAI Inc.", "Every page footer reads \"© Harmony. A monday.com company.\"", "status.harmony.ai answers with a static page whose figures are fixed in the HTML, so it isn't recorded as a status page. No changelog was found.", "harmony.ai/.well-known/security.txt returns 404. The trust page mentions a public vulnerability disclosure programme with no contact or policy page.", "The API (api.harmony.ai, api.eu.harmony.ai), the MCP server and the docs (docs.harmony.ai) are all on harmony.ai." ], "score": 65 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/harmony-ai.json", "live": { "slug": "harmony-ai", "probe": { "target": "https://api.harmony.ai", "method": "get", "lastAt": "2026-11-07T19:22:10.737840617Z", "lastOk": true, "lastStatus": 200, "lastMs": 522, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 359, "p95ms24h": 468, "samples24h": 238, "samples30d": 4716, "days": [ { "date": "2026-10-19", "probes": 93, "ok": 93 }, { "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": 251 }, { "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": 197, "ok": 197 } ] }, "securityTxt": { "url": "https://harmony.ai/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-07T16:01:26.127476473Z" }, "llmsTxt": { "url": "https://docs.harmony.ai/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:32:40.378262959Z" }, "domain": { "domain": "harmony.ai", "registered": "2017-12-15", "source": "https://rdap.identitydigital.services/rdap/domain/harmony.ai", "checkedAt": "2026-11-01T14:20:07.94158803Z" }, "pages": [ { "url": "https://harmony.ai/pricing", "kind": "pricing", "status": 200, "checkedAt": "2026-11-07T14:10:48.010179693Z", "changedAt": "2026-11-03T07:51:05.56975783Z", "fingerprint": "f62d643ad00f" }, { "url": "https://harmony.ai/privacy", "kind": "privacy", "status": 200, "checkedAt": "2026-11-07T14:10:50.732899954Z", "changedAt": "2026-10-26T03:17:34.825130584Z", "fingerprint": "2549291512c0" }, { "url": "https://harmony.ai/terms", "kind": "terms", "status": 200, "checkedAt": "2026-11-07T14:10:52.32719922Z", "changedAt": "2026-10-26T03:17:36.790922651Z", "fingerprint": "18dd7579f68c" } ], "mcpTools": { "url": "https://api.harmony.ai/api/mcp", "checkedAt": "2026-11-07T01:45:19.147133087Z", "status": "auth", "note": "asks for credentials before listing its tools", "changedAt": "2026-11-07T01:45:19.147133087Z" }, "updatedAt": "2026-11-07T19:22:10.737840617Z" } }, "edges": [ { "by": 46, "category": "schema", "leads": "harmony-ai", "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": "A public OpenAPI 3.0.3 file covering all 11 operations at docs.harmony.ai/openapi.json (25). llms.txt, llms-full.txt and Markdown pages (10). Each operation has a short description, and the guides say who the API is for, that multi-customer integrations aren't supported, and what each write does to calling (12 of 20). 45 enums, a page size bounded at 1 to 100, required fields and a 1,000-contact cap on imports (12 of 15). The docs have curl and TypeScript examples and a documented error body with named codes, while the OpenAPI file has no examples (11 of 15). The major version is in the path and a versioning policy is published, with no changelog (7 of 15)." }, "scores": { "a": 31, "b": 77 } }, { "by": 36, "category": "ergonomics", "leads": "harmony-ai", "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": "Lists take `limit` up to 100 and a CSV form, with no field selection or summaries (15 of 25). Cursor pagination with `nextToken`, and contact search filters by status, source, workflow, date added and a search term (18 of 20). Every error has a stable `code`, a `requestId` and an `x-request-id` header, with specific 422 reasons and a 409 that lists the matching contacts (17 of 20). No idempotency keys. Upserts deduplicate by the Account's fields and the docs spell out when a retry calls a contact twice. The six MCP tools are read-only, though no annotations were seen since the tool list wasn't fetched from the server (10 of 20). Few required fields, no SDK in any language (5 of 15)." }, "scores": { "a": 29, "b": 65 } }, { "by": 35, "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). Pro is $0.39 a minute plus a $250 monthly platform fee, published without a login, with the minute rate varying by voice model and a custom implementation fee (15 of 20). A Try for free signup is linked, with no trial terms on public pages and the signup not tried, so no free tier is counted (0). A person signs up in a browser and creates keys in the web app (0)." }, "scores": { "a": 50, "b": 15 } }, { "by": 32, "category": "transparency", "leads": "harmony-ai", "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 conflicting terms. The Terms of Service are One AI Inc.'s, undated, referring to oneai.com sites and pricing, while the DPA of 10 September 2026 names monday.com Ltd. and incorporates monday.com's Terms of Service (7 of 30). Data handling statements disagree. The privacy policy (24 August 2026) keeps data while the account is active and says data may be used to train One AI's systems. The trust page says retention is configurable with no cross-customer training. The terms say all calls are recorded unless the customer opts out in writing, and the trust page lists US, EU and APAC regions while the sub-processor page lists US and EU. The DPA commits to deletion or return at termination (10 of 30). The versioning page keeps an old major version for at least 12 months after a new one, once the API is generally available (10 of 20). Nine sub-processors named with hosting regions, with a seven-day objection window in the DPA (18 of 20)." }, "scores": { "a": 23, "b": 55 } }, { "by": 19, "category": "maintenance", "leads": "harmony-ai", "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 for a closed service. The press page dates the launch to October 2026, within 30 days (30). No changelog or dated releases (0). Support is through a contact form and the docs' request ID guidance, with no public changelog or community channel found (4 of 15). A hosted MCP server, not in the official registry, and no SDK (5 of 15). No package to assess (3 of 10)." }, "scores": { "a": 23, "b": 42 } }, { "by": 18, "category": "security", "leads": "harmony-ai", "name": "Security \u0026 auth", "reasons": { "a": "No credential exists for callers. llms.txt gives auth 'none', the README says the server is 'public, like the links themselves', and the two agent cards read declare no security scheme. There is nothing to leak or rotate, but fone.me and an owner can tell callers apart only by the name they give ('Maria via ChatGPT' in the README) and by traffic, and no caller identity or verification is documented (10 of 30). Three of four MCP tools are lookups; message_agent and A2A message/send reach any owner's agent. On the owner's side the vendor says the agent asks before agreeing to anything or spending money, the owner approves what it will say before a call, outbound calls run only 8 am to 9 pm local, pause when reported and stop permanently on request, and the owner can take over any chat. No read-only mode and no confirmation on the caller's side (8 of 20). message_agent returns text generated from what the owner taught the agent, and every agent on the platform reads messages from anyone; the only guidance is the how-it-works statement that the agent keeps relationship status, health, money and address private, with no documented prompt-injection or spam handling for the open channel, and the call-screening page says it does not promise to block calls (4 of 15). Owners see every call and chat with a transcript in one inbox; nothing is logged for the calling agent (8 of 15). /.well-known/security.txt answers with the app shell, and no disclosure policy, bug bounty or certification appears on any page read (0 of 20). 10+8+4+8+0 = 30.", "b": "Revocable Bearer keys, shown once, with a last-used time, but no scopes, no expiry and the full access of the user who made them. Keys never travel in a URL (20 of 30). The MCP server is read-only, but a REST key can import contacts into workflows that place real calls, with no read-only key (8 of 20). The MCP docs say tool results carry text from contacts and teammates and tell the user to treat it as untrusted input (10 of 15). Request IDs on every response and key last-used times. No audit log of account actions documented (6 of 15). harmony.ai/.well-known/security.txt returns 404. The trust page claims SOC 2 Type II, ISO 27001, an annual pen test and a public disclosure programme with bounties, but names no auditor, report, certificate or contact, and shares reports only under NDA (4 of 20)." }, "scores": { "a": 30, "b": 48 } } ], "facts": [ { "a": "Platform", "b": "HTTP API", "name": "Kind" }, { "a": "Fone", "b": "monday.com Ltd. (Harmony.ai)", "name": "Vendor" }, { "a": "https://www.fone.me/mcp", "b": "https://api.harmony.ai", "name": "Hosted endpoint" }, { "a": "Streamable HTTP", "b": "HTTP, Streamable HTTP", "name": "Transports" }, { "a": "None", "b": "API key", "name": "Auth" }, { "a": "Freemium", "b": "Paid", "name": "Pricing" }, { "a": "not published", "b": "$0.39 per minute of call", "name": "Price for voice agents" }, { "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": "Proprietary service. The Terms of Service on harmony.ai are One AI Inc.'s, while the Data Processing Addendum names monday.com Ltd. and incorporates monday.com's Terms of Service. No open-source code or published package was found", "name": "Licence" }, { "a": "4", "b": "6", "name": "Tools exposed" }, { "a": "no", "b": "yes", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "2026-10-05", "b": "none", "name": "Last release" }, { "a": "couldn't be read", "b": "no date given", "name": "Terms last updated" }, { "a": "couldn't be read", "b": "2026-08-24", "name": "Privacy policy last updated" }, { "a": "couldn't be read", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "couldn't be read", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "couldn't be read", "b": "not found in the text", "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": "2.3/5 (4)", "name": "Agent reviews" } ], "faq": [ { "answer": "Harmony.ai scores 43.4 (E) on agent readiness against fone.me's 28.3 (F), and leads in 6 of 7 scored categories. fone.me leads on payments \u0026 pricing.", "question": "Which is better for AI agents, fone.me or Harmony.ai?" }, { "answer": "Yes. fone.me has a hosted endpoint at https://www.fone.me/mcp and Harmony.ai at https://api.harmony.ai.", "question": "Can an agent call fone.me and Harmony.ai without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Payments \u0026 pricing, 50 against 15" ], "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": [ "Schema \u0026 documentation, 77 against 31", "Agent ergonomics, 65 against 29", "Security \u0026 auth, 48 against 30", "Maintenance \u0026 community, 42 against 23", "Transparency \u0026 trust, 55 against 23" ], "also": null, "goodFor": "Sales and revenue teams, especially monday.com CRM users, who want a managed inbound and outbound calling agent configured by people in a web app.", "slug": "harmony-ai", "watchFor": "The API is in beta, and the docs say operations can change in breaking ways" } ], "history": { "fone-me": null, "harmony-ai": [ { "causes": [ "method" ], "date": "2026-10-30", "delta": -0.2, "from": 43.6, "fromGrade": "E", "to": 43.4, "toGrade": "E" }, { "causes": [ "method" ], "date": "2026-10-27", "delta": 0.1, "from": 43.5, "fromGrade": "E", "to": 43.6, "toGrade": "E" } ] }, "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-harmony-ai.json", "title": "Amazon Nova 2 Sonic vs Harmony.ai", "url": "https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-harmony-ai" }, { "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-harmony-ai.json", "title": "AssemblyAI Voice Agent API vs Harmony.ai", "url": "https://www.anchorterminal.com/compare/assemblyai-voice-agent-vs-harmony-ai" }, { "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-harmony-ai.json", "title": "Bland AI API + MCP vs Harmony.ai", "url": "https://www.anchorterminal.com/compare/bland-ai-vs-harmony-ai" }, { "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-harmony-ai.json", "title": "Bolna API + MCP vs Harmony.ai", "url": "https://www.anchorterminal.com/compare/bolna-vs-harmony-ai" }, { "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-harmony-ai.json", "title": "Deepgram Voice Agent API vs Harmony.ai", "url": "https://www.anchorterminal.com/compare/deepgram-voice-agent-vs-harmony-ai" }, { "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-harmony-ai.json", "title": "ElevenLabs Agents API + MCP vs Harmony.ai", "url": "https://www.anchorterminal.com/compare/elevenlabs-agents-vs-harmony-ai" }, { "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-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/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-harmony-ai.json", "title": "Gemini Live API vs Harmony.ai", "url": "https://www.anchorterminal.com/compare/gemini-live-vs-harmony-ai" }, { "json": "https://www.anchorterminal.com/compare/gpt-live-vs-harmony-ai.json", "title": "GPT-Live vs Harmony.ai", "url": "https://www.anchorterminal.com/compare/gpt-live-vs-harmony-ai" }, { "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/harmony-ai-vs-livekit-agents.json", "title": "Harmony.ai vs LiveKit Agents", "url": "https://www.anchorterminal.com/compare/harmony-ai-vs-livekit-agents" }, { "json": "https://www.anchorterminal.com/compare/harmony-ai-vs-openai-realtime.json", "title": "Harmony.ai vs OpenAI Realtime API", "url": "https://www.anchorterminal.com/compare/harmony-ai-vs-openai-realtime" }, { "json": "https://www.anchorterminal.com/compare/harmony-ai-vs-pipecat.json", "title": "Harmony.ai vs Pipecat", "url": "https://www.anchorterminal.com/compare/harmony-ai-vs-pipecat" }, { "json": "https://www.anchorterminal.com/compare/harmony-ai-vs-placecall.json", "title": "Harmony.ai vs PlaceCall", "url": "https://www.anchorterminal.com/compare/harmony-ai-vs-placecall" }, { "json": "https://www.anchorterminal.com/compare/harmony-ai-vs-retell-ai.json", "title": "Harmony.ai vs Retell AI API + MCP", "url": "https://www.anchorterminal.com/compare/harmony-ai-vs-retell-ai" }, { "json": "https://www.anchorterminal.com/compare/harmony-ai-vs-rime-prism.json", "title": "Harmony.ai vs Rime Prism", "url": "https://www.anchorterminal.com/compare/harmony-ai-vs-rime-prism" }, { "json": "https://www.anchorterminal.com/compare/harmony-ai-vs-synthflow.json", "title": "Harmony.ai vs Synthflow API + MCP", "url": "https://www.anchorterminal.com/compare/harmony-ai-vs-synthflow" }, { "json": "https://www.anchorterminal.com/compare/harmony-ai-vs-ultravox.json", "title": "Harmony.ai vs Ultravox Realtime API", "url": "https://www.anchorterminal.com/compare/harmony-ai-vs-ultravox" }, { "json": "https://www.anchorterminal.com/compare/harmony-ai-vs-vaani-voice.json", "title": "Harmony.ai vs Vaani Developer Platform", "url": "https://www.anchorterminal.com/compare/harmony-ai-vs-vaani-voice" }, { "json": "https://www.anchorterminal.com/compare/harmony-ai-vs-vapi.json", "title": "Harmony.ai vs Vapi API + MCP", "url": "https://www.anchorterminal.com/compare/harmony-ai-vs-vapi" }, { "json": "https://www.anchorterminal.com/compare/harmony-ai-vs-vocily.json", "title": "Harmony.ai vs Vocily AI", "url": "https://www.anchorterminal.com/compare/harmony-ai-vs-vocily" }, { "json": "https://www.anchorterminal.com/compare/harmony-ai-vs-vogent.json", "title": "Harmony.ai vs Vogent API", "url": "https://www.anchorterminal.com/compare/harmony-ai-vs-vogent" }, { "json": "https://www.anchorterminal.com/compare/harmony-ai-vs-pipecat-phonellm.json", "title": "Harmony.ai vs Pipecat PhoneLLM", "url": "https://www.anchorterminal.com/compare/harmony-ai-vs-pipecat-phonellm" } ], "panel": null, "scores": [ { "by": 3, "edge": "harmony-ai", "fone-me": 15, "harmony-ai": 18, "key": "reliability", "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 46, "edge": "harmony-ai", "fone-me": 31, "harmony-ai": 77, "key": "schema", "name": "Schema \u0026 documentation", "weight": 13 }, { "by": 36, "edge": "harmony-ai", "fone-me": 29, "harmony-ai": 65, "key": "ergonomics", "name": "Agent ergonomics", "weight": 13 }, { "by": 18, "edge": "harmony-ai", "fone-me": 30, "harmony-ai": 48, "key": "security", "name": "Security \u0026 auth", "weight": 14 }, { "by": 35, "edge": "fone-me", "fone-me": 50, "harmony-ai": 15, "key": "payments", "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 19, "edge": "harmony-ai", "fone-me": 23, "harmony-ai": 42, "key": "maintenance", "name": "Maintenance \u0026 community", "weight": 7 }, { "by": 32, "edge": "harmony-ai", "fone-me": 23, "harmony-ai": 55, "key": "transparency", "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "Harmony.ai scores 43.4 (E) on agent readiness against fone.me's 28.3 (F), and leads in 6 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.", "harmony-ai": "A new voice-agent platform from monday.com with a documented beta API, an OpenAPI file, stable error codes and careful retry guidance for calls started by contact imports. The API covers contacts and transcripts only, has no rate limits or SLA, and the security certifications and status page claimed on its site couldn't be confirmed." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/fone-me-vs-harmony-ai", "json": "https://www.anchorterminal.com/compare/fone-me-vs-harmony-ai.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/fone-me-vs-harmony-ai.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/fone-me-vs-harmony-ai.min.md" }, "markdown": "Harmony.ai scores 43.4 (E) on agent readiness against fone.me's 28.3 (F), and leads in 6 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 #1429 of 1510. Markdown https://www.anchorterminal.com/tools/fone-me.md · JSON https://www.anchorterminal.com/api/v1/tools/fone-me.json\n- Harmony.ai: grade E, 43.4/100, rank #1251 of 1510. Markdown https://www.anchorterminal.com/tools/harmony-ai.md · JSON https://www.anchorterminal.com/api/v1/tools/harmony-ai.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 15\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### Harmony.ai (E)\n\nGood for: Sales and revenue teams, especially monday.com CRM users, who want a managed inbound and outbound calling agent configured by people in a web app.\n\nAhead on:\n- Schema \u0026 documentation, 77 against 31\n- Agent ergonomics, 65 against 29\n- Security \u0026 auth, 48 against 30\n- Maintenance \u0026 community, 42 against 23\n- Transparency \u0026 trust, 55 against 23\n\nWatch for: The API is in beta, and the docs say operations can change in breaking ways\n\n\n## Why the edge\n\n### Schema \u0026 documentation: Harmony.ai +46\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- Harmony.ai (77): A public OpenAPI 3.0.3 file covering all 11 operations at docs.harmony.ai/openapi.json (25). llms.txt, llms-full.txt and Markdown pages (10). Each operation has a short description, and the guides say who the API is for, that multi-customer integrations aren't supported, and what each write does to calling (12 of 20). 45 enums, a page size bounded at 1 to 100, required fields and a 1,000-contact cap on imports (12 of 15). The docs have curl and TypeScript examples and a documented error body with named codes, while the OpenAPI file has no examples (11 of 15). The major version is in the path and a versioning policy is published, with no changelog (7 of 15).\n\n### Agent ergonomics: Harmony.ai +36\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- Harmony.ai (65): Lists take `limit` up to 100 and a CSV form, with no field selection or summaries (15 of 25). Cursor pagination with `nextToken`, and contact search filters by status, source, workflow, date added and a search term (18 of 20). Every error has a stable `code`, a `requestId` and an `x-request-id` header, with specific 422 reasons and a 409 that lists the matching contacts (17 of 20). No idempotency keys. Upserts deduplicate by the Account's fields and the docs spell out when a retry calls a contact twice. The six MCP tools are read-only, though no annotations were seen since the tool list wasn't fetched from the server (10 of 20). Few required fields, no SDK in any language (5 of 15).\n\n### Payments \u0026 pricing: fone.me +35\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- Harmony.ai (15): No x402, MPP or L402 (0 of 40). Pro is $0.39 a minute plus a $250 monthly platform fee, published without a login, with the minute rate varying by voice model and a custom implementation fee (15 of 20). A Try for free signup is linked, with no trial terms on public pages and the signup not tried, so no free tier is counted (0). A person signs up in a browser and creates keys in the web app (0).\n\n### Transparency \u0026 trust: Harmony.ai +32\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- Harmony.ai (55): Closed service with conflicting terms. The Terms of Service are One AI Inc.'s, undated, referring to oneai.com sites and pricing, while the DPA of 10 September 2026 names monday.com Ltd. and incorporates monday.com's Terms of Service (7 of 30). Data handling statements disagree. The privacy policy (24 August 2026) keeps data while the account is active and says data may be used to train One AI's systems. The trust page says retention is configurable with no cross-customer training. The terms say all calls are recorded unless the customer opts out in writing, and the trust page lists US, EU and APAC regions while the sub-processor page lists US and EU. The DPA commits to deletion or return at termination (10 of 30). The versioning page keeps an old major version for at least 12 months after a new one, once the API is generally available (10 of 20). Nine sub-processors named with hosting regions, with a seven-day objection window in the DPA (18 of 20).\n\n### Maintenance \u0026 community: Harmony.ai +19\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- Harmony.ai (42): Read for a closed service. The press page dates the launch to October 2026, within 30 days (30). No changelog or dated releases (0). Support is through a contact form and the docs' request ID guidance, with no public changelog or community channel found (4 of 15). A hosted MCP server, not in the official registry, and no SDK (5 of 15). No package to assess (3 of 10).\n\n### Security \u0026 auth: Harmony.ai +18\n\n- fone.me (30): No credential exists for callers. llms.txt gives auth 'none', the README says the server is 'public, like the links themselves', and the two agent cards read declare no security scheme. There is nothing to leak or rotate, but fone.me and an owner can tell callers apart only by the name they give ('Maria via ChatGPT' in the README) and by traffic, and no caller identity or verification is documented (10 of 30). Three of four MCP tools are lookups; message_agent and A2A message/send reach any owner's agent. On the owner's side the vendor says the agent asks before agreeing to anything or spending money, the owner approves what it will say before a call, outbound calls run only 8 am to 9 pm local, pause when reported and stop permanently on request, and the owner can take over any chat. No read-only mode and no confirmation on the caller's side (8 of 20). message_agent returns text generated from what the owner taught the agent, and every agent on the platform reads messages from anyone; the only guidance is the how-it-works statement that the agent keeps relationship status, health, money and address private, with no documented prompt-injection or spam handling for the open channel, and the call-screening page says it does not promise to block calls (4 of 15). Owners see every call and chat with a transcript in one inbox; nothing is logged for the calling agent (8 of 15). /.well-known/security.txt answers with the app shell, and no disclosure policy, bug bounty or certification appears on any page read (0 of 20). 10+8+4+8+0 = 30.\n- Harmony.ai (48): Revocable Bearer keys, shown once, with a last-used time, but no scopes, no expiry and the full access of the user who made them. Keys never travel in a URL (20 of 30). The MCP server is read-only, but a REST key can import contacts into workflows that place real calls, with no read-only key (8 of 20). The MCP docs say tool results carry text from contacts and teammates and tell the user to treat it as untrusted input (10 of 15). Request IDs on every response and key last-used times. No audit log of account actions documented (6 of 15). harmony.ai/.well-known/security.txt returns 404. The trust page claims SOC 2 Type II, ISO 27001, an annual pen test and a public disclosure programme with bounties, but names no auditor, report, certificate or contact, and shares reports only under NDA (4 of 20).\n\n## Score by category\n\n| Category | Weight | fone.me | Harmony.ai | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 15 | 18 | Harmony.ai +3 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 31 | 77 | Harmony.ai +46 |\n| Agent ergonomics | 13% (16.2 this run) | 29 | 65 | Harmony.ai +36 |\n| Security \u0026 auth | 14% (17.5 this run) | 30 | 48 | Harmony.ai +18 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 50 | 15 | fone.me +35 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 23 | 42 | Harmony.ai +19 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 23 | 55 | Harmony.ai +32 |\n| Negative events | ≤15 | 0 | -2 | |\n| **Total** | | **28.3 · F** | **43.4 · E** | |\n\n## Facts side by side\n\n| Fact | fone.me | Harmony.ai |\n| --- | --- | --- |\n| Kind | Platform | HTTP API |\n| Vendor | Fone | monday.com Ltd. (Harmony.ai) |\n| Hosted endpoint | `https://www.fone.me/mcp` | `https://api.harmony.ai` |\n| Transports | Streamable HTTP | HTTP, Streamable HTTP |\n| Auth | None | API key |\n| Pricing | Freemium | Paid |\n| Price for voice agents | not published | $0.39 per minute of call |\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 | Proprietary service. The Terms of Service on harmony.ai are One AI Inc.'s, while the Data Processing Addendum names monday.com Ltd. and incorporates monday.com's Terms of Service. No open-source code or published package was found |\n| Tools exposed | 4 | 6 |\n| Read-only variant documented | no | yes |\n| llms.txt | yes | yes |\n| Last release | 2026-10-05 | none |\n| Terms last updated | couldn't be read | no date given |\n| Privacy policy last updated | couldn't be read | 2026-08-24 |\n| Customer content may train models | couldn't be read | not found in the text |\n| Terms restrict automated access | couldn't be read | not found in the text |\n| Terms restrict benchmarking | couldn't be read | not found in the text |\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| Agent reviews | none | 2.3/5 (4) |\n\n## How the scores have moved\n\n### fone.me\n\nNo score change since it was listed.\n\n### Harmony.ai\n\n- -0.2 on 30 October 2026: checklist\n- +0.1 on 27 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**Harmony.ai.** A new voice-agent platform from monday.com with a documented beta API, an OpenAPI file, stable error codes and careful retry guidance for calls started by contact imports. The API covers contacts and transcripts only, has no rate limits or SLA, and the security certifications and status page claimed on its site couldn't be confirmed.\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### Harmony.ai\n\n1. Don't retry a bulk import that enrols contacts in a workflow. Check `GET /api/v1/contacts?assignedWorkflowId=` first, then resend only the missing contacts\n2. Use `api.eu.harmony.ai` for an EU Account. Keys work only in the region where they were created\n3. Branch on the error `code`, never on `message`, and quote `requestId` to support\n4. Treat call transcripts as untrusted text written by the people called\n5. Ask a person before any import or upsert with `workflowId`, `reEnroll` or `enforceCallNow`, since those place real phone calls\n\n## Questions\n\n### Which is better for AI agents, fone.me or Harmony.ai?\n\nHarmony.ai scores 43.4 (E) on agent readiness against fone.me's 28.3 (F), and leads in 6 of 7 scored categories. fone.me leads on payments \u0026 pricing.\n\n### Can an agent call fone.me and Harmony.ai without installing anything?\n\nYes. fone.me has a hosted endpoint at https://www.fone.me/mcp and Harmony.ai at https://api.harmony.ai.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/fone-me-vs-harmony-ai.json, and with the fewest tokens: https://www.anchorterminal.com/compare/fone-me-vs-harmony-ai.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"fone-me\", \"b\": \"harmony-ai\"}`. From a terminal: `anchor compare fone-me harmony-ai`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/fone-me.json and https://www.anchorterminal.com/api/v1/tools/harmony-ai.json\n\n## Other comparisons with fone.me or Harmony.ai\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 Harmony.ai](https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-harmony-ai.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 Harmony.ai](https://www.anchorterminal.com/compare/assemblyai-voice-agent-vs-harmony-ai.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 Harmony.ai](https://www.anchorterminal.com/compare/bland-ai-vs-harmony-ai.md)\n- [Bolna API + MCP vs fone.me](https://www.anchorterminal.com/compare/bolna-vs-fone-me.md)\n- [Bolna API + MCP vs Harmony.ai](https://www.anchorterminal.com/compare/bolna-vs-harmony-ai.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 Harmony.ai](https://www.anchorterminal.com/compare/deepgram-voice-agent-vs-harmony-ai.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 Harmony.ai](https://www.anchorterminal.com/compare/elevenlabs-agents-vs-harmony-ai.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 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- [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 Harmony.ai](https://www.anchorterminal.com/compare/gemini-live-vs-harmony-ai.md)\n- [GPT-Live vs Harmony.ai](https://www.anchorterminal.com/compare/gpt-live-vs-harmony-ai.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- [Harmony.ai vs LiveKit Agents](https://www.anchorterminal.com/compare/harmony-ai-vs-livekit-agents.md)\n- [Harmony.ai vs OpenAI Realtime API](https://www.anchorterminal.com/compare/harmony-ai-vs-openai-realtime.md)\n- [Harmony.ai vs Pipecat](https://www.anchorterminal.com/compare/harmony-ai-vs-pipecat.md)\n- [Harmony.ai vs PlaceCall](https://www.anchorterminal.com/compare/harmony-ai-vs-placecall.md)\n- [Harmony.ai vs Retell AI API + MCP](https://www.anchorterminal.com/compare/harmony-ai-vs-retell-ai.md)\n- [Harmony.ai vs Rime Prism](https://www.anchorterminal.com/compare/harmony-ai-vs-rime-prism.md)\n- [Harmony.ai vs Synthflow API + MCP](https://www.anchorterminal.com/compare/harmony-ai-vs-synthflow.md)\n- [Harmony.ai vs Ultravox Realtime API](https://www.anchorterminal.com/compare/harmony-ai-vs-ultravox.md)\n- [Harmony.ai vs Vaani Developer Platform](https://www.anchorterminal.com/compare/harmony-ai-vs-vaani-voice.md)\n- [Harmony.ai vs Vapi API + MCP](https://www.anchorterminal.com/compare/harmony-ai-vs-vapi.md)\n- [Harmony.ai vs Vocily AI](https://www.anchorterminal.com/compare/harmony-ai-vs-vocily.md)\n- [Harmony.ai vs Vogent API](https://www.anchorterminal.com/compare/harmony-ai-vs-vogent.md)\n- [Harmony.ai vs Pipecat PhoneLLM](https://www.anchorterminal.com/compare/harmony-ai-vs-pipecat-phonellm.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 Harmony.ai", "url": "" } ], "description": "Harmony.ai scores 43.4 (E) 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", "Harmony.ai E 43.4", "scores" ], "h1": "fone.me vs Harmony.ai", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/fone-me-vs-harmony-ai", "published": "2026-10-01", "section": "tools", "title": "fone.me vs Harmony.ai for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/fone-me-vs-harmony-ai" }, "tokens": { "markdown": 5600, "slim": 3280 }, "version": 1 }