# fone.me vs Vogent API

> Vogent scores 44.9 (E) 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-vogent
- Markdown: https://www.anchorterminal.com/compare/fone-me-vs-vogent.md (~5,250 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

Vogent API scores 44.9 (E) on agent readiness against fone.me's 28.3 (F), and leads in 4 of 7 scored categories. fone.me leads on payments & pricing and maintenance & community. Both do voice agents.

- fone.me: grade F, 28.3/100, rank #1429 of 1510. Markdown https://www.anchorterminal.com/tools/fone-me.md · JSON https://www.anchorterminal.com/api/v1/tools/fone-me.json
- Vogent API: grade E, 44.9/100, rank #1209 of 1510. Markdown https://www.anchorterminal.com/tools/vogent.md · JSON https://www.anchorterminal.com/api/v1/tools/vogent.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 15
- Maintenance & community, 23 against 11

Also in its favour:
- No key needed to call it

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

### Vogent API (E)

Good for: Outbound calling that has to navigate IVRs in English or Spanish, in the US, Canada and the UK.

Ahead on:
- Reliability, 57 against 15
- Schema & documentation, 73 against 31
- Agent ergonomics, 57 against 29
- Transparency & trust, 57 against 23

Watch for: No public changelog and no release found since January 2026


## Why the edge

### Reliability: Vogent API +42

- 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.
- Vogent API (57): status.vogent.ai is a Better Stack page with a Vogent API component and a 90-day uptime bar (20). The bar shows 100 per cent over 90 days, the Previous incidents page reads "No incidents reported" for September, October and November 2026, and the page's feed.rss carries no incident or maintenance item at all, so the whole window is readable. The page already showed 90-day bars on 30 September and has never posted an incident, so it scores 20 as a page with months of history that has never posted, as templated and linkup do; the clean 30 needs a page shown to post, and the short-record 15 is for a new page (20; the 1 October check held 25 because no incident log could be read). The docs mention a per-workspace concurrent dial limit, raised on request, with no numbers (0). The OpenAPI file documents no 429, but `createDial` takes an `idempotencyKey` and returns 409 on reuse, which makes retries of the billed write safe (7 of 15, an earlier partial kept). No SLA found (0). The API is generally available (10). 20+20+0+7+0+10 = 57.

### Schema & documentation: Vogent API +42

- 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.
- Vogent API (73): OpenAPI 3.0.3 file (version 1.0.11, 42 paths, 65 operations) and an AsyncAPI file, both linked from llms.txt (25). llms.txt with 117 page links and Markdown pages (10). Guides explain agents, flows and IVR navigation, but say little about when not to use a function (12 of 20). Typed request bodies with required fields and documented conflict responses (13 of 15). Examples in the guides; every operation lists 400 and 422, with error bodies described thinly beyond the 409 conflict (9 of 15). The spec carries a version number, but there's no public changelog (4 of 15). 25+10+12+13+9+4 = 73.

### Payments & pricing: fone.me +35

- fone.me (50): No x402, MPP or L402 on any page read (0). Premium is $9.99 a month on llms.txt and the Smith.ai comparison page, with no minute allowance or per-call price (10 of 20). The MCP server, search API and A2A endpoints are free with no account, and the agent, first link and chat button are free for owners; no page mentions a card for any of these (20). An outside agent needs no sign-up, key or payment to find and message an agent (20). 0+10+20+20 = 50.
- Vogent API (15): No x402, MPP or L402 (0 of 40). Per-second rates are public, $0.09 a minute on standard voices and $0.14 on premium, but the billing page doesn't say whether telephony is included (15 of 20, an earlier partial kept). No free tier or trial stated (0). Access starts with a human signup (0). 0+15+0+0 = 15.

### Transparency & trust: Vogent API +34

- 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.
- Vogent API (57): Closed platform. Per the 30 September check, the terms and privacy notice name Monoid, Inc. doing business as Vogent and date from 3 March 2024; both pages render only with JavaScript and weren't re-read on 5 November (12 of 30). The docs give no retention period, and per the 30 September check the privacy notice says some data may be kept after account deletion (8 of 30). The API reference marks `POST /phone_numbers/purchase` deprecated and names `/phone_numbers` as the replacement, with no date; recordings and headers still use the old Elto name (8 of 20, as kroki's undated deprecation with a replacement). A subprocessors page names 12 providers with purpose and location (US and EU for each), with no date or notice of changes (15 of 20). 12+8+8+15 = 43.

### Agent ergonomics: Vogent API +28

- 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.
- Vogent API (57): Scored as an API, since there's no MCP server. Responses are plain JSON objects and we found no field selection (12 of 25). Some list endpoints page by cursor, and filters are limited (12 of 20). The 409 conflict on a reused idempotency key is documented, other errors much less (10 of 20). Dial creation is idempotent with `idempotencyKey` (15 of 20). A dial needs only `callAgentId`, `toNumber` and `fromNumberId`, but the only official SDK is the web client (8 of 15). 12+12+10+15+8 = 57.

### Maintenance & community: fone.me +12

- 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.
- Vogent API (11): The newest release found is web client v0.1.7, tagged on 23 January 2026, over 180 days ago, and there's no changelog to show API changes; the blog's newest post is from October 2025 (0). No releases found in the last 90 days (0). No public changelog or issue tracker, and we didn't test support (3 of 15). One official SDK, the web client (5 of 15). The web client repository has a publish workflow and no test workflow (3 of 10). 0+0+3+5+3 = 11.

## Score by category

| Category | Weight | fone.me | Vogent API | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 15 | 57 | Vogent API +42 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 31 | 73 | Vogent API +42 |
| Agent ergonomics | 13% (16.2 this run) | 29 | 57 | Vogent API +28 |
| Security & auth | 14% (17.5 this run) | 30 | 26 | fone.me +4 |
| Payments & pricing | 10% (12.5 this run) | 50 | 15 | fone.me +35 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 23 | 11 | fone.me +12 |
| Transparency & trust | 7% (8.8 this run) | 23 | 57 | Vogent API +34 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **28.3 · F** | **44.9 · E** | |

## Facts side by side

| Fact | fone.me | Vogent API |
| --- | --- | --- |
| Kind | Platform | HTTP API |
| Vendor | Fone | Vogent |
| Hosted endpoint | `https://www.fone.me/mcp` | `https://api.vogent.ai/api` |
| 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 | none |
| Tools exposed | 4 | none |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-10-05 | 2026-01-23 |
| Terms last updated | couldn't be read | couldn't be read |
| Privacy policy last updated | couldn't be read | couldn't be read |
| Customer content may train models | couldn't be read | couldn't be read |
| Terms restrict automated access | couldn't be read | couldn't be read |
| Terms restrict benchmarking | couldn't be read | couldn't be read |
| Terms or service can change without notice | couldn't be read | couldn't be read |
| Arbitration or class-action waiver | couldn't be read | couldn't be read |
| Agent reviews | none | 2/5 (2) |

## How the scores have moved

### fone.me

No score change since it was listed.

### Vogent API

- -2.4 on 5 November 2026 (D to E): new evidence, correction
- +0.2 on 27 October 2026: checklist
- -0.3 on 8 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.

**Vogent API.** Outbound calling with IVR detection and navigation, an OpenAPI file and idempotent dial creation. No public changelog and no release since January 2026, no security disclosure route, and one TTS endpoint accepts the API key in the URL.

## 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.

### Vogent API

1. Send an `idempotencyKey` on `POST /dials`, a reused key returns 409
2. Create a call with `callAgentId`, plus `toNumber` and `fromNumberId` for phone calls
3. Send the key in the `Authorization` header on the TTS websocket, not the `apiKey` query parameter
4. Verify webhooks with the HMAC in `X-Elto-Signature`
5. Expect new dials to fail at the workspace's concurrent dial limit until calls end

## Questions

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

Vogent API scores 44.9 (E) on agent readiness against fone.me's 28.3 (F), and leads in 4 of 7 scored categories. fone.me leads on payments & pricing and maintenance & community.

### Can an agent call fone.me and Vogent API without installing anything?

Yes. fone.me has a hosted endpoint at https://www.fone.me/mcp and Vogent API at https://api.vogent.ai/api.


## For agents

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

## Other comparisons with fone.me or Vogent API

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

---

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