# fone.me vs Pipecat (slim)

> Pipecat scores 65.2 (B) 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/fone-me-vs-pipecat.md (~6,400 tokens) · this version ~4,030 tokens · JSON https://www.anchorterminal.com/compare/fone-me-vs-pipecat.json · canonical https://www.anchorterminal.com/compare/fone-me-vs-pipecat
- 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)

Pipecat scores 65.2 (B) on agent readiness against fone.me's 28.3 (F), and leads in every scored category. Both do voice agents.

- fone.me: F 28.3, rank #1429 of 1510 · https://www.anchorterminal.com/tools/fone-me.min.md
- Pipecat: B 65.2, rank #428 of 1510 · https://www.anchorterminal.com/tools/pipecat.min.md
- 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. Also A hosted endpoint, with nothing to install; No incidents deducted, where Pipecat loses 9 points for them.
- Pipecat, good for Python teams that want to own a voice agent's pipeline, pick each speech and model provider, and host it themselves or on Pipecat Cloud. Ahead on Reliability, 68 against 15; Schema & documentation, 92 against 31; Agent ergonomics, 72 against 29; Security & auth, 67 against 30; Payments & pricing, 60 against 50; Maintenance & community, 85 against 23; Transparency & trust, 83 against 23. Also Free to start without a card; Open source.

| Category | fone.me | Pipecat |
| --- | --- | --- |
| Reliability (16%) | 15 | 68 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 31 | 92 |
| Agent ergonomics (13%) | 29 | 72 |
| Security & auth (14%) | 30 | 67 |
| Payments & pricing (10%) | 50 | 60 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 23 | 85 |
| Transparency & trust (7%) | 23 | 83 |

| Fact (where they differ) | fone.me | Pipecat |
| --- | --- | --- |
| Kind | Platform | Agent framework |
| Vendor | Fone | Daily |
| Hosted endpoint | `https://www.fone.me/mcp` | no (local only) |
| Transports | Streamable HTTP |  |
| Pricing | Freemium | Free |
| Price for voice agents | not published | $0.01 per minute of call |
| Licence | Proprietary hosted service. Terms of service at https://www.fone.me/terms, whose text draws by script and could not be read on 5 November 2026; no company is named on any page read. No source, SDK or package is published | BSD-2-Clause for the framework. Pipecat Cloud is a hosted service under Daily's terms of service |
| Tools exposed | 4 | none |
| Last release | 2026-10-05 | 2026-10-28 |
| Terms last updated | couldn't be read | 2025-03-31 |
| Privacy policy last updated | couldn't be read | 2025-01-06 |
| Customer content may train models | couldn't be read | not found in the text |
| Terms restrict automated access | couldn't be read | not found in the text |
| Terms restrict benchmarking | couldn't be read | not found in the text |
| Terms or service can change without notice | couldn't be read | not found in the text |
| Arbitration or class-action waiver | couldn't be read | not found in the text |
| Popularity | none | 16k stars, 98k npm/wk, 302k PyPI/wk |
| Agent reviews | none | 3/5 (4) |

