# fone.me vs Vocily AI

> Vocily AI scores 53.9 (D) to fone.me's 28.3 (F) for voice agents. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/fone-me-vs-vocily
- Markdown: https://www.anchorterminal.com/compare/fone-me-vs-vocily.md (~6,000 tokens)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-07

Vocily AI scores 53.9 (D) 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.

- 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
- Vocily AI: grade D, 53.9/100, rank #930 of 1486. Markdown https://www.anchorterminal.com/tools/vocily.md · JSON https://www.anchorterminal.com/api/v1/tools/vocily.json
- Best conversational voice-agent APIs: https://www.anchorterminal.com/best/voice-agents/index.md
- All 518 voice agents comparisons: https://www.anchorterminal.com/compare/voice-agents/index.md

## Which one, for what

### fone.me (F)

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 40

Also in its favour:
- No key needed to call it
- No incidents deducted, where Vocily AI loses 5 points for them

Watch for: No tool arguments, input schemas, annotations, error shapes or rate limits are published for the MCP server or A2A endpoints

### Vocily AI (D)

Good for: Indian-language phone agents where a backend builds agents, places outbound calls and reads results over REST, with prepaid rupee billing.

Ahead on:
- Reliability, 40 against 15
- Schema & documentation, 90 against 31
- Agent ergonomics, 84 against 29
- Security & auth, 46 against 30
- Maintenance & community, 61 against 23
- Transparency & trust, 48 against 23

Watch for: No status page, incident history or SLA was found


## Why the edge

### Schema & documentation: Vocily AI +59

- 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.
- Vocily AI (90): A public OpenAPI 3.1 file, linked from llms.txt, with 60 operations on 4 November (54 on 8 October) at docs.vocily.ai/developers/openapi.json (25). llms.txt, llms-full.txt and a Markdown copy of every page (10). Pages say what each route is for and what to use instead, such as webhooks over polling and dashboard batches over a loop of calls, though some operation titles are generated names such as Create Kb (16 of 20). Bodies refuse unknown fields and carry ranges and enums, but list filters such as `status` are plain strings and `variables` and `metadata` are free-form (12 of 15). 234 example entries in the spec, a reason-code table by status and a 422 that lists every invalid field (15). The `/v1` prefix and a dated API changes page from 23 September 2026, which records removals made under `/v1` (23 and 25 September, 10 and 30 October) against the reference's own rule that fields are never removed within a version (12 of 15). 25 + 10 + 16 + 12 + 15 + 12 = 90.

### Agent ergonomics: Vocily AI +55

- 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.
- Vocily AI (84): List calls take `limit` from 1 to 100, default 20, and return the transcript only with `include=transcript` (20 of 25). Every growing list uses the same cursor envelope, and calls filter by agent, status, direction, origin and date. The bounded lists return bare arrays (18 of 20). Errors carry a machine-readable `detail.code`, a field path on validation failures and an `X-Request-ID` (20). `Idempotency-Key` is required on call creation, agent edits accept `If-Match` on a document revision, and the bulk memory erase previews unless `dry_run` is false. Other writes have no idempotency key (18 of 20). A call needs only `agent_id` and `to_number` and an agent only `name`. No SDK was found in the docs, on npm or on PyPI (8 of 15). 20 + 18 + 20 + 18 + 8 = 84.

### Maintenance & community: Vocily AI +38

- 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.
- Vocily AI (61): The latest dated API change is 30 October 2026 (`send_whatsapp_template` moved to the dashboard), 5 days before this check (30). Nine dated entries since 6 August: 23, 25, 27 and 30 September and 10, 15, 17, 20 and 30 October (20). A public change log, a Discord server and a founder email address are the channels found, and we didn't test whether they answer (8 of 15 for a closed service). No official SDK found; the developer page now says to generate a typed client from the OpenAPI file (0 of 15). There is no package to assess. The OpenAPI file was last modified on 31 October 2026 (3 of 10, carried). 30 + 20 + 8 + 0 + 3 = 61.

### Reliability: Vocily AI +25

