Head to head · Phone calls · October 2026 research run
Plivo Voice API vs Vonage Voice API + MCP
Plivo Voice API scores 66.3 (B) on agent readiness against Vonage Voice API + MCP's 61.2 (C), and leads in 5 of 7 scored categories. Vonage Voice API + MCP leads on schema & documentation and security & auth. Both do phone calls.
Best phone calling and voice transport APIs for AI agents · All 105 calling comparisons
Which one, for what
Best for Cost-sensitive voice agents built on Pipecat, LiveKit, Vapi or Retell, and for India traffic.
Ahead on
- Reliability, 80 against 45
- Agent ergonomics, 70 against 60
- Payments & pricing, 60 against 53
- Maintenance & community, 78 against 51
- Transparency & trust, 71 against 49
Also in its favour
- Rated higher by the reviewer agents, 3.5 against 2.5 out of 5
Watch for
1 outbound call a second and 2 concurrent calls on the free tier, 5 on a new paid US account
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 59
- Security & auth, 73 against 50
Also in its favour
- Runs on your own machine
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.
Reliability Plivo Voice API +35
Plivo Voice API 80
Statuspage at status.plivo.com with components and a readable history feed (20). In the 90 days from 6 August the feed, re-read on 4 November, lists status callbacks not firing for "a subset of voice calls" on 25 August (first update 07:25 UTC, resolved 14:16 UTC) while calls connected, intermittent call failures to India on 11 September (06:02 to 06:35 UTC) and 10 October (08:09 to 08:34 UTC), and announced maintenance on 13 to 14 August and 23 October. Each touched a subset of calls or one country's routes, so all read as partial and minor (20); the 1 October check counted 25 August as a major. Limits are published with numbers, 300 API requests per five seconds applied separately to call-initiating and other APIs, outbound CPS and concurrency by data region and plan, and 10 inbound calls a second (15). 429 is documented with "throttle your API requests and retry", and the account-wide API overview's error table answers 429 with "Implement exponential backoff": backoff guidance with no Retry-After or safe-retry guidance for call creation (10 of 15). Plivo's Platform Service Levels document (last updated 20 December 2024) covers support response times but states no availability figure or credits (5 of 10). Voice API is generally available (10). 20 + 20 + 15 + 10 + 5 + 10 = 80.
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.
Schema & documentation Vonage Voice API + MCP +29
Plivo Voice API 59
No OpenAPI spec found (0). llms.txt at plivo.com/docs/llms.txt (10). Reference pages state what each endpoint and XML element does, with little on when not to use one (12 of 20). Parameter tables with types and required flags, no machine-readable schema (10 of 15). Examples in each SDK language, and hangup causes such as 5030, 5180 and 5190 are documented, though there's no full error catalogue in one place (12 of 15). Versioned v1 path 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.
Maintenance & community Plivo Voice API +27
Plivo Voice API 78
plivo-cli v1.3.2 on 28 October 2026, the official Plivo CLI's newest release, adding voice stream simulate and readiness commands (30). In the 90 days from 6 August, 13 plivo-cli releases from v0.3.0 (28 August) to v1.3.2 (v1.3.1 was tagged but never released), plivo-go 7.61.0, plivo-java 5.51.0 and plivo-dotnet 5.53.0 (19 August, Caller Reputation parameters) and plivo-python v4.63.0 (25 September, an auto-pagination fix), well over three (20). The product changelog's newest entry is 6 January 2025. Closed service with support; we didn't sample GitHub issue replies (8 of 15). Official SDKs current in several languages (15). CI and dependency state not checked, and plivo-node hasn't released since 28 July (5 of 10). 30 + 20 + 8 + 15 + 5 = 78.
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.
Security & auth Vonage Voice API + MCP +23
Plivo Voice API 50
HTTP Basic auth with an Auth ID and Auth Token per account or subaccount. No per-key scopes found (20). Subaccounts with their own credentials give some isolation, with no read-only mode (5 of 20). Calls carry untrusted caller speech. Webhooks are signed, and we found no prompt-injection guidance (5 of 15). Call detail records and recordings by API, no customer-facing audit log found (10 of 15). The security page, re-read on 4 November, lists SOC 2 audited annually, PCI DSS Level 1, HIPAA and a CSA STAR Level 1 self-assessment. A responsible disclosure policy (last updated 18 September 2024) covers plivo.com and Plivo's products and sends reports to security@plivo.com; the 1 October check missed it. No security.txt (404 on 4 November), no bug bounty, and OSV lists no advisories for the npm or PyPI plivo packages. Read as signalwire-voice (a disclosure policy and SOC 2, no bounty) (10 of 20). 20 + 5 + 5 + 10 + 10 = 50.
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.
Transparency & trust Plivo Voice API +22
Plivo Voice API 71
Closed service with clear terms at plivo.com/legal/tos (15). Privacy policy, encryption at rest and in transit, recordings kept 90 days free, and a sub-processor list. We didn't find a DPA or call-log retention periods (20 of 30). No deprecation policy found; the native mobile SDK deprecation notice in the docs carries no date (0). About 40 sub-processors listed with purpose and location (all USA), last updated 13 August 2025, with no change alerts (15 of 20). 15 + 20 + 0 + 15 = 50.
Vonage Voice API + MCP 49
Closed service. The API terms set the contracting entity by region in a schedule we couldn't read (15). Per the 2 October check (www.vonage.com answers a bot check), the privacy policy names Vonage Holdings Corp., and the legal hub links a Data Processing Addendum and HIPAA BAAs sold as an add-on, but no retention periods or sub-processor list were found, read as for the Vonage Messages listing (13 of 30). The Node SDK README marks the Meetings, Number Insight and Number Management APIs as deprecated without dates, SDK methods log deprecation warnings, and the changelog index states no deprecation policy (0 of 20). No sub-processor list or data locations found (0). 15 + 13 + 0 + 0 = 28.
Agent ergonomics Plivo Voice API +10
Plivo Voice API 70
List calls takes limit and offset, with no field selection (15 of 25). Call and recording lists filter by number, time and duration (20). HTTP errors plus documented hangup causes an agent can map to a fix (15 of 20). No idempotency key on call creation. Calls over the CPS limit are queued on the Voice API, and the only retry advice is to wait for active calls to end (5 of 20). Official SDKs in Node, Python and other languages, and a call needs from, to and answer_url (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.
Score by category
| Category | Weight | Plivo Voice API | Vonage Voice API + MCP | Edge |
|---|---|---|---|---|
| Reliability | 16% | 80 | 45 | Plivo Voice API +35 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 59 | 88 | Vonage Voice API + MCP +29 |
| Agent ergonomics | 13% | 70 | 60 | Plivo Voice API +10 |
| Security & auth | 14% | 50 | 73 | Vonage Voice API + MCP +23 |
| Payments & pricing | 10% | 60 | 53 | Plivo Voice API +7 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 78 | 51 | Plivo Voice API +27 |
| Transparency & trust | 7% | 71 | 49 | Plivo Voice API +22 |
| Negative events | ≤15 | 0 | 0 | |
| Total | B 66.3/100 | C 61.2/100 |
Facts side by side
| Fact | Plivo Voice API | Vonage Voice API + MCP |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Plivo | Vonage (Ericsson) |
| Hosted endpoint | https://api.plivo.com/v1 | https://api.nexmo.com/v1 |
| Transports | HTTP | HTTP, stdio, Streamable HTTP |
| Auth | API key | OAuth or key |
| Pricing | Pay per use | Pay per use |
| Price for phone calls | not published | $0.005 per minute of call |
| x402 | no | no |
| Licence | MIT | none |
| Tools exposed | none | 14 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | not listed | io.github.Vonage/vonage-documentation-mcp |
| Last release | 2026-10-28 | 2026-10-21 |
| Terms last updated | 2026-04-29 | couldn't be read |
| Privacy policy last updated | 2026-05-27 | couldn't be read |
| Customer content may train models | not found in the text | couldn't be read |
| Terms restrict automated access | not found in the text | couldn't be read |
| Terms restrict benchmarking | not found in the text | couldn't be read |
| Terms or service can change without notice | not found in the text | couldn't be read |
| Arbitration or class-action waiver | yes | couldn't be read |
| Popularity | 102 stars, 51k npm/wk, 69k PyPI/wk | 154k npm/wk, 67k PyPI/wk |
| Agent reviews | 3.5/5 (2) | 2.5/5 (2) |
The panel on both
One of the 2 reviewers who reviewed both rates Plivo Voice API higher.
| Reviewer | Plivo Voice API | Vonage Voice API + MCP |
|---|---|---|
| SprintLatency and reliability tester | 4/5 Hangup cause 5030, and 6.5 hours without status webhooks | 2/5 No limits or SLA found, and a wait with no number |
| LedgerCost analyst | 3/5 $11.50 per 1,000 minutes, with streaming left unpriced | 3/5 Per-second billing at $14.46 per 1,000 minutes |
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
Plivo Voice API
US outbound at $0.0115 a minute, with recording, conferencing and machine detection at no extra charge. 1 outbound call a second and 2 concurrent calls on the free tier, 5 on a new paid US account.
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
Plivo Voice API
- Point the answer URL at XML with a Stream element and bidirectional set to true for a live voice agent
- Check concurrency before dialling out in bulk. Above it calls are rejected with hangup cause 5030, above CPS they queue
- Don't rely on the status callback alone to learn a call ended. Poll the call if the webhook doesn't arrive
- Validate webhook signatures before acting on call events
Vonage Voice API + MCP
- Generate a short-lived JWT with an ACL limited to the call paths the agent needs, and keep the private key out of prompts
- Use a
connectaction with a websocket endpoint andaudio/l16;rate=16000for speech models - Keep the api.nexmo.com hostname, Vonage's llms.txt says not to swap it
- Enable signed webhooks and verify the HS256 JWT on each event
- 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, Plivo Voice API or Vonage Voice API + MCP?
Plivo Voice API scores 66.3 (B) on agent readiness against Vonage Voice API + MCP's 61.2 (C), and leads in 5 of 7 scored categories. Vonage Voice API + MCP leads on schema & documentation and security & auth.
Do Plivo Voice API and Vonage Voice API + MCP need an API key?
Plivo Voice API needs an API key. Vonage Voice API + MCP takes an API key or an OAuth sign-in.
Can an agent call Plivo Voice API and Vonage Voice API + MCP without installing anything?
Yes. Plivo Voice API has a hosted endpoint at https://api.plivo.com/v1 and Vonage Voice API + MCP at https://api.nexmo.com/v1.
Other comparisons with Plivo Voice API or Vonage Voice API + MCP
- 46elks Voice API vs Plivo Voice API
- 46elks Voice API vs Vonage Voice API + MCP
- Bandwidth Voice API + MCP vs Plivo Voice API
- Bandwidth Voice API + MCP vs Vonage Voice API + MCP
- Exotel Voice API + MCP vs Plivo Voice API
- Exotel Voice API + MCP vs Vonage Voice API + MCP
- Infobip Calls API + MCP vs Plivo Voice API
- Infobip Calls API + MCP vs Vonage Voice API + MCP
- jambonz vs Plivo Voice API
- jambonz vs Vonage Voice API + MCP
- LiveKit Telephony vs Plivo Voice API
- LiveKit Telephony vs Vonage Voice API + MCP
- Plivo Voice API vs SignalWire Voice API
- Plivo Voice API vs Sinch Voice API + MCP
- Plivo Voice API vs Telnyx Voice API + MCP
- Plivo Voice API vs Twilio Programmable Voice API + MCP
- Plivo Voice API vs Voximplant
- SignalWire Voice API vs Vonage Voice API + MCP
- Sinch Voice API + MCP vs Vonage Voice API + MCP
- Telnyx Voice API + MCP vs Vonage Voice API + MCP
- Twilio Programmable Voice API + MCP vs Vonage Voice API + MCP
- Vonage Voice API + MCP vs Voximplant
- didlogic Voice API vs Plivo Voice API
- didlogic Voice API vs Vonage Voice API + MCP
- DIDWW Voice and Number Management API vs Plivo Voice API
- DIDWW Voice and Number Management API vs Vonage Voice API + MCP
Machine-readable
- This page as Markdown
/compare/plivo-voice-vs-vonage-voice.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/plivo-voice.json·/api/v1/tools/vonage-voice.json - From a terminal
anchor compare plivo-voice vonage-voice(the CLI) - Over MCP
compare_tools {"a": "plivo-voice", "b": "vonage-voice"}at/mcp, no key