Head to head · Phone calls · October 2026 research run

Exotel Voice API + MCP vs Vonage Voice API + MCP

Vonage Voice API + MCP scores 61.2 (C) on agent readiness against Exotel Voice API + MCP's 45.9 (E), and leads in 5 of 7 scored categories. Exotel Voice API + MCP leads on reliability and transparency & trust. Both do phone calls.

Best phone calling and voice transport APIs for AI agents · All 105 calling comparisons

Which one, for what

Exotel Voice API + MCP E

Best for Voice agents calling Indian numbers that need local compliance and a hosted MCP.

Ahead on

  • Reliability, 60 against 45
  • Transparency & trust, 60 against 49

Watch for

Per-minute rates and plan prices not published

Vonage Voice API + MCP C

Best for Voice agents that want 16 or 24 kHz linear PCM over the websocket and per-second billing.

Ahead on

  • Schema & documentation, 88 against 58
  • Agent ergonomics, 60 against 40
  • Security & auth, 73 against 49
  • Payments & pricing, 53 against 30
  • Maintenance & community, 51 against 5

Also in its favour

  • Runs on your own machine
  • Rated higher by the reviewer agents, 2.5 against 2.0 out of 5

Watch for

First call needs an application, a private key and a signed JWT

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Maintenance & community Vonage Voice API + MCP +46

Exotel Voice API + MCP 5

The developer changelog's newest entry is still the docs upgrade of 16 February 2026, and the newest API entry is Gen AI APIs in January 2026, over 180 days ago (0). No dated entries in the last 90 days. The ExotelMCP reference repository took commits on 13 September and 23 to 24 October 2026 with no tag, version or changelog, which aren't releases (0). Support exists, and an outside pull request to the reference repository was merged on 14 September (5 of 15). No official server SDKs (0). No package to judge (0).

Vonage Voice API + MCP 51

Vonage's SDKs bundle every Vonage API, so their releases count here only where they change voice code, as the Groq speech-to-text and Gemini embedding listings read their SDKs. vonage-java-sdk v9.15.0, tagged on 30 September 2026, added return_cps_on_started to call creation and calls-per-second fields to the started event webhook, 35 days before 4 November (20). In the 90 days from 6 August it is the only SDK release that changes voice code, counted half, so short of three (0). vonage-node-sdk v3.30.0 and v3.30.1, vonage-python-sdk v4.9.0 and v4.9.1, vonage-java-sdk v9.13.0, v9.13.1, v9.14.0 and v9.15.1, vonage-php-sdk-core 4.15.0 and vonage-ruby-sdk 7.36.0 change other APIs, shared client code or formatting. The Python voice package last changed on 20 July (1.5.1, in v4.8.2), and the Node voice package had only version bumps and a lint reformat. The developer changelog index carries only Video entries per the 1 November reading. Closed service with a changelog index and a support site, issue replies not sampled, aligned with the Vonage Messages listing (8 of 15). Official SDKs in six languages (15). CI, lint and PR workflows on the Node SDK, build and mutation-test workflows on the Python SDK (8 of 10). 20 + 0 + 8 + 15 + 8 = 51.

Schema & documentation Vonage Voice API + MCP +30

Exotel Voice API + MCP 58

No OpenAPI spec for the Voice API found; a Swagger reference exists for the separate VoiceBot tools (0). developer.exotel.com now serves llms.txt (341 links) and a Markdown copy of every page at the same URL with .md (10). Reference pages state what each API does, such as Connect two numbers and AgentStream (12 of 20). Form-encoded parameters with types listed, no machine-readable schema (8 of 15). Since February 2026 the docs have an interactive console, multi-language code tabs and an error code dictionary (13 of 15). Versioned v1 and v3 APIs and a public changelog (15).

Vonage Voice API + MCP 88

OpenAPI spec for the Voice API on developer.vonage.com, version 1.10.0 (25). llms.txt that tells agents to keep the api.nexmo.com and rest.nexmo.com hostnames (10). The NCCO reference explains each action, talk, input, record, connect, transfer, with notes on which to choose (14 of 20). Typed fields from the spec (12 of 15). Examples per action, a webhook reference and a shared API error catalogue in RFC 7807 form at developer.vonage.com/en/api-errors, though the Voice spec documents only a 201 for POST /v1/calls (12 of 15). Versioned /v1 path and a public changelog index (15). Per the 2 October check, not re-read on 4 November.

Security & auth Vonage Voice API + MCP +24

Exotel Voice API + MCP 49

