{
  "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": "Vaani Developer Platform scores 44.6 (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": "vaani-voice",
      "name": "Vaani Developer Platform",
      "vendor": "Vaani AI Research Private Limited",
      "vendorUrl": "https://www.vaani.dev",
      "kind": "http-api",
      "category": "voice-agents",
      "summary": "Vaani is a hosted voice-agent platform from Bengaluru for outbound and inbound phone calls, browser WebRTC sessions and calling campaigns. Agents reach it through a REST API, a Python SDK and a local MCP server.",
      "url": "https://www.anchorterminal.com/tools/vaani-voice",
      "markdownUrl": "https://www.anchorterminal.com/tools/vaani-voice.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/vaani-voice.min.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/vaani-voice.json",
      "dns": "vaani-voice.grade.anchorterminal.com",
      "license": "Proprietary hosted service under Vaani AI Research's terms of service. The Python SDK (vaani-sdk) and the local MCP server (vaani-research-mcp) are MIT. The SDK's full source ships in its PyPI sdist, and the MCP server's npm package holds only the bundled JavaScript",
      "transports": [
        "http",
        "stdio"
      ],
      "remoteUrl": "https://api.vaanivoice.ai",
      "packages": [
        {
          "registry": "pypi",
          "name": "vaani-sdk"
        },
        {
          "registry": "npm",
          "name": "vaani-research-mcp"
        }
      ],
      "auth": "api-key",
      "authNotes": "An API key (`vaani_...`) sent as the `X-API-Key` header, created by a signed-in user in the dashboard under Settings, API Keys. Keys are shown once, several can be active, and rotation means creating a new one and deleting the old one. Every key reaches the whole workspace, with no per-agent, read-only or scoped keys. The live-captions WebSocket URL carries its own short-lived token in the query string, bound to one call (24 hours by default). Campaign webhooks are signed with HMAC-SHA256 over a timestamp and the body.",
      "pricing": "usage",
      "pricingNotes": "Pay as you go from a prepaid wallet. The Vaani platform fee is ₹1 ($0.02) a minute, with telephony, speech recognition, the language model and the voice billed on top at the providers' unit rates shown in the calculator. The page's illustrative production stack comes to ₹5.66 a minute. A phone number is ₹600 ($10) a month, extra concurrency ₹2,000 for 5 lines a month, and the plan includes 2 concurrent calls. Warm transfers (₹0.50) and two other add-ons are free under an early launch offer. Bringing your own provider keys needs Enterprise, which is priced on request. No free credit or trial allowance is stated (https://www.vaani.dev/pricing, checked 2026-11-02).",
      "priceSummary": "$10 / mo",
      "where": "both",
      "x402": {
        "level": "no",
        "evidence": "No x402, MPP or L402 in the docs (llms-full.txt), the OpenAPI file, the pricing page or the SDK and MCP source. Access starts with an email sign-up and a dashboard key, and calls are paid from a prepaid wallet (checked 2026-11-02).",
        "endpoints": []
      },
      "toolCount": 9,
      "popularity": {
        "githubStars": null,
        "npmWeekly": 14,
        "pypiWeekly": 19,
        "asOf": "2026-11-02"
      },
      "docsUrl": "https://docs.vaani.dev",
      "llmsTxt": "https://docs.vaani.dev/llms.txt",
      "openapi": "https://docs.vaani.dev/api-reference/openapi.json",
      "capabilities": [
        "voice.agent",
        "voice.pipeline",
        "voice.tools",
        "voice.telephony",
        "voice.recording"
      ],
      "tags": [
        "hosted",
        "india",
        "closed-source",
        "mcp",
        "openapi",
        "llms-txt",
        "python",
        "webhooks",
        "webrtc",
        "pipeline",
        "telephony",
        "prepaid",
        "usage-priced",
        "enterprise",
        "no-status-page",
        "new"
      ],
      "lastRelease": "2026-10-14",
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 44.6,
        "grade": "E",
        "agentReady": false,
        "rank": 1214,
        "ranked": true,
        "rankOf": 1510,
        "categoryRank": 24,
        "methodology": "0.7",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 64,
          "maintenance": 59,
          "payments": 22,
          "reliability": 28,
          "schema": 57,
          "security": 44,
          "transparency": 42
        },
        "pending": [
          "performance",
          "tasks"
        ],
        "assessment": {
          "confidence": "medium",
          "date": "2026-11-02"
        },
        "negative": 0,
        "verdict": "Docs are detailed and served as llms.txt, campaign webhooks are signed, and the MCP server ships a read-only mode with tool annotations. Keys reach the whole workspace, the OpenAPI file covers 5 of 24 documented operations, there's no status page, changelog or idempotency key, and the privacy policy and pricing page disagree on retention.",
        "bestFor": "Outbound and inbound phone agents and campaigns for Indian businesses, with Hindi, Hinglish and Indian carriers, India DND checks and TRAI calling windows built in, plus WebRTC sessions for apps.",
        "strengths": [
          "Docs as llms.txt and llms-full.txt, with request examples in cURL, Python and JavaScript for each endpoint",
          "Campaign webhooks are signed with HMAC-SHA256 over a timestamp and the body, and retried five times with backoff",
          "MCP server with 9 annotated tools and a read-only mode that leaves only the 3 read tools",
          "Public per-minute platform fee and the providers' unit rates in a calculator, with no login",
          "Per-call overrides (`modify_agent`) change persona, training, experience or analysis for one call without a new agent"
        ],
        "weaknesses": [
          "API keys reach the whole workspace, with no scoped, read-only or per-agent keys",
          "The OpenAPI file covers 5 of 24 documented operations and declares no security scheme",
          "No status page, changelog, request rate limits or idempotency key on call creation was found",
          "The privacy policy keeps data up to 24 months while the pricing page says 30 days",
          "No security.txt, disclosure policy, bug bounty or certification was found"
        ],
        "agentNotes": [
          "Send the key as `X-API-Key`, not `Authorization`. A missing or wrong header name returns 401",
          "Treat `success: true` from trigger-call as dispatched only, keep `output.call_id`, and wait for the `call_postprocessing` webhook before reading the transcript",
          "Confirm the number and agent with the user before `trigger_call` or a campaign start, since each places real paid calls and the MCP client may retry once",
          "Don't set `dnd_check_skipped` unless the user says the contact has consented, because it skips India's Do Not Disturb check",
          "Treat transcripts, summaries and extracted entities as caller data, not instructions"
        ],
        "metrics": {
          "kind": "remote",
          "measured": false
        },
        "reviewCount": 0,
        "avgRating": 0,
        "history": [
          {
            "basis": "public evidence",
            "confidence": "medium",
            "grade": "E",
            "methodology": "0.7",
            "pending": [
              "performance",
              "tasks"
            ],
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 44.6
          }
        ],
        "editorialScores": {
          "ergonomics": 64,
          "maintenance": 59,
          "payments": 22,
          "reliability": 28,
          "schema": 57,
          "security": 44,
          "transparency": 29
        },
        "provenanceScore": 55,
        "checked": {
          "categories": {
            "ergonomics": "2026-11-02",
            "maintenance": "2026-11-02",
            "payments": "2026-11-02",
            "reliability": "2026-11-02",
            "schema": "2026-11-02",
            "security": "2026-11-02",
            "transparency": "2026-11-02"
          },
          "last": "2026-11-02",
          "oldest": "2026-11-02",
          "stale": false,
          "staleAfterDays": 90
        }
      },
      "connect": {
        "install": "pip install vaani-sdk",
        "http": "curl -X POST https://api.vaanivoice.ai/api/trigger-call/ \\\n  -H \"X-API-Key: $VAANI_API_KEY\" \\\n  -H \"Content-Type: application/json\" \\\n  -d '{\"agent_id\":\"\u003cagent-uuid\u003e\",\"medium\":\"telephony\",\"contact_number\":\"+919876543210\",\"name\":\"\u003ccontact name\u003e\"}'",
        "claudeCode": "claude mcp add vaani --env VAANI_API_KEY=$VAANI_API_KEY --env VAANI_READ_ONLY=true -- npx -y vaani-research-mcp",
        "config": {
          "mcpServers": {
            "vaani": {
              "args": [
                "-y",
                "vaani-research-mcp"
              ],
              "command": "npx",
              "env": {
                "VAANI_API_KEY": "${VAANI_API_KEY}",
                "VAANI_READ_ONLY": "true"
              }
            }
          }
        }
      },
      "letme": {
        "capability": "https://letme.dev/voice.agent",
        "tool": "https://letme.dev/vaani-voice"
      },
      "area": "voice",
      "unitPrices": [
        {
          "item": "Platform fee, pay as you go",
          "unit": "call-minute",
          "usd": 0.02,
          "note": "₹1 a minute. Telephony, speech recognition, LLM and voice billed on top at provider rates"
        },
        {
          "item": "Phone number rental",
          "unit": "month",
          "usd": 10,
          "note": "₹600 a month, varies by country"
        },
        {
          "item": "Warm transfer",
          "unit": "tx",
          "usd": 0.01,
          "note": "₹0.50 a transfer, free under the early launch offer. The transferred leg's telephony is extra"
        }
      ],
      "provenance": {
        "legalEntity": "Vaani AI Research Private Limited (Bengaluru, India, CIN U62099KA2025PTC201212)",
        "domain": "vaani.dev",
        "domainRegistered": "2026-10-02",
        "domainNote": "vaani.dev is a new brand domain, registered on 2 October 2026 per RDAP. The API and docs host vaanivoice.ai was registered on 11 March 2026, and the company domain vaaniresearch.com on 18 July 2024.",
        "endpointOnVendorDomain": true,
        "terms": "https://www.vaani.dev/legal/terms",
        "privacy": "https://www.vaani.dev/legal/privacy",
        "statusPage": "",
        "changelog": "",
        "securityTxt": "none",
        "checked": "2026-11-02",
        "notes": [
          "The terms and privacy policy name Vaani AI Research Private Limited, registered under Indian law at 17, 2nd Floor, 7th Main Road, II Stage, Hoysala Nagar, Indiranagar, Bengaluru 560038, with Indian law and Bengaluru courts. The terms footer gives the CIN U62099KA2025PTC201212. Neither page carries a date.",
          "The terms are written for the website www.vaaniresearch.com and cover acceptable use, liability and termination without notice. They say nothing about billing, refunds, API use or customer data.",
          "No security.txt on www.vaani.dev or www.vaaniresearch.com (404). status.vaani.dev and status.vaanivoice.ai don't resolve and no status page is linked.",
          "No changelog or release notes page was found in the docs or on the site. PyPI and npm release dates are the only dated record.",
          "docs.vaani.dev's robots.txt allows crawling and carries Content-Signal ai-train=yes, search=yes, ai-input=yes. www.vaani.dev and www.vaaniresearch.com answer robots.txt with 404."
        ],
        "score": 55
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/vaani-voice.json",
      "live": {
        "slug": "vaani-voice",
        "probe": {
          "target": "https://api.vaanivoice.ai",
          "method": "get",
          "lastAt": "2026-11-07T19:22:42.583651588Z",
          "lastOk": true,
          "lastStatus": 200,
          "lastMs": 781,
          "authRequired": false,
          "uptime24h": 100,
          "uptime30d": 100,
          "p50ms24h": 710,
          "p95ms24h": 912,
          "samples24h": 238,
          "samples30d": 1250,
          "days": [
            {
              "date": "2026-11-02",
              "probes": 133,
              "ok": 133
            },
            {
              "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
            }
          ]
        },
        "versions": [
          {
            "registry": "npm",
            "name": "vaani-research-mcp",
            "version": "0.1.1",
            "seenAt": "2026-11-07T00:14:31.178305746Z"
          },
          {
            "registry": "pypi",
            "name": "vaani-sdk",
            "version": "0.3.1",
            "released": "2026-09-28",
            "seenAt": "2026-11-07T00:14:30.883134724Z"
          }
        ],
        "npmWeekly": 17,
        "pypiWeekly": 23,
        "securityTxt": {
          "url": "https://vaani.dev/.well-known/security.txt",
          "state": "none",
          "checkedAt": "2026-11-07T16:01:36.172191348Z"
        },
        "llmsTxt": {
          "url": "https://docs.vaani.dev/llms.txt",
          "ok": true,
          "status": 200,
          "checkedAt": "2026-11-07T15:34:15.815128709Z"
        },
        "pages": [
          {
            "url": "https://www.vaani.dev/pricing",
            "kind": "pricing",
            "status": 200,
            "checkedAt": "2026-11-07T14:36:27.424648185Z",
            "changedAt": "0001-01-01T00:00:00Z",
            "fingerprint": "8b61ea69c446"
          },
          {
            "url": "https://www.vaani.dev/legal/privacy",
            "kind": "privacy",
            "status": 200,
            "checkedAt": "2026-11-07T14:36:23.232334034Z",
            "changedAt": "0001-01-01T00:00:00Z",
            "fingerprint": "680a5d8fb534"
          },
          {
            "url": "https://www.vaani.dev/legal/terms",
            "kind": "terms",
            "status": 200,
            "checkedAt": "2026-11-07T14:36:25.399816113Z",
            "changedAt": "0001-01-01T00:00:00Z",
            "fingerprint": "30d77be4b4f4"
          }
        ],
        "updatedAt": "2026-11-07T19:22:42.583651588Z"
      }
    },
    "edges": [
      {
        "by": 36,
        "category": "maintenance",
        "leads": "vaani-voice",
        "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": "vaani-research-mcp 0.1.1 on 2026-10-14 (30). In the last 90 days, vaani-sdk 0.3.1 on 28 September and three npm versions (0.0.0-stage, 0.1.0, 0.1.1) within 40 minutes on 14 October. No dated changelog, so half (10 of 20). A closed service with no public changelog, issue tracker or community channel found. Contact is hello@vaaniresearch.com and a booking link, and we didn't test whether they answer. The MCP repository on GitHub couldn't be read from this session (4 of 15, the closed-service reading). A current official Python SDK, released seven times since April 2026. The MCP server isn't in the official MCP registry (10 of 15). The SDK's sdist ships its tests and current httpx and pydantic dependencies, and the MCP package runs its tests before publishing, but no public CI was found and the SDK has no repository (5 of 10). 30+10+4+10+5 = 59."
        },
        "scores": {
          "a": 23,
          "b": 59
        }
      },
      {
        "by": 35,
        "category": "ergonomics",
        "leads": "vaani-voice",
        "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": "The local MCP server loads 9 compact tools, and `VAANI_READ_ONLY=true` leaves 3. Transcripts are cut at 20,000 characters by default with a note. The REST API has no field selection or summaries, so 3 off (22 of 25). Call history pages by `page` and `page_size` up to 200 with no filters. The MCP agent filter runs client-side on one page. Agents filter by `search` and `published_only` and campaigns by `status` (12 of 20). Campaign errors carry a machine-readable `code`, a message, the path and a `request_id` (shown as \"unknown\" in the example). Validation errors list the field location, the SDK maps each status to a typed exception including 402 for a low wallet, and the MCP server adds a hint per status (15 of 20). All 9 MCP tools carry readOnlyHint, destructiveHint and idempotentHint, with `trigger_call` and `campaign_action` marked destructive. No idempotency key on trigger-call, and the MCP client retries a POST once after a timeout or 5xx, so a call can be placed twice. The webhook docs say to deduplicate by event id (8 of 20). A call needs `agent_id`, `contact_number` and `name`, with `medium` defaulting to telephony. One official SDK, Python, sync and async. The npm package is an MCP server, not an SDK (7 of 15). 22+12+15+8+7 = 64."
        },
        "scores": {
          "a": 29,
          "b": 64
        }
      },
      {
        "by": 28,
        "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 ₹1 ($0.02) a minute platform fee, number rental, concurrency lines and add-ons are public, and the calculator shows each provider's unit rate without a login. Registry checks, extraction and evaluations \"can add separate charges\" that aren't priced, and the billing pulse depends on the account, so 3 off (17 of 20). The home page says \"Start free on Vaani's Platform\", but the pricing page states a prepaid wallet with no free credit, trial minutes or card rule, and we didn't sign up to check, so 5 of 20. A person signs up with email verification at platform.vaani.dev and creates keys in the dashboard (0). 0+17+5+0 = 22."
        },
        "scores": {
          "a": 50,
          "b": 22
        }
      },
      {
        "by": 26,
        "category": "schema",
        "leads": "vaani-voice",
        "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.1 file at docs.vaani.dev/api-reference/openapi.json, version 2.0.0, but it holds 5 of the 24 operations in the API reference (trigger-call, call history, transcript, stream, call details). It declares the key only as a header parameter with no security scheme, its trigger-call schema leaves out `medium` and `modify_agent`, and four response schemas are empty. The MCP tools have typed zod inputs (8 of 25). llms.txt, llms-full.txt and a Markdown copy of each page on Mintlify (10). Pages explain what each route is for and warn where it matters, such as dispatch acceptance not meaning a completed call, transcripts returning 404 while processing, and real paid calls from trigger_call (14 of 20). Ranges and enums are documented (`medium`, `voice_speed` 0.6 to 1.4, `page_size` up to 200, campaign retries 1 to 10, campaign status), but `metadata`, `modify_agent` and three MCP tool payloads are free-form objects (9 of 15). Request examples in cURL, Python and JavaScript on every endpoint, a campaign error-code table, 422 and 404 bodies and an SDK exception table by status. No single error reference for the whole API (12 of 15). The docs state API version 2.0.0, but no changelog or release notes page was found (4 of 15). 8+10+14+9+12+4 = 57."
        },
        "scores": {
          "a": 31,
          "b": 57
        }
      },
      {
        "by": 19,
        "category": "transparency",
        "leads": "vaani-voice",
        "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": "A closed service. The terms name Vaani AI Research Private Limited, its Bengaluru address, CIN, Indian law and Bengaluru courts, but they're undated, written for the website www.vaaniresearch.com, and say nothing on billing, refunds, API use or customer data. The SDK and MCP server are MIT, with the SDK's full source in its PyPI sdist (14 of 30). The privacy policy (undated) keeps data, including voice recordings, for up to 24 months, while the pricing table gives 30 days' retention on pay as you go and zero retention on Enterprise. Voice data trains models only with explicit consent. No DPA found (8 of 30). No deprecation policy. The privacy policy promises 15 days' notice of significant changes, and the terms allow changes and termination without notice (2 of 20). The privacy policy names vendor categories (cloud hosting, analytics, voice transcription) and says data may be stored outside India. Model and telephony providers can be read from the calculator, and India data residency is offered on demand. No subprocessor list or data location for the hosted service (5 of 20). 14+8+2+5 = 29."
        },
        "scores": {
          "a": 23,
          "b": 42
        }
      },
      {
        "by": 14,
        "category": "security",
        "leads": "vaani-voice",
        "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": "Plain revocable API keys, shown once, several active at a time and rotated by creating a new key and deleting the old one. Every key reaches the whole workspace, with no scoped, read-only or per-agent keys (20). Campaign webhooks are signed with HMAC-SHA256 over a timestamp and the body, with a five-minute replay window in the example (+2). The live-captions URL carries a call-bound token in the query string for 24 hours by default, the documented way for browsers to connect, so 3 off as a judgement call, less than the full 10 because it isn't the account key (19 of 30). The MCP server has a read-only mode and destructive annotations, and its docs, tool descriptions and bundled prompt say to confirm the number and agent with the user before a call. The API itself has no read-only key and nothing stops a call without confirmation (12 of 20). The tool returns transcripts, summaries and entities drawn from callers' speech. No guidance on treating them as untrusted data was found. Agent guardrails exist for the voice agent's own replies (3 of 15). Each call keeps a record in call history and call details, and keys are labelled so calls can be traced to a key, but no account or key audit log is documented (7 of 15). No security.txt (404 on both domains), disclosure policy, bug bounty or certification. vaaniresearch.com marks its security standards \"In Progress\", the pricing page lists HIPAA compliance on Enterprise with no report or BAA found, and the privacy policy promises breach notice in line with applicable law (3 of 20). 19+12+3+7+3 = 44."
        },
        "scores": {
          "a": 30,
          "b": 44
        }
      }
    ],
    "facts": [
      {
        "a": "Platform",
        "b": "HTTP API",
        "name": "Kind"
      },
      {
        "a": "Fone",
        "b": "Vaani AI Research Private Limited",
        "name": "Vendor"
      },
      {
        "a": "https://www.fone.me/mcp",
        "b": "https://api.vaanivoice.ai",
        "name": "Hosted endpoint"
      },
      {
        "a": "Streamable HTTP",
        "b": "HTTP, stdio",
        "name": "Transports"
      },
      {
        "a": "None",
        "b": "API key",
        "name": "Auth"
      },
      {
        "a": "Freemium",
        "b": "Pay per use",
        "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": "Proprietary hosted service under Vaani AI Research's terms of service. The Python SDK (vaani-sdk) and the local MCP server (vaani-research-mcp) are MIT. The SDK's full source ships in its PyPI sdist, and the MCP server's npm package holds only the bundled JavaScript",
        "name": "Licence"
      },
      {
        "a": "4",
        "b": "9",
        "name": "Tools exposed"
      },
      {
        "a": "no",
        "b": "yes",
        "name": "Read-only variant documented"
      },
      {
        "a": "yes",
        "b": "yes",
        "name": "llms.txt"
      },
      {
        "a": "2026-10-05",
        "b": "2026-10-14",
        "name": "Last release"
      },
      {
        "a": "couldn't be read",
        "b": "no date given",
        "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": "yes",
        "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": "14 npm/wk, 19 PyPI/wk",
        "name": "Popularity"
      }
    ],
    "faq": [
      {
        "answer": "Vaani Developer Platform scores 44.6 (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 Vaani Developer Platform?"
      },
      {
        "answer": "Yes. fone.me has a hosted endpoint at https://www.fone.me/mcp and Vaani Developer Platform at https://api.vaanivoice.ai.",
        "question": "Can an agent call fone.me and Vaani Developer Platform without installing anything?"
      }
    ],
    "goodFor": [
      {
        "aheadOn": [
          "Payments \u0026 pricing, 50 against 22"
        ],
        "also": [
          "No key needed to call it"
        ],
        "goodFor": "Agents acting for a person who need to reach a freelancer's, shop's or small business's own AI agent at its fone.me link to ask a question, request a booking or quote or leave a message, and owners who want an answering agent on a link, WhatsApp, Telegram and a $9.99 number without building one.",
        "slug": "fone-me",
        "watchFor": "No tool arguments, input schemas, annotations, error shapes or rate limits are published for the MCP server or A2A endpoints"
      },
      {
        "aheadOn": [
          "Reliability, 28 against 15",
          "Schema \u0026 documentation, 57 against 31",
          "Agent ergonomics, 64 against 29",
          "Security \u0026 auth, 44 against 30",
          "Maintenance \u0026 community, 59 against 23",
          "Transparency \u0026 trust, 42 against 23"
        ],
        "also": [
          "Runs on your own machine"
        ],
        "goodFor": "Outbound and inbound phone agents and campaigns for Indian businesses, with Hindi, Hinglish and Indian carriers, India DND checks and TRAI calling windows built in, plus WebRTC sessions for apps.",
        "slug": "vaani-voice",
        "watchFor": "API keys reach the whole workspace, with no scoped, read-only or per-agent keys"
      }
    ],
    "history": null,
    "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-vaani-voice.json",
        "title": "Amazon Nova 2 Sonic vs Vaani Developer Platform",
        "url": "https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-vaani-voice"
      },
      {
        "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-vaani-voice.json",
        "title": "AssemblyAI Voice Agent API vs Vaani Developer Platform",
        "url": "https://www.anchorterminal.com/compare/assemblyai-voice-agent-vs-vaani-voice"
      },
      {
        "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-vaani-voice.json",
        "title": "Bland AI API + MCP vs Vaani Developer Platform",
        "url": "https://www.anchorterminal.com/compare/bland-ai-vs-vaani-voice"
      },
      {
        "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-vaani-voice.json",
        "title": "Bolna API + MCP vs Vaani Developer Platform",
        "url": "https://www.anchorterminal.com/compare/bolna-vs-vaani-voice"
      },
      {
        "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-vaani-voice.json",
        "title": "Deepgram Voice Agent API vs Vaani Developer Platform",
        "url": "https://www.anchorterminal.com/compare/deepgram-voice-agent-vs-vaani-voice"
      },
      {
        "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-vaani-voice.json",
        "title": "ElevenLabs Agents API + MCP vs Vaani Developer Platform",
        "url": "https://www.anchorterminal.com/compare/elevenlabs-agents-vs-vaani-voice"
      },
      {
        "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-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-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-vaani-voice.json",
        "title": "Gemini Live API vs Vaani Developer Platform",
        "url": "https://www.anchorterminal.com/compare/gemini-live-vs-vaani-voice"
      },
      {
        "json": "https://www.anchorterminal.com/compare/gpt-live-vs-vaani-voice.json",
        "title": "GPT-Live vs Vaani Developer Platform",
        "url": "https://www.anchorterminal.com/compare/gpt-live-vs-vaani-voice"
      },
      {
        "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/hume-evi-vs-vaani-voice.json",
        "title": "Hume EVI (Empathic Voice Interface) vs Vaani Developer Platform",
        "url": "https://www.anchorterminal.com/compare/hume-evi-vs-vaani-voice"
      },
      {
        "json": "https://www.anchorterminal.com/compare/inworld-realtime-vs-vaani-voice.json",
        "title": "Inworld Realtime API vs Vaani Developer Platform",
        "url": "https://www.anchorterminal.com/compare/inworld-realtime-vs-vaani-voice"
      },
      {
        "json": "https://www.anchorterminal.com/compare/livekit-agents-vs-vaani-voice.json",
        "title": "LiveKit Agents vs Vaani Developer Platform",
        "url": "https://www.anchorterminal.com/compare/livekit-agents-vs-vaani-voice"
      },
      {
        "json": "https://www.anchorterminal.com/compare/openai-realtime-vs-vaani-voice.json",
        "title": "OpenAI Realtime API vs Vaani Developer Platform",
        "url": "https://www.anchorterminal.com/compare/openai-realtime-vs-vaani-voice"
      },
      {
        "json": "https://www.anchorterminal.com/compare/pipecat-vs-vaani-voice.json",
        "title": "Pipecat vs Vaani Developer Platform",
        "url": "https://www.anchorterminal.com/compare/pipecat-vs-vaani-voice"
      },
      {
        "json": "https://www.anchorterminal.com/compare/placecall-vs-vaani-voice.json",
        "title": "PlaceCall vs Vaani Developer Platform",
        "url": "https://www.anchorterminal.com/compare/placecall-vs-vaani-voice"
      },
      {
        "json": "https://www.anchorterminal.com/compare/retell-ai-vs-vaani-voice.json",
        "title": "Retell AI API + MCP vs Vaani Developer Platform",
        "url": "https://www.anchorterminal.com/compare/retell-ai-vs-vaani-voice"
      },
      {
        "json": "https://www.anchorterminal.com/compare/rime-prism-vs-vaani-voice.json",
        "title": "Rime Prism vs Vaani Developer Platform",
        "url": "https://www.anchorterminal.com/compare/rime-prism-vs-vaani-voice"
      },
      {
        "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/ultravox-vs-vaani-voice.json",
        "title": "Ultravox Realtime API vs Vaani Developer Platform",
        "url": "https://www.anchorterminal.com/compare/ultravox-vs-vaani-voice"
      },
      {
        "json": "https://www.anchorterminal.com/compare/vaani-voice-vs-vapi.json",
        "title": "Vaani Developer Platform vs Vapi API + MCP",
        "url": "https://www.anchorterminal.com/compare/vaani-voice-vs-vapi"
      },
      {
        "json": "https://www.anchorterminal.com/compare/vaani-voice-vs-vocily.json",
        "title": "Vaani Developer Platform vs Vocily AI",
        "url": "https://www.anchorterminal.com/compare/vaani-voice-vs-vocily"
      },
      {
        "json": "https://www.anchorterminal.com/compare/vaani-voice-vs-vogent.json",
        "title": "Vaani Developer Platform vs Vogent API",
        "url": "https://www.anchorterminal.com/compare/vaani-voice-vs-vogent"
      },
      {
        "json": "https://www.anchorterminal.com/compare/cuelight-vs-vaani-voice.json",
        "title": "CueLight vs Vaani Developer Platform",
        "url": "https://www.anchorterminal.com/compare/cuelight-vs-vaani-voice"
      },
      {
        "json": "https://www.anchorterminal.com/compare/pipecat-phonellm-vs-vaani-voice.json",
        "title": "Pipecat PhoneLLM vs Vaani Developer Platform",
        "url": "https://www.anchorterminal.com/compare/pipecat-phonellm-vs-vaani-voice"
      }
    ],
    "panel": null,
    "scores": [
      {
        "by": 13,
        "edge": "vaani-voice",
        "fone-me": 15,
        "key": "reliability",
        "name": "Reliability",
        "vaani-voice": 28,
        "weight": 16
      },
      {
        "key": "performance",
        "name": "Performance",
        "pending": true,
        "weight": 10
      },
      {
        "by": 26,
        "edge": "vaani-voice",
        "fone-me": 31,
        "key": "schema",
        "name": "Schema \u0026 documentation",
        "vaani-voice": 57,
        "weight": 13
      },
      {
        "by": 35,
        "edge": "vaani-voice",
        "fone-me": 29,
        "key": "ergonomics",
        "name": "Agent ergonomics",
        "vaani-voice": 64,
        "weight": 13
      },
      {
        "by": 14,
        "edge": "vaani-voice",
        "fone-me": 30,
        "key": "security",
        "name": "Security \u0026 auth",
        "vaani-voice": 44,
        "weight": 14
      },
      {
        "by": 28,
        "edge": "fone-me",
        "fone-me": 50,
        "key": "payments",
        "name": "Payments \u0026 pricing",
        "vaani-voice": 22,
        "weight": 10
      },
      {
        "key": "tasks",
        "name": "Task success",
        "pending": true,
        "weight": 10
      },
      {
        "by": 36,
        "edge": "vaani-voice",
        "fone-me": 23,
        "key": "maintenance",
        "name": "Maintenance \u0026 community",
        "vaani-voice": 59,
        "weight": 7
      },
      {
        "by": 19,
        "edge": "vaani-voice",
        "fone-me": 23,
        "key": "transparency",
        "name": "Transparency \u0026 trust",
        "vaani-voice": 42,
        "weight": 7
      }
    ],
    "summary": "Vaani Developer Platform scores 44.6 (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.",
      "vaani-voice": "Docs are detailed and served as llms.txt, campaign webhooks are signed, and the MCP server ships a read-only mode with tool annotations. Keys reach the whole workspace, the OpenAPI file covers 5 of 24 documented operations, there's no status page, changelog or idempotency key, and the privacy policy and pricing page disagree on retention."
    }
  },
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/compare/fone-me-vs-vaani-voice",
    "json": "https://www.anchorterminal.com/compare/fone-me-vs-vaani-voice.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/compare/fone-me-vs-vaani-voice.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/compare/fone-me-vs-vaani-voice.min.md"
  },
  "markdown": "Vaani Developer Platform scores 44.6 (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- Vaani Developer Platform: grade E, 44.6/100, rank #1214 of 1510. Markdown https://www.anchorterminal.com/tools/vaani-voice.md · JSON https://www.anchorterminal.com/api/v1/tools/vaani-voice.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 22\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### Vaani Developer Platform (E)\n\nGood for: Outbound and inbound phone agents and campaigns for Indian businesses, with Hindi, Hinglish and Indian carriers, India DND checks and TRAI calling windows built in, plus WebRTC sessions for apps.\n\nAhead on:\n- Reliability, 28 against 15\n- Schema \u0026 documentation, 57 against 31\n- Agent ergonomics, 64 against 29\n- Security \u0026 auth, 44 against 30\n- Maintenance \u0026 community, 59 against 23\n- Transparency \u0026 trust, 42 against 23\n\nAlso in its favour:\n- Runs on your own machine\n\nWatch for: API keys reach the whole workspace, with no scoped, read-only or per-agent keys\n\n\n## Why the edge\n\n### Maintenance \u0026 community: Vaani Developer Platform +36\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- Vaani Developer Platform (59): vaani-research-mcp 0.1.1 on 2026-10-14 (30). In the last 90 days, vaani-sdk 0.3.1 on 28 September and three npm versions (0.0.0-stage, 0.1.0, 0.1.1) within 40 minutes on 14 October. No dated changelog, so half (10 of 20). A closed service with no public changelog, issue tracker or community channel found. Contact is hello@vaaniresearch.com and a booking link, and we didn't test whether they answer. The MCP repository on GitHub couldn't be read from this session (4 of 15, the closed-service reading). A current official Python SDK, released seven times since April 2026. The MCP server isn't in the official MCP registry (10 of 15). The SDK's sdist ships its tests and current httpx and pydantic dependencies, and the MCP package runs its tests before publishing, but no public CI was found and the SDK has no repository (5 of 10). 30+10+4+10+5 = 59.\n\n### Agent ergonomics: Vaani Developer Platform +35\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- Vaani Developer Platform (64): The local MCP server loads 9 compact tools, and `VAANI_READ_ONLY=true` leaves 3. Transcripts are cut at 20,000 characters by default with a note. The REST API has no field selection or summaries, so 3 off (22 of 25). Call history pages by `page` and `page_size` up to 200 with no filters. The MCP agent filter runs client-side on one page. Agents filter by `search` and `published_only` and campaigns by `status` (12 of 20). Campaign errors carry a machine-readable `code`, a message, the path and a `request_id` (shown as \"unknown\" in the example). Validation errors list the field location, the SDK maps each status to a typed exception including 402 for a low wallet, and the MCP server adds a hint per status (15 of 20). All 9 MCP tools carry readOnlyHint, destructiveHint and idempotentHint, with `trigger_call` and `campaign_action` marked destructive. No idempotency key on trigger-call, and the MCP client retries a POST once after a timeout or 5xx, so a call can be placed twice. The webhook docs say to deduplicate by event id (8 of 20). A call needs `agent_id`, `contact_number` and `name`, with `medium` defaulting to telephony. One official SDK, Python, sync and async. The npm package is an MCP server, not an SDK (7 of 15). 22+12+15+8+7 = 64.\n\n### Payments \u0026 pricing: fone.me +28\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- Vaani Developer Platform (22): No x402, MPP or L402 (0 of 40). The ₹1 ($0.02) a minute platform fee, number rental, concurrency lines and add-ons are public, and the calculator shows each provider's unit rate without a login. Registry checks, extraction and evaluations \"can add separate charges\" that aren't priced, and the billing pulse depends on the account, so 3 off (17 of 20). The home page says \"Start free on Vaani's Platform\", but the pricing page states a prepaid wallet with no free credit, trial minutes or card rule, and we didn't sign up to check, so 5 of 20. A person signs up with email verification at platform.vaani.dev and creates keys in the dashboard (0). 0+17+5+0 = 22.\n\n### Schema \u0026 documentation: Vaani Developer Platform +26\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- Vaani Developer Platform (57): A public OpenAPI 3.1 file at docs.vaani.dev/api-reference/openapi.json, version 2.0.0, but it holds 5 of the 24 operations in the API reference (trigger-call, call history, transcript, stream, call details). It declares the key only as a header parameter with no security scheme, its trigger-call schema leaves out `medium` and `modify_agent`, and four response schemas are empty. The MCP tools have typed zod inputs (8 of 25). llms.txt, llms-full.txt and a Markdown copy of each page on Mintlify (10). Pages explain what each route is for and warn where it matters, such as dispatch acceptance not meaning a completed call, transcripts returning 404 while processing, and real paid calls from trigger_call (14 of 20). Ranges and enums are documented (`medium`, `voice_speed` 0.6 to 1.4, `page_size` up to 200, campaign retries 1 to 10, campaign status), but `metadata`, `modify_agent` and three MCP tool payloads are free-form objects (9 of 15). Request examples in cURL, Python and JavaScript on every endpoint, a campaign error-code table, 422 and 404 bodies and an SDK exception table by status. No single error reference for the whole API (12 of 15). The docs state API version 2.0.0, but no changelog or release notes page was found (4 of 15). 8+10+14+9+12+4 = 57.\n\n### Transparency \u0026 trust: Vaani Developer Platform +19\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- Vaani Developer Platform (42): A closed service. The terms name Vaani AI Research Private Limited, its Bengaluru address, CIN, Indian law and Bengaluru courts, but they're undated, written for the website www.vaaniresearch.com, and say nothing on billing, refunds, API use or customer data. The SDK and MCP server are MIT, with the SDK's full source in its PyPI sdist (14 of 30). The privacy policy (undated) keeps data, including voice recordings, for up to 24 months, while the pricing table gives 30 days' retention on pay as you go and zero retention on Enterprise. Voice data trains models only with explicit consent. No DPA found (8 of 30). No deprecation policy. The privacy policy promises 15 days' notice of significant changes, and the terms allow changes and termination without notice (2 of 20). The privacy policy names vendor categories (cloud hosting, analytics, voice transcription) and says data may be stored outside India. Model and telephony providers can be read from the calculator, and India data residency is offered on demand. No subprocessor list or data location for the hosted service (5 of 20). 14+8+2+5 = 29.\n\n### Security \u0026 auth: Vaani Developer Platform +14\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- Vaani Developer Platform (44): Plain revocable API keys, shown once, several active at a time and rotated by creating a new key and deleting the old one. Every key reaches the whole workspace, with no scoped, read-only or per-agent keys (20). Campaign webhooks are signed with HMAC-SHA256 over a timestamp and the body, with a five-minute replay window in the example (+2). The live-captions URL carries a call-bound token in the query string for 24 hours by default, the documented way for browsers to connect, so 3 off as a judgement call, less than the full 10 because it isn't the account key (19 of 30). The MCP server has a read-only mode and destructive annotations, and its docs, tool descriptions and bundled prompt say to confirm the number and agent with the user before a call. The API itself has no read-only key and nothing stops a call without confirmation (12 of 20). The tool returns transcripts, summaries and entities drawn from callers' speech. No guidance on treating them as untrusted data was found. Agent guardrails exist for the voice agent's own replies (3 of 15). Each call keeps a record in call history and call details, and keys are labelled so calls can be traced to a key, but no account or key audit log is documented (7 of 15). No security.txt (404 on both domains), disclosure policy, bug bounty or certification. vaaniresearch.com marks its security standards \"In Progress\", the pricing page lists HIPAA compliance on Enterprise with no report or BAA found, and the privacy policy promises breach notice in line with applicable law (3 of 20). 19+12+3+7+3 = 44.\n\n## Score by category\n\n| Category | Weight | fone.me | Vaani Developer Platform | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 15 | 28 | Vaani Developer Platform +13 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 31 | 57 | Vaani Developer Platform +26 |\n| Agent ergonomics | 13% (16.2 this run) | 29 | 64 | Vaani Developer Platform +35 |\n| Security \u0026 auth | 14% (17.5 this run) | 30 | 44 | Vaani Developer Platform +14 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 50 | 22 | fone.me +28 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 23 | 59 | Vaani Developer Platform +36 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 23 | 42 | Vaani Developer Platform +19 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **28.3 · F** | **44.6 · E** | |\n\n## Facts side by side\n\n| Fact | fone.me | Vaani Developer Platform |\n| --- | --- | --- |\n| Kind | Platform | HTTP API |\n| Vendor | Fone | Vaani AI Research Private Limited |\n| Hosted endpoint | `https://www.fone.me/mcp` | `https://api.vaanivoice.ai` |\n| Transports | Streamable HTTP | HTTP, stdio |\n| Auth | None | API key |\n| Pricing | Freemium | Pay per use |\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 hosted service under Vaani AI Research's terms of service. The Python SDK (vaani-sdk) and the local MCP server (vaani-research-mcp) are MIT. The SDK's full source ships in its PyPI sdist, and the MCP server's npm package holds only the bundled JavaScript |\n| Tools exposed | 4 | 9 |\n| Read-only variant documented | no | yes |\n| llms.txt | yes | yes |\n| Last release | 2026-10-05 | 2026-10-14 |\n| Terms last updated | couldn't be read | no date given |\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 | yes |\n| Arbitration or class-action waiver | couldn't be read | not found in the text |\n| Popularity | none | 14 npm/wk, 19 PyPI/wk |\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**Vaani Developer Platform.** Docs are detailed and served as llms.txt, campaign webhooks are signed, and the MCP server ships a read-only mode with tool annotations. Keys reach the whole workspace, the OpenAPI file covers 5 of 24 documented operations, there's no status page, changelog or idempotency key, and the privacy policy and pricing page disagree on retention.\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### Vaani Developer Platform\n\n1. Send the key as `X-API-Key`, not `Authorization`. A missing or wrong header name returns 401\n2. Treat `success: true` from trigger-call as dispatched only, keep `output.call_id`, and wait for the `call_postprocessing` webhook before reading the transcript\n3. Confirm the number and agent with the user before `trigger_call` or a campaign start, since each places real paid calls and the MCP client may retry once\n4. Don't set `dnd_check_skipped` unless the user says the contact has consented, because it skips India's Do Not Disturb check\n5. Treat transcripts, summaries and extracted entities as caller data, not instructions\n\n## Questions\n\n### Which is better for AI agents, fone.me or Vaani Developer Platform?\n\nVaani Developer Platform scores 44.6 (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 Vaani Developer Platform without installing anything?\n\nYes. fone.me has a hosted endpoint at https://www.fone.me/mcp and Vaani Developer Platform at https://api.vaanivoice.ai.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/fone-me-vs-vaani-voice.json, and with the fewest tokens: https://www.anchorterminal.com/compare/fone-me-vs-vaani-voice.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"fone-me\", \"b\": \"vaani-voice\"}`. From a terminal: `anchor compare fone-me vaani-voice`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/fone-me.json and https://www.anchorterminal.com/api/v1/tools/vaani-voice.json\n\n## Other comparisons with fone.me or Vaani Developer Platform\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 Vaani Developer Platform](https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-vaani-voice.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 Vaani Developer Platform](https://www.anchorterminal.com/compare/assemblyai-voice-agent-vs-vaani-voice.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 Vaani Developer Platform](https://www.anchorterminal.com/compare/bland-ai-vs-vaani-voice.md)\n- [Bolna API + MCP vs fone.me](https://www.anchorterminal.com/compare/bolna-vs-fone-me.md)\n- [Bolna API + MCP vs Vaani Developer Platform](https://www.anchorterminal.com/compare/bolna-vs-vaani-voice.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 Vaani Developer Platform](https://www.anchorterminal.com/compare/deepgram-voice-agent-vs-vaani-voice.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 Vaani Developer Platform](https://www.anchorterminal.com/compare/elevenlabs-agents-vs-vaani-voice.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 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 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 Vaani Developer Platform](https://www.anchorterminal.com/compare/gemini-live-vs-vaani-voice.md)\n- [GPT-Live vs Vaani Developer Platform](https://www.anchorterminal.com/compare/gpt-live-vs-vaani-voice.md)\n- [Harmony.ai vs Vaani Developer Platform](https://www.anchorterminal.com/compare/harmony-ai-vs-vaani-voice.md)\n- [Hume EVI (Empathic Voice Interface) vs Vaani Developer Platform](https://www.anchorterminal.com/compare/hume-evi-vs-vaani-voice.md)\n- [Inworld Realtime API vs Vaani Developer Platform](https://www.anchorterminal.com/compare/inworld-realtime-vs-vaani-voice.md)\n- [LiveKit Agents vs Vaani Developer Platform](https://www.anchorterminal.com/compare/livekit-agents-vs-vaani-voice.md)\n- [OpenAI Realtime API vs Vaani Developer Platform](https://www.anchorterminal.com/compare/openai-realtime-vs-vaani-voice.md)\n- [Pipecat vs Vaani Developer Platform](https://www.anchorterminal.com/compare/pipecat-vs-vaani-voice.md)\n- [PlaceCall vs Vaani Developer Platform](https://www.anchorterminal.com/compare/placecall-vs-vaani-voice.md)\n- [Retell AI API + MCP vs Vaani Developer Platform](https://www.anchorterminal.com/compare/retell-ai-vs-vaani-voice.md)\n- [Rime Prism vs Vaani Developer Platform](https://www.anchorterminal.com/compare/rime-prism-vs-vaani-voice.md)\n- [Synthflow API + MCP vs Vaani Developer Platform](https://www.anchorterminal.com/compare/synthflow-vs-vaani-voice.md)\n- [Ultravox Realtime API vs Vaani Developer Platform](https://www.anchorterminal.com/compare/ultravox-vs-vaani-voice.md)\n- [Vaani Developer Platform vs Vapi API + MCP](https://www.anchorterminal.com/compare/vaani-voice-vs-vapi.md)\n- [Vaani Developer Platform vs Vocily AI](https://www.anchorterminal.com/compare/vaani-voice-vs-vocily.md)\n- [Vaani Developer Platform vs Vogent API](https://www.anchorterminal.com/compare/vaani-voice-vs-vogent.md)\n- [CueLight vs Vaani Developer Platform](https://www.anchorterminal.com/compare/cuelight-vs-vaani-voice.md)\n- [Pipecat PhoneLLM vs Vaani Developer Platform](https://www.anchorterminal.com/compare/pipecat-phonellm-vs-vaani-voice.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 Vaani Developer Platform",
        "url": ""
      }
    ],
    "description": "Vaani Developer Platform scores 44.6 (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",
      "Vaani Developer Platform E 44.6",
      "scores"
    ],
    "h1": "fone.me vs Vaani Developer Platform",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/compare/fone-me-vs-vaani-voice",
    "published": "2026-10-01",
    "section": "tools",
    "title": "fone.me vs Vaani Developer Platform for AI agents (2026)",
    "toc": null,
    "updated": "2026-11-07",
    "url": "https://www.anchorterminal.com/compare/fone-me-vs-vaani-voice"
  },
  "tokens": {
    "markdown": 6550,
    "slim": 4080
  },
  "version": 1
}