{ "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": "Synthflow API + MCP scores 47.3 (D) 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": "synthflow", "name": "Synthflow API + MCP", "vendor": "Synthflow", "vendorUrl": "https://synthflow.ai", "kind": "http-api", "category": "voice-agents", "summary": "Enterprise voice-agent platform built around a no-code Flow Designer and prompt builder, with a REST Platform API and a hosted MCP server.", "url": "https://www.anchorterminal.com/tools/synthflow", "markdownUrl": "https://www.anchorterminal.com/tools/synthflow.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/synthflow.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/synthflow.json", "dns": "synthflow.grade.anchorterminal.com", "repo": "https://github.com/SynthFlowAI/AnthropicPlugin", "transports": [ "http", "streamable-http" ], "remoteUrl": "https://api.synthflow.ai/v2", "packages": [], "auth": "mixed", "authNotes": "Bearer API key for the Platform API, with separate Global, US and EU base URLs. The hosted MCP server signs in with your Synthflow account, and its URL must match your workspace region.", "pricing": "paid", "pricingNotes": "Sales-led only. Synthflow is sold as an annual enterprise agreement scoped on call volume, concurrency, telephony, integrations and security, with no free plan, trial or rate by the minute. The earlier self-serve Pro, Growth and Agency plans are no longer sold (https://synthflow.ai/pricing).", "priceSummary": "Paid", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the docs, pricing page or MCP docs (checked 2026-11-04).", "endpoints": [] }, "toolCount": 66, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-09-30" }, "docsUrl": "https://docs.synthflow.ai", "llmsTxt": "https://docs.synthflow.ai/llms.txt", "openapi": "https://docs.synthflow.ai/openapi.json", "capabilities": [ "voice.agent", "voice.pipeline", "voice.tools", "voice.telephony" ], "tags": [ "hosted", "closed-source", "mcp", "llms-txt", "openapi", "webhooks", "pipeline", "enterprise" ], "lastRelease": "2026-10-23", "graded": true, "anchor": { "graded": true, "score": 47.3, "grade": "D", "agentReady": false, "rank": 1157, "ranked": true, "rankOf": 1510, "categoryRank": 21, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 45, "maintenance": 65, "payments": 0, "reliability": 55, "schema": 62, "security": 55, "transparency": 75 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-04" }, "negative": -3, "negativeNotes": [ "-3, a change that broke working requests, posted after it took effect. From 12:00 UTC on 23 October to 16:00 UTC on 26 October 2026, `PUT /v2/subaccounts/{subaccount_id}` requests that included `operation_type` or `products` failed with 400 after an internal infrastructure change, and nothing in those requests was saved. Synthflow reverted it and posted the account on its status page afterwards. https://status.synthflow.ai/feed.atom" ], "verdict": "Synthflow publishes a dated changelog with dated deprecation notices, Global, US and EU regions for the API and MCP server, and a trust centre listing SOC 2 Type 2 and ISO 27001. Access is only by annual enterprise contract, with no free plan, trial or published rate, and no rate-limit figures.", "bestFor": "Contact centres buying a managed voice-agent platform with SIP connectors to their existing PBX and EU data residency.", "strengths": [ "Changelog posts on ten days between 9 and 30 October 2026, with API Changes and Deprecation Notices categories and an RSS feed", "Global, US and EU regions for the API and the MCP server, each with its own base URL", "Status page with Dashboard, API and calling components per region, and incidents written up with cause and scope", "Trust centre lists SOC 2 Type 2, ISO/IEC 27001 and HIPAA, with reports on NDA request and 20 named subprocessors with purposes and locations", "Per-agent 30-day retention toggle and PII redaction for transcripts, webhooks and logs" ], "weaknesses": [ "Annual enterprise contract only, with no free plan, trial or rate by the minute", "No published concurrency or calls-per-second figures, and no backoff or idempotency guidance for 429", "No official SDK packages, and the Claude plugin repository has no CI", "`PUT /v2/subaccounts` rejected two documented fields from 23 to 26 October 2026 after an internal change", "`publish_agent_draft`, `rollback_agent_version` and `batch_update_agents_by_filter` run through MCP without confirmation" ], "agentNotes": [ "Use the MCP and API base URL that matches the workspace region (Global, US or EU)", "Send destructive MCP tools again with `confirmed=true` only after a person approves", "Expect 429 when concurrency or calls per second run out, and leave at least a second between call starts outside Campaigns", "Move from `recording_url` to the Get a recording endpoint before 10 January 2027", "Read the transfer failure reason on a failed transfer before retrying it" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 2, "avgRating": 2, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "D", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 47.3 } ], "editorialScores": { "ergonomics": 45, "maintenance": 65, "payments": 0, "reliability": 55, "schema": 62, "security": 55, "transparency": 68 }, "provenanceScore": 82, "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 -X POST https://api.synthflow.ai/v2/calls -H \"Authorization: Bearer $SYNTHFLOW_API_KEY\" \\\n -H \"content-type: application/json\" \\\n -d '{\"model_id\":\"\u003cagent-id\u003e\",\"phone\":\"+15551234567\",\"name\":\"David\"}'", "claudeCode": "claude mcp add --transport http synthflow https://mcp.synthflow.ai/mcp" }, "letme": { "capability": "https://letme.dev/voice.agent", "tool": "https://letme.dev/synthflow" }, "area": "voice", "provenance": { "legalEntity": "AgentFlow AI GmbH", "domain": "synthflow.ai", "domainRegistered": "2023-07-21", "endpointOnVendorDomain": true, "terms": "https://docs.synthflow.ai/terms-conditions", "privacy": "https://docs.synthflow.ai/privacy-policy", "statusPage": "https://status.synthflow.ai", "changelog": "https://docs.synthflow.ai/changelog", "securityTxt": "none", "checked": "2026-11-04", "notes": [ "The Subscriber Terms (version 1.0, last updated 13 May 2026) name AgentFlow AI GmbH, registered at the local court of Charlottenburg under HRB 255004 B, Kurfürstendamm 15, 10719 Berlin.", "The status page at status.synthflow.ai runs on incident.io, with Dashboard, API and End to End calling components for Legacy, US and EU infrastructure.", "synthflow.ai/.well-known/security.txt returns 404 (4 November 2026). The trust centre at security.synthflow.ai is run on SafeBase.", "The registration date of synthflow.ai has no first-hand source we could read on 4 November 2026." ], "score": 82 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/synthflow.json", "live": { "slug": "synthflow", "probe": { "target": "https://api.synthflow.ai/v2", "method": "get", "lastAt": "2026-11-07T19:22:37.191760141Z", "lastOk": true, "lastStatus": 404, "lastMs": 268, "authRequired": false, "uptime24h": 100, "uptime30d": 99.99, "p50ms24h": 216, "p95ms24h": 447, "samples24h": 238, "samples30d": 7920, "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": 253 }, { "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": 249 }, { "date": "2026-10-26", "probes": 252, "ok": 252 }, { "date": "2026-10-27", "probes": 249, "ok": 249 }, { "date": "2026-10-28", "probes": 250, "ok": 250 }, { "date": "2026-10-29", "probes": 249, "ok": 249 }, { "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 } ] }, "vendorStatus": { "page": "https://status.synthflow.ai", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-11-07T19:23:49.139447262Z" }, "githubStars": 0, "securityTxt": { "url": "https://synthflow.ai/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-07T16:00:37.012918414Z" }, "llmsTxt": { "url": "https://docs.synthflow.ai/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:34:05.343006996Z" }, "domain": { "domain": "synthflow.ai", "registered": "2023-07-21", "source": "https://rdap.identitydigital.services/rdap/domain/synthflow.ai", "checkedAt": "2026-11-01T14:08:46.202924518Z" }, "pages": [ { "url": "https://docs.synthflow.ai/changelog", "kind": "changelog", "status": 200, "checkedAt": "2026-11-07T14:08:16.305098813Z", "changedAt": "2026-11-06T13:30:35.671235385Z", "fingerprint": "e371e7e41e75" }, { "url": "https://synthflow.ai/pricing", "kind": "pricing", "status": 200, "checkedAt": "2026-11-07T14:21:37.566787318Z", "changedAt": "2026-11-06T13:43:04.747170265Z", "fingerprint": "a5a3170c3c78" }, { "url": "https://docs.synthflow.ai/privacy-policy", "kind": "privacy", "status": 200, "checkedAt": "2026-11-07T14:08:18.832503841Z", "changedAt": "2026-10-29T05:06:05.220387717Z", "fingerprint": "3738d5638558" }, { "url": "https://docs.synthflow.ai/terms-conditions", "kind": "terms", "status": 200, "checkedAt": "2026-11-07T14:08:20.742266544Z", "changedAt": "2026-10-29T05:06:07.003894551Z", "fingerprint": "79b6301d26e0" } ], "mcpTools": { "url": "https://mcp.synthflow.ai/mcp", "checkedAt": "2026-11-07T01:48:11.228612533Z", "status": "auth", "note": "asks for credentials before listing its tools", "changedAt": "2026-11-07T01:48:11.228612533Z" }, "github": { "repo": "synthflowai/anthropicplugin", "checkedAt": "2026-11-02T09:29:46.136470387Z", "stars": 0, "archived": false, "issuesEnabled": true, "pushedAt": "2026-07-30T07:56:34Z", "openIssues": 0, "openPRs": 0, "issuesOpened90d": 0, "issuesClosed90d": 0, "prsMerged90d": 0 }, "updatedAt": "2026-11-07T19:23:49.139447262Z" } }, "edges": [ { "by": 52, "category": "transparency", "leads": "synthflow", "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 platform with clear terms. The Subscriber Terms (version 1.0, 13 May 2026) name AgentFlow AI GmbH, Berlin, HRB 255004 B (15). Recordings, transcripts and caller IDs can be set to delete after 30 days per agent, PII redaction is available, and a DPA and BAA are offered. Otherwise the privacy policy keeps data until it is no longer needed, with no platform retention period (18 of 30). The changelog's Deprecation Notices carry dates. `recording_url` on the calls endpoints ends on 10 January 2027, announced on 22 October, and Salesforce actions need reconnecting by 30 November 2026. No written policy with a notice period found (15). The trust centre page lists 20 subprocessors, each with its purpose and processing location, among them AWS, Google Cloud, Microsoft Azure, OpenAI, Anthropic, Deepgram, ElevenLabs and Twilio. 18 process in the US and EU and two, Cerebrium and Hex Tech, in the US. The docs give Global, US and EU regions (20). 15 + 18 + 15 + 20 = 68." }, "scores": { "a": 23, "b": 75 } }, { "by": 50, "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). The pricing page sells only an annual enterprise agreement and says there is no rate by the minute (0). It also says there is no free plan or trial (0). An agent can't get access without a sales process (0)." }, "scores": { "a": 50, "b": 0 } }, { "by": 42, "category": "maintenance", "leads": "synthflow", "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": "API changes dated 23 October 2026 (List agent versions, new MCP server tools), 12 days before this check. The 30 October entry is a dashboard function the API doesn't serve (30). Ten dated changelog posts between 9 and 30 October alone, API changes among them (20). Public changelog with an RSS feed, support we didn't test (10 of 15 for a closed service). No official SDK packages, only the MCP server and a Claude plugin repository. Earlier partial kept (5 of 15). No packages. The plugin repository has no CI and its last commit is 30 July 2026. Down from 3, which no package earned (0)." }, "scores": { "a": 23, "b": 65 } }, { "by": 40, "category": "reliability", "leads": "synthflow", "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": "Status page at status.synthflow.ai, now on incident.io, with Dashboard, API and End to End calling components for the Legacy, US and EU infrastructure, and a 90-day history on the page that covers the window from 6 August (20). In the 90 days from 6 August there were post-call AI outputs missing from webhooks from 08:20 to 11:10 UTC on 7 August (calls and webhook delivery unaffected), 9 to 12 minutes of failed calls in the EU and US regions with intermittent warm-transfer failures on 17 August, a white-label login fault on 7 September, `PUT /v2/subaccounts` rejecting two fields from 23 to 26 October, dashboard access and slower API responses on 26 October, and the settings page and SSO login unavailable for some workspaces from 27 October, which also hid some subaccount workspaces in the dashboard. Each touched one function, region or group of requests, so all read as minor. The 7 August webhook fault was counted as a major on 1 October (20). Concurrency and calls-per-second limits are set per contract and no numbers are published (0). The concurrency page documents 429 on reaching either limit and suggests a 1-second delay between calls started from automation tools, with no Retry-After, backoff or idempotency guidance. Earlier partial kept (5). No SLA published, and the pricing page sets availability terms in each agreement (0). The Platform API is generally available (10)." }, "scores": { "a": 15, "b": 55 } }, { "by": 31, "category": "schema", "leads": "synthflow", "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": "The 1 October check read an OpenAPI file at docs.synthflow.ai/openapi.json. No docs page read on 4 November links it, llms.txt, the API introduction and the Make a call reference included, and the reference pages give typed request bodies, three regional servers and Bearer authentication only as rendered pages. A file with no visible link isn't counted as a published contract, down from 25 (0). llms.txt, llms-full.txt and a Markdown copy of every page (10). Guides cover agents, actions and SIP connectors with when-to-use advice (14 of 20). Typed request bodies, with agent configuration as large nested objects (12 of 15). Examples throughout and nine named transfer failure reasons (11 of 15). A dated changelog with Product Updates, API Changes and Deprecation Notices categories, an RSS feed and a v2 API (15). 0 + 10 + 14 + 12 + 11 + 15 = 62." }, "scores": { "a": 31, "b": 62 } }, { "by": 25, "category": "security", "leads": "synthflow", "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": "Bearer API keys made per workspace under Workspace Settings, with 2FA and SSO on the account. The MCP server signs in through Synthflow in a browser and picks the workspace and region, with an API key for headless use (20). Deletes are confirmation-gated, but there's no read-only key and other writes run without a check (10 of 20). No prompt-injection guidance found, though the MCP server has a `fetch_url` tool and knowledge bases crawl websites. PII redaction for transcripts, webhooks and logs is a separate data control (5 of 15). Call logs and webhook delivery logs, and no audit log of account actions documented (8 of 15). The SafeBase trust centre at security.synthflow.ai lists SOC 2 Type 2, ISO/IEC 27001, ISO/IEC 42001 and HIPAA, with reports behind an NDA request, and states a responsible disclosure process with no reporting address. No security.txt (404) and no public bug bounty. Read as SOC 2 Type 2 and ISO 27001 claims with no disclosure route, as people-data-labs, fireworks-inference and complyadvantage are (12). 20 + 10 + 5 + 8 + 12 = 55." }, "scores": { "a": 30, "b": 55 } } ], "facts": [ { "a": "Platform", "b": "HTTP API", "name": "Kind" }, { "a": "Fone", "b": "Synthflow", "name": "Vendor" }, { "a": "https://www.fone.me/mcp", "b": "https://api.synthflow.ai/v2", "name": "Hosted endpoint" }, { "a": "Streamable HTTP", "b": "HTTP, Streamable HTTP", "name": "Transports" }, { "a": "None", "b": "OAuth or key", "name": "Auth" }, { "a": "Freemium", "b": "Paid", "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": "none", "name": "Licence" }, { "a": "4", "b": "66", "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-10-23", "name": "Last release" }, { "a": "couldn't be read", "b": "2026-05-13", "name": "Terms last updated" }, { "a": "couldn't be read", "b": "no date given", "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": "not found in the text", "name": "Terms or service can change without notice" }, { "a": "couldn't be read", "b": "not found in the text", "name": "Arbitration or class-action waiver" }, { "a": "none", "b": "2/5 (2)", "name": "Agent reviews" } ], "faq": [ { "answer": "Synthflow API + MCP scores 47.3 (D) 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 Synthflow API + MCP?" }, { "answer": "Yes. fone.me has a hosted endpoint at https://www.fone.me/mcp and Synthflow API + MCP at https://api.synthflow.ai/v2.", "question": "Can an agent call fone.me and Synthflow API + MCP without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Payments \u0026 pricing, 50 against 0" ], "also": [ "No key needed to call it", "No incidents deducted, where Synthflow API + MCP loses 3 points for them" ], "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, 62 against 31", "Agent ergonomics, 45 against 29", "Security \u0026 auth, 55 against 30", "Maintenance \u0026 community, 65 against 23", "Transparency \u0026 trust, 75 against 23" ], "also": null, "goodFor": "Contact centres buying a managed voice-agent platform with SIP connectors to their existing PBX and EU data residency.", "slug": "synthflow", "watchFor": "Annual enterprise contract only, with no free plan, trial or rate by the minute" } ], "history": { "fone-me": null, "synthflow": [ { "causes": [ "product", "evidence", "correction", "event" ], "date": "2026-11-04", "delta": -4, "from": 51.3, "fromGrade": "D", "to": 47.3, "toGrade": "D" }, { "causes": [ "method" ], "date": "2026-10-27", "delta": 0.2, "from": 51.1, "fromGrade": "D", "to": 51.3, "toGrade": "D" }, { "causes": [ "method" ], "date": "2026-10-08", "delta": -0.2, "from": 51.3, "fromGrade": "D", "to": 51.1, "toGrade": "D" } ] }, "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-synthflow.json", "title": "Amazon Nova 2 Sonic vs Synthflow API + MCP", "url": "https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-synthflow" }, { "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-synthflow.json", "title": "AssemblyAI Voice Agent API vs Synthflow API + MCP", "url": "https://www.anchorterminal.com/compare/assemblyai-voice-agent-vs-synthflow" }, { "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-synthflow.json", "title": "Bland AI API + MCP vs Synthflow API + MCP", "url": "https://www.anchorterminal.com/compare/bland-ai-vs-synthflow" }, { "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-synthflow.json", "title": "Bolna API + MCP vs Synthflow API + MCP", "url": "https://www.anchorterminal.com/compare/bolna-vs-synthflow" }, { "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-synthflow.json", "title": "Deepgram Voice Agent API vs Synthflow API + MCP", "url": "https://www.anchorterminal.com/compare/deepgram-voice-agent-vs-synthflow" }, { "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-synthflow.json", "title": "ElevenLabs Agents API + MCP vs Synthflow API + MCP", "url": "https://www.anchorterminal.com/compare/elevenlabs-agents-vs-synthflow" }, { "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-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-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-synthflow.json", "title": "Gemini Live API vs Synthflow API + MCP", "url": "https://www.anchorterminal.com/compare/gemini-live-vs-synthflow" }, { "json": "https://www.anchorterminal.com/compare/gpt-live-vs-synthflow.json", "title": "GPT-Live vs Synthflow API + MCP", "url": "https://www.anchorterminal.com/compare/gpt-live-vs-synthflow" }, { "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/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/inworld-realtime-vs-synthflow.json", "title": "Inworld Realtime API vs Synthflow API + MCP", "url": "https://www.anchorterminal.com/compare/inworld-realtime-vs-synthflow" }, { "json": "https://www.anchorterminal.com/compare/livekit-agents-vs-synthflow.json", "title": "LiveKit Agents vs Synthflow API + MCP", "url": "https://www.anchorterminal.com/compare/livekit-agents-vs-synthflow" }, { "json": "https://www.anchorterminal.com/compare/openai-realtime-vs-synthflow.json", "title": "OpenAI Realtime API vs Synthflow API + MCP", "url": "https://www.anchorterminal.com/compare/openai-realtime-vs-synthflow" }, { "json": "https://www.anchorterminal.com/compare/pipecat-vs-synthflow.json", "title": "Pipecat vs Synthflow API + MCP", "url": "https://www.anchorterminal.com/compare/pipecat-vs-synthflow" }, { "json": "https://www.anchorterminal.com/compare/placecall-vs-synthflow.json", "title": "PlaceCall vs Synthflow API + MCP", "url": "https://www.anchorterminal.com/compare/placecall-vs-synthflow" }, { "json": "https://www.anchorterminal.com/compare/retell-ai-vs-synthflow.json", "title": "Retell AI API + MCP vs Synthflow API + MCP", "url": "https://www.anchorterminal.com/compare/retell-ai-vs-synthflow" }, { "json": "https://www.anchorterminal.com/compare/rime-prism-vs-synthflow.json", "title": "Rime Prism vs Synthflow API + MCP", "url": "https://www.anchorterminal.com/compare/rime-prism-vs-synthflow" }, { "json": "https://www.anchorterminal.com/compare/synthflow-vs-ultravox.json", "title": "Synthflow API + MCP vs Ultravox Realtime API", "url": "https://www.anchorterminal.com/compare/synthflow-vs-ultravox" }, { "json": "https://www.anchorterminal.com/compare/synthflow-vs-vaani-voice.json", "title": "Synthflow API + MCP vs Vaani Developer Platform", "url": "https://www.anchorterminal.com/compare/synthflow-vs-vaani-voice" }, { "json": "https://www.anchorterminal.com/compare/synthflow-vs-vapi.json", "title": "Synthflow API + MCP vs Vapi API + MCP", "url": "https://www.anchorterminal.com/compare/synthflow-vs-vapi" }, { "json": "https://www.anchorterminal.com/compare/synthflow-vs-vocily.json", "title": "Synthflow API + MCP vs Vocily AI", "url": "https://www.anchorterminal.com/compare/synthflow-vs-vocily" }, { "json": "https://www.anchorterminal.com/compare/synthflow-vs-vogent.json", "title": "Synthflow API + MCP vs Vogent API", "url": "https://www.anchorterminal.com/compare/synthflow-vs-vogent" }, { "json": "https://www.anchorterminal.com/compare/cuelight-vs-synthflow.json", "title": "CueLight vs Synthflow API + MCP", "url": "https://www.anchorterminal.com/compare/cuelight-vs-synthflow" }, { "json": "https://www.anchorterminal.com/compare/pipecat-phonellm-vs-synthflow.json", "title": "Pipecat PhoneLLM vs Synthflow API + MCP", "url": "https://www.anchorterminal.com/compare/pipecat-phonellm-vs-synthflow" } ], "panel": null, "scores": [ { "by": 40, "edge": "synthflow", "fone-me": 15, "key": "reliability", "name": "Reliability", "synthflow": 55, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 31, "edge": "synthflow", "fone-me": 31, "key": "schema", "name": "Schema \u0026 documentation", "synthflow": 62, "weight": 13 }, { "by": 16, "edge": "synthflow", "fone-me": 29, "key": "ergonomics", "name": "Agent ergonomics", "synthflow": 45, "weight": 13 }, { "by": 25, "edge": "synthflow", "fone-me": 30, "key": "security", "name": "Security \u0026 auth", "synthflow": 55, "weight": 14 }, { "by": 50, "edge": "fone-me", "fone-me": 50, "key": "payments", "name": "Payments \u0026 pricing", "synthflow": 0, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 42, "edge": "synthflow", "fone-me": 23, "key": "maintenance", "name": "Maintenance \u0026 community", "synthflow": 65, "weight": 7 }, { "by": 52, "edge": "synthflow", "fone-me": 23, "key": "transparency", "name": "Transparency \u0026 trust", "synthflow": 75, "weight": 7 } ], "summary": "Synthflow API + MCP scores 47.3 (D) 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.", "synthflow": "Synthflow publishes a dated changelog with dated deprecation notices, Global, US and EU regions for the API and MCP server, and a trust centre listing SOC 2 Type 2 and ISO 27001. Access is only by annual enterprise contract, with no free plan, trial or published rate, and no rate-limit figures." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/fone-me-vs-synthflow", "json": "https://www.anchorterminal.com/compare/fone-me-vs-synthflow.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/fone-me-vs-synthflow.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/fone-me-vs-synthflow.min.md" }, "markdown": "Synthflow API + MCP scores 47.3 (D) 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- Synthflow API + MCP: grade D, 47.3/100, rank #1157 of 1510. Markdown https://www.anchorterminal.com/tools/synthflow.md · JSON https://www.anchorterminal.com/api/v1/tools/synthflow.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 0\n\nAlso in its favour:\n- No key needed to call it\n- No incidents deducted, where Synthflow API + MCP loses 3 points for them\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### Synthflow API + MCP (D)\n\nGood for: Contact centres buying a managed voice-agent platform with SIP connectors to their existing PBX and EU data residency.\n\nAhead on:\n- Reliability, 55 against 15\n- Schema \u0026 documentation, 62 against 31\n- Agent ergonomics, 45 against 29\n- Security \u0026 auth, 55 against 30\n- Maintenance \u0026 community, 65 against 23\n- Transparency \u0026 trust, 75 against 23\n\nWatch for: Annual enterprise contract only, with no free plan, trial or rate by the minute\n\n\n## Why the edge\n\n### Transparency \u0026 trust: Synthflow API + MCP +52\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- Synthflow API + MCP (75): Closed platform with clear terms. The Subscriber Terms (version 1.0, 13 May 2026) name AgentFlow AI GmbH, Berlin, HRB 255004 B (15). Recordings, transcripts and caller IDs can be set to delete after 30 days per agent, PII redaction is available, and a DPA and BAA are offered. Otherwise the privacy policy keeps data until it is no longer needed, with no platform retention period (18 of 30). The changelog's Deprecation Notices carry dates. `recording_url` on the calls endpoints ends on 10 January 2027, announced on 22 October, and Salesforce actions need reconnecting by 30 November 2026. No written policy with a notice period found (15). The trust centre page lists 20 subprocessors, each with its purpose and processing location, among them AWS, Google Cloud, Microsoft Azure, OpenAI, Anthropic, Deepgram, ElevenLabs and Twilio. 18 process in the US and EU and two, Cerebrium and Hex Tech, in the US. The docs give Global, US and EU regions (20). 15 + 18 + 15 + 20 = 68.\n\n### Payments \u0026 pricing: fone.me +50\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- Synthflow API + MCP (0): No x402, MPP or L402 (0 of 40). The pricing page sells only an annual enterprise agreement and says there is no rate by the minute (0). It also says there is no free plan or trial (0). An agent can't get access without a sales process (0).\n\n### Maintenance \u0026 community: Synthflow API + MCP +42\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- Synthflow API + MCP (65): API changes dated 23 October 2026 (List agent versions, new MCP server tools), 12 days before this check. The 30 October entry is a dashboard function the API doesn't serve (30). Ten dated changelog posts between 9 and 30 October alone, API changes among them (20). Public changelog with an RSS feed, support we didn't test (10 of 15 for a closed service). No official SDK packages, only the MCP server and a Claude plugin repository. Earlier partial kept (5 of 15). No packages. The plugin repository has no CI and its last commit is 30 July 2026. Down from 3, which no package earned (0).\n\n### Reliability: Synthflow API + MCP +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- Synthflow API + MCP (55): Status page at status.synthflow.ai, now on incident.io, with Dashboard, API and End to End calling components for the Legacy, US and EU infrastructure, and a 90-day history on the page that covers the window from 6 August (20). In the 90 days from 6 August there were post-call AI outputs missing from webhooks from 08:20 to 11:10 UTC on 7 August (calls and webhook delivery unaffected), 9 to 12 minutes of failed calls in the EU and US regions with intermittent warm-transfer failures on 17 August, a white-label login fault on 7 September, `PUT /v2/subaccounts` rejecting two fields from 23 to 26 October, dashboard access and slower API responses on 26 October, and the settings page and SSO login unavailable for some workspaces from 27 October, which also hid some subaccount workspaces in the dashboard. Each touched one function, region or group of requests, so all read as minor. The 7 August webhook fault was counted as a major on 1 October (20). Concurrency and calls-per-second limits are set per contract and no numbers are published (0). The concurrency page documents 429 on reaching either limit and suggests a 1-second delay between calls started from automation tools, with no Retry-After, backoff or idempotency guidance. Earlier partial kept (5). No SLA published, and the pricing page sets availability terms in each agreement (0). The Platform API is generally available (10).\n\n### Schema \u0026 documentation: Synthflow API + MCP +31\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- Synthflow API + MCP (62): The 1 October check read an OpenAPI file at docs.synthflow.ai/openapi.json. No docs page read on 4 November links it, llms.txt, the API introduction and the Make a call reference included, and the reference pages give typed request bodies, three regional servers and Bearer authentication only as rendered pages. A file with no visible link isn't counted as a published contract, down from 25 (0). llms.txt, llms-full.txt and a Markdown copy of every page (10). Guides cover agents, actions and SIP connectors with when-to-use advice (14 of 20). Typed request bodies, with agent configuration as large nested objects (12 of 15). Examples throughout and nine named transfer failure reasons (11 of 15). A dated changelog with Product Updates, API Changes and Deprecation Notices categories, an RSS feed and a v2 API (15). 0 + 10 + 14 + 12 + 11 + 15 = 62.\n\n### Security \u0026 auth: Synthflow API + MCP +25\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- Synthflow API + MCP (55): Bearer API keys made per workspace under Workspace Settings, with 2FA and SSO on the account. The MCP server signs in through Synthflow in a browser and picks the workspace and region, with an API key for headless use (20). Deletes are confirmation-gated, but there's no read-only key and other writes run without a check (10 of 20). No prompt-injection guidance found, though the MCP server has a `fetch_url` tool and knowledge bases crawl websites. PII redaction for transcripts, webhooks and logs is a separate data control (5 of 15). Call logs and webhook delivery logs, and no audit log of account actions documented (8 of 15). The SafeBase trust centre at security.synthflow.ai lists SOC 2 Type 2, ISO/IEC 27001, ISO/IEC 42001 and HIPAA, with reports behind an NDA request, and states a responsible disclosure process with no reporting address. No security.txt (404) and no public bug bounty. Read as SOC 2 Type 2 and ISO 27001 claims with no disclosure route, as people-data-labs, fireworks-inference and complyadvantage are (12). 20 + 10 + 5 + 8 + 12 = 55.\n\n## Score by category\n\n| Category | Weight | fone.me | Synthflow API + MCP | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 15 | 55 | Synthflow API + MCP +40 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 31 | 62 | Synthflow API + MCP +31 |\n| Agent ergonomics | 13% (16.2 this run) | 29 | 45 | Synthflow API + MCP +16 |\n| Security \u0026 auth | 14% (17.5 this run) | 30 | 55 | Synthflow API + MCP +25 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 50 | 0 | fone.me +50 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 23 | 65 | Synthflow API + MCP +42 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 23 | 75 | Synthflow API + MCP +52 |\n| Negative events | ≤15 | 0 | -3 | |\n| **Total** | | **28.3 · F** | **47.3 · D** | |\n\n## Facts side by side\n\n| Fact | fone.me | Synthflow API + MCP |\n| --- | --- | --- |\n| Kind | Platform | HTTP API |\n| Vendor | Fone | Synthflow |\n| Hosted endpoint | `https://www.fone.me/mcp` | `https://api.synthflow.ai/v2` |\n| Transports | Streamable HTTP | HTTP, Streamable HTTP |\n| Auth | None | OAuth or key |\n| Pricing | Freemium | Paid |\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 | none |\n| Tools exposed | 4 | 66 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| Last release | 2026-10-05 | 2026-10-23 |\n| Terms last updated | couldn't be read | 2026-05-13 |\n| Privacy policy last updated | couldn't be read | no date given |\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 | not found in the text |\n| Arbitration or class-action waiver | couldn't be read | not found in the text |\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### Synthflow API + MCP\n\n- -4.0 on 4 November 2026: product, new evidence, correction, negative event\n- +0.2 on 27 October 2026: checklist\n- -0.2 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**Synthflow API + MCP.** Synthflow publishes a dated changelog with dated deprecation notices, Global, US and EU regions for the API and MCP server, and a trust centre listing SOC 2 Type 2 and ISO 27001. Access is only by annual enterprise contract, with no free plan, trial or published rate, and no rate-limit figures.\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### Synthflow API + MCP\n\n1. Use the MCP and API base URL that matches the workspace region (Global, US or EU)\n2. Send destructive MCP tools again with `confirmed=true` only after a person approves\n3. Expect 429 when concurrency or calls per second run out, and leave at least a second between call starts outside Campaigns\n4. Move from `recording_url` to the Get a recording endpoint before 10 January 2027\n5. Read the transfer failure reason on a failed transfer before retrying it\n\n## Questions\n\n### Which is better for AI agents, fone.me or Synthflow API + MCP?\n\nSynthflow API + MCP scores 47.3 (D) 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 Synthflow API + MCP without installing anything?\n\nYes. fone.me has a hosted endpoint at https://www.fone.me/mcp and Synthflow API + MCP at https://api.synthflow.ai/v2.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/fone-me-vs-synthflow.json, and with the fewest tokens: https://www.anchorterminal.com/compare/fone-me-vs-synthflow.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"fone-me\", \"b\": \"synthflow\"}`. From a terminal: `anchor compare fone-me synthflow`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/fone-me.json and https://www.anchorterminal.com/api/v1/tools/synthflow.json\n\n## Other comparisons with fone.me or Synthflow API + MCP\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 Synthflow API + MCP](https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-synthflow.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 Synthflow API + MCP](https://www.anchorterminal.com/compare/assemblyai-voice-agent-vs-synthflow.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 Synthflow API + MCP](https://www.anchorterminal.com/compare/bland-ai-vs-synthflow.md)\n- [Bolna API + MCP vs fone.me](https://www.anchorterminal.com/compare/bolna-vs-fone-me.md)\n- [Bolna API + MCP vs Synthflow API + MCP](https://www.anchorterminal.com/compare/bolna-vs-synthflow.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 Synthflow API + MCP](https://www.anchorterminal.com/compare/deepgram-voice-agent-vs-synthflow.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 Synthflow API + MCP](https://www.anchorterminal.com/compare/elevenlabs-agents-vs-synthflow.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 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 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 Synthflow API + MCP](https://www.anchorterminal.com/compare/gemini-live-vs-synthflow.md)\n- [GPT-Live vs Synthflow API + MCP](https://www.anchorterminal.com/compare/gpt-live-vs-synthflow.md)\n- [Harmony.ai vs Synthflow API + MCP](https://www.anchorterminal.com/compare/harmony-ai-vs-synthflow.md)\n- [Hume EVI (Empathic Voice Interface) vs Synthflow API + MCP](https://www.anchorterminal.com/compare/hume-evi-vs-synthflow.md)\n- [Inworld Realtime API vs Synthflow API + MCP](https://www.anchorterminal.com/compare/inworld-realtime-vs-synthflow.md)\n- [LiveKit Agents vs Synthflow API + MCP](https://www.anchorterminal.com/compare/livekit-agents-vs-synthflow.md)\n- [OpenAI Realtime API vs Synthflow API + MCP](https://www.anchorterminal.com/compare/openai-realtime-vs-synthflow.md)\n- [Pipecat vs Synthflow API + MCP](https://www.anchorterminal.com/compare/pipecat-vs-synthflow.md)\n- [PlaceCall vs Synthflow API + MCP](https://www.anchorterminal.com/compare/placecall-vs-synthflow.md)\n- [Retell AI API + MCP vs Synthflow API + MCP](https://www.anchorterminal.com/compare/retell-ai-vs-synthflow.md)\n- [Rime Prism vs Synthflow API + MCP](https://www.anchorterminal.com/compare/rime-prism-vs-synthflow.md)\n- [Synthflow API + MCP vs Ultravox Realtime API](https://www.anchorterminal.com/compare/synthflow-vs-ultravox.md)\n- [Synthflow API + MCP vs Vaani Developer Platform](https://www.anchorterminal.com/compare/synthflow-vs-vaani-voice.md)\n- [Synthflow API + MCP vs Vapi API + MCP](https://www.anchorterminal.com/compare/synthflow-vs-vapi.md)\n- [Synthflow API + MCP vs Vocily AI](https://www.anchorterminal.com/compare/synthflow-vs-vocily.md)\n- [Synthflow API + MCP vs Vogent API](https://www.anchorterminal.com/compare/synthflow-vs-vogent.md)\n- [CueLight vs Synthflow API + MCP](https://www.anchorterminal.com/compare/cuelight-vs-synthflow.md)\n- [Pipecat PhoneLLM vs Synthflow API + MCP](https://www.anchorterminal.com/compare/pipecat-phonellm-vs-synthflow.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 Synthflow API + MCP", "url": "" } ], "description": "Synthflow scores 47.3 (D) 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", "Synthflow API + MCP D 47.3", "scores" ], "h1": "fone.me vs Synthflow API + MCP", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/fone-me-vs-synthflow", "published": "2026-10-01", "section": "tools", "title": "fone.me vs Synthflow for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/fone-me-vs-synthflow" }, "tokens": { "markdown": 6000, "slim": 3580 }, "version": 1 }