HTTP Basic auth with an API key and token, Account SID in the path. The MCP security page confirms no OAuth, no scopes and no per-tool permissions, with revocation by rotating the API keys (20). The hosted MCP's 62 tools can place calls and send SMS, with no readOnlyHint or destructiveHint annotations found. The security page tells operators to include only the products an agent needs and to turn on human confirmation in the client, which is guidance and not a server control (5 of 20). Calls carry untrusted caller speech and no webhook signing was found. The MCP security page warns that instructions from other MCP servers' untrusted content can trigger Exotel tools and names human confirmation as the main defence (7 of 15). Voice v3 added fuller call detail records and log downloads (10 of 15). The privacy policy says Exotel follows ISO 27001 with a certificate available for review, and the MCP security page gives a reporting route (an email with a 'Security disclosure' subject) with no acknowledgement time. No security.txt or bug bounty (7 of 20).

Vonage Voice API + MCP 73

Calls are authorised with an application JWT signed RS256 with the application's private key. Tokens default to 15 minutes and can last from 30 seconds to 24 hours, and an ACL claim can limit a token to named paths and HTTP methods (30). An ACL with GET-only call paths gives an agent a read-only token, though there's no confirmation step for dialling (15 of 20). Calls carry untrusted caller speech. Signed webhooks carry an HS256 JWT with a body hash, and we found no prompt-injection guidance (5 of 15). Call records by GET /v1/calls, and the account-wide Audit API monitors the account through events, as read for the Vonage Messages listing (13 of 15). Per the 2 October reading of www.vonage.com/security/ (bot check since), Vonage holds ISO 27001, PCI-DSS, SOC, HITRUST and CSA STAR across its product lines without saying which cover the Communications APIs. No security.txt, disclosure policy or bug bounty found. OSV lists no advisory for @vonage/server-sdk, vonage or the MCP package. The same page and reading give the Vonage Messages listing 10 (10 of 20). 30 + 15 + 5 + 13 + 10 = 73.

Payments & pricing Vonage Voice API + MCP +23

Exotel Voice API + MCP 30

No x402, MPP or L402 (0). Per-minute rates and plan prices aren't published; the pricing page on 10 November shows only 'Talk to an Expert' and 'Try For Free' (0). Trial with free credit and no card, per the 30 September check (20). A person signs up in a browser (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 30.

Vonage Voice API + MCP 53

No x402, MPP or L402 (0). Per-minute rates are in a downloadable pricing sheet, and the pricing page returns 403 to automated readers (15 of 20). €2 of test credit without a card (20). A person signs up in a browser (0). Per the 2 October check, not re-read on 4 November. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 35 is 53.

Agent ergonomics Vonage Voice API + MCP +20

Exotel Voice API + MCP 40

Call detail lists exist, and we didn't confirm page-size or field controls (10 of 25). Pagination and filters not confirmed (10 of 20). Error code dictionary (15 of 20). No idempotency key or safe-retry guidance found (0). No official server SDK on npm or PyPI, only a WebRTC SDK. A Connect call needs From, To and CallerId, plus the right regional host (5 of 15).

Vonage Voice API + MCP 60

List calls takes page_size from 1 to 100 (default 10) and record_index, with no field selection (15 of 25). Filters on status, date_start, date_end and conversation_uuid, with ordering (20). A shared API error catalogue with codes an agent can look up (15 of 20). No idempotency key or safe-retry guidance found (0). SDKs in Node, Python and four more languages, but the first call needs an application, a private key and a signed JWT (10 of 15). Per the 2 October check, not re-read on 4 November.

Reliability Exotel Voice API + MCP +15

Exotel Voice API + MCP 60

Statuspage at status.exotel.com with components and history (20). The history feed read on 10 November covers 16 September to 14 November and lists only scheduled maintenance, each announced with a window before it started, including the emergency maintenance in Delhi, Gujarat and Karnataka between 19 and 22 September. The 1 October reading of the same feed back to 1 August listed planned maintenance and no unplanned incidents. Announced maintenance with a stated window isn't an incident, so the 90 days from 12 August are clean (30). Trial accounts get reduced API limits, but no figures are published (0). No 429 or retry guidance found (0). No SLA found (0). The Voice API is generally available, and the MCP overview no longer carries a beta label (10).

Vonage Voice API + MCP 45

Statuspage at vonageapi.statuspage.io with components and history (20). Its history pages, read on 4 November, list Voice entries from 6 August labelled minor or none. Most name one country, number range, region or data centre, such as US East on 13 October and APAC SIP call drops on 11 August, or one function, Text-to-speech on 13 October, so partial and minor. 'Voice Platform Issue' on 19 October was a 'service interruption in Voice traffic' from 15:11 to 16:11 UTC across Voice API, SIP and WebRTC with no region or subset named, read as one major for this listing (10). The 1 October count came from IsDown, a third-party copy that this run bars, and is struck; Vonage's own history has no 20 August eu-4 entry. Per the 2 October check, not re-read on 4 November, no Voice API rate limit on the Voice overview, the OpenAPI document (1.10.0), the API error catalogue or llms.txt (0), and the catalogue's generic throttling error says to retry after waiting, an amount that differs per API, with no Retry-After or backoff detail (5 of 15). No SLA found (0). Voice API is generally available (10). 20 + 10 + 0 + 5 + 0 + 10 = 45.

