# fone.me vs PlaceCall (slim)

> PlaceCall scores 54 (C) 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-placecall.md (~6,150 tokens) · this version ~3,730 tokens · JSON https://www.anchorterminal.com/compare/fone-me-vs-placecall.json · canonical https://www.anchorterminal.com/compare/fone-me-vs-placecall
- 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)

PlaceCall scores 54 (C) on agent readiness against fone.me's 28.3 (F), and leads in 6 of 7 scored categories. Both do voice agents.

- fone.me: F 28.3, rank #1429 of 1510 · https://www.anchorterminal.com/tools/fone-me.min.md
- PlaceCall: C 54, rank #924 of 1510 · https://www.anchorterminal.com/tools/placecall.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 No key needed to call it; No incidents deducted, where PlaceCall loses 5 points for them.
- PlaceCall, good for An agent that needs a phone call to a US business done for it, such as checking stock, hours or a quote, or booking and cancelling, with an outcome and transcript at the end. Ahead on Reliability, 45 against 15; Schema & documentation, 57 against 31; Agent ergonomics, 81 against 29; Security & auth, 60 against 30; Maintenance & community, 74 against 23; Transparency & trust, 50 against 23. Also Free to start without a card.

| Category | fone.me | PlaceCall |
| --- | --- | --- |
| Reliability (16%) | 15 | 45 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 31 | 57 |
| Agent ergonomics (13%) | 29 | 81 |
| Security & auth (14%) | 30 | 60 |
| Payments & pricing (10%) | 50 | 50 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 23 | 74 |
| Transparency & trust (7%) | 23 | 50 |

| Fact (where they differ) | fone.me | PlaceCall |
| --- | --- | --- |
| Kind | Platform | HTTP API |
| Vendor | Fone | VOYGR Tech, Inc. |
| Hosted endpoint | `https://www.fone.me/mcp` | `https://api.voygr.tech/mcp` |
| Transports | Streamable HTTP | HTTP, Streamable HTTP |
| Auth | None | OAuth or key |
| Pricing | Freemium | Pay per use |
| Licence | Proprietary hosted service. Terms of service at https://www.fone.me/terms, whose text draws by script and could not be read on 5 November 2026; no company is named on any page read. No source, SDK or package is published | Proprietary service under VOYGR's API Terms of Service. The skill, plugin manifests and AGENTS.md in voygr-tech/placecall are MIT |
| MCP registry | not listed | `io.github.voygr-tech/placecall` |
| Last release | 2026-10-05 | 2026-10-28 |
| Agent reviews | none | 3.5/5 (4) |