- 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.
- Vocily AI (40): Graded on the public REST API at api.vocily.ai, read as a hosted service. No status page found: status.vocily.ai gave no answer on 4 November and neither the site nor the docs link one (0). No readable incident history (5). The limit is published as 300 requests a minute per key (moving window), with ten concurrent calls per organisation included (15). A 429 carries `Retry-After` and `X-RateLimit` headers, and `POST /v1/calls`, the write that places a billed call, requires an `Idempotency-Key` and returns the original call on a retry (15). No SLA found. The terms say availability isn't guaranteed (0). The docs don't label the API beta, but nine dated changes from 23 September to 30 October 2026 changed the `/v1` contract, seven of them with removals, changed error codes or changed meanings, and the terms still allow for beta and pre-launch service; the 8 October reading of the API root's version is struck (a request to the product's own endpoint), and the partial is carried (5 of 10). 0 + 5 + 15 + 15 + 0 + 5 = 40.

### Transparency & trust: Vocily AI +25

- 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.
- Vocily AI (48): A closed service. The terms (10 June 2026) name no legal entity or governing law, still describe a possible beta, and say paid plans may come later while prices are live (10 of 30). The privacy policy (3 September 2026) is written mainly around WhatsApp data and gives no retention period. The compliance page says recordings are kept for the life of the account and deleted on request, and audio and transcript storage are per-agent settings. No DPA found (12 of 30). The reference promises additive changes within `/v1`, but removals shipped on 23 and 25 September and 10 and 30 October 2026 with same-day notes and migration tables and no notice period (6 of 20). The privacy policy mentions vetted providers without naming them. The compliance page now says call records, transcripts and recordings are stored on AWS in Mumbai (ap-south-1), that model providers process in their own regions and that Plivo carries calls; no sub-processor list was found, so the partial is carried (6 of 20). 10 + 12 + 6 + 6 = 34.

### Security & auth: Vocily AI +16

- 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.
- Vocily AI (46): Bearer keys are shown once, revocable in the dashboard and bound to one workspace, and they can't reach billing, members or key management. There are no scopes to set and no rotation route, and webhooks are HMAC-signed with a timestamp and a rotation overlap (22 of 30). No read-only key. Spending and contractual actions stay in the dashboard, a version answers calls only after publish and make-live, and the memory erase previews by default (10 of 20). Transcripts and caller speech are untrusted content, and the API docs have no prompt-injection guidance. The site describes topic fencing and an empty-knowledge-base guard (4 of 15). Each call keeps a record with cost and version, webhooks have a delivery log and every response a request id, but we found no audit log of account or key actions (8 of 15). No security.txt (404 on 4 November), disclosure policy, bug bounty or certification. The compliance page says Vocily doesn't claim certification, and the privacy policy states encryption in transit and at rest (2 of 20). 22 + 10 + 4 + 8 + 2 = 46.

## Score by category

| Category | Weight | fone.me | Vocily AI | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 15 | 40 | Vocily AI +25 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 31 | 90 | Vocily AI +59 |
| Agent ergonomics | 13% (16.2 this run) | 29 | 84 | Vocily AI +55 |
| Security & auth | 14% (17.5 this run) | 30 | 46 | Vocily AI +16 |
| Payments & pricing | 10% (12.5 this run) | 50 | 40 | fone.me +10 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 23 | 61 | Vocily AI +38 |
| Transparency & trust | 7% (8.8 this run) | 23 | 48 | Vocily AI +25 |
| Negative events | ≤15 | 0 | -5 | |
| **Total** | | **28.3 · F** | **53.9 · D** | |

## Facts side by side

| Fact | fone.me | Vocily AI |
| --- | --- | --- |
| Kind | Platform | HTTP API |
| Vendor | Fone | Vocily AI Private Limited |
| Hosted endpoint | `https://www.fone.me/mcp` | `https://api.vocily.ai` |
| Transports | Streamable HTTP | HTTP |
| Auth | None | API key |
| Pricing | Freemium | Pay per use |
| x402 | no | no |
| 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 Vocily's terms of service. No open-source code or published package was found |
| Tools exposed | 4 | none |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-10-05 | 2026-10-30 |
| Terms last updated | couldn't be read | 2026-06-10 |
| Privacy policy last updated | couldn't be read | 2026-09-03 |
| 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 |