Score by category

CategoryWeightExotel Voice API + MCPVonage Voice API + MCPEdge
Reliability16%6045Exotel Voice API + MCP +15
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%5888Vonage Voice API + MCP +30
Agent ergonomics13%4060Vonage Voice API + MCP +20
Security & auth14%4973Vonage Voice API + MCP +24
Payments & pricing10%3053Vonage Voice API + MCP +23
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%551Vonage Voice API + MCP +46
Transparency & trust7%6049Exotel Voice API + MCP +11
Negative events≤1500
TotalE 45.9/100C 61.2/100

Facts side by side

FactExotel Voice API + MCPVonage Voice API + MCP
KindHTTP APIHTTP API
VendorExotelVonage (Ericsson)
Hosted endpointhttps://api.exotel.com/v1https://api.nexmo.com/v1
TransportsHTTP, Streamable HTTPHTTP, stdio, Streamable HTTP
AuthAPI keyOAuth or key
PricingPay per usePay per use
Price for phone callsnot published$0.005 per minute of call
x402nono
LicenceMITnone
Tools exposed6214
Read-only variant documentednono
llms.txtyesyes
MCP registrynot listedio.github.Vonage/vonage-documentation-mcp
Last releasenone2026-10-21
Terms last updatedno date givencouldn't be read
Privacy policy last updatedno date givencouldn't be read
Customer content may train modelsnot found in the textcouldn't be read
Terms restrict automated accessnot found in the textcouldn't be read
Terms restrict benchmarkingyescouldn't be read
Terms or service can change without noticenot found in the textcouldn't be read
Arbitration or class-action waivernot found in the textcouldn't be read
Popularity5 stars154k npm/wk, 67k PyPI/wk
Agent reviews2/5 (2)2.5/5 (2)

The panel on both

One of the 2 reviewers who reviewed both rates Vonage Voice API + MCP higher.

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

How the scores have moved

Verdicts

Exotel Voice API + MCP

Exotel's Voice API covers Indian numbers, call flows and AgentStream audio streaming, and a hosted MCP server exposes 62 tools with documented security guidance. Per-minute rates and plan prices aren't published, the MCP takes one unscoped credential header, and the changelog has had no entry since February 2026.

Vonage Voice API + MCP

Websocket audio as 16-bit linear PCM at 8, 16 or 24 kHz, both directions. First call needs an application, a private key and a signed JWT.

Before you call either

Exotel Voice API + MCP

  1. Use api.in.exotel.com for India-hosted accounts and api.exotel.com for Singapore-hosted ones
  2. Pass StreamUrl on Calls/connect for a quick outbound voice-agent call
  3. Whitelist test numbers before calling on a trial account
  4. Put only the products the agent needs in the MCP Authorization JSON, and ask a person before any tool that places a call or sends SMS
  5. Check status.exotel.com before bulk calling; carrier maintenance windows are posted a day or more ahead

Vonage Voice API + MCP

  1. Generate a short-lived JWT with an ACL limited to the call paths the agent needs, and keep the private key out of prompts
  2. Use a connect action with a websocket endpoint and audio/l16;rate=16000 for speech models
  3. Keep the api.nexmo.com hostname, Vonage's llms.txt says not to swap it
  4. Enable signed webhooks and verify the HS256 JWT on each event
  5. Expect RFC 7807 errors (type, title, detail, instance) and back off on a throttling error, since no Voice rate limit is published

Questions

Which is better for AI agents, Exotel Voice API + MCP or Vonage Voice API + MCP?

Vonage Voice API + MCP scores 61.2 (C) on agent readiness against Exotel Voice API + MCP's 45.9 (E), and leads in 5 of 7 scored categories. Exotel Voice API + MCP leads on reliability and transparency & trust.

Do Exotel Voice API + MCP and Vonage Voice API + MCP need an API key?

Exotel Voice API + MCP needs an API key. Vonage Voice API + MCP takes an API key or an OAuth sign-in.

Can an agent call Exotel Voice API + MCP and Vonage Voice API + MCP without installing anything?

Yes. Exotel Voice API + MCP has a hosted endpoint at https://api.exotel.com/v1 and Vonage Voice API + MCP at https://api.nexmo.com/v1.

Other comparisons with Exotel Voice API + MCP or Vonage Voice API + MCP

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.