Why the edge:
- Agent ergonomics, PlaceCall +52: 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.); PlaceCall 81 (Four MCP tools per the README and the skill (`suggest_places`, `place_call`, `get_call_result`, `answer_question`), so context cost is small (25). GET /calls takes `limit`, lists most recent first without transcripts, and the event feed resumes from an `after_event_id` cursor, but no filters on the call list were found (12 of 20). Errors carry an `error_code` and a `hint`, a 422 for missing slots lists each one with a `suggested_question`, and a 402 names `needed_credits` (20). Idempotency keys on POST /calls with 409 `idempotency_conflict`, `idempotency_in_progress` and `idempotency_state_unknown` answers, and a retry procedure that lists calls before re-dialling. MCP tool annotations were not readable (16 of 20). A call needs only `target_phone` and `brief`, with `language` defaulting to `auto`. No SDK packages in any language, only plugins, a skill and the API (8 of 15). 25 + 12 + 20 + 16 + 8 = 81.)
- Maintenance & community, PlaceCall +51: 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.); PlaceCall 74 (Plugin version 6.5.1 went into all five manifests on 28 October 2026 with a fix to the skill's polling, and the API terms were updated on 23 October (30). In the 90 days from 6 August the repository shipped nine plugin versions, 6.0.0 (26 August) to 6.5.1 (28 October), one of them tagged (v6.0.2, 2 October). Each version changes the skill's content, so none is packaging only and each counts in full, as fullstory's and Bland's plugin versions do (20). The API is closed. There is a support address and a founders' address but no public changelog, and the GitHub issue tracker could not be read from this session (6 of 15, the closed-service reading). Listed in the official MCP registry under the verified io.github.voygr-tech namespace since 2 October 2026 (15). The repository holds no CI and no code to build. Its five manifests agree on version 6.5.1 (3 of 10). 30 + 20 + 6 + 15 + 3 = 74.)
- Reliability, PlaceCall +30: 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.); PlaceCall 45 (Read with the hosted lines. No status page was found on voygr.tech or in the repository, and status.voygr.tech still does not resolve (0). With no published history the incident line takes 5. The skill in the repository publishes rate limits of 10 requests a second and 120 a minute on free and paid keys, plus a daily call ceiling (15). It says to honour Retry-After on 429 and `resume_at` on a 503 for maintenance, and every POST /calls carries an Idempotency-Key whose replay returns the stored response with `Idempotent-Replayed: true` (15). No SLA for any tier (0). Nothing in the skill, README or product page calls the API beta or preview (10). api.voygr.tech's robots.txt now disallows ClaudeBot and names neither Claude-User nor Claude-SearchBot, so the 17 October readings of its OpenAPI spec, llms.txt, llms-full.txt, docs, checkout pages, /v1/pricing and protected-resource metadata are struck, and these lines now rest on the skill repository. 0 + 5 + 15 + 15 + 0 + 10 = 45.)
- Security & auth, PlaceCall +30: 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.); PlaceCall 60 (Two credential models. The REST API takes one `X-API-Key` per account with no scopes. Since 24 October (6.5.0) a key can be issued by email code through POST /signup and /signup/verify, and a new key replaces the old one (`replaced_previous_key`), with /recover emailing a fresh key. The plugins sign in to the MCP server with OAuth. The two scopes read on 17 October came from api.voygr.tech metadata, now struck. We read the mix as plain revocable keys (20 of 30). No read-only key. The skill tells the agent to confirm the number and the brief with the user before dialling, and an owner can set a concurrent-call limit (10 of 20). The tool returns what people say on calls, and the skill says to treat transcripts, summaries and extracted fields as data, never as instructions (14 of 15). Each call can be listed and read back with its transcript, the notice it spoke and its charge, and /v1/usage shows the balance. No account audit log was found (11 of 15). SECURITY.md asks for reports to support@voygr.tech. No security.txt on voygr.tech (404), bug bounty or certification was found (5 of 20). 20 + 10 + 14 + 11 + 5 = 60.)
- Transparency & trust, PlaceCall +27: 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.); PlaceCall 50 (Closed service with dated API terms (last updated 23 October 2026), and the skill and manifests are MIT (15). The API terms and the privacy policy (6 October 2026) agree on 90 days' retention for recordings and transcripts. A DPA is available only by negotiation, the privacy policy names VOYGR an independent controller of call recipients' data for its own purposes, and it allows de-identified data to be used and shared (20 of 30). The terms reserve the right to change or remove endpoints with or without notice and promise no backward compatibility. The skill marks `outcome_type` deprecated with no date, and the merged-transcript endpoints were removed with no dated notice (3 of 20). No subprocessor list or data locations. The privacy policy names only categories of service providers (5 of 20). 15 + 20 + 3 + 5 = 43.)
- Schema & documentation, PlaceCall +26: 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.); PlaceCall 57 (No machine-readable contract can be read today. api.voygr.tech's robots.txt now disallows ClaudeBot and names neither Claude-User nor Claude-SearchBot, so the 17 October readings of its OpenAPI spec, llms.txt, llms-full.txt, docs, checkout pages, /v1/pricing and protected-resource metadata are struck, and no copy of the spec sits on voygr.tech or in the repository, so the contract line is unread and not credited (0). The repository's SKILL.md, AGENTS.md and llms-install.md are Markdown references written for agents (10). The skill says when to use each route and when not to, such as never re-dialling a `place_call` that timed out and polling instead of waiting for `transcript_ready` (16 of 20). It lists the 13 accepted languages, the four intents with their required slots and the length limits on the notice fields, but `slots` stays a free-form object (11 of 15). curl examples for each route and a table of error codes with their meaning (15). Plugin versions in five manifests and dated API terms, but no API changelog (5 of 15). 0 + 10 + 16 + 11 + 15 + 5 = 57.)