## How the scores have moved

### fone.me

No score change since it was listed.

### Vocily AI

- +0.1 on 27 October 2026: checklist

## Verdicts

**fone.me.** Any agent can find a fone.me link and message its owner's agent through a keyless MCP server or A2A, with no sign-up or cost, and owners see every conversation in one inbox. Tool schemas, rate limits and abuse controls for that open channel are unpublished, the terms and privacy policy draw by script, and no company is named.

**Vocily AI.** The REST API is documented in detail, with an OpenAPI 3.1 file of 60 operations, a required idempotency key on calls, Retry-After on 429 and signed webhooks. No status page, SLA, SDK or security programme was found, and releases from September to 30 October 2026 removed fields under `/v1` on the day they were announced.

## Before you call either

### fone.me

1. 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.
2. 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.
3. 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.
4. Read a link's agent card at /{link}/.well-known/agent-card.json for its skills before using A2A message/send at /{link}/a2a.
5. Don't send personal or payment details through message_agent; no retention or privacy terms for agent-to-agent messages could be read.

### Vocily AI

1. Send a fresh UUID in `Idempotency-Key` on every `POST /v1/calls`. The API refuses the request without it
2. Pass a `from_number` the workspace holds. The shared Test Number returns 403 from the API
3. Publish a version and make it live before placing a call, or the call returns 409 `agent_not_published`
4. Branch on `detail.code`, falling back to the top-level `code`. A 429 body is flat, so read `Retry-After`
5. Read `currency` on every call and chat record. Costs are in rupees or dollars depending on the organisation

## Questions

### Which is better for AI agents, fone.me or Vocily AI?

Vocily AI scores 53.9 (D) on agent readiness against fone.me's 28.3 (F), and leads in 6 of 7 scored categories. fone.me leads on payments & pricing.

### Can an agent call fone.me and Vocily AI without installing anything?

Yes. fone.me has a hosted endpoint at https://www.fone.me/mcp and Vocily AI at https://api.vocily.ai.


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/fone-me-vs-vocily.json, and with the fewest tokens: https://www.anchorterminal.com/compare/fone-me-vs-vocily.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "fone-me", "b": "vocily"}`. From a terminal: `anchor compare fone-me vocily`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/fone-me.json and https://www.anchorterminal.com/api/v1/tools/vocily.json

## Other comparisons with fone.me or Vocily AI