Why the edge:
- Maintenance & community, Pipecat +62: 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.); Pipecat 85 (pipecat-ai 1.15.0, dated 28 October 2026 in the changelog and tagged that day, 4 days before the check (30). Nine releases in the 90 days to 1 November, 1.8.0 on 26 August to 1.15.0 (20). Issue and pull-request reply times couldn't be read, since GitHub's pages answer 403, and the 17 October figures came from a third-party copy of GitHub data, now struck. The clone shows 151 pull requests from outside forks merged in the 90 days to 1 November, fixes that cite the issues they close, and a needs-repro workflow that labels issues (13 of 25, was 15). The Python framework and the JavaScript client (`@pipecat-ai/client-js` 1.16.0, tagged 28 October) are current, with client SDKs in six languages (15). CI, coverage, a licence check, a uv lockfile and trusted publishing to PyPI are configured. Dependabot was added on 23 October, for the pinned GitHub Actions only, and a passing main wasn't confirmed (7 of 10). 30 + 20 + 13 + 15 + 7 = 85.)
- Schema & documentation, Pipecat +61: 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.); Pipecat 92 (Framework reading. Typed Python (py.typed) with an API reference page per service, transport, frame type and utility (25). llms.txt, Markdown copies of each page and llms-full.txt (4.7 MB on 1 November) (10). Guides say when to reach for Flows, multiple LLM agents or a single pipeline, and the error-handling page says which failures are worth retrying. The OpenTelemetry reference now gives `PipelineWorker` defaults of `enable_tracing` False and `enable_turn_tracking` True, matching the 1.15.0 source, so the mismatch the 17 October check found is gone (16 of 20, was 14). Pydantic `Settings` classes per service, a provider-neutral `FunctionSchema`, and an `ErrorCategory` enum (12 of 15). Example folders from function calling and MCP to telephony, and documented error categories and Pipecat Cloud error codes (14 of 15). Dated changelog with pull-request links, towncrier fragments and a migration guide to 1.0 (15). 25 + 10 + 16 + 12 + 14 + 15 = 92.)
- Transparency & trust, Pipecat +60: 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.); Pipecat 83 (BSD-2-Clause (30). The framework keeps no data. Daily's privacy policy (6 January 2025) keeps personal data while an account is open, the Pipecat Cloud security guide says session data is removed when a session ends, logs are stored by default and administrative API calls are kept a year, and Daily publishes a DPA (1 May 2025) and a sub-processor list (1 September 2026), per the 17 October check. Control-plane data is in the US whatever the agent's region (24 of 30). The changelog has Deprecated sections in most releases, and recent entries name removal in 2.0.0, with a migration guide to 1.0, but no dated removal windows (13 of 20). No telemetry found, and tracing is opt-in, which the OpenTelemetry reference now states too. The optional ai-coustics filter still registers a Pipecat identifier with that vendor's SDK in 1.15.0, which the docs don't mention (18 of 20, was 16). 30 + 24 + 13 + 18 = 85.)
- Reliability, Pipecat +53: 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.); Pipecat 68 (Local-software reading of the framework. pipecat-ai installs from PyPI with Python 3.11 or later declared (1.15.0's pyproject), and a compatibility workflow builds it on 3.11 to 3.14 (20). A public tests workflow runs pytest (406 Python files under tests/ in 1.15.0), on pushes to main and on pull requests, with coverage and licence-check jobs, but GitHub's Actions pages weren't readable on 17 October or 1 November, so a green main is not confirmed (15 of 25). The issue tracker couldn't be read, since GitHub's pages answer 403. The 17 October reading of open issues came from a third-party copy of GitHub data, which we no longer use, so it is struck. The clone shows 3,539 commits in the 90 days to 1 November, fixes that cite the issues they close (#6162 on 15 October, #6256 on 20 October, #6410 from an outside contributor on 28 October) and 151 merged pull requests from outside forks, so 8 of 25 on that evidence alone (was 12). Keep a Changelog with dates, semver stated and breaking changes flagged with a warning sign, but minor releases keep carrying them, 16 flagged in 1.8.0, 4 in 1.9.0, 4 in 1.10.0, 6 in 1.13.0, 1 in 1.14.0 and 5 in 1.15.0 (10 of 15). 1.15.0, classed Production/Stable (15). 20 + 15 + 8 + 10 + 15 = 68.)
- Agent ergonomics, Pipecat +43: 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.); Pipecat 72 (Framework reading. `MCPClient` registers an MCP server's tools with the LLM, with `tools_filter` to allow only named tools and `tools_arguments` to fix values and hide them from the schema. The repository's streamable HTTP MCP example is about 130 lines of code, most of it the voice pipeline rather than the tool wiring (20 of 25). `tools_output_filters` trims tool results, and context summarisation and Flows context strategies limit what the model sees (15 of 20). Errors carry a category that marks permanent failures, services expose `is_usable`, `ProcessorUnusablePolicy` decides whether a bot ends, and MCP failures return to the model as text (17 of 20). Function calls cancel on interruption by default, with per-tool timeouts and opt-in asynchronous or model-cancellable calls, but there is no idempotency guidance for tools with side effects (10 of 20). A bot needs a transport, speech-to-text, LLM, text-to-speech, VAD and context aggregators wired by hand, which `pipecat init` scaffolds. Server code is Python only, with client SDKs in six languages (10 of 15).)
- Security & auth, Pipecat +37: 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.); Pipecat 67 (Framework reading, as for the frameworks category. We found no telemetry in the source, and tracing is off by default and needs an exporter the developer supplies. The two credential flaws the 17 October check found on 1.12.0 are fixed in released versions. 1.13.0 (18 October) makes the services for OpenAI-compatible providers raise an error when given no key instead of falling back to `OPENAI_API_KEY`, and masks API keys, tokens and signed URLs in error messages, and 1.14.0 (23 October) closes a gap in that masking (30 of 30, was 20). No tool-approval or confirmation primitive. `tools_filter` allowlists MCP tools and `tools_arguments` pins values the model cannot change (8 of 20). A caller's speech and MCP tool results go to the model, and we found no prompt-injection guidance in the docs, re-searched in llms-full.txt on 1 November (3 of 15). OpenTelemetry spans per service and tool call, with `FunctionCallObserver` and `LLMLogObserver` for per-call visibility (15). SECURITY.md routes reports to an email address at Daily, and GitHub advisories are published with CVEs and fixed versions, four since April 2026 (OSV, re-read on 1 November, lists no new one). The `OPENAI_API_KEY` fix shipped without an advisory. No security.txt or bug bounty. Daily states SOC 2 Type 2, which isn't scored for a framework (11 of 20). 30 + 8 + 3 + 15 + 11 = 67.)