# ElevenLabs Agents API + MCP vs fone.me (slim)

> ElevenLabs Agents scores 72.6 (BB) to fone.me's 28.3 (F) for voice agents. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/elevenlabs-agents-vs-fone-me.md (~6,350 tokens) · this version ~3,830 tokens · JSON https://www.anchorterminal.com/compare/elevenlabs-agents-vs-fone-me.json · canonical https://www.anchorterminal.com/compare/elevenlabs-agents-vs-fone-me
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

ElevenLabs Agents API + MCP scores 72.6 (BB) on agent readiness against fone.me's 28.3 (F), and leads in 6 of 7 scored categories. fone.me leads on payments & pricing. Both do voice agents.

- ElevenLabs Agents API + MCP: BB 72.6, rank #121 of 1486 · https://www.anchorterminal.com/tools/elevenlabs-agents.min.md
- fone.me: F 28.3, rank #1406 of 1486 · https://www.anchorterminal.com/tools/fone-me.min.md
- ElevenLabs Agents API + MCP, good for Teams that want a managed pipeline with ElevenLabs voices, a choice of LLM, wide telephony integration and web and mobile SDKs. Ahead on Reliability, 75 against 15; Schema & documentation, 92 against 31; Agent ergonomics, 77 against 29; Security & auth, 83 against 30; Maintenance & community, 85 against 23; Transparency & trust, 78 against 23. Also Agent-ready, a grade of BB or better.
- fone.me, good 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. Ahead on Payments & pricing, 50 against 35. Also No key needed to call it; No incidents deducted, where ElevenLabs Agents API + MCP loses 3 points for them.

| Category | ElevenLabs Agents API + MCP | fone.me |
| --- | --- | --- |
| Reliability (16%) | 75 | 15 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 92 | 31 |
| Agent ergonomics (13%) | 77 | 29 |
| Security & auth (14%) | 83 | 30 |
| Payments & pricing (10%) | 35 | 50 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 85 | 23 |
| Transparency & trust (7%) | 78 | 23 |

| Fact (where they differ) | ElevenLabs Agents API + MCP | fone.me |
| --- | --- | --- |
| Kind | HTTP API | Platform |
| Vendor | ElevenLabs | Fone |
| Hosted endpoint | `https://api.elevenlabs.io/v1/convai` | `https://www.fone.me/mcp` |
| Transports | HTTP, Streamable HTTP | Streamable HTTP |
| Auth | OAuth or key | None |
| Price for voice agents | $0.08 per minute of call | not published |
| Licence | MIT (SDKs) | 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 |
| Tools exposed | none | 4 |
| MCP registry | `io.elevenlabs/mcp` | not listed |
| Last release | 2026-10-29 | 2026-10-05 |
| Terms last updated | 2026-03-31 | couldn't be read |
| Privacy policy last updated | 2026-05-20 | couldn't be read |
| Customer content may train models | yes, with an opt-out | couldn't be read |
| Terms restrict automated access | not found in the text | couldn't be read |
| Terms restrict benchmarking | not found in the text | couldn't be read |
| Terms or service can change without notice | yes | couldn't be read |
| Arbitration or class-action waiver | yes | couldn't be read |
| Popularity | 114 stars, 1.2M npm/wk, 2.2M PyPI/wk | none |
| Agent reviews | 3.5/5 (2) | none |

Why the edge:
- Maintenance & community, ElevenLabs Agents API + MCP +62: ElevenLabs Agents API + MCP 85 (Changelog entry on 26 October 2026, and @elevenlabs/client 1.32.1 and @elevenlabs/react 1.20.2 tagged on 29 October (30). Weekly entries, with 108 tags in the agents packages repository since 3 August (20). Weekly changelog and incident write-ups on the status page, support we didn't test (12 of 15 for a closed service). Python and JavaScript SDKs with over a million weekly downloads each per the 1 October check, plus mobile SDKs (15). MIT SDKs on GitHub (8 of 10). 30 + 20 + 12 + 15 + 8 = 85.); 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.)
- Schema & documentation, ElevenLabs Agents API + MCP +61: ElevenLabs Agents API + MCP 92 (Public OpenAPI at api.elevenlabs.io/openapi.json (25). llms.txt with Markdown copies of each page (10). The docs explain each agent setting with guidance on when to use it, such as turn timeout and soft-timeout fillers (16 of 20). The OpenAPI types every field, but `conversation_config` is a large nested object (12 of 15). The errors page lists codes, types and fixes, and every error carries a `request_id` (14 of 15). Weekly dated changelog entries and a versioned API (15).); 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.)
- Reliability, ElevenLabs Agents API + MCP +60: ElevenLabs Agents API + MCP 75 (Read as a hosted service. Status page at status.elevenlabs.io (incident.io) with an ElevenAgents component group (Conversations, Telephony, Integrations, Other Agents APIs, Quality, RAG, UI) and dated component history (20). Re-read on 1 November from the history page, which dates each component's impact, as the ElevenLabs text-to-speech and voice cloning listings were read; the incidents feed was re-posted on 21 October and leaves older incidents out. In the 90 days from 3 August, ten incidents touched Agents components, all partial or under an hour. The longest, from 08:50 UTC on 13 October, a database behind the Agents platform in the US stalled, and the write-up says roughly 45 per cent of US calls failed and 7 per cent of API requests returned errors until 14:18 UTC, on seven Agents components marked partial outage. That is a share of requests in one region, read as partial, as hubspot-mcp's "many customers in North America" was and as the ElevenLabs text-to-speech and voice cloning listings read this incident, not every user in a region as in google-drive-api's regional major. The others are Inbound Twilio calls on 18 August (under 1 per cent), EU batch calling delays on 27 August, EU conversation history on 10 September, some calls failing to start on 18 and 19 September (1 hour 25 minutes), the EU platform unresponsive from 13:40 to 14:18 UTC on 28 September (38 minutes, one region), a usage datastore fault from 15:56 to 19:36 UTC on 29 September that caused latency and some failed requests on Agents conversations, STT and Creative products (partial outage), EU SIP calls with static IPs from 9:53 to 12:06 UTC on 6 October (one region, one call path) and SIP conversations from 14:21 to 15:15 UTC on 8 October. Minor only (20 of 30, was 5). Concurrency per plan is published, from 4 calls on Free to 40 on Business with burst to three times the cap (15). The errors page returns 429 with `rate_limit_exceeded`, `concurrent_limit_exceeded` or `system_busy` and tells callers to back off exponentially. No Retry-After header and no idempotency keys found (10 of 15). No SLA found for a self-serve tier, and Enterprise lists custom terms around SLAs (0). Agents is generally available (10). 20 + 20 + 15 + 10 + 0 + 10 = 75.); 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.)
- Transparency & trust, ElevenLabs Agents API + MCP +55: ElevenLabs Agents API + MCP 78 (Closed service with clear terms and MIT SDKs (18 of 30). Conversation data is kept 2 years by default, set per agent in days, with per-agent zero retention mode and audio saving that can be turned off, and the statements agree (22 of 30). Dated changelog entries, but we didn't find a deprecation policy for the agents product (10 of 20). EU, India and Singapore residency endpoints are documented. We didn't check the subprocessor list this run (15 of 20).); 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.)
- Security & auth, ElevenLabs Agents API + MCP +53: ElevenLabs Agents API + MCP 83 (The hosted MCP server signs in with OAuth and asks for scoped access to agents and speech. API keys can be limited to endpoint groups, given a credit limit, owned by a service account, rotated, and are disabled if found on GitHub (30). Scoped keys and signed URLs for private agents keep the main key off clients (17 of 20). Agents pass caller speech to an LLM. The guardrails docs, generally available since 19 October 2026, describe a Manipulation guardrail that detects prompt injection in user turns and can end the conversation, included at no extra cost, and the MCP security page recommends Always Ask approval for tool calls. It is a setting the builder turns on, not a default we could confirm (12 of 15, was 5). Audit logs cover over 100 endpoints through `GET /v1/workspace/audit-logs`, but only on Enterprise, and every conversation keeps a transcript (12 of 15). security.txt valid to 6 October 2027 (re-read on 1 November) and HIPAA BAAs are available with zero retention mode. We didn't re-check certifications or a bug bounty (12 of 20). 30 + 17 + 12 + 12 + 12 = 83.); 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.)
- Agent ergonomics, ElevenLabs Agents API + MCP +48: ElevenLabs Agents API + MCP 77 (We couldn't count the hosted MCP server's tools, since the docs list about ten capabilities without a tool list, so we scored context cost on the API, where list endpoints take page sizes and cursors (18 of 25). Conversation lists page and filter (18 of 20). Typed error codes with suggested fixes (18 of 20). MCP clients can set each tool to ask first and the docs warn that deleting an agent is destructive, but we found no idempotency keys (8 of 20). Few required fields to create an agent and official SDKs for Python, JavaScript, React, Swift, Kotlin and Flutter (15).); 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.)