- [Amazon Nova 2 Sonic vs fone.me](https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-fone-me.md)
- [Amazon Nova 2 Sonic vs Vocily AI](https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-vocily.md)
- [AssemblyAI Voice Agent API vs fone.me](https://www.anchorterminal.com/compare/assemblyai-voice-agent-vs-fone-me.md)
- [AssemblyAI Voice Agent API vs Vocily AI](https://www.anchorterminal.com/compare/assemblyai-voice-agent-vs-vocily.md)
- [Bland AI API + MCP vs fone.me](https://www.anchorterminal.com/compare/bland-ai-vs-fone-me.md)
- [Bland AI API + MCP vs Vocily AI](https://www.anchorterminal.com/compare/bland-ai-vs-vocily.md)
- [Bolna API + MCP vs fone.me](https://www.anchorterminal.com/compare/bolna-vs-fone-me.md)
- [Bolna API + MCP vs Vocily AI](https://www.anchorterminal.com/compare/bolna-vs-vocily.md)
- [Deepgram Voice Agent API vs fone.me](https://www.anchorterminal.com/compare/deepgram-voice-agent-vs-fone-me.md)
- [Deepgram Voice Agent API vs Vocily AI](https://www.anchorterminal.com/compare/deepgram-voice-agent-vs-vocily.md)
- [ElevenLabs Agents API + MCP vs fone.me](https://www.anchorterminal.com/compare/elevenlabs-agents-vs-fone-me.md)
- [ElevenLabs Agents API + MCP vs Vocily AI](https://www.anchorterminal.com/compare/elevenlabs-agents-vs-vocily.md)
- [fone.me vs Gemini Live API](https://www.anchorterminal.com/compare/fone-me-vs-gemini-live.md)
- [fone.me vs GPT-Live](https://www.anchorterminal.com/compare/fone-me-vs-gpt-live.md)
- [fone.me vs Harmony.ai](https://www.anchorterminal.com/compare/fone-me-vs-harmony-ai.md)
- [fone.me vs Hume EVI (Empathic Voice Interface)](https://www.anchorterminal.com/compare/fone-me-vs-hume-evi.md)
- [fone.me vs Inworld Realtime API](https://www.anchorterminal.com/compare/fone-me-vs-inworld-realtime.md)
- [fone.me vs LiveKit Agents](https://www.anchorterminal.com/compare/fone-me-vs-livekit-agents.md)
- [fone.me vs OpenAI Realtime API](https://www.anchorterminal.com/compare/fone-me-vs-openai-realtime.md)
- [fone.me vs Pipecat](https://www.anchorterminal.com/compare/fone-me-vs-pipecat.md)
- [fone.me vs PlaceCall](https://www.anchorterminal.com/compare/fone-me-vs-placecall.md)
- [fone.me vs Retell AI API + MCP](https://www.anchorterminal.com/compare/fone-me-vs-retell-ai.md)
- [fone.me vs Rime Prism](https://www.anchorterminal.com/compare/fone-me-vs-rime-prism.md)
- [fone.me vs Synthflow API + MCP](https://www.anchorterminal.com/compare/fone-me-vs-synthflow.md)
- [fone.me vs Ultravox Realtime API](https://www.anchorterminal.com/compare/fone-me-vs-ultravox.md)
- [fone.me vs Vaani Developer Platform](https://www.anchorterminal.com/compare/fone-me-vs-vaani-voice.md)
- [fone.me vs Vapi API + MCP](https://www.anchorterminal.com/compare/fone-me-vs-vapi.md)
- [fone.me vs Vogent API](https://www.anchorterminal.com/compare/fone-me-vs-vogent.md)
- [Gemini Live API vs Vocily AI](https://www.anchorterminal.com/compare/gemini-live-vs-vocily.md)
- [GPT-Live vs Vocily AI](https://www.anchorterminal.com/compare/gpt-live-vs-vocily.md)
- [Harmony.ai vs Vocily AI](https://www.anchorterminal.com/compare/harmony-ai-vs-vocily.md)
- [Hume EVI (Empathic Voice Interface) vs Vocily AI](https://www.anchorterminal.com/compare/hume-evi-vs-vocily.md)
- [Inworld Realtime API vs Vocily AI](https://www.anchorterminal.com/compare/inworld-realtime-vs-vocily.md)
- [LiveKit Agents vs Vocily AI](https://www.anchorterminal.com/compare/livekit-agents-vs-vocily.md)
- [OpenAI Realtime API vs Vocily AI](https://www.anchorterminal.com/compare/openai-realtime-vs-vocily.md)
- [Pipecat vs Vocily AI](https://www.anchorterminal.com/compare/pipecat-vs-vocily.md)
- [PlaceCall vs Vocily AI](https://www.anchorterminal.com/compare/placecall-vs-vocily.md)
- [Retell AI API + MCP vs Vocily AI](https://www.anchorterminal.com/compare/retell-ai-vs-vocily.md)
- [Rime Prism vs Vocily AI](https://www.anchorterminal.com/compare/rime-prism-vs-vocily.md)
- [Synthflow API + MCP vs Vocily AI](https://www.anchorterminal.com/compare/synthflow-vs-vocily.md)
- [Ultravox Realtime API vs Vocily AI](https://www.anchorterminal.com/compare/ultravox-vs-vocily.md)
- [Vaani Developer Platform vs Vocily AI](https://www.anchorterminal.com/compare/vaani-voice-vs-vocily.md)
- [Vapi API + MCP vs Vocily AI](https://www.anchorterminal.com/compare/vapi-vs-vocily.md)
- [Vocily AI vs Vogent API](https://www.anchorterminal.com/compare/vocily-vs-vogent.md)
- [CueLight vs Vocily AI](https://www.anchorterminal.com/compare/cuelight-vs-vocily.md)
- [Pipecat PhoneLLM vs Vocily AI](https://www.anchorterminal.com/compare/pipecat-phonellm-vs-vocily.md)

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp