{
  "data": {
    "a": {
      "slug": "fone-me",
      "name": "fone.me",
      "vendor": "Fone",
      "vendorUrl": "https://www.fone.me",
      "kind": "platform",
      "category": "voice-agents",
      "summary": "fone.me is a hosted AI agent at a personal link that answers calls and messages for a person or small business over web chat, voice, WhatsApp, Telegram and a Premium number. Other agents reach it through keyless MCP and A2A.",
      "url": "https://www.anchorterminal.com/tools/fone-me",
      "markdownUrl": "https://www.anchorterminal.com/tools/fone-me.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/fone-me.min.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/fone-me.json",
      "dns": "fone-me.grade.anchorterminal.com",
      "license": "Proprietary hosted service. Terms of service at https://www.fone.me/terms, whose text draws by script and could not be read on 5 November 2026; no company is named on any page read. No source, SDK or package is published",
      "transports": [
        "streamable-http"
      ],
      "remoteUrl": "https://www.fone.me/mcp",
      "packages": [],
      "auth": "none",
      "authNotes": "No credential for callers. llms.txt gives the MCP server at https://www.fone.me/mcp as Streamable HTTP with auth 'none', and the README of the GitHub repository spearisa/fone-me-mcp says 'public, like the links themselves'. The A2A agent cards read (demo and maxr) declare no securitySchemes or security. The search API at /api/agents/search takes a query with no key per llms.txt. Owners sign in with Apple, Google or email to set up an agent; no owner API key, scopes or tokens are documented.",
      "pricing": "freemium",
      "pricingNotes": "The agent, the first link and the website chat button are free. Premium is $9.99 a month (llms.txt and https://www.fone.me/alternatives/smith-ai) and adds the agent's own phone number, calling minutes and more links, with cancellation at any time; no page read gives the minute allowance, the number of links, the countries for numbers or the payment method. Outbound calls use Premium minutes and international calls use more minutes per minute. Callers and outside agents pay nothing (checked 2026-11-05).",
      "priceSummary": "$9.99 / mo",
      "where": "hosted",
      "x402": {
        "level": "no",
        "evidence": "No x402, MPP or L402 in llms.txt, the guide pages read, the MCP repository README and server.json, or the two agent cards (checked 2026-11-05). The MCP server and A2A endpoints are free and keyless; Premium is a monthly subscription with no payment route stated.",
        "endpoints": []
      },
      "toolCount": 4,
      "popularity": {
        "githubStars": null,
        "npmWeekly": null,
        "pypiWeekly": null,
        "asOf": "2026-11-05"
      },
      "docsUrl": "https://www.fone.me/llms.txt",
      "llmsTxt": "https://www.fone.me/llms.txt",
      "capabilities": [
        "voice.agent",
        "voice.telephony",
        "voice.calls",
        "messaging.whatsapp",
        "messaging.inbound"
      ],
      "tags": [
        "hosted",
        "official",
        "closed-source",
        "mcp",
        "remote-mcp",
        "no-auth",
        "keyless",
        "a2a",
        "llms-txt",
        "whatsapp",
        "telegram",
        "ios",
        "freemium",
        "free-tier",
        "no-status-page"
      ],
      "lastRelease": "2026-10-05",
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 28.3,
        "grade": "F",
        "agentReady": false,
        "rank": 1406,
        "ranked": true,
        "rankOf": 1486,
        "categoryRank": 26,
        "methodology": "0.7",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 29,
          "maintenance": 23,
          "payments": 50,
          "reliability": 15,
          "schema": 31,
          "security": 30,
          "transparency": 23
        },
        "pending": [
          "performance",
          "tasks"
        ],
        "assessment": {
          "confidence": "low",
          "date": "2026-11-05"
        },
        "negative": 0,
        "verdict": "Any agent can find a fone.me link and message its owner's agent through a keyless MCP server or A2A, with no sign-up or cost, and owners see every conversation in one inbox. Tool schemas, rate limits and abuse controls for that open channel are unpublished, the terms and privacy policy draw by script, and no company is named.",
        "bestFor": "Agents acting for a person who need to reach a freelancer's, shop's or small business's own AI agent at its fone.me link to ask a question, request a booking or quote or leave a message, and owners who want an answering agent on a link, WhatsApp, Telegram and a $9.99 number without building one.",
        "strengths": [
          "Keyless MCP server and per-link A2A endpoints let any agent find, look up and message a person's or business's agent without an account or payment",
          "Agent cards follow A2A 0.3.0 with skills, input and output modes and a JSON-RPC transport, readable at an address robots.txt allows",
          "Outbound calls disclose the agent and transcription, run only 8 am to 9 pm in the callee's time zone and stop permanently on a do-not-call request",
          "Owners see every call and chat with a transcript in one inbox, can take over at any time and approve what the agent will say before it calls",
          "Free agent, first link and website chat button, with Premium at $9.99 a month for a number and calling minutes"
        ],
        "weaknesses": [
          "No tool arguments, input schemas, annotations, error shapes or rate limits are published for the MCP server or A2A endpoints",
          "message_agent and A2A reach any person's agent with no caller identity, and no spam, rate or abuse control for that channel is documented",
          "The terms, privacy policy, data-deletion page, FAQ and support page draw by script, and no company, address or country of incorporation is named on any page read",
          "No status page, changelog, security.txt, SLA or published minute allowance for Premium",
          "robots.txt disallows the /mcp, /api/ and /*/a2a paths that llms.txt advertises to agents"
        ],
        "agentNotes": [
          "Connect to https://www.fone.me/mcp with no credentials; use find_agents or get_agent before message_agent so the message goes to the right person's link.",
          "Say who you are acting for in every message_agent call; the owner reads it in an inbox as a named conversation, and conversations continue across calls.",
          "Treat replies as the owner's agent speaking from what it was taught, not a commitment; the vendor says it asks its owner before agreeing to anything or spending money.",
          "Read a link's agent card at /{link}/.well-known/agent-card.json for its skills before using A2A message/send at /{link}/a2a.",
          "Don't send personal or payment details through message_agent; no retention or privacy terms for agent-to-agent messages could be read."
        ],
        "metrics": {
          "kind": "remote",
          "measured": false
        },
        "reviewCount": 0,
        "avgRating": 0,
        "history": [
          {
            "basis": "public evidence",
            "confidence": "low",
            "grade": "F",
            "methodology": "0.7",
            "pending": [
              "performance",
              "tasks"
            ],
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 28.3
          }
        ],
        "editorialScores": {
          "ergonomics": 29,
          "maintenance": 23,
          "payments": 50,
          "reliability": 15,
          "schema": 31,
          "security": 30,
          "transparency": 13
        },
        "provenanceScore": 32,
        "checked": {
          "categories": {
            "ergonomics": "2026-11-05",
            "maintenance": "2026-11-05",
            "payments": "2026-11-05",
            "reliability": "2026-11-05",
            "schema": "2026-11-05",
            "security": "2026-11-05",
            "transparency": "2026-11-05"
          },
          "last": "2026-11-05",
          "oldest": "2026-11-05",
          "stale": false,
          "staleAfterDays": 90
        }
      },
      "connect": {
        "config": {
          "mcpServers": {
            "fone.me": {
              "type": "http",
              "url": "https://www.fone.me/mcp"
            }
          }
        }
      },
      "letme": {
        "capability": "https://letme.dev/voice.agent",
        "tool": "https://letme.dev/fone-me"
      },
      "area": "voice",
      "unitPrices": [
        {
          "item": "Premium",
          "unit": "month",
          "usd": 9.99,
          "note": "own fone.me number, calling minutes (allowance not published) and more links; the agent, first link and chat button are free"
        }
      ],
      "provenance": {
        "legalEntity": "",
        "domain": "fone.me",
        "domainRegistered": "",
        "endpointOnVendorDomain": true,
        "terms": "https://www.fone.me/terms",
        "privacy": "https://www.fone.me/privacy",
        "statusPage": "",
        "changelog": "",
        "securityTxt": "none",
        "checked": "2026-11-05",
        "notes": [
          "No legal entity is named on any page read. Page metadata gives the author and site name as 'Fone', and llms.txt gives San Francisco, CA, USA as a location. The terms, privacy policy and data-deletion page draw their text by script and showed only titles, so whether they name a company is unchecked, not absent.",
          "The README of github.com/spearisa/fone-me-mcp ends 'Operated by zwilio'. No fone.me page read names zwilio or links the repository, and three web searches found no company of that name, so it is not recorded as the legal entity.",
          "The MCP server, the search API and the A2A endpoints are on www.fone.me, the vendor's own domain. robots.txt disallows /mcp, /api/ and /*/a2a, so none was fetched; the agent cards it allows were read for two links.",
          "No status page or changelog found. /.well-known/security.txt answers with the app's HTML shell, recorded as none. /status failed to load.",
          "RDAP for fone.me, the Wayback Machine, the official MCP registry and the App Store listing (id 6759304762) were not read; each fetch needed an approval that did not come. firstReleased 2025-11-05 is the earliest sitemap lastmod (/sha_krux), a lower bound only, and falls one year to the day before the check, so the sitemap may cap its dates."
        ],
        "score": 32
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/fone-me.json",
      "live": {
        "slug": "fone-me",
        "probe": {
          "target": "https://www.fone.me/mcp",
          "method": "get",
          "lastAt": "2026-11-07T18:20:25.611446017Z",
          "lastOk": true,
          "lastStatus": 405,
          "lastMs": 233,
          "authRequired": false,
          "uptime24h": 100,
          "uptime30d": 100,
          "p50ms24h": 215,
          "p95ms24h": 511,
          "samples24h": 200,
          "samples30d": 200,
          "days": [
            {
              "date": "2026-11-06",
              "probes": 13,
              "ok": 13
            },
            {
              "date": "2026-11-07",
              "probes": 187,
              "ok": 187
            }
          ]
        },
        "securityTxt": {
          "url": "https://fone.me/.well-known/security.txt",
          "state": "none",
          "checkedAt": "2026-11-07T15:59:59.997697627Z"
        },
        "llmsTxt": {
          "url": "https://www.fone.me/llms.txt",
          "ok": true,
          "status": 200,
          "checkedAt": "2026-11-07T15:32:32.136376991Z"
        },
        "pages": [
          {
            "url": "https://www.fone.me/privacy",
            "kind": "privacy",
            "status": 200,
            "checkedAt": "2026-11-07T14:28:42.001987885Z",
            "changedAt": "0001-01-01T00:00:00Z",
            "fingerprint": "e3b0c44298fc"
          },
          {
            "url": "https://www.fone.me/terms",
            "kind": "terms",
            "status": 200,
            "checkedAt": "2026-11-07T14:28:44.174787172Z",
            "changedAt": "0001-01-01T00:00:00Z",
            "fingerprint": "e3b0c44298fc"
          }
        ],
        "mcpTools": {
          "url": "https://www.fone.me/mcp",
          "checkedAt": "2026-11-07T01:44:39.315960369Z",
          "status": "ok",
          "note": "answered without the initialize handshake",
          "tools": [
            {
              "name": "find_agents",
              "title": "Find people and businesses on fone.me",
              "description": "Search fone.me for people's and businesses' AI agents by what they do or offer (e.g. 'dog walker', 'real estate agent in Miami', 'Spanish tutor'). Returns their fone.me links.",
              "inputSchema": {
                "properties": {
                  "limit": {
                    "description": "How many results (1-10). Default 5.",
                    "type": "number"
                  },
                  "query": {
                    "description": "What you're looking for, in plain words.",
                    "type": "string"
                  }
                },
                "required": [
                  "query"
                ],
                "type": "object"
              },
              "annotations": {
                "openWorldHint": true,
                "readOnlyHint": true,
                "title": "Find people and businesses on fone.me"
              }
            },
            {
              "name": "get_agent",
              "title": "Look up a fone.me agent",
              "description": "Get who is behind a fone.me link (e.g. fone.me/samspearin) and what their agent can help with, before messaging it.",
              "inputSchema": {
                "properties": {
                  "link": {
                    "description": "A fone.me link or name, e.g. 'fone.me/sam' or 'sam'.",
                    "type": "string"
                  }
                },
                "required": [
                  "link"
                ],
                "type": "object"
              },
              "annotations": {
                "openWorldHint": true,
                "readOnlyHint": true,
                "title": "Look up a fone.me agent"
              }
            },
            {
              "name": "message_agent",
              "title": "Message a fone.me agent",
              "description": "Send a message to the AI agent at a fone.me link and get its reply — ask a question, request a booking or a quote, or leave a message for the person. The conversation continues across calls. Say who you're asking for in on_behalf_of.",
              "inputSchema": {
                "properties": {
                  "link": {
                    "description": "A fone.me link or name, e.g. 'fone.me/samspearin'.",
                    "type": "string"
                  },
                  "message": {
                    "description": "What to say to the agent.",
                    "type": "string"
                  },
                  "on_behalf_of": {
                    "description": "The name of the person you're asking for (shown to the owner).",
                    "type": "string"
                  }
                },
                "required": [
                  "link",
                  "message"
                ],
                "type": "object"
              },
              "annotations": {
                "destructiveHint": false,
                "idempotentHint": false,
                "openWorldHint": true,
                "readOnlyHint": false,
                "title": "Message a fone.me agent"
              }
            },
            {
              "name": "add_chat_to_website",
              "title": "Add an AI chat button to a website",
              "description": "Get the one-line code that puts a fone.me AI agent on a website: a chat button in the corner where visitors chat, call by voice, or continue on WhatsApp or Telegram, and the agent answers questions, takes messages and booking requests for the owner. Use it when someone building or editing a website (HTML, Next.js, React, WordPress, Shopify, Wix, Squarespace, Webflow, Framer) wants a chatbot, AI receptionist, live chat or contact widget. Free to start. Give the person's fone.me link if they have one.",
              "inputSchema": {
                "properties": {
                  "link": {
                    "description": "The site owner's fone.me link, e.g. 'fone.me/joes-plumbing' or 'joes-plumbing'. Leave out if they don't have one yet.",
                    "type": "string"
                  },
                  "site": {
                    "description": "What the site is built with: html, nextjs, react, wordpress, shopify, wix, squarespace, webflow, framer. Default html.",
                    "type": "string"
                  }
                },
                "type": "object"
              },
              "annotations": {
                "openWorldHint": true,
                "readOnlyHint": true,
                "title": "Add an AI chat button to a website"
              }
            }
          ],
          "schemaTokens": 725,
          "changedAt": "2026-11-07T01:44:39.315960369Z",
          "check": {
            "checker": "anchor-check/1.0",
            "totalTokens": 725,
            "counts": {
              "error": 0,
              "note": 1,
              "warn": 1
            },
            "findings": [
              {
                "rule": "TC18",
                "severity": "warn",
                "tool": "add_chat_to_website",
                "message": "readOnlyHint is true but the name says \"add\"",
                "fix": "If it changes anything, readOnlyHint must be false."
              },
              {
                "rule": "TC24",
                "severity": "note",
                "message": "4 of 4 tools have no outputSchema",
                "fix": "Declare outputSchema for tools that return structured data, and return structuredContent that matches it."
              }
            ]
          }
        },
        "updatedAt": "2026-11-07T18:20:25.611446017Z"
      }
    },
    "answer": "Vapi API + MCP scores 64.7 (B) 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": "vapi",
      "name": "Vapi API + MCP",
      "vendor": "Vapi",
      "vendorUrl": "https://vapi.ai",
      "kind": "http-api",
      "category": "voice-agents",
      "summary": "Developer platform for phone and web voice agents.",
      "url": "https://www.anchorterminal.com/tools/vapi",
      "markdownUrl": "https://www.anchorterminal.com/tools/vapi.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/vapi.min.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/vapi.json",
      "dns": "vapi.grade.anchorterminal.com",
      "repo": "https://github.com/VapiAI/mcp-server",
      "license": "MIT (MCP server)",
      "transports": [
        "http",
        "streamable-http",
        "stdio"
      ],
      "remoteUrl": "https://api.vapi.ai",
      "packages": [
        {
          "registry": "npm",
          "name": "@vapi-ai/server-sdk"
        },
        {
          "registry": "npm",
          "name": "@vapi-ai/web"
        },
        {
          "registry": "pypi",
          "name": "vapi_server_sdk"
        },
        {
          "registry": "npm",
          "name": "@vapi-ai/mcp-server"
        }
      ],
      "auth": "api-key",
      "authNotes": "Private API key as a bearer token for the REST API and the hosted MCP server at `https://mcp.vapi.ai/mcp` (an SSE endpoint also exists). A separate public key is for browser calls with the Web SDK. The local MCP server reads `VAPI_TOKEN`.",
      "pricing": "usage",
      "pricingNotes": "Usage only is $0.05 a minute Vapi hosting, plus transcriber, model, voice and telephony at provider cost, prepaid with $5 of free credits to start. Vapi telephony, SIP, WebSockets and WebRTC transport are free, Twilio inbound runs $0.008 a minute and outbound $0.014. Success Packages add support and limits on top of usage, Core $29 a month and Pro 10 per cent of the hosting fee with a $999 monthly minimum. Add-ons include HIPAA at $2,000 a month and extra concurrent lines at $10 a line a month. The vendor's calculator puts 1,000 minutes with Deepgram, OpenAI and ElevenLabs at roughly $0.08 to $0.13 a minute all in (https://vapi.ai/pricing).",
      "priceSummary": "$29 / mo",
      "where": "both",
      "x402": {
        "level": "no",
        "evidence": "No x402 support in the docs, pricing page or MCP docs (checked 2026-09-30).",
        "endpoints": []
      },
      "toolCount": 13,
      "popularity": {
        "githubStars": 57,
        "npmWeekly": 177088,
        "pypiWeekly": 42248,
        "asOf": "2026-09-30"
      },
      "docsUrl": "https://docs.vapi.ai",
      "llmsTxt": "https://docs.vapi.ai/llms.txt",
      "openapi": "https://docs.vapi.ai/openapi/api-reference.json",
      "capabilities": [
        "voice.agent",
        "voice.pipeline",
        "voice.speech-to-speech",
        "voice.tools",
        "voice.telephony"
      ],
      "tags": [
        "hosted",
        "closed-source",
        "no-card",
        "mcp",
        "llms-txt",
        "openapi",
        "typescript",
        "python",
        "webhooks",
        "streaming",
        "pipeline",
        "speech-to-speech",
        "enterprise"
      ],
      "lastRelease": "2026-10-30",
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 64.7,
        "grade": "B",
        "agentReady": false,
        "rank": 457,
        "ranked": true,
        "rankOf": 1486,
        "categoryRank": 10,
        "methodology": "0.7",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 67,
          "maintenance": 88,
          "payments": 35,
          "reliability": 70,
          "schema": 89,
          "security": 61,
          "transparency": 75
        },
        "pending": [
          "performance",
          "tasks"
        ],
        "assessment": {
          "confidence": "medium",
          "date": "2026-11-02"
        },
        "negative": -4,
        "negativeNotes": [
          "2026-06-03. A compromised developer GitHub token was used to push malicious code to Vapi repositories and publish four malicious `@vapi-ai/server-sdk` versions (0.11.1, 0.11.2, 1.2.1, 1.2.2) to npm. Vapi says they were removed within about three hours with zero downloads and no customer data exposed, and it published a write-up. Fixed and documented, so we deduct 4 of a possible 15 (https://vapi.ai/blog/our-response-to-june-3-supply-chain-incident)."
        ],
        "verdict": "Voice agents can combine supported transcription, model and voice providers, including customer-supplied endpoints, with a weekly changelog and an OpenAPI file. Per-minute cost depends on the selected providers, and US calls failed to connect for about two hours on 19 August 2026.",
        "bestFor": "Developers who want to choose every provider, bring their own keys and tune cost against latency.",
        "strengths": [
          "Any mix of transcriber, model and voice provider, or your own keys and endpoints",
          "OpenAPI file with 145 operations, llms.txt and a weekly changelog",
          "Public keys limited to allowed origins and assistants",
          "99 per cent uptime SLA on the Pro package, 99.9 per cent on Premier",
          "Versioned assistants and tools with draft, publish and traffic splitting"
        ],
        "weaknesses": [
          "Real per-minute cost depends on provider choices",
          "Usage only has 4 concurrent lines and 14 days of retention",
          "The MCP server's `create_call` places real calls with no annotation",
          "No request rate limits, Retry-After or idempotency keys for calls found",
          "Malicious SDK versions reached npm for about three hours on 3 June 2026"
        ],
        "agentNotes": [
          "Read `subscriptionLimits.concurrencyBlocked` in the `POST /call` response, a full account queues the call rather than failing",
          "Confirm with a person before `create_call` through the MCP server, the server won't ask",
          "Pin transcriber, model and voice and set fallback plans so one provider outage doesn't drop calls",
          "Read the call log's cost breakdown to see what each provider charged",
          "Check `@vapi-ai/server-sdk` isn't pinned to 0.11.1, 0.11.2, 1.2.1 or 1.2.2"
        ],
        "metrics": {
          "kind": "remote",
          "measured": false
        },
        "reviewCount": 2,
        "avgRating": 2.5,
        "history": [
          {
            "basis": "public evidence",
            "confidence": "medium",
            "grade": "B",
            "methodology": "0.7",
            "pending": [
              "performance",
              "tasks"
            ],
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 64.7
          }
        ],
        "editorialScores": {
          "ergonomics": 67,
          "maintenance": 88,
          "payments": 35,
          "reliability": 70,
          "schema": 89,
          "security": 61,
          "transparency": 70
        },
        "provenanceScore": 79,
        "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",
          "lastMoved": "2026-11-02",
          "oldest": "2026-11-02",
          "stale": false,
          "staleAfterDays": 90
        }
      },
      "connect": {
        "http": "curl https://api.vapi.ai/call -H \"Authorization: Bearer $VAPI_API_KEY\" \\\n  -H \"content-type: application/json\" \\\n  -d '{\"assistantId\":\"\u003cassistant-id\u003e\",\"phoneNumberId\":\"\u003cphone-number-id\u003e\",\"customer\":{\"number\":\"+15551234567\"}}'",
        "claudeCode": "claude mcp add --transport http vapi https://mcp.vapi.ai/mcp --header \"Authorization: Bearer $VAPI_API_KEY\"",
        "config": {
          "mcpServers": {
            "vapi": {
              "args": [
                "-y",
                "@vapi-ai/mcp-server"
              ],
              "command": "npx",
              "env": {
                "VAPI_TOKEN": "${VAPI_API_KEY}"
              }
            }
          }
        }
      },
      "letme": {
        "capability": "https://letme.dev/voice.agent",
        "tool": "https://letme.dev/vapi"
      },
      "area": "voice",
      "unitPrices": [
        {
          "item": "Vapi hosting",
          "unit": "call-minute",
          "usd": 0.05,
          "note": "platform fee only, transcriber, model, voice and telephony billed on top at cost"
        },
        {
          "item": "Twilio outbound transport",
          "unit": "call-minute",
          "usd": 0.014,
          "note": "US, passed through"
        },
        {
          "item": "Twilio inbound transport",
          "unit": "call-minute",
          "usd": 0.008,
          "note": "US, passed through"
        },
        {
          "item": "Core Success Package",
          "unit": "month",
          "usd": 29
        },
        {
          "item": "Pro Success Package minimum",
          "unit": "month",
          "usd": 999,
          "note": "10 per cent of hosting fees, $999 minimum"
        },
        {
          "item": "Extra concurrent call line",
          "unit": "month",
          "usd": 10
        },
        {
          "item": "HIPAA add-on",
          "unit": "month",
          "usd": 2000
        }
      ],
      "provenance": {
        "legalEntity": "Vapi Inc.",
        "domain": "vapi.ai",
        "domainRegistered": "2023-08-22",
        "endpointOnVendorDomain": true,
        "terms": "https://vapi.ai/terms-of-service",
        "privacy": "https://vapi.ai/privacy",
        "statusPage": "https://status.vapi.ai",
        "changelog": "https://docs.vapi.ai/whats-new",
        "securityTxt": "none",
        "checked": "2026-11-02",
        "notes": [
          "The terms name Vapi Inc., a Delaware corporation.",
          "status.vapi.ai moved from Statuspage to Better Stack; the old history feeds redirect to the new page. docs.vapi.ai/changelog answers 308 to /whats-new. vapi.ai/.well-known/security.txt answers 404 (2 November 2026)."
        ],
        "score": 79
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/vapi.json",
      "live": {
        "slug": "vapi",
        "probe": {
          "target": "https://api.vapi.ai",
          "method": "get",
          "lastAt": "2026-11-07T18:21:03.227221001Z",
          "lastOk": true,
          "lastStatus": 200,
          "lastMs": 274,
          "authRequired": false,
          "uptime24h": 100,
          "uptime30d": 99.95,
          "p50ms24h": 195,
          "p95ms24h": 292,
          "samples24h": 239,
          "samples30d": 7910,
          "days": [
            {
              "date": "2026-10-07",
              "probes": 272,
              "ok": 272
            },
            {
              "date": "2026-10-08",
              "probes": 268,
              "ok": 268
            },
            {
              "date": "2026-10-09",
              "probes": 250,
              "ok": 250
            },
            {
              "date": "2026-10-10",
              "probes": 247,
              "ok": 247
            },
            {
              "date": "2026-10-11",
              "probes": 247,
              "ok": 247
            },
            {
              "date": "2026-10-12",
              "probes": 247,
              "ok": 247
            },
            {
              "date": "2026-10-13",
              "probes": 248,
              "ok": 247
            },
            {
              "date": "2026-10-14",
              "probes": 249,
              "ok": 249
            },
            {
              "date": "2026-10-15",
              "probes": 253,
              "ok": 253
            },
            {
              "date": "2026-10-16",
              "probes": 252,
              "ok": 250
            },
            {
              "date": "2026-10-17",
              "probes": 253,
              "ok": 253
            },
            {
              "date": "2026-10-18",
              "probes": 256,
              "ok": 256
            },
            {
              "date": "2026-10-19",
              "probes": 255,
              "ok": 255
            },
            {
              "date": "2026-10-20",
              "probes": 252,
              "ok": 251
            },
            {
              "date": "2026-10-21",
              "probes": 253,
              "ok": 253
            },
            {
              "date": "2026-10-22",
              "probes": 253,
              "ok": 253
            },
            {
              "date": "2026-10-23",
              "probes": 248,
              "ok": 248
            },
            {
              "date": "2026-10-24",
              "probes": 251,
              "ok": 251
            },
            {
              "date": "2026-10-25",
              "probes": 250,
              "ok": 250
            },
            {
              "date": "2026-10-26",
              "probes": 252,
              "ok": 252
            },
            {
              "date": "2026-10-27",
              "probes": 249,
              "ok": 249
            },
            {
              "date": "2026-10-28",
              "probes": 250,
              "ok": 250
            },
            {
              "date": "2026-10-29",
              "probes": 249,
              "ok": 249
            },
            {
              "date": "2026-10-30",
              "probes": 249,
              "ok": 249
            },
            {
              "date": "2026-10-31",
              "probes": 251,
              "ok": 251
            },
            {
              "date": "2026-11-01",
              "probes": 249,
              "ok": 249
            },
            {
              "date": "2026-11-02",
              "probes": 250,
              "ok": 250
            },
            {
              "date": "2026-11-03",
              "probes": 248,
              "ok": 248
            },
            {
              "date": "2026-11-04",
              "probes": 246,
              "ok": 246
            },
            {
              "date": "2026-11-05",
              "probes": 185,
              "ok": 185
            },
            {
              "date": "2026-11-06",
              "probes": 241,
              "ok": 241
            },
            {
              "date": "2026-11-07",
              "probes": 187,
              "ok": 187
            }
          ]
        },
        "vendorStatus": {
          "page": "https://status.vapi.ai",
          "indicator": "unknown",
          "summary": "no machine-readable status found",
          "checkedAt": "2026-11-07T04:48:55.101667666Z"
        },
        "versions": [
          {
            "registry": "github",
            "name": "VapiAI/mcp-server",
            "version": "v0.0.11",
            "released": "2026-08-14",
            "seenAt": "2026-11-07T00:14:41.338728393Z"
          },
          {
            "registry": "npm",
            "name": "@vapi-ai/mcp-server",
            "version": "0.0.11",
            "seenAt": "2026-11-07T00:14:39.631756284Z"
          },
          {
            "registry": "npm",
            "name": "@vapi-ai/server-sdk",
            "version": "3.0.0",
            "seenAt": "2026-11-07T00:14:36.102978581Z"
          },
          {
            "registry": "npm",
            "name": "@vapi-ai/web",
            "version": "3.1.0",
            "seenAt": "2026-11-07T00:14:37.537614698Z"
          },
          {
            "registry": "pypi",
            "name": "vapi_server_sdk",
            "version": "3.0.0",
            "released": "2026-10-12",
            "seenAt": "2026-11-07T00:14:39.346932666Z"
          }
        ],
        "githubStars": 58,
        "npmWeekly": 249693,
        "pypiWeekly": 47727,
        "securityTxt": {
          "url": "https://vapi.ai/.well-known/security.txt",
          "state": "none",
          "checkedAt": "2026-11-07T16:00:27.624825772Z"
        },
        "llmsTxt": {
          "url": "https://docs.vapi.ai/llms.txt",
          "ok": true,
          "status": 200,
          "checkedAt": "2026-11-07T15:34:15.675112395Z"
        },
        "domain": {
          "domain": "vapi.ai",
          "registered": "2023-08-22",
          "source": "https://rdap.identitydigital.services/rdap/domain/vapi.ai",
          "checkedAt": "2026-11-01T14:07:40.214661468Z"
        },
        "pages": [
          {
            "url": "https://docs.vapi.ai/changelog",
            "kind": "changelog",
            "status": 304,
            "checkedAt": "2026-11-02T07:16:03.992497602Z",
            "changedAt": "2026-10-30T05:39:08.495265872Z",
            "fingerprint": "9ad0df101778"
          },
          {
            "url": "https://docs.vapi.ai/whats-new",
            "kind": "changelog",
            "status": 200,
            "checkedAt": "2026-11-07T14:08:35.441677574Z",
            "changedAt": "2026-11-06T13:30:52.143488122Z",
            "fingerprint": "d5be5d776e11"
          },
          {
            "url": "https://docs.vapi.ai/workflows/legacy-migration",
            "kind": "deprecations",
            "status": 200,
            "checkedAt": "2026-11-07T14:08:38.856791746Z",
            "changedAt": "2026-11-06T13:30:55.192057735Z",
            "fingerprint": "f5d1ee6643b6"
          },
          {
            "url": "https://vapi.ai/pricing",
            "kind": "pricing",
            "status": 200,
            "checkedAt": "2026-11-07T14:23:09.810870391Z",
            "changedAt": "2026-10-06T16:13:21.353726202Z",
            "fingerprint": "d528b534573c"
          },
          {
            "url": "https://vapi.ai/privacy",
            "kind": "privacy",
            "status": 200,
            "checkedAt": "2026-11-07T14:23:12.039918505Z",
            "changedAt": "0001-01-01T00:00:00Z",
            "fingerprint": "f13594373bcf"
          },
          {
            "url": "https://vapi.ai/terms-of-service",
            "kind": "terms",
            "status": 200,
            "checkedAt": "2026-11-07T14:23:14.057724268Z",
            "changedAt": "0001-01-01T00:00:00Z",
            "fingerprint": "4b1fd29445f7"
          }
        ],
        "mcpTools": {
          "url": "https://mcp.vapi.ai/mcp",
          "checkedAt": "2026-11-07T01:48:56.638230428Z",
          "status": "auth",
          "note": "asks for credentials before listing its tools",
          "changedAt": "2026-11-07T01:48:56.638230428Z"
        },
        "github": {
          "repo": "vapiai/mcp-server",
          "checkedAt": "2026-11-02T09:35:05.863304357Z",
          "stars": 58,
          "archived": false,
          "issuesEnabled": true,
          "pushedAt": "2026-10-27T23:52:50Z",
          "openIssues": 5,
          "openPRs": 10,
          "issuesOpened90d": 1,
          "issuesClosed90d": 0,
          "prsMerged90d": 9,
          "ci": {
            "branch": "main",
            "runs": 3,
            "success": 3,
            "failure": 0,
            "other": 0,
            "latest": "success",
            "latestAt": "2026-01-28T04:36:11Z"
          },
          "replies": {
            "sampled": 6,
            "unanswered": 5,
            "medianDays": 29.6
          }
        },
        "updatedAt": "2026-11-07T18:21:03.227221001Z"
      }
    },
    "edges": [
      {
        "by": 65,
        "category": "maintenance",
        "leads": "vapi",
        "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": "The changelog's newest entry is the week of 26 October 2026, and `@vapi-ai/web` 3.1.0 was tagged on 30 October (30). Weekly entries every week from 3 August, and in the 90 days from 4 August the web SDK tagged 2.6.2, 2.6.3, 2.7.0, 2.7.1, 3.0.0, 3.0.1 and 3.1.0, the Python SDK 3.0.0 (12 October), the TypeScript SDK 2.0.1 and the MCP server 0.0.10 and 0.0.11 (20). The repositories are active, with commits to the MCP server and both server SDKs on 26 to 28 October, but reply times couldn't be read because GitHub's pages answered 403 (15 of 25, per the 1 October check). Server SDKs, web SDK and MCP server on npm and PyPI (15). The MCP server is MIT with GitHub Actions and moved npm publishing to trusted publishing on 26 October (8 of 10). 30 + 20 + 15 + 15 + 8 = 88."
        },
        "scores": {
          "a": 23,
          "b": 88
        }
      },
      {
        "by": 58,
        "category": "schema",
        "leads": "vapi",
        "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": "OpenAPI 3.1.0 at docs.vapi.ai/openapi/api-reference.json with 145 operations on 76 paths, linked from llms.txt. api.vapi.ai's robots.txt now disallows /api*, so the api.vapi.ai/api-json path the 1 October check read wasn't requested (25). llms.txt with Markdown copies of every page and a docs MCP server (10). Guides explain when to use squads, tools and fallback plans (15 of 20). The OpenAPI types every field, though assistant configuration is a large nested object (12 of 15). Examples throughout and a call-errors guide that explains ended reasons, with less on REST error bodies (12 of 15). A weekly changelog, now at docs.vapi.ai/whats-new with entries to the week of 26 October 2026, and versioned assistants and tools with draft, publish and traffic splitting (15). 25 + 10 + 15 + 12 + 12 + 15 = 89."
        },
        "scores": {
          "a": 31,
          "b": 89
        }
      },
      {
        "by": 55,
        "category": "reliability",
        "leads": "vapi",
        "name": "Reliability",
        "reasons": {
          "a": "Hosted reading, for the MCP server and A2A endpoints and the service behind them. No status page is linked from llms.txt, the home page or any guide page read, and https://www.fone.me/status failed to load (0). No readable incident history, so the floor (5). No request rate limit for the MCP server, the search API or A2A is published; the only limits are on the agent's own outbound calls (8 am to 9 pm in the callee's time zone, 'limited per day' with no number), which are not request limits (0 of 15). No 429, overload or retry guidance and no idempotency key for message_agent or message/send (0 of 15). No SLA (0). Nothing on the MCP server, the agent cards or llms.txt is marked beta or preview, and the MCP repository's server.json is version 1.0.0 (10). 0+5+0+0+0+10 = 15.",
          "b": "status.vapi.ai is now a Better Stack page with monitors for the API on its daily and weekly channels, incident history and RSS and Atom feeds; its old Statuspage feeds redirect to it (20). In the 90 days from 4 August the feed lists twelve incidents. Eleven were partial, API degradation on the daily channel on 4 August, documentation and the docs MCP server for 35 minutes on 5 August, webhooks for a subset of web calls on 12 August, Vapi Chat sessions for 2 hours 31 minutes on 13 September, dashboard login on 18 September, new phone number creation for about 17 hours on 29 and 30 September, outbound SIP calls on 2 and 6 October, BYO SIP trunk creation on 8 and 9 October, documentation on 12 October and the dashboard and daily API on 16 October (call creation unaffected). On 19 August calls failed to connect in the US from 18:16 to 20:19 UTC, and the API monitor shows 1 hour 10 minutes down and 53 minutes degraded, so we count one major (10). The 1 October check dated that incident to 12 August. Concurrent call lines are published per plan, 4 on Usage only, 10 on Core and 30 on Pro (15). A full account queues the call and `subscriptionLimits.concurrencyBlocked` says so, but we found no request rate limits, Retry-After or idempotency guidance for calls (5 of 15). The Pro package carries a 99 per cent uptime SLA and Premier 99.9 per cent, re-read on 2 November (10). The API is generally available (10). 20 + 10 + 15 + 5 + 10 + 10 = 70."
        },
        "scores": {
          "a": 15,
          "b": 70
        }
      },
      {
        "by": 52,
        "category": "transparency",
        "leads": "vapi",
        "name": "Transparency \u0026 trust",
        "reasons": {
          "a": "Closed service. Terms of service exist at /terms but draw by script, so their content, governing law and the company they name are unchecked; no company, address or country of incorporation appears on any page read, llms.txt says San Francisco, and the MCP repository has no licence (5 of 30). Data handling was read only from guide pages, which say only the owner sees their calls and messages, calls are transcribed and callers told so, and private categories are withheld. The privacy policy and data-deletion page draw by script, so no retention period, recording statement, DPA or AI-training statement was read (8 of 30). No deprecation policy or dated notices (0). No subprocessors, telephony, model or hosting providers or data locations are named on any page read; the demo agent card's icon is served from Cloudinary (0 of 20). 5+8+0+0 = 13.",
          "b": "Closed platform with clear terms, and the MCP server is MIT (18 of 30). Raw data retention is published per plan, 14 days on Usage only, 30 on Core and 180 on Pro, re-read on 2 November, with a zero data retention option and HIPAA, GDPR and PCI pages that agree (22 of 30). Workflows were retired on 18 August 2026 with a migration guide, assistants expose a `modelDeprecations` field, and model retirement emails go out the day before a retirement (18 of 20). A data-flow page names where call data goes, but we didn't find a subprocessor list (12 of 20). 18 + 22 + 18 + 12 = 70."
        },
        "scores": {
          "a": 23,
          "b": 75
        }
      },
      {
        "by": 38,
        "category": "ergonomics",
        "leads": "vapi",
        "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 MCP server's source and README register 13 tools for assistants, calls, phone numbers and tools, and the docs page lists 10; the 1 October count of 20 isn't in the repository (15 of 25). Call and assistant lists take limits and date filters (17 of 20). Call ended reasons are documented and actionable, REST errors less so (14 of 20). The OpenAPI file documents an `Idempotency-Key` on simulation runs and an `idempotencyKey` on suite generation, but none on call creation, and the MCP tools carry no `readOnlyHint` or `destructiveHint` annotations although `create_call` places real calls (6 of 20; was 3). Server SDKs for TypeScript and Python plus web and mobile clients (15). 15 + 17 + 14 + 6 + 15 = 67."
        },
        "scores": {
          "a": 29,
          "b": 67
        }
      },
      {
        "by": 31,
        "category": "security",
        "leads": "vapi",
        "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": "Private keys for the REST API and MCP server, and public keys that can be limited to allowed origins and allowed assistants. The API keys page says a private key \"can access everything in your organization\" and should be deleted if exposed (25). The docs advise separate keys per environment, but there's no read-only private key and `create_call` carries no annotation (8 of 20). Assistants listen to callers. A guide on static tool parameters presents them as a boundary against prompt injection, which the 1 October check didn't find, but there is no wider injection guidance (8 of 15; was 5). Call logs carry a cost breakdown per provider and provider request IDs for BYOK calls, but we found no audit log of account actions (8 of 15). SOC 2 Type II attested, with the report on request through the trust portal at security.vapi.ai, and HIPAA, GDPR and PCI pages. vapi.ai/.well-known/security.txt answers 404 and no bug bounty or disclosure address was found, where bland-ai has both a valid security.txt and a disclosure address (17). The June 2026 npm incident was written up in public (12 of 20). 25 + 8 + 8 + 8 + 12 = 61."
        },
        "scores": {
          "a": 30,
          "b": 61
        }
      }
    ],
    "facts": [
      {
        "a": "Platform",
        "b": "HTTP API",
        "name": "Kind"
      },
      {
        "a": "Fone",
        "b": "Vapi",
        "name": "Vendor"
      },
      {
        "a": "https://www.fone.me/mcp",
        "b": "https://api.vapi.ai",
        "name": "Hosted endpoint"
      },
      {
        "a": "Streamable HTTP",
        "b": "HTTP, Streamable 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": "MIT (MCP server)",
        "name": "Licence"
      },
      {
        "a": "4",
        "b": "13",
        "name": "Tools exposed"
      },
      {
        "a": "no",
        "b": "no",
        "name": "Read-only variant documented"
      },
      {
        "a": "yes",
        "b": "yes",
        "name": "llms.txt"
      },
      {
        "a": "2026-10-05",
        "b": "2026-10-30",
        "name": "Last release"
      },
      {
        "a": "couldn't be read",
        "b": "2026-09-14",
        "name": "Terms last updated"
      },
      {
        "a": "couldn't be read",
        "b": "2023-09-09",
        "name": "Privacy policy last updated"
      },
      {
        "a": "couldn't be read",
        "b": "yes",
        "name": "Customer content may train models"
      },
      {
        "a": "couldn't be read",
        "b": "yes",
        "name": "Terms restrict automated access"
      },
      {
        "a": "couldn't be read",
        "b": "not found in the text",
        "name": "Terms restrict benchmarking"
      },
      {
        "a": "couldn't be read",
        "b": "yes",
        "name": "Terms or service can change without notice"
      },
      {
        "a": "couldn't be read",
        "b": "yes",
        "name": "Arbitration or class-action waiver"
      },
      {
        "a": "none",
        "b": "57 stars, 177k npm/wk, 42k PyPI/wk",
        "name": "Popularity"
      },
      {
        "a": "none",
        "b": "2.5/5 (2)",
        "name": "Agent reviews"
      }
    ],
    "faq": [
      {
        "answer": "Vapi API + MCP scores 64.7 (B) 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 Vapi API + MCP?"
      },
      {
        "answer": "Yes. fone.me has a hosted endpoint at https://www.fone.me/mcp and Vapi API + MCP at https://api.vapi.ai.",
        "question": "Can an agent call fone.me and Vapi API + MCP without installing anything?"
      }
    ],
    "goodFor": [
      {
        "aheadOn": [
          "Payments \u0026 pricing, 50 against 35"
        ],
        "also": [
          "No key needed to call it",
          "No incidents deducted, where Vapi API + MCP loses 4 points for them"
        ],
        "goodFor": "Agents acting for a person who need to reach a freelancer's, shop's or small business's own AI agent at its fone.me link to ask a question, request a booking or quote or leave a message, and owners who want an answering agent on a link, WhatsApp, Telegram and a $9.99 number without building one.",
        "slug": "fone-me",
        "watchFor": "No tool arguments, input schemas, annotations, error shapes or rate limits are published for the MCP server or A2A endpoints"
      },
      {
        "aheadOn": [
          "Reliability, 70 against 15",
          "Schema \u0026 documentation, 89 against 31",
          "Agent ergonomics, 67 against 29",
          "Security \u0026 auth, 61 against 30",
          "Maintenance \u0026 community, 88 against 23",
          "Transparency \u0026 trust, 75 against 23"
        ],
        "also": [
          "Runs on your own machine",
          "Free to start without a card"
        ],
        "goodFor": "Developers who want to choose every provider, bring their own keys and tune cost against latency.",
        "slug": "vapi",
        "watchFor": "Real per-minute cost depends on provider choices"
      }
    ],
    "history": {
      "fone-me": null,
      "vapi": [
        {
          "causes": [
            "evidence"
          ],
          "date": "2026-11-02",
          "delta": 1,
          "from": 63.7,
          "fromGrade": "B",
          "to": 64.7,
          "toGrade": "B"
        },
        {
          "causes": [
            "method"
          ],
          "date": "2026-10-27",
          "delta": 0.2,
          "from": 63.5,
          "fromGrade": "B",
          "to": 63.7,
          "toGrade": "B"
        },
        {
          "causes": [
            "method"
          ],
          "date": "2026-10-08",
          "delta": -0.2,
          "from": 63.7,
          "fromGrade": "B",
          "to": 63.5,
          "toGrade": "B"
        }
      ]
    },
    "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-vapi.json",
        "title": "Amazon Nova 2 Sonic vs Vapi API + MCP",
        "url": "https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-vapi"
      },
      {
        "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-vapi.json",
        "title": "AssemblyAI Voice Agent API vs Vapi API + MCP",
        "url": "https://www.anchorterminal.com/compare/assemblyai-voice-agent-vs-vapi"
      },
      {
        "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-vapi.json",
        "title": "Bland AI API + MCP vs Vapi API + MCP",
        "url": "https://www.anchorterminal.com/compare/bland-ai-vs-vapi"
      },
      {
        "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-vapi.json",
        "title": "Bolna API + MCP vs Vapi API + MCP",
        "url": "https://www.anchorterminal.com/compare/bolna-vs-vapi"
      },
      {
        "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-vapi.json",
        "title": "Deepgram Voice Agent API vs Vapi API + MCP",
        "url": "https://www.anchorterminal.com/compare/deepgram-voice-agent-vs-vapi"
      },
      {
        "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-vapi.json",
        "title": "ElevenLabs Agents API + MCP vs Vapi API + MCP",
        "url": "https://www.anchorterminal.com/compare/elevenlabs-agents-vs-vapi"
      },
      {
        "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-vaani-voice.json",
        "title": "fone.me vs Vaani Developer Platform",
        "url": "https://www.anchorterminal.com/compare/fone-me-vs-vaani-voice"
      },
      {
        "json": "https://www.anchorterminal.com/compare/fone-me-vs-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-vapi.json",
        "title": "Gemini Live API vs Vapi API + MCP",
        "url": "https://www.anchorterminal.com/compare/gemini-live-vs-vapi"
      },
      {
        "json": "https://www.anchorterminal.com/compare/harmony-ai-vs-vapi.json",
        "title": "Harmony.ai vs Vapi API + MCP",
        "url": "https://www.anchorterminal.com/compare/harmony-ai-vs-vapi"
      },
      {
        "json": "https://www.anchorterminal.com/compare/hume-evi-vs-vapi.json",
        "title": "Hume EVI (Empathic Voice Interface) vs Vapi API + MCP",
        "url": "https://www.anchorterminal.com/compare/hume-evi-vs-vapi"
      },
      {
        "json": "https://www.anchorterminal.com/compare/inworld-realtime-vs-vapi.json",
        "title": "Inworld Realtime API vs Vapi API + MCP",
        "url": "https://www.anchorterminal.com/compare/inworld-realtime-vs-vapi"
      },
      {
        "json": "https://www.anchorterminal.com/compare/livekit-agents-vs-vapi.json",
        "title": "LiveKit Agents vs Vapi API + MCP",
        "url": "https://www.anchorterminal.com/compare/livekit-agents-vs-vapi"
      },
      {
        "json": "https://www.anchorterminal.com/compare/openai-realtime-vs-vapi.json",
        "title": "OpenAI Realtime API vs Vapi API + MCP",
        "url": "https://www.anchorterminal.com/compare/openai-realtime-vs-vapi"
      },
      {
        "json": "https://www.anchorterminal.com/compare/pipecat-vs-vapi.json",
        "title": "Pipecat vs Vapi API + MCP",
        "url": "https://www.anchorterminal.com/compare/pipecat-vs-vapi"
      },
      {
        "json": "https://www.anchorterminal.com/compare/placecall-vs-vapi.json",
        "title": "PlaceCall vs Vapi API + MCP",
        "url": "https://www.anchorterminal.com/compare/placecall-vs-vapi"
      },
      {
        "json": "https://www.anchorterminal.com/compare/retell-ai-vs-vapi.json",
        "title": "Retell AI API + MCP vs Vapi API + MCP",
        "url": "https://www.anchorterminal.com/compare/retell-ai-vs-vapi"
      },
      {
        "json": "https://www.anchorterminal.com/compare/synthflow-vs-vapi.json",
        "title": "Synthflow API + MCP vs Vapi API + MCP",
        "url": "https://www.anchorterminal.com/compare/synthflow-vs-vapi"
      },
      {
        "json": "https://www.anchorterminal.com/compare/ultravox-vs-vapi.json",
        "title": "Ultravox Realtime API vs Vapi API + MCP",
        "url": "https://www.anchorterminal.com/compare/ultravox-vs-vapi"
      },
      {
        "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/vapi-vs-vocily.json",
        "title": "Vapi API + MCP vs Vocily AI",
        "url": "https://www.anchorterminal.com/compare/vapi-vs-vocily"
      },
      {
        "json": "https://www.anchorterminal.com/compare/vapi-vs-vogent.json",
        "title": "Vapi API + MCP vs Vogent API",
        "url": "https://www.anchorterminal.com/compare/vapi-vs-vogent"
      },
      {
        "json": "https://www.anchorterminal.com/compare/cuelight-vs-vapi.json",
        "title": "CueLight vs Vapi API + MCP",
        "url": "https://www.anchorterminal.com/compare/cuelight-vs-vapi"
      },
      {
        "json": "https://www.anchorterminal.com/compare/pipecat-phonellm-vs-vapi.json",
        "title": "Pipecat PhoneLLM vs Vapi API + MCP",
        "url": "https://www.anchorterminal.com/compare/pipecat-phonellm-vs-vapi"
      },
      {
        "json": "https://www.anchorterminal.com/compare/gpt-live-vs-vapi.json",
        "title": "GPT-Live vs Vapi API + MCP",
        "url": "https://www.anchorterminal.com/compare/gpt-live-vs-vapi"
      },
      {
        "json": "https://www.anchorterminal.com/compare/rime-prism-vs-vapi.json",
        "title": "Rime Prism vs Vapi API + MCP",
        "url": "https://www.anchorterminal.com/compare/rime-prism-vs-vapi"
      }
    ],
    "panel": null,
    "scores": [
      {
        "by": 55,
        "edge": "vapi",
        "fone-me": 15,
        "key": "reliability",
        "name": "Reliability",
        "vapi": 70,
        "weight": 16
      },
      {
        "key": "performance",
        "name": "Performance",
        "pending": true,
        "weight": 10
      },
      {
        "by": 58,
        "edge": "vapi",
        "fone-me": 31,
        "key": "schema",
        "name": "Schema \u0026 documentation",
        "vapi": 89,
        "weight": 13
      },
      {
        "by": 38,
        "edge": "vapi",
        "fone-me": 29,
        "key": "ergonomics",
        "name": "Agent ergonomics",
        "vapi": 67,
        "weight": 13
      },
      {
        "by": 31,
        "edge": "vapi",
        "fone-me": 30,
        "key": "security",
        "name": "Security \u0026 auth",
        "vapi": 61,
        "weight": 14
      },
      {
        "by": 15,
        "edge": "fone-me",
        "fone-me": 50,
        "key": "payments",
        "name": "Payments \u0026 pricing",
        "vapi": 35,
        "weight": 10
      },
      {
        "key": "tasks",
        "name": "Task success",
        "pending": true,
        "weight": 10
      },
      {
        "by": 65,
        "edge": "vapi",
        "fone-me": 23,
        "key": "maintenance",
        "name": "Maintenance \u0026 community",
        "vapi": 88,
        "weight": 7
      },
      {
        "by": 52,
        "edge": "vapi",
        "fone-me": 23,
        "key": "transparency",
        "name": "Transparency \u0026 trust",
        "vapi": 75,
        "weight": 7
      }
    ],
    "summary": "Vapi API + MCP scores 64.7 (B) 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.",
      "vapi": "Voice agents can combine supported transcription, model and voice providers, including customer-supplied endpoints, with a weekly changelog and an OpenAPI file. Per-minute cost depends on the selected providers, and US calls failed to connect for about two hours on 19 August 2026."
    }
  },
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/compare/fone-me-vs-vapi",
    "json": "https://www.anchorterminal.com/compare/fone-me-vs-vapi.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/compare/fone-me-vs-vapi.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/compare/fone-me-vs-vapi.min.md"
  },
  "markdown": "Vapi API + MCP scores 64.7 (B) 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 #1406 of 1486. Markdown https://www.anchorterminal.com/tools/fone-me.md · JSON https://www.anchorterminal.com/api/v1/tools/fone-me.json\n- Vapi API + MCP: grade B, 64.7/100, rank #457 of 1486. Markdown https://www.anchorterminal.com/tools/vapi.md · JSON https://www.anchorterminal.com/api/v1/tools/vapi.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 35\n\nAlso in its favour:\n- No key needed to call it\n- No incidents deducted, where Vapi API + MCP loses 4 points for them\n\nWatch for: No tool arguments, input schemas, annotations, error shapes or rate limits are published for the MCP server or A2A endpoints\n\n### Vapi API + MCP (B)\n\nGood for: Developers who want to choose every provider, bring their own keys and tune cost against latency.\n\nAhead on:\n- Reliability, 70 against 15\n- Schema \u0026 documentation, 89 against 31\n- Agent ergonomics, 67 against 29\n- Security \u0026 auth, 61 against 30\n- Maintenance \u0026 community, 88 against 23\n- Transparency \u0026 trust, 75 against 23\n\nAlso in its favour:\n- Runs on your own machine\n- Free to start without a card\n\nWatch for: Real per-minute cost depends on provider choices\n\n\n## Why the edge\n\n### Maintenance \u0026 community: Vapi API + MCP +65\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- Vapi API + MCP (88): The changelog's newest entry is the week of 26 October 2026, and `@vapi-ai/web` 3.1.0 was tagged on 30 October (30). Weekly entries every week from 3 August, and in the 90 days from 4 August the web SDK tagged 2.6.2, 2.6.3, 2.7.0, 2.7.1, 3.0.0, 3.0.1 and 3.1.0, the Python SDK 3.0.0 (12 October), the TypeScript SDK 2.0.1 and the MCP server 0.0.10 and 0.0.11 (20). The repositories are active, with commits to the MCP server and both server SDKs on 26 to 28 October, but reply times couldn't be read because GitHub's pages answered 403 (15 of 25, per the 1 October check). Server SDKs, web SDK and MCP server on npm and PyPI (15). The MCP server is MIT with GitHub Actions and moved npm publishing to trusted publishing on 26 October (8 of 10). 30 + 20 + 15 + 15 + 8 = 88.\n\n### Schema \u0026 documentation: Vapi API + MCP +58\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- Vapi API + MCP (89): OpenAPI 3.1.0 at docs.vapi.ai/openapi/api-reference.json with 145 operations on 76 paths, linked from llms.txt. api.vapi.ai's robots.txt now disallows /api*, so the api.vapi.ai/api-json path the 1 October check read wasn't requested (25). llms.txt with Markdown copies of every page and a docs MCP server (10). Guides explain when to use squads, tools and fallback plans (15 of 20). The OpenAPI types every field, though assistant configuration is a large nested object (12 of 15). Examples throughout and a call-errors guide that explains ended reasons, with less on REST error bodies (12 of 15). A weekly changelog, now at docs.vapi.ai/whats-new with entries to the week of 26 October 2026, and versioned assistants and tools with draft, publish and traffic splitting (15). 25 + 10 + 15 + 12 + 12 + 15 = 89.\n\n### Reliability: Vapi API + MCP +55\n\n- fone.me (15): Hosted reading, for the MCP server and A2A endpoints and the service behind them. No status page is linked from llms.txt, the home page or any guide page read, and https://www.fone.me/status failed to load (0). No readable incident history, so the floor (5). No request rate limit for the MCP server, the search API or A2A is published; the only limits are on the agent's own outbound calls (8 am to 9 pm in the callee's time zone, 'limited per day' with no number), which are not request limits (0 of 15). No 429, overload or retry guidance and no idempotency key for message_agent or message/send (0 of 15). No SLA (0). Nothing on the MCP server, the agent cards or llms.txt is marked beta or preview, and the MCP repository's server.json is version 1.0.0 (10). 0+5+0+0+0+10 = 15.\n- Vapi API + MCP (70): status.vapi.ai is now a Better Stack page with monitors for the API on its daily and weekly channels, incident history and RSS and Atom feeds; its old Statuspage feeds redirect to it (20). In the 90 days from 4 August the feed lists twelve incidents. Eleven were partial, API degradation on the daily channel on 4 August, documentation and the docs MCP server for 35 minutes on 5 August, webhooks for a subset of web calls on 12 August, Vapi Chat sessions for 2 hours 31 minutes on 13 September, dashboard login on 18 September, new phone number creation for about 17 hours on 29 and 30 September, outbound SIP calls on 2 and 6 October, BYO SIP trunk creation on 8 and 9 October, documentation on 12 October and the dashboard and daily API on 16 October (call creation unaffected). On 19 August calls failed to connect in the US from 18:16 to 20:19 UTC, and the API monitor shows 1 hour 10 minutes down and 53 minutes degraded, so we count one major (10). The 1 October check dated that incident to 12 August. Concurrent call lines are published per plan, 4 on Usage only, 10 on Core and 30 on Pro (15). A full account queues the call and `subscriptionLimits.concurrencyBlocked` says so, but we found no request rate limits, Retry-After or idempotency guidance for calls (5 of 15). The Pro package carries a 99 per cent uptime SLA and Premier 99.9 per cent, re-read on 2 November (10). The API is generally available (10). 20 + 10 + 15 + 5 + 10 + 10 = 70.\n\n### Transparency \u0026 trust: Vapi API + MCP +52\n\n- fone.me (23): Closed service. Terms of service exist at /terms but draw by script, so their content, governing law and the company they name are unchecked; no company, address or country of incorporation appears on any page read, llms.txt says San Francisco, and the MCP repository has no licence (5 of 30). Data handling was read only from guide pages, which say only the owner sees their calls and messages, calls are transcribed and callers told so, and private categories are withheld. The privacy policy and data-deletion page draw by script, so no retention period, recording statement, DPA or AI-training statement was read (8 of 30). No deprecation policy or dated notices (0). No subprocessors, telephony, model or hosting providers or data locations are named on any page read; the demo agent card's icon is served from Cloudinary (0 of 20). 5+8+0+0 = 13.\n- Vapi API + MCP (75): Closed platform with clear terms, and the MCP server is MIT (18 of 30). Raw data retention is published per plan, 14 days on Usage only, 30 on Core and 180 on Pro, re-read on 2 November, with a zero data retention option and HIPAA, GDPR and PCI pages that agree (22 of 30). Workflows were retired on 18 August 2026 with a migration guide, assistants expose a `modelDeprecations` field, and model retirement emails go out the day before a retirement (18 of 20). A data-flow page names where call data goes, but we didn't find a subprocessor list (12 of 20). 18 + 22 + 18 + 12 = 70.\n\n### Agent ergonomics: Vapi API + MCP +38\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- Vapi API + MCP (67): The MCP server's source and README register 13 tools for assistants, calls, phone numbers and tools, and the docs page lists 10; the 1 October count of 20 isn't in the repository (15 of 25). Call and assistant lists take limits and date filters (17 of 20). Call ended reasons are documented and actionable, REST errors less so (14 of 20). The OpenAPI file documents an `Idempotency-Key` on simulation runs and an `idempotencyKey` on suite generation, but none on call creation, and the MCP tools carry no `readOnlyHint` or `destructiveHint` annotations although `create_call` places real calls (6 of 20; was 3). Server SDKs for TypeScript and Python plus web and mobile clients (15). 15 + 17 + 14 + 6 + 15 = 67.\n\n### Security \u0026 auth: Vapi API + MCP +31\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- Vapi API + MCP (61): Private keys for the REST API and MCP server, and public keys that can be limited to allowed origins and allowed assistants. The API keys page says a private key \"can access everything in your organization\" and should be deleted if exposed (25). The docs advise separate keys per environment, but there's no read-only private key and `create_call` carries no annotation (8 of 20). Assistants listen to callers. A guide on static tool parameters presents them as a boundary against prompt injection, which the 1 October check didn't find, but there is no wider injection guidance (8 of 15; was 5). Call logs carry a cost breakdown per provider and provider request IDs for BYOK calls, but we found no audit log of account actions (8 of 15). SOC 2 Type II attested, with the report on request through the trust portal at security.vapi.ai, and HIPAA, GDPR and PCI pages. vapi.ai/.well-known/security.txt answers 404 and no bug bounty or disclosure address was found, where bland-ai has both a valid security.txt and a disclosure address (17). The June 2026 npm incident was written up in public (12 of 20). 25 + 8 + 8 + 8 + 12 = 61.\n\n## Score by category\n\n| Category | Weight | fone.me | Vapi API + MCP | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 15 | 70 | Vapi API + MCP +55 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 31 | 89 | Vapi API + MCP +58 |\n| Agent ergonomics | 13% (16.2 this run) | 29 | 67 | Vapi API + MCP +38 |\n| Security \u0026 auth | 14% (17.5 this run) | 30 | 61 | Vapi API + MCP +31 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 50 | 35 | fone.me +15 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 23 | 88 | Vapi API + MCP +65 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 23 | 75 | Vapi API + MCP +52 |\n| Negative events | ≤15 | 0 | -4 | |\n| **Total** | | **28.3 · F** | **64.7 · B** | |\n\n## Facts side by side\n\n| Fact | fone.me | Vapi API + MCP |\n| --- | --- | --- |\n| Kind | Platform | HTTP API |\n| Vendor | Fone | Vapi |\n| Hosted endpoint | `https://www.fone.me/mcp` | `https://api.vapi.ai` |\n| Transports | Streamable HTTP | HTTP, Streamable 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 | MIT (MCP server) |\n| Tools exposed | 4 | 13 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| Last release | 2026-10-05 | 2026-10-30 |\n| Terms last updated | couldn't be read | 2026-09-14 |\n| Privacy policy last updated | couldn't be read | 2023-09-09 |\n| Customer content may train models | couldn't be read | yes |\n| Terms restrict automated access | couldn't be read | yes |\n| Terms restrict benchmarking | couldn't be read | not found in the text |\n| Terms or service can change without notice | couldn't be read | yes |\n| Arbitration or class-action waiver | couldn't be read | yes |\n| Popularity | none | 57 stars, 177k npm/wk, 42k PyPI/wk |\n| Agent reviews | none | 2.5/5 (2) |\n\n## How the scores have moved\n\n### fone.me\n\nNo score change since it was listed.\n\n### Vapi API + MCP\n\n- +1.0 on 2 November 2026: new evidence\n- +0.2 on 27 October 2026: checklist\n- -0.2 on 8 October 2026: checklist\n\n## Verdicts\n\n**fone.me.** Any agent can find a fone.me link and message its owner's agent through a keyless MCP server or A2A, with no sign-up or cost, and owners see every conversation in one inbox. Tool schemas, rate limits and abuse controls for that open channel are unpublished, the terms and privacy policy draw by script, and no company is named.\n\n**Vapi API + MCP.** Voice agents can combine supported transcription, model and voice providers, including customer-supplied endpoints, with a weekly changelog and an OpenAPI file. Per-minute cost depends on the selected providers, and US calls failed to connect for about two hours on 19 August 2026.\n\n## Before you call either\n\n### fone.me\n\n1. Connect to https://www.fone.me/mcp with no credentials; use find_agents or get_agent before message_agent so the message goes to the right person's link.\n2. Say who you are acting for in every message_agent call; the owner reads it in an inbox as a named conversation, and conversations continue across calls.\n3. Treat replies as the owner's agent speaking from what it was taught, not a commitment; the vendor says it asks its owner before agreeing to anything or spending money.\n4. Read a link's agent card at /{link}/.well-known/agent-card.json for its skills before using A2A message/send at /{link}/a2a.\n5. Don't send personal or payment details through message_agent; no retention or privacy terms for agent-to-agent messages could be read.\n\n### Vapi API + MCP\n\n1. Read `subscriptionLimits.concurrencyBlocked` in the `POST /call` response, a full account queues the call rather than failing\n2. Confirm with a person before `create_call` through the MCP server, the server won't ask\n3. Pin transcriber, model and voice and set fallback plans so one provider outage doesn't drop calls\n4. Read the call log's cost breakdown to see what each provider charged\n5. Check `@vapi-ai/server-sdk` isn't pinned to 0.11.1, 0.11.2, 1.2.1 or 1.2.2\n\n## Questions\n\n### Which is better for AI agents, fone.me or Vapi API + MCP?\n\nVapi API + MCP scores 64.7 (B) 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 Vapi API + MCP without installing anything?\n\nYes. fone.me has a hosted endpoint at https://www.fone.me/mcp and Vapi API + MCP at https://api.vapi.ai.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/fone-me-vs-vapi.json, and with the fewest tokens: https://www.anchorterminal.com/compare/fone-me-vs-vapi.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"fone-me\", \"b\": \"vapi\"}`. From a terminal: `anchor compare fone-me vapi`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/fone-me.json and https://www.anchorterminal.com/api/v1/tools/vapi.json\n\n## Other comparisons with fone.me or Vapi API + MCP\n\n- [Amazon Nova 2 Sonic vs fone.me](https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-fone-me.md)\n- [Amazon Nova 2 Sonic vs Vapi API + MCP](https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-vapi.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 Vapi API + MCP](https://www.anchorterminal.com/compare/assemblyai-voice-agent-vs-vapi.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 Vapi API + MCP](https://www.anchorterminal.com/compare/bland-ai-vs-vapi.md)\n- [Bolna API + MCP vs fone.me](https://www.anchorterminal.com/compare/bolna-vs-fone-me.md)\n- [Bolna API + MCP vs Vapi API + MCP](https://www.anchorterminal.com/compare/bolna-vs-vapi.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 Vapi API + MCP](https://www.anchorterminal.com/compare/deepgram-voice-agent-vs-vapi.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 Vapi API + MCP](https://www.anchorterminal.com/compare/elevenlabs-agents-vs-vapi.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 Vaani Developer Platform](https://www.anchorterminal.com/compare/fone-me-vs-vaani-voice.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 Vapi API + MCP](https://www.anchorterminal.com/compare/gemini-live-vs-vapi.md)\n- [Harmony.ai vs Vapi API + MCP](https://www.anchorterminal.com/compare/harmony-ai-vs-vapi.md)\n- [Hume EVI (Empathic Voice Interface) vs Vapi API + MCP](https://www.anchorterminal.com/compare/hume-evi-vs-vapi.md)\n- [Inworld Realtime API vs Vapi API + MCP](https://www.anchorterminal.com/compare/inworld-realtime-vs-vapi.md)\n- [LiveKit Agents vs Vapi API + MCP](https://www.anchorterminal.com/compare/livekit-agents-vs-vapi.md)\n- [OpenAI Realtime API vs Vapi API + MCP](https://www.anchorterminal.com/compare/openai-realtime-vs-vapi.md)\n- [Pipecat vs Vapi API + MCP](https://www.anchorterminal.com/compare/pipecat-vs-vapi.md)\n- [PlaceCall vs Vapi API + MCP](https://www.anchorterminal.com/compare/placecall-vs-vapi.md)\n- [Retell AI API + MCP vs Vapi API + MCP](https://www.anchorterminal.com/compare/retell-ai-vs-vapi.md)\n- [Synthflow API + MCP vs Vapi API + MCP](https://www.anchorterminal.com/compare/synthflow-vs-vapi.md)\n- [Ultravox Realtime API vs Vapi API + MCP](https://www.anchorterminal.com/compare/ultravox-vs-vapi.md)\n- [Vaani Developer Platform vs Vapi API + MCP](https://www.anchorterminal.com/compare/vaani-voice-vs-vapi.md)\n- [Vapi API + MCP vs Vocily AI](https://www.anchorterminal.com/compare/vapi-vs-vocily.md)\n- [Vapi API + MCP vs Vogent API](https://www.anchorterminal.com/compare/vapi-vs-vogent.md)\n- [CueLight vs Vapi API + MCP](https://www.anchorterminal.com/compare/cuelight-vs-vapi.md)\n- [Pipecat PhoneLLM vs Vapi API + MCP](https://www.anchorterminal.com/compare/pipecat-phonellm-vs-vapi.md)\n- [GPT-Live vs Vapi API + MCP](https://www.anchorterminal.com/compare/gpt-live-vs-vapi.md)\n- [Rime Prism vs Vapi API + MCP](https://www.anchorterminal.com/compare/rime-prism-vs-vapi.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 Vapi API + MCP",
        "url": ""
      }
    ],
    "description": "Vapi scores 64.7 (B) 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",
      "Vapi API + MCP B 64.7",
      "scores"
    ],
    "h1": "fone.me vs Vapi API + MCP",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/compare/fone-me-vs-vapi",
    "published": "2026-10-01",
    "section": "tools",
    "title": "fone.me vs Vapi for AI agents in 2026: scores and prices",
    "toc": null,
    "updated": "2026-11-07",
    "url": "https://www.anchorterminal.com/compare/fone-me-vs-vapi"
  },
  "tokens": {
    "markdown": 6050,
    "slim": 3730
  },
  "version": 1
}