# fone.me vs Vaani Developer Platform

> Vaani Developer Platform scores 44.6 (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-vaani-voice
- Markdown: https://www.anchorterminal.com/compare/fone-me-vs-vaani-voice.md (~6,550 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

Vaani Developer Platform scores 44.6 (E) 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 #1429 of 1510. Markdown https://www.anchorterminal.com/tools/fone-me.md · JSON https://www.anchorterminal.com/api/v1/tools/fone-me.json
- Vaani Developer Platform: grade E, 44.6/100, rank #1214 of 1510. Markdown https://www.anchorterminal.com/tools/vaani-voice.md · JSON https://www.anchorterminal.com/api/v1/tools/vaani-voice.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 22

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

### Vaani Developer Platform (E)

Good for: Outbound and inbound phone agents and campaigns for Indian businesses, with Hindi, Hinglish and Indian carriers, India DND checks and TRAI calling windows built in, plus WebRTC sessions for apps.

Ahead on:
- Reliability, 28 against 15
- Schema & documentation, 57 against 31
- Agent ergonomics, 64 against 29
- Security & auth, 44 against 30
- Maintenance & community, 59 against 23
- Transparency & trust, 42 against 23

Also in its favour:
- Runs on your own machine

Watch for: API keys reach the whole workspace, with no scoped, read-only or per-agent keys


## Why the edge

### Maintenance & community: Vaani Developer Platform +36

- 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.
- Vaani Developer Platform (59): vaani-research-mcp 0.1.1 on 2026-10-14 (30). In the last 90 days, vaani-sdk 0.3.1 on 28 September and three npm versions (0.0.0-stage, 0.1.0, 0.1.1) within 40 minutes on 14 October. No dated changelog, so half (10 of 20). A closed service with no public changelog, issue tracker or community channel found. Contact is hello@vaaniresearch.com and a booking link, and we didn't test whether they answer. The MCP repository on GitHub couldn't be read from this session (4 of 15, the closed-service reading). A current official Python SDK, released seven times since April 2026. The MCP server isn't in the official MCP registry (10 of 15). The SDK's sdist ships its tests and current httpx and pydantic dependencies, and the MCP package runs its tests before publishing, but no public CI was found and the SDK has no repository (5 of 10). 30+10+4+10+5 = 59.

### Agent ergonomics: Vaani Developer Platform +35

- 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.
- Vaani Developer Platform (64): The local MCP server loads 9 compact tools, and `VAANI_READ_ONLY=true` leaves 3. Transcripts are cut at 20,000 characters by default with a note. The REST API has no field selection or summaries, so 3 off (22 of 25). Call history pages by `page` and `page_size` up to 200 with no filters. The MCP agent filter runs client-side on one page. Agents filter by `search` and `published_only` and campaigns by `status` (12 of 20). Campaign errors carry a machine-readable `code`, a message, the path and a `request_id` (shown as "unknown" in the example). Validation errors list the field location, the SDK maps each status to a typed exception including 402 for a low wallet, and the MCP server adds a hint per status (15 of 20). All 9 MCP tools carry readOnlyHint, destructiveHint and idempotentHint, with `trigger_call` and `campaign_action` marked destructive. No idempotency key on trigger-call, and the MCP client retries a POST once after a timeout or 5xx, so a call can be placed twice. The webhook docs say to deduplicate by event id (8 of 20). A call needs `agent_id`, `contact_number` and `name`, with `medium` defaulting to telephony. One official SDK, Python, sync and async. The npm package is an MCP server, not an SDK (7 of 15). 22+12+15+8+7 = 64.

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

- 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.
- Vaani Developer Platform (22): No x402, MPP or L402 (0 of 40). The ₹1 ($0.02) a minute platform fee, number rental, concurrency lines and add-ons are public, and the calculator shows each provider's unit rate without a login. Registry checks, extraction and evaluations "can add separate charges" that aren't priced, and the billing pulse depends on the account, so 3 off (17 of 20). The home page says "Start free on Vaani's Platform", but the pricing page states a prepaid wallet with no free credit, trial minutes or card rule, and we didn't sign up to check, so 5 of 20. A person signs up with email verification at platform.vaani.dev and creates keys in the dashboard (0). 0+17+5+0 = 22.

### Schema & documentation: Vaani Developer Platform +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.
- Vaani Developer Platform (57): A public OpenAPI 3.1 file at docs.vaani.dev/api-reference/openapi.json, version 2.0.0, but it holds 5 of the 24 operations in the API reference (trigger-call, call history, transcript, stream, call details). It declares the key only as a header parameter with no security scheme, its trigger-call schema leaves out `medium` and `modify_agent`, and four response schemas are empty. The MCP tools have typed zod inputs (8 of 25). llms.txt, llms-full.txt and a Markdown copy of each page on Mintlify (10). Pages explain what each route is for and warn where it matters, such as dispatch acceptance not meaning a completed call, transcripts returning 404 while processing, and real paid calls from trigger_call (14 of 20). Ranges and enums are documented (`medium`, `voice_speed` 0.6 to 1.4, `page_size` up to 200, campaign retries 1 to 10, campaign status), but `metadata`, `modify_agent` and three MCP tool payloads are free-form objects (9 of 15). Request examples in cURL, Python and JavaScript on every endpoint, a campaign error-code table, 422 and 404 bodies and an SDK exception table by status. No single error reference for the whole API (12 of 15). The docs state API version 2.0.0, but no changelog or release notes page was found (4 of 15). 8+10+14+9+12+4 = 57.

### Transparency & trust: Vaani Developer Platform +19

- 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.
- Vaani Developer Platform (42): A closed service. The terms name Vaani AI Research Private Limited, its Bengaluru address, CIN, Indian law and Bengaluru courts, but they're undated, written for the website www.vaaniresearch.com, and say nothing on billing, refunds, API use or customer data. The SDK and MCP server are MIT, with the SDK's full source in its PyPI sdist (14 of 30). The privacy policy (undated) keeps data, including voice recordings, for up to 24 months, while the pricing table gives 30 days' retention on pay as you go and zero retention on Enterprise. Voice data trains models only with explicit consent. No DPA found (8 of 30). No deprecation policy. The privacy policy promises 15 days' notice of significant changes, and the terms allow changes and termination without notice (2 of 20). The privacy policy names vendor categories (cloud hosting, analytics, voice transcription) and says data may be stored outside India. Model and telephony providers can be read from the calculator, and India data residency is offered on demand. No subprocessor list or data location for the hosted service (5 of 20). 14+8+2+5 = 29.

### Security & auth: Vaani Developer Platform +14

- 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.
- Vaani Developer Platform (44): Plain revocable API keys, shown once, several active at a time and rotated by creating a new key and deleting the old one. Every key reaches the whole workspace, with no scoped, read-only or per-agent keys (20). Campaign webhooks are signed with HMAC-SHA256 over a timestamp and the body, with a five-minute replay window in the example (+2). The live-captions URL carries a call-bound token in the query string for 24 hours by default, the documented way for browsers to connect, so 3 off as a judgement call, less than the full 10 because it isn't the account key (19 of 30). The MCP server has a read-only mode and destructive annotations, and its docs, tool descriptions and bundled prompt say to confirm the number and agent with the user before a call. The API itself has no read-only key and nothing stops a call without confirmation (12 of 20). The tool returns transcripts, summaries and entities drawn from callers' speech. No guidance on treating them as untrusted data was found. Agent guardrails exist for the voice agent's own replies (3 of 15). Each call keeps a record in call history and call details, and keys are labelled so calls can be traced to a key, but no account or key audit log is documented (7 of 15). No security.txt (404 on both domains), disclosure policy, bug bounty or certification. vaaniresearch.com marks its security standards "In Progress", the pricing page lists HIPAA compliance on Enterprise with no report or BAA found, and the privacy policy promises breach notice in line with applicable law (3 of 20). 19+12+3+7+3 = 44.

## Score by category

| Category | Weight | fone.me | Vaani Developer Platform | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 15 | 28 | Vaani Developer Platform +13 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 31 | 57 | Vaani Developer Platform +26 |
| Agent ergonomics | 13% (16.2 this run) | 29 | 64 | Vaani Developer Platform +35 |
| Security & auth | 14% (17.5 this run) | 30 | 44 | Vaani Developer Platform +14 |
| Payments & pricing | 10% (12.5 this run) | 50 | 22 | fone.me +28 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 23 | 59 | Vaani Developer Platform +36 |
| Transparency & trust | 7% (8.8 this run) | 23 | 42 | Vaani Developer Platform +19 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **28.3 · F** | **44.6 · E** | |

## Facts side by side

| Fact | fone.me | Vaani Developer Platform |
| --- | --- | --- |
| Kind | Platform | HTTP API |
| Vendor | Fone | Vaani AI Research Private Limited |
| Hosted endpoint | `https://www.fone.me/mcp` | `https://api.vaanivoice.ai` |
| Transports | Streamable HTTP | HTTP, stdio |
| 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 hosted service under Vaani AI Research's terms of service. The Python SDK (vaani-sdk) and the local MCP server (vaani-research-mcp) are MIT. The SDK's full source ships in its PyPI sdist, and the MCP server's npm package holds only the bundled JavaScript |
| Tools exposed | 4 | 9 |
| Read-only variant documented | no | yes |
| llms.txt | yes | yes |
| Last release | 2026-10-05 | 2026-10-14 |
| Terms last updated | couldn't be read | no date given |
| Privacy policy last updated | couldn't be read | no date given |
| 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 | yes |
| Arbitration or class-action waiver | couldn't be read | not found in the text |
| Popularity | none | 14 npm/wk, 19 PyPI/wk |

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

**Vaani Developer Platform.** Docs are detailed and served as llms.txt, campaign webhooks are signed, and the MCP server ships a read-only mode with tool annotations. Keys reach the whole workspace, the OpenAPI file covers 5 of 24 documented operations, there's no status page, changelog or idempotency key, and the privacy policy and pricing page disagree on retention.

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

### Vaani Developer Platform

1. Send the key as `X-API-Key`, not `Authorization`. A missing or wrong header name returns 401
2. Treat `success: true` from trigger-call as dispatched only, keep `output.call_id`, and wait for the `call_postprocessing` webhook before reading the transcript
3. Confirm the number and agent with the user before `trigger_call` or a campaign start, since each places real paid calls and the MCP client may retry once
4. Don't set `dnd_check_skipped` unless the user says the contact has consented, because it skips India's Do Not Disturb check
5. Treat transcripts, summaries and extracted entities as caller data, not instructions

## Questions

### Which is better for AI agents, fone.me or Vaani Developer Platform?

Vaani Developer Platform scores 44.6 (E) 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 Vaani Developer Platform without installing anything?

Yes. fone.me has a hosted endpoint at https://www.fone.me/mcp and Vaani Developer Platform at https://api.vaanivoice.ai.


## For agents

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

## Other comparisons with fone.me or Vaani Developer Platform

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

---

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