{ "data": { "a": { "slug": "bland-ai", "name": "Bland AI API + MCP", "vendor": "Bland AI", "vendorUrl": "https://www.bland.ai", "kind": "http-api", "category": "voice-agents", "summary": "Phone-first voice-agent platform that runs its own speech recognition, language model, TTS and telephony, billed as one per-minute rate.", "url": "https://www.anchorterminal.com/tools/bland-ai", "markdownUrl": "https://www.anchorterminal.com/tools/bland-ai.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/bland-ai.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/bland-ai.json", "dns": "bland-ai.grade.anchorterminal.com", "transports": [ "http", "streamable-http", "stdio" ], "remoteUrl": "https://api.bland.ai/v1", "packages": [ { "registry": "npm", "name": "bland-cli" } ], "auth": "api-key", "authNotes": "API key in the `Authorization` header for REST, and as `Bearer org_...` for the hosted MCP server at `https://api.bland.ai/v1/mcp`. The `bland mcp` command in the CLI runs a local stdio server. An agent can sign its owner up through a device-code flow or a headless flow that needs a texted 6-digit code from the owner.", "pricing": "freemium", "pricingNotes": "Start is free to join with 2 credits and an inbound number, no card, then $0.14 a connected minute and $0.05 a transfer minute, 10 concurrent calls, 100 calls an hour and 100 a day. Build is $299 a month with $0.12 a minute, $0.04 transfer, 50 concurrent calls, 1,000 an hour and 2,000 a day. The billing docs still list Scale at $499 a month with $0.11 a minute, $0.03 transfer, 100 concurrent calls and 5,000 calls a day, though the pricing page now shows only Start, Build and Enterprise. Enterprise is custom. Every outbound attempt has a $0.015 minimum and failed calls are charged $0.015. SMS is $0.02 a message. The rate covers STT, LLM, TTS and telephony, and BYO Twilio customers pay no transfer fee. An Agent Phone Plan for personal AI agents is $29.99 a month ($14.99 the first month) (https://www.bland.ai/pricing, https://docs.bland.ai/platform/billing).", "priceSummary": "$299 / mo", "where": "both", "x402": { "level": "no", "evidence": "No x402 support in the docs, pricing page or MCP docs (checked 2026-09-30). Headless signup for the Agent Phone Plan answers HTTP 402 with a Machine Payments Protocol challenge settled through Stripe Link, which is a different protocol from x402 and only covers that plan (https://docs.bland.ai/platform/agent-headless-onboarding).", "endpoints": [] }, "toolCount": 42, "popularity": { "githubStars": null, "npmWeekly": 1179, "pypiWeekly": null, "asOf": "2026-09-30" }, "docsUrl": "https://docs.bland.ai", "llmsTxt": "https://docs.bland.ai/llms.txt", "capabilities": [ "voice.agent", "voice.pipeline", "voice.tools", "voice.telephony" ], "tags": [ "hosted", "closed-source", "freemium", "no-card", "mcp", "llms-txt", "webhooks", "pipeline", "enterprise" ], "lastRelease": "2026-09-13", "graded": true, "anchor": { "graded": true, "score": 67, "grade": "B", "agentReady": false, "rank": 342, "ranked": true, "rankOf": 1486, "categoryRank": 7, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 53, "maintenance": 70, "payments": 65, "reliability": 65, "schema": 68, "security": 79, "transparency": 72 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-02" }, "negative": 0, "verdict": "One per-minute rate covering STT, LLM, TTS and telephony, $0.14 on Start and $0.12 on Build, and restricted keys with per-resource scopes rolling out. No OpenAPI document, the MCP server lists over 340 tools without toolsets, and the product changelog's newest entry is from 3 August 2026.", "bestFor": "Teams that want one predictable per-minute bill for outbound and inbound phone agents, and personal agents that need their own US number.", "strengths": [ "One per-minute rate covering STT, LLM, TTS and telephony, $0.14 on Start and $0.12 on Build", "Start plan with 2 credits and an inbound number, no card", "Restricted API keys with per-resource scopes and OAuth client credentials, rolling out by organisation", "Headless agent signup that needs only a 6-digit texted code from the owner", "Subprocessor list with locations and a valid security.txt" ], "weaknesses": [ "No OpenAPI document", "The hosted MCP server lists 62 dedicated and 282 API Reference tools with no toolsets", "Failed calls and outbound attempts cost $0.015 each", "No product changelog entry since 3 August 2026", "Privacy policy gives no retention period for recordings or transcripts" ], "agentNotes": [ "Call `wait_for_call` (it waits up to 45 seconds) instead of polling `get_call_log`", "Keep client tool-approval prompts on for destructive MCP tools; the server no longer asks for confirmation", "Space calls to the same number at least 10 seconds apart or expect a 429", "Budget $0.015 for every outbound attempt, including ones that never connect", "Use a restricted key with only the scopes you need for REST calls; the MCP server needs a full-access key or sign-in" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 2, "avgRating": 3, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 67 } ], "editorialScores": { "ergonomics": 53, "maintenance": 70, "payments": 65, "reliability": 65, "schema": 68, "security": 79, "transparency": 55 }, "provenanceScore": 89, "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 -X POST https://api.bland.ai/v1/calls -H \"Authorization: $BLAND_API_KEY\" \\\n -H \"content-type: application/json\" \\\n -d '{\"phone_number\":\"+15551234567\",\"task\":\"Confirm tomorrow 3pm appointment and ask if they need to reschedule.\"}'", "claudeCode": "claude mcp add --transport http bland https://api.bland.ai/v1/mcp --header \"Authorization: Bearer $BLAND_API_KEY\"", "config": { "mcpServers": { "bland": { "args": [ "bland-cli", "mcp" ], "command": "npx", "env": { "BLAND_API_KEY": "${BLAND_API_KEY}" } } } } }, "letme": { "capability": "https://letme.dev/voice.agent", "tool": "https://letme.dev/bland-ai" }, "area": "voice", "unitPrices": [ { "item": "Start plan connected minute", "unit": "call-minute", "usd": 0.14, "note": "all in, STT, LLM, TTS and telephony" }, { "item": "Build plan connected minute", "unit": "call-minute", "usd": 0.12, "note": "all in, plus $299 a month" }, { "item": "Start plan transfer minute", "unit": "call-minute", "usd": 0.05, "note": "Bland numbers only" }, { "item": "Build plan", "unit": "month", "usd": 299 }, { "item": "Agent Phone Plan", "unit": "month", "usd": 29.99, "note": "$14.99 the first month" } ], "provenance": { "legalEntity": "Intelliga Corporation", "domain": "bland.ai", "domainRegistered": "2023-07-30", "endpointOnVendorDomain": true, "terms": "https://www.bland.ai/legal/terms", "privacy": "https://www.bland.ai/legal/privacy", "statusPage": "https://status.bland.ai", "changelog": "https://www.bland.ai/changelog", "securityTxt": "valid", "checked": "2026-11-02", "notes": [ "The terms (last updated 2026-08-28) define Bland AI as Intelliga Corporation, d/b/a Bland AI, and the privacy policy (last updated 2026-06-23) names Intelliga Corp DBA Bland AI. The 1 October check recorded Bland Inc. from the terms, which the page doesn't say.", "security.txt re-read on 2 November, valid until 2027-04-05." ], "score": 89 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/bland-ai.json", "live": { "slug": "bland-ai", "probe": { "target": "https://api.bland.ai/v1", "method": "get", "lastAt": "2026-11-07T18:20:14.153132337Z", "lastOk": true, "lastStatus": 404, "lastMs": 455, "authRequired": false, "uptime24h": 100, "uptime30d": 99.99, "p50ms24h": 286, "p95ms24h": 921, "samples24h": 239, "samples30d": 7910, "days": [ { "date": "2026-10-07", "probes": 272, "ok": 272 }, { "date": "2026-10-08", "probes": 268, "ok": 268 }, { "date": "2026-10-09", "probes": 250, "ok": 250 }, { "date": "2026-10-10", "probes": 247, "ok": 247 }, { "date": "2026-10-11", "probes": 247, "ok": 247 }, { "date": "2026-10-12", "probes": 247, "ok": 247 }, { "date": "2026-10-13", "probes": 248, "ok": 248 }, { "date": "2026-10-14", "probes": 249, "ok": 249 }, { "date": "2026-10-15", "probes": 253, "ok": 253 }, { "date": "2026-10-16", "probes": 252, "ok": 252 }, { "date": "2026-10-17", "probes": 253, "ok": 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": 251, "ok": 251 }, { "date": "2026-10-29", "probes": 249, "ok": 249 }, { "date": "2026-10-30", "probes": 248, "ok": 248 }, { "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.bland.ai", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-11-07T18:20:36.672065774Z" }, "versions": [ { "registry": "npm", "name": "bland-cli", "version": "0.10.1", "seenAt": "2026-11-06T23:11:32.614044276Z" } ], "npmWeekly": 927, "securityTxt": { "url": "https://bland.ai/.well-known/security.txt", "state": "valid", "expires": "2027-04-05T00:00:00.000Z", "checkedAt": "2026-11-07T16:01:45.257873207Z" }, "llmsTxt": { "url": "https://docs.bland.ai/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:31:43.530476107Z" }, "domain": { "domain": "bland.ai", "registered": "2023-07-30", "source": "https://rdap.identitydigital.services/rdap/domain/bland.ai", "checkedAt": "2026-11-01T14:10:34.382724721Z" }, "pages": [ { "url": "https://www.bland.ai/changelog", "kind": "changelog", "status": 200, "checkedAt": "2026-11-07T14:25:48.675285316Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "d73002ae0cca" }, { "url": "https://docs.bland.ai/platform/billing", "kind": "deprecations", "status": 200, "checkedAt": "2026-11-07T14:05:18.42108214Z", "changedAt": "2026-11-04T08:20:07.196287026Z", "fingerprint": "8af49f4a7052" }, { "url": "https://www.bland.ai/pricing", "kind": "pricing", "status": 200, "checkedAt": "2026-11-07T14:25:54.983972534Z", "changedAt": "2026-11-03T08:03:50.581468723Z", "fingerprint": "668a77131455" }, { "url": "https://www.bland.ai/legal/privacy", "kind": "privacy", "status": 200, "checkedAt": "2026-11-07T14:25:51.186792164Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "b2d6dc77b3fe" }, { "url": "https://www.bland.ai/legal/terms", "kind": "terms", "status": 200, "checkedAt": "2026-11-07T14:25:53.200511189Z", "changedAt": "2026-10-16T22:34:47.650331397Z", "fingerprint": "ff68518bd660" } ], "mcpTools": { "url": "https://api.bland.ai/v1/mcp", "checkedAt": "2026-11-07T01:42:51.648544902Z", "status": "auth", "note": "asks for credentials before listing its tools", "changedAt": "2026-11-07T01:42:51.648544902Z" }, "updatedAt": "2026-11-07T18:20:14.153132337Z" } }, "answer": "Bland AI API + MCP scores 67 (B) on agent readiness against fone.me's 28.3 (F), and leads in every scored category.", "b": { "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" } }, "edges": [ { "by": 50, "category": "reliability", "leads": "bland-ai", "name": "Reliability", "reasons": { "a": "Atlassian Statuspage at status.bland.ai with US, Asia Pacific and Canada components and an incident history back to 20 October 2025, read on 2 November through its history feed (20). Six incidents in the 90 days from 4 August. Five were partial and read as minor, latency of 30 minutes on 27 August and 35 minutes on 14 September, delayed or missing audio on BTTS V3 voices for about two hours on 25 September (some calls, one voice family), variable extraction failing for some customers for about an hour on 5 October, and inbound calls in the US region failing for 8 minutes on 19 October with outbound unaffected. On 14 October, from about 3:00 to 4:10 PM PT, an upstream outage took down the language model every agent uses in conversation, live calls went silent or slow and outbound dispatch was paused, which we count as one major (10). Numeric limits are published, 10 concurrent, 100 an hour and 100 a day on Start, 50, 1,000 and 2,000 on Build, 120 MCP requests a minute and one call per number every 10 seconds (15). The call API documents 429 responses with messages, but we found no Retry-After, backoff or idempotency guidance (5 of 15). The pricing page claims a 99.9 per cent uptime SLA on every plan, while the terms of 28 August 2026 give no uptime commitment and no credits, so we give half (5). The API is generally available (10). 20 + 10 + 15 + 5 + 5 + 10 = 65.", "b": "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." }, "scores": { "a": 65, "b": 15 } }, { "by": 49, "category": "security", "leads": "bland-ai", "name": "Security \u0026 auth", "reasons": { "a": "Organisation API keys, several per organisation and each revocable on its own, and since the 1 October check restricted keys with per-resource scopes (`calls:read`, `calls:create`, `agents:write` and others) and OAuth client credentials with the same permissions for short-lived tokens (an organisation that doesn't see OAuth clients in its dashboard is told to contact support). Restricted keys are rolling out by organisation and aren't available on pinned deployments, credited as conditional availability elsewhere in this run (30). A key can now be limited to read scopes, sign-in connections to the MCP server take `mcp:read` or `mcp:write` scopes, and destructive tools carry an annotation for the client's approval prompt. The server no longer asks for confirmation itself, and personas, numbers and tools stay full-access only (15 of 20). Agents read caller speech and transcripts, which are untrusted, and we found guard rails mentioned in the CLI but no prompt-injection guidance (5 of 15). Audit logs exist but are an enterprise function and don't record API key use, and every call has a log; the key list shows who created each key (12 of 15). security.txt valid until 2027-04-05 (re-read on 2 November), a trust portal, SOC 2 Type II and a PCI DSS assessment by a QSA per the vendor, and a disclosure address. No bug bounty found (17 of 20). 30 + 15 + 5 + 12 + 17 = 79.", "b": "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." }, "scores": { "a": 79, "b": 30 } }, { "by": 49, "category": "transparency", "leads": "bland-ai", "name": "Transparency \u0026 trust", "reasons": { "a": "Closed source with clear terms (15). The privacy policy (last updated 23 June 2026) keeps data 'as long as necessary' with no periods for recordings or transcripts, and the trust page says zero-retention processing is available. The terms and the privacy policy both name Intelliga Corporation, doing business as Bland AI (12 of 30). The December 2025 price change was announced with a date and transition credits, and the migration from pathways and personas to agents carries a 15 November 2026 deadline in the docs, but we found no deprecation policy (8 of 20). A subprocessor list of 17 entries with locations, updated 8 September 2026, per the 1 October check, not re-read on 2 November (20). 15 + 12 + 8 + 20 = 55.", "b": "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." }, "scores": { "a": 72, "b": 23 } }, { "by": 47, "category": "maintenance", "leads": "bland-ai", "name": "Maintenance \u0026 community", "reasons": { "a": "The newest entry in the product changelog is still 3 August 2026, 91 days before 2 November. Bland's official plugin for its hosted MCP server and Norm agent builder (CINTELLILABS/bland-plugins, MIT, linked from the docs) keeps a dated changelog, with bland 2.2.1 and norm 1.11.1 on 20 October 2026 (30). In the 90 days from 4 August, that changelog has 30 dated releases on 13 days from 8 September to 20 October, and the migration guide dates the agent architecture change to September 2026, while the product changelog's 6 July, 21 July and 3 August entries have left the window; the CLI's npm dates couldn't be read (20). Public changelog, no public issue tracker, and we didn't test support (8 of 15 for a closed service). Official tooling is the `bland-cli` npm package (Node 18 or later), a web SDK and a TTS Node library, with no server SDK in a second language (8 of 15). No public repository or CI for the CLI (4 of 10). 30 + 20 + 8 + 8 + 4 = 70.", "b": "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." }, "scores": { "a": 70, "b": 23 } }, { "by": 37, "category": "schema", "leads": "bland-ai", "name": "Schema \u0026 documentation", "reasons": { "a": "No OpenAPI document found. The MCP server's dedicated tools take typed inputs and its API Reference tools take each reference page's parameters, but no machine-readable contract is published (5 of 25). llms.txt with 551 entries, each page served as Markdown (10). MCP tool descriptions say when to use a tool, for example the reference tells agents to use `send_call` and to choose one of `agent_id`, `persona_id`, `pathway_id` or `task` (14 of 20). The REST reference types every parameter with enums and defaults, though pathways travel as a raw graph and `call_bland_api` is a free-form passthrough (11 of 15). Errors for 400, 401, 402, 403, 404, 429 and 500 are documented with example messages (13 of 15). Versioned v1 and v2 APIs, agent versions and environments, and a dated changelog (15). 5 + 10 + 14 + 11 + 13 + 15 = 68.", "b": "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." }, "scores": { "a": 68, "b": 31 } }, { "by": 24, "category": "ergonomics", "leads": "bland-ai", "name": "Agent ergonomics", "reasons": { "a": "The hosted MCP server lists 62 dedicated tools and 282 API Reference tools, one per reference page, plus 3 prompts on key connections. Sign-in connections see a smaller allowlist, but there are no toolsets or dynamic loading (5 of 25). List endpoints such as audit logs and knowledge bases page and filter, but we found no field selection on call logs (14 of 20). Errors carry codes and readable messages, and a restricted key's 403 names the permission it lacks (16 of 20). Every MCP tool carries a read, write or destructive annotation, but there are no idempotency keys on call creation (10 of 20). A call needs only `phone_number` and a `task`, `agent_id`, `persona_id` or `pathway_id`, with defaults for voice and temperature. Official tooling is the Node CLI, a web SDK and a TTS Node library, and we found no Python SDK (8 of 15). 5 + 14 + 16 + 10 + 8 = 53.", "b": "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." }, "scores": { "a": 53, "b": 29 } } ], "facts": [ { "a": "HTTP API", "b": "Platform", "name": "Kind" }, { "a": "Bland AI", "b": "Fone", "name": "Vendor" }, { "a": "https://api.bland.ai/v1", "b": "https://www.fone.me/mcp", "name": "Hosted endpoint" }, { "a": "HTTP, Streamable HTTP, stdio", "b": "Streamable HTTP", "name": "Transports" }, { "a": "API key", "b": "None", "name": "Auth" }, { "a": "Freemium", "b": "Freemium", "name": "Pricing" }, { "a": "$29.99 per month (plan)", "b": "not published", "name": "Price for voice agents" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "none", "b": "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", "name": "Licence" }, { "a": "42", "b": "4", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "2026-09-13", "b": "2026-10-05", "name": "Last release" }, { "a": "2026-08-28", "b": "couldn't be read", "name": "Terms last updated" }, { "a": "2026-06-23", "b": "couldn't be read", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "couldn't be read", "name": "Customer content may train models" }, { "a": "yes", "b": "couldn't be read", "name": "Terms restrict automated access" }, { "a": "not found in the text", "b": "couldn't be read", "name": "Terms restrict benchmarking" }, { "a": "yes", "b": "couldn't be read", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "couldn't be read", "name": "Arbitration or class-action waiver" }, { "a": "1.2k npm/wk", "b": "none", "name": "Popularity" }, { "a": "3/5 (2)", "b": "none", "name": "Agent reviews" } ], "faq": [ { "answer": "Bland AI API + MCP scores 67 (B) on agent readiness against fone.me's 28.3 (F), and leads in every scored category.", "question": "Which is better for AI agents, Bland AI API + MCP or fone.me?" }, { "answer": "Yes. Bland AI API + MCP has a hosted endpoint at https://api.bland.ai/v1 and fone.me at https://www.fone.me/mcp.", "question": "Can an agent call Bland AI API + MCP and fone.me without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 65 against 15", "Schema \u0026 documentation, 68 against 31", "Agent ergonomics, 53 against 29", "Security \u0026 auth, 79 against 30", "Payments \u0026 pricing, 65 against 50", "Maintenance \u0026 community, 70 against 23", "Transparency \u0026 trust, 72 against 23" ], "also": [ "Runs on your own machine", "Free to start without a card" ], "goodFor": "Teams that want one predictable per-minute bill for outbound and inbound phone agents, and personal agents that need their own US number.", "slug": "bland-ai", "watchFor": "No OpenAPI document" }, { "aheadOn": null, "also": [ "No key needed to call it" ], "goodFor": "Agents acting for a person who need to reach a freelancer's, shop's or small business's own AI agent at its fone.me link to ask a question, request a booking or quote or leave a message, and owners who want an answering agent on a link, WhatsApp, Telegram and a $9.99 number without building one.", "slug": "fone-me", "watchFor": "No tool arguments, input schemas, annotations, error shapes or rate limits are published for the MCP server or A2A endpoints" } ], "history": { "bland-ai": [ { "causes": [ "product" ], "date": "2026-11-02", "delta": 3.1, "from": 63.9, "fromGrade": "B", "to": 67, "toGrade": "B" }, { "causes": [ "evidence" ], "date": "2026-10-27", "delta": 0.1, "from": 63.8, "fromGrade": "B", "to": 63.9, "toGrade": "B" }, { "causes": [ "method" ], "date": "2026-10-08", "delta": -0.3, "from": 64.1, "fromGrade": "B", "to": 63.8, "toGrade": "B" } ], "fone-me": null }, "job": { "capability": "voice.agent", "name": "Voice agents" }, "others": [ { "json": "https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-bland-ai.json", "title": "Amazon Nova 2 Sonic vs Bland AI API + MCP", "url": "https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-bland-ai" }, { "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/assemblyai-voice-agent-vs-bland-ai.json", "title": "AssemblyAI Voice Agent API vs Bland AI API + MCP", "url": "https://www.anchorterminal.com/compare/assemblyai-voice-agent-vs-bland-ai" }, { "json": "https://www.anchorterminal.com/compare/assemblyai-voice-agent-vs-fone-me.json", "title": "AssemblyAI Voice Agent API vs fone.me", "url": "https://www.anchorterminal.com/compare/assemblyai-voice-agent-vs-fone-me" }, { "json": "https://www.anchorterminal.com/compare/bland-ai-vs-bolna.json", "title": "Bland AI API + MCP vs Bolna API + MCP", "url": "https://www.anchorterminal.com/compare/bland-ai-vs-bolna" }, { "json": "https://www.anchorterminal.com/compare/bland-ai-vs-deepgram-voice-agent.json", "title": "Bland AI API + MCP vs Deepgram Voice Agent API", "url": "https://www.anchorterminal.com/compare/bland-ai-vs-deepgram-voice-agent" }, { "json": "https://www.anchorterminal.com/compare/bland-ai-vs-elevenlabs-agents.json", "title": "Bland AI API + MCP vs ElevenLabs Agents API + MCP", "url": "https://www.anchorterminal.com/compare/bland-ai-vs-elevenlabs-agents" }, { "json": "https://www.anchorterminal.com/compare/bland-ai-vs-gemini-live.json", "title": "Bland AI API + MCP vs Gemini Live API", "url": "https://www.anchorterminal.com/compare/bland-ai-vs-gemini-live" }, { "json": "https://www.anchorterminal.com/compare/bland-ai-vs-gpt-live.json", "title": "Bland AI API + MCP vs GPT-Live", "url": "https://www.anchorterminal.com/compare/bland-ai-vs-gpt-live" }, { "json": "https://www.anchorterminal.com/compare/bland-ai-vs-harmony-ai.json", "title": "Bland AI API + MCP vs Harmony.ai", "url": "https://www.anchorterminal.com/compare/bland-ai-vs-harmony-ai" }, { "json": "https://www.anchorterminal.com/compare/bland-ai-vs-hume-evi.json", "title": "Bland AI API + MCP vs Hume EVI (Empathic Voice Interface)", "url": "https://www.anchorterminal.com/compare/bland-ai-vs-hume-evi" }, { "json": "https://www.anchorterminal.com/compare/bland-ai-vs-inworld-realtime.json", "title": "Bland AI API + MCP vs Inworld Realtime API", "url": "https://www.anchorterminal.com/compare/bland-ai-vs-inworld-realtime" }, { "json": "https://www.anchorterminal.com/compare/bland-ai-vs-livekit-agents.json", "title": "Bland AI API + MCP vs LiveKit Agents", "url": "https://www.anchorterminal.com/compare/bland-ai-vs-livekit-agents" }, { "json": "https://www.anchorterminal.com/compare/bland-ai-vs-openai-realtime.json", "title": "Bland AI API + MCP vs OpenAI Realtime API", "url": "https://www.anchorterminal.com/compare/bland-ai-vs-openai-realtime" }, { "json": "https://www.anchorterminal.com/compare/bland-ai-vs-pipecat.json", "title": "Bland AI API + MCP vs Pipecat", "url": "https://www.anchorterminal.com/compare/bland-ai-vs-pipecat" }, { "json": "https://www.anchorterminal.com/compare/bland-ai-vs-placecall.json", "title": "Bland AI API + MCP vs PlaceCall", "url": "https://www.anchorterminal.com/compare/bland-ai-vs-placecall" }, { "json": "https://www.anchorterminal.com/compare/bland-ai-vs-retell-ai.json", "title": "Bland AI API + MCP vs Retell AI API + MCP", "url": "https://www.anchorterminal.com/compare/bland-ai-vs-retell-ai" }, { "json": "https://www.anchorterminal.com/compare/bland-ai-vs-rime-prism.json", "title": "Bland AI API + MCP vs Rime Prism", "url": "https://www.anchorterminal.com/compare/bland-ai-vs-rime-prism" }, { "json": "https://www.anchorterminal.com/compare/bland-ai-vs-synthflow.json", "title": "Bland AI API + MCP vs Synthflow API + MCP", "url": "https://www.anchorterminal.com/compare/bland-ai-vs-synthflow" }, { "json": "https://www.anchorterminal.com/compare/bland-ai-vs-ultravox.json", "title": "Bland AI API + MCP vs Ultravox Realtime API", "url": "https://www.anchorterminal.com/compare/bland-ai-vs-ultravox" }, { "json": "https://www.anchorterminal.com/compare/bland-ai-vs-vaani-voice.json", "title": "Bland AI API + MCP vs Vaani Developer Platform", "url": "https://www.anchorterminal.com/compare/bland-ai-vs-vaani-voice" }, { "json": "https://www.anchorterminal.com/compare/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/bland-ai-vs-vocily.json", "title": "Bland AI API + MCP vs Vocily AI", "url": "https://www.anchorterminal.com/compare/bland-ai-vs-vocily" }, { "json": "https://www.anchorterminal.com/compare/bland-ai-vs-vogent.json", "title": "Bland AI API + MCP vs Vogent API", "url": "https://www.anchorterminal.com/compare/bland-ai-vs-vogent" }, { "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/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/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/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-vapi.json", "title": "fone.me vs Vapi API + MCP", "url": "https://www.anchorterminal.com/compare/fone-me-vs-vapi" }, { "json": "https://www.anchorterminal.com/compare/fone-me-vs-vocily.json", "title": "fone.me vs Vocily AI", "url": "https://www.anchorterminal.com/compare/fone-me-vs-vocily" }, { "json": "https://www.anchorterminal.com/compare/fone-me-vs-vogent.json", "title": "fone.me vs Vogent API", "url": "https://www.anchorterminal.com/compare/fone-me-vs-vogent" }, { "json": "https://www.anchorterminal.com/compare/bland-ai-vs-cuelight.json", "title": "Bland AI API + MCP vs CueLight", "url": "https://www.anchorterminal.com/compare/bland-ai-vs-cuelight" }, { "json": "https://www.anchorterminal.com/compare/bland-ai-vs-pipecat-phonellm.json", "title": "Bland AI API + MCP vs Pipecat PhoneLLM", "url": "https://www.anchorterminal.com/compare/bland-ai-vs-pipecat-phonellm" } ], "panel": null, "scores": [ { "bland-ai": 65, "by": 50, "edge": "bland-ai", "fone-me": 15, "key": "reliability", "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "bland-ai": 68, "by": 37, "edge": "bland-ai", "fone-me": 31, "key": "schema", "name": "Schema \u0026 documentation", "weight": 13 }, { "bland-ai": 53, "by": 24, "edge": "bland-ai", "fone-me": 29, "key": "ergonomics", "name": "Agent ergonomics", "weight": 13 }, { "bland-ai": 79, "by": 49, "edge": "bland-ai", "fone-me": 30, "key": "security", "name": "Security \u0026 auth", "weight": 14 }, { "bland-ai": 65, "by": 15, "edge": "bland-ai", "fone-me": 50, "key": "payments", "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "bland-ai": 70, "by": 47, "edge": "bland-ai", "fone-me": 23, "key": "maintenance", "name": "Maintenance \u0026 community", "weight": 7 }, { "bland-ai": 72, "by": 49, "edge": "bland-ai", "fone-me": 23, "key": "transparency", "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "Bland AI API + MCP scores 67 (B) on agent readiness against fone.me's 28.3 (F), and leads in every scored category. Both do voice agents.", "tasks": null, "tutorials": [], "verdicts": { "bland-ai": "One per-minute rate covering STT, LLM, TTS and telephony, $0.14 on Start and $0.12 on Build, and restricted keys with per-resource scopes rolling out. No OpenAPI document, the MCP server lists over 340 tools without toolsets, and the product changelog's newest entry is from 3 August 2026.", "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." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/bland-ai-vs-fone-me", "json": "https://www.anchorterminal.com/compare/bland-ai-vs-fone-me.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/bland-ai-vs-fone-me.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/bland-ai-vs-fone-me.min.md" }, "markdown": "Bland AI API + MCP scores 67 (B) on agent readiness against fone.me's 28.3 (F), and leads in every scored category. Both do voice agents.\n\n- Bland AI API + MCP: grade B, 67/100, rank #342 of 1486. Markdown https://www.anchorterminal.com/tools/bland-ai.md · JSON https://www.anchorterminal.com/api/v1/tools/bland-ai.json\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- 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### Bland AI API + MCP (B)\n\nGood for: Teams that want one predictable per-minute bill for outbound and inbound phone agents, and personal agents that need their own US number.\n\nAhead on:\n- Reliability, 65 against 15\n- Schema \u0026 documentation, 68 against 31\n- Agent ergonomics, 53 against 29\n- Security \u0026 auth, 79 against 30\n- Payments \u0026 pricing, 65 against 50\n- Maintenance \u0026 community, 70 against 23\n- Transparency \u0026 trust, 72 against 23\n\nAlso in its favour:\n- Runs on your own machine\n- Free to start without a card\n\nWatch for: No OpenAPI document\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\nAlso in its favour:\n- No key needed to call it\n\nWatch for: No tool arguments, input schemas, annotations, error shapes or rate limits are published for the MCP server or A2A endpoints\n\n\n## Why the edge\n\n### Reliability: Bland AI API + MCP +50\n\n- Bland AI API + MCP (65): Atlassian Statuspage at status.bland.ai with US, Asia Pacific and Canada components and an incident history back to 20 October 2025, read on 2 November through its history feed (20). Six incidents in the 90 days from 4 August. Five were partial and read as minor, latency of 30 minutes on 27 August and 35 minutes on 14 September, delayed or missing audio on BTTS V3 voices for about two hours on 25 September (some calls, one voice family), variable extraction failing for some customers for about an hour on 5 October, and inbound calls in the US region failing for 8 minutes on 19 October with outbound unaffected. On 14 October, from about 3:00 to 4:10 PM PT, an upstream outage took down the language model every agent uses in conversation, live calls went silent or slow and outbound dispatch was paused, which we count as one major (10). Numeric limits are published, 10 concurrent, 100 an hour and 100 a day on Start, 50, 1,000 and 2,000 on Build, 120 MCP requests a minute and one call per number every 10 seconds (15). The call API documents 429 responses with messages, but we found no Retry-After, backoff or idempotency guidance (5 of 15). The pricing page claims a 99.9 per cent uptime SLA on every plan, while the terms of 28 August 2026 give no uptime commitment and no credits, so we give half (5). The API is generally available (10). 20 + 10 + 15 + 5 + 5 + 10 = 65.\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\n### Security \u0026 auth: Bland AI API + MCP +49\n\n- Bland AI API + MCP (79): Organisation API keys, several per organisation and each revocable on its own, and since the 1 October check restricted keys with per-resource scopes (`calls:read`, `calls:create`, `agents:write` and others) and OAuth client credentials with the same permissions for short-lived tokens (an organisation that doesn't see OAuth clients in its dashboard is told to contact support). Restricted keys are rolling out by organisation and aren't available on pinned deployments, credited as conditional availability elsewhere in this run (30). A key can now be limited to read scopes, sign-in connections to the MCP server take `mcp:read` or `mcp:write` scopes, and destructive tools carry an annotation for the client's approval prompt. The server no longer asks for confirmation itself, and personas, numbers and tools stay full-access only (15 of 20). Agents read caller speech and transcripts, which are untrusted, and we found guard rails mentioned in the CLI but no prompt-injection guidance (5 of 15). Audit logs exist but are an enterprise function and don't record API key use, and every call has a log; the key list shows who created each key (12 of 15). security.txt valid until 2027-04-05 (re-read on 2 November), a trust portal, SOC 2 Type II and a PCI DSS assessment by a QSA per the vendor, and a disclosure address. No bug bounty found (17 of 20). 30 + 15 + 5 + 12 + 17 = 79.\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\n### Transparency \u0026 trust: Bland AI API + MCP +49\n\n- Bland AI API + MCP (72): Closed source with clear terms (15). The privacy policy (last updated 23 June 2026) keeps data 'as long as necessary' with no periods for recordings or transcripts, and the trust page says zero-retention processing is available. The terms and the privacy policy both name Intelliga Corporation, doing business as Bland AI (12 of 30). The December 2025 price change was announced with a date and transition credits, and the migration from pathways and personas to agents carries a 15 November 2026 deadline in the docs, but we found no deprecation policy (8 of 20). A subprocessor list of 17 entries with locations, updated 8 September 2026, per the 1 October check, not re-read on 2 November (20). 15 + 12 + 8 + 20 = 55.\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\n### Maintenance \u0026 community: Bland AI API + MCP +47\n\n- Bland AI API + MCP (70): The newest entry in the product changelog is still 3 August 2026, 91 days before 2 November. Bland's official plugin for its hosted MCP server and Norm agent builder (CINTELLILABS/bland-plugins, MIT, linked from the docs) keeps a dated changelog, with bland 2.2.1 and norm 1.11.1 on 20 October 2026 (30). In the 90 days from 4 August, that changelog has 30 dated releases on 13 days from 8 September to 20 October, and the migration guide dates the agent architecture change to September 2026, while the product changelog's 6 July, 21 July and 3 August entries have left the window; the CLI's npm dates couldn't be read (20). Public changelog, no public issue tracker, and we didn't test support (8 of 15 for a closed service). Official tooling is the `bland-cli` npm package (Node 18 or later), a web SDK and a TTS Node library, with no server SDK in a second language (8 of 15). No public repository or CI for the CLI (4 of 10). 30 + 20 + 8 + 8 + 4 = 70.\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\n### Schema \u0026 documentation: Bland AI API + MCP +37\n\n- Bland AI API + MCP (68): No OpenAPI document found. The MCP server's dedicated tools take typed inputs and its API Reference tools take each reference page's parameters, but no machine-readable contract is published (5 of 25). llms.txt with 551 entries, each page served as Markdown (10). MCP tool descriptions say when to use a tool, for example the reference tells agents to use `send_call` and to choose one of `agent_id`, `persona_id`, `pathway_id` or `task` (14 of 20). The REST reference types every parameter with enums and defaults, though pathways travel as a raw graph and `call_bland_api` is a free-form passthrough (11 of 15). Errors for 400, 401, 402, 403, 404, 429 and 500 are documented with example messages (13 of 15). Versioned v1 and v2 APIs, agent versions and environments, and a dated changelog (15). 5 + 10 + 14 + 11 + 13 + 15 = 68.\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\n### Agent ergonomics: Bland AI API + MCP +24\n\n- Bland AI API + MCP (53): The hosted MCP server lists 62 dedicated tools and 282 API Reference tools, one per reference page, plus 3 prompts on key connections. Sign-in connections see a smaller allowlist, but there are no toolsets or dynamic loading (5 of 25). List endpoints such as audit logs and knowledge bases page and filter, but we found no field selection on call logs (14 of 20). Errors carry codes and readable messages, and a restricted key's 403 names the permission it lacks (16 of 20). Every MCP tool carries a read, write or destructive annotation, but there are no idempotency keys on call creation (10 of 20). A call needs only `phone_number` and a `task`, `agent_id`, `persona_id` or `pathway_id`, with defaults for voice and temperature. Official tooling is the Node CLI, a web SDK and a TTS Node library, and we found no Python SDK (8 of 15). 5 + 14 + 16 + 10 + 8 = 53.\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\n## Score by category\n\n| Category | Weight | Bland AI API + MCP | fone.me | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 65 | 15 | Bland AI API + MCP +50 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 68 | 31 | Bland AI API + MCP +37 |\n| Agent ergonomics | 13% (16.2 this run) | 53 | 29 | Bland AI API + MCP +24 |\n| Security \u0026 auth | 14% (17.5 this run) | 79 | 30 | Bland AI API + MCP +49 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 65 | 50 | Bland AI API + MCP +15 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 70 | 23 | Bland AI API + MCP +47 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 72 | 23 | Bland AI API + MCP +49 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **67 · B** | **28.3 · F** | |\n\n## Facts side by side\n\n| Fact | Bland AI API + MCP | fone.me |\n| --- | --- | --- |\n| Kind | HTTP API | Platform |\n| Vendor | Bland AI | Fone |\n| Hosted endpoint | `https://api.bland.ai/v1` | `https://www.fone.me/mcp` |\n| Transports | HTTP, Streamable HTTP, stdio | Streamable HTTP |\n| Auth | API key | None |\n| Pricing | Freemium | Freemium |\n| Price for voice agents | $29.99 per month (plan) | not published |\n| x402 | no | no |\n| Licence | none | 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 |\n| Tools exposed | 42 | 4 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| Last release | 2026-09-13 | 2026-10-05 |\n| Terms last updated | 2026-08-28 | couldn't be read |\n| Privacy policy last updated | 2026-06-23 | couldn't be read |\n| Customer content may train models | not found in the text | couldn't be read |\n| Terms restrict automated access | yes | couldn't be read |\n| Terms restrict benchmarking | not found in the text | couldn't be read |\n| Terms or service can change without notice | yes | couldn't be read |\n| Arbitration or class-action waiver | not found in the text | couldn't be read |\n| Popularity | 1.2k npm/wk | none |\n| Agent reviews | 3/5 (2) | none |\n\n## How the scores have moved\n\n### Bland AI API + MCP\n\n- +3.1 on 2 November 2026: product\n- +0.1 on 27 October 2026: new evidence\n- -0.3 on 8 October 2026: checklist\n\n### fone.me\n\nNo score change since it was listed.\n\n## Verdicts\n\n**Bland AI API + MCP.** One per-minute rate covering STT, LLM, TTS and telephony, $0.14 on Start and $0.12 on Build, and restricted keys with per-resource scopes rolling out. No OpenAPI document, the MCP server lists over 340 tools without toolsets, and the product changelog's newest entry is from 3 August 2026.\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## Before you call either\n\n### Bland AI API + MCP\n\n1. Call `wait_for_call` (it waits up to 45 seconds) instead of polling `get_call_log`\n2. Keep client tool-approval prompts on for destructive MCP tools; the server no longer asks for confirmation\n3. Space calls to the same number at least 10 seconds apart or expect a 429\n4. Budget $0.015 for every outbound attempt, including ones that never connect\n5. Use a restricted key with only the scopes you need for REST calls; the MCP server needs a full-access key or sign-in\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## Questions\n\n### Which is better for AI agents, Bland AI API + MCP or fone.me?\n\nBland AI API + MCP scores 67 (B) on agent readiness against fone.me's 28.3 (F), and leads in every scored category.\n\n### Can an agent call Bland AI API + MCP and fone.me without installing anything?\n\nYes. Bland AI API + MCP has a hosted endpoint at https://api.bland.ai/v1 and fone.me at https://www.fone.me/mcp.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/bland-ai-vs-fone-me.json, and with the fewest tokens: https://www.anchorterminal.com/compare/bland-ai-vs-fone-me.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"bland-ai\", \"b\": \"fone-me\"}`. From a terminal: `anchor compare bland-ai fone-me`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/bland-ai.json and https://www.anchorterminal.com/api/v1/tools/fone-me.json\n\n## Other comparisons with Bland AI API + MCP or fone.me\n\n- [Amazon Nova 2 Sonic vs Bland AI API + MCP](https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-bland-ai.md)\n- [Amazon Nova 2 Sonic vs fone.me](https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-fone-me.md)\n- [AssemblyAI Voice Agent API vs Bland AI API + MCP](https://www.anchorterminal.com/compare/assemblyai-voice-agent-vs-bland-ai.md)\n- [AssemblyAI Voice Agent API vs fone.me](https://www.anchorterminal.com/compare/assemblyai-voice-agent-vs-fone-me.md)\n- [Bland AI API + MCP vs Bolna API + MCP](https://www.anchorterminal.com/compare/bland-ai-vs-bolna.md)\n- [Bland AI API + MCP vs Deepgram Voice Agent API](https://www.anchorterminal.com/compare/bland-ai-vs-deepgram-voice-agent.md)\n- [Bland AI API + MCP vs ElevenLabs Agents API + MCP](https://www.anchorterminal.com/compare/bland-ai-vs-elevenlabs-agents.md)\n- [Bland AI API + MCP vs Gemini Live API](https://www.anchorterminal.com/compare/bland-ai-vs-gemini-live.md)\n- [Bland AI API + MCP vs GPT-Live](https://www.anchorterminal.com/compare/bland-ai-vs-gpt-live.md)\n- [Bland AI API + MCP vs Harmony.ai](https://www.anchorterminal.com/compare/bland-ai-vs-harmony-ai.md)\n- [Bland AI API + MCP vs Hume EVI (Empathic Voice Interface)](https://www.anchorterminal.com/compare/bland-ai-vs-hume-evi.md)\n- [Bland AI API + MCP vs Inworld Realtime API](https://www.anchorterminal.com/compare/bland-ai-vs-inworld-realtime.md)\n- [Bland AI API + MCP vs LiveKit Agents](https://www.anchorterminal.com/compare/bland-ai-vs-livekit-agents.md)\n- [Bland AI API + MCP vs OpenAI Realtime API](https://www.anchorterminal.com/compare/bland-ai-vs-openai-realtime.md)\n- [Bland AI API + MCP vs Pipecat](https://www.anchorterminal.com/compare/bland-ai-vs-pipecat.md)\n- [Bland AI API + MCP vs PlaceCall](https://www.anchorterminal.com/compare/bland-ai-vs-placecall.md)\n- [Bland AI API + MCP vs Retell AI API + MCP](https://www.anchorterminal.com/compare/bland-ai-vs-retell-ai.md)\n- [Bland AI API + MCP vs Rime Prism](https://www.anchorterminal.com/compare/bland-ai-vs-rime-prism.md)\n- [Bland AI API + MCP vs Synthflow API + MCP](https://www.anchorterminal.com/compare/bland-ai-vs-synthflow.md)\n- [Bland AI API + MCP vs Ultravox Realtime API](https://www.anchorterminal.com/compare/bland-ai-vs-ultravox.md)\n- [Bland AI API + MCP vs Vaani Developer Platform](https://www.anchorterminal.com/compare/bland-ai-vs-vaani-voice.md)\n- [Bland AI API + MCP vs Vapi API + MCP](https://www.anchorterminal.com/compare/bland-ai-vs-vapi.md)\n- [Bland AI API + MCP vs Vocily AI](https://www.anchorterminal.com/compare/bland-ai-vs-vocily.md)\n- [Bland AI API + MCP vs Vogent API](https://www.anchorterminal.com/compare/bland-ai-vs-vogent.md)\n- [Bolna API + MCP vs fone.me](https://www.anchorterminal.com/compare/bolna-vs-fone-me.md)\n- [Deepgram Voice Agent API vs fone.me](https://www.anchorterminal.com/compare/deepgram-voice-agent-vs-fone-me.md)\n- [ElevenLabs Agents API + MCP vs fone.me](https://www.anchorterminal.com/compare/elevenlabs-agents-vs-fone-me.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 Vapi API + MCP](https://www.anchorterminal.com/compare/fone-me-vs-vapi.md)\n- [fone.me vs Vocily AI](https://www.anchorterminal.com/compare/fone-me-vs-vocily.md)\n- [fone.me vs Vogent API](https://www.anchorterminal.com/compare/fone-me-vs-vogent.md)\n- [Bland AI API + MCP vs CueLight](https://www.anchorterminal.com/compare/bland-ai-vs-cuelight.md)\n- [Bland AI API + MCP vs Pipecat PhoneLLM](https://www.anchorterminal.com/compare/bland-ai-vs-pipecat-phonellm.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "attributionRequired": true, "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-11-07", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.7", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run", "terms": "https://www.anchorterminal.com/terms/#data" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Bland AI API + MCP vs fone.me", "url": "" } ], "description": "Bland AI scores 67 (B) to fone.me's 28.3 (F) for voice agents. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Bland AI API + MCP B 67", "fone.me F 28.3", "scores" ], "h1": "Bland AI API + MCP vs fone.me", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/bland-ai-vs-fone-me", "published": "2026-10-01", "section": "tools", "title": "Bland AI vs fone.me for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/bland-ai-vs-fone-me" }, "tokens": { "markdown": 6300, "slim": 3930 }, "version": 1 }