Head to head · SMS · October 2026 research run

Plivo API vs Vonage Messages API + MCP

Vonage Messages API + MCP scores 69.2 (B) on agent readiness against Plivo API's 66.1 (B), and leads in 3 of 7 scored categories. Plivo API leads on reliability, agent ergonomics and transparency & trust. Both do sms.

Best SMS, WhatsApp and messaging APIs for AI agents · All 190 messaging comparisons

Which one, for what

Plivo API B

Best for Cost-sensitive SMS and WhatsApp sends from code, and for teams that also use Plivo voice.

Ahead on

  • Reliability, 90 against 77
  • Agent ergonomics, 57 against 50
  • Transparency & trust, 71 against 49

Also in its favour

  • Rated higher by the reviewer agents, 3.5 against 3.0 out of 5

Watch for

No OpenAPI spec

Vonage Messages API + MCP B

Best for Agents that need several chat channels behind one call with SMS failover.

Ahead on

  • Schema & documentation, 90 against 59
  • Security & auth, 73 against 50

Also in its favour

  • Runs on your own machine

Watch for

No idempotency key, and channel rejections arrive only by status webhook after a 202

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.

Schema & documentation Vonage Messages API + MCP +31

Plivo API 59

No OpenAPI spec found (0). llms.txt at plivo.com/docs/llms.txt (10). Reference pages state what each endpoint 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. We didn't recheck the messaging error list this run (12 of 15). Versioned v1 path and a public changelog (15).

Vonage Messages API + MCP 90

OpenAPI 3.0.3 spec for the Messages API, version 1.20.0 on 1 November, with POST /messages and PATCH /messages/{message_uuid} (25). llms.txt that tells agents to keep the api.nexmo.com hostnames and use the Messages API over the legacy SMS API (10). The reference explains each channel's message types, with less on when not to use one (14 of 20). Typed fields from the spec (12 of 15). Examples per channel and a shared API error catalogue (14 of 15). Versioned /v1 path, a versioned spec and a public changelog index (15).

Security & auth Vonage Messages API + MCP +23

Plivo API 50

HTTP Basic auth with an Auth ID and Auth Token per account or subaccount, the Auth ID also in every path. No per-key scopes found (20). Subaccounts with their own credentials give some isolation, with no read-only mode (5 of 20). Inbound SMS and WhatsApp bodies are untrusted text. Webhooks are signed, and we found no prompt-injection guidance (5 of 15). Message detail records by API, no customer-facing audit log found (10 of 15). SOC 2 audited annually, PCI DSS Level 1 and HIPAA per the security page. 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), no bug bounty, and OSV lists no advisories for the npm or PyPI plivo packages, read as plivo-voice and signalwire-voice (10 of 20). 20 + 5 + 5 + 10 + 10 = 50.

Vonage Messages API + MCP 73

Sends can be authorised with an application JWT signed RS256, whose ACL claim limits paths and methods and whose lifetime runs from 30 seconds to 24 hours, or with Basic auth on the account key and secret (30). JWT ACLs can narrow a token, with no confirmation step for sends (15 of 20). Inbound messages are untrusted text. Webhooks carry an HS256 JWT with a payload_hash of the body, and we found no prompt-injection guidance (5 of 15). Message records through the Reports API, which the MCP's get-records-report tool calls, and an Audit API that monitors the account through events, priced at $550 a month on the pricing page (13 of 15). Per the 2 October check (www.vonage.com answered a bot check on 1 November), the security page says Vonage holds ISO 27001, PCI-DSS, SOC, HITRUST and CSA STAR across its product lines without saying which cover the Communications APIs, and links a CSA STAR registry entry. www.vonage.com/.well-known/security.txt answered 404 on 1 November, and no disclosure policy or bug bounty was found. OSV lists no advisory for @vonage/server-sdk, vonage, @vonage/messages or the MCP package (10 of 20).

Transparency & trust Plivo API +22

Plivo API 71

Closed service with clear terms at plivo.com/legal/tos (15). Privacy policy, encryption at rest and in transit, and a sub-processor list. We didn't find a DPA or message-log retention periods (20 of 30). No deprecation policy or dated notices found (0). About 40 sub-processors listed with purpose and location (all USA), last updated 2025-08-13, with no change alerts (15 of 20).

Vonage Messages API + MCP 49

Closed service. The legal hub, DPA and privacy pages are per the 2 October check, since www.vonage.com answered a bot check on 1 November. The API terms set the contracting entity by region in a schedule, and the terms body didn't render for our reader on 2 October either. The MCP server is Apache-2.0 (15). The legal hub links a Data Processing Addendum and HIPAA BAAs are sold as an add-on, but we found no retention periods, and the privacy policy page rendered only as a landing page (13 of 30). SDK deprecation warnings, but no dated deprecation policy found (0 of 20). No sub-processor list or data locations found on the legal hub, the security page or the DPA landing page (0).

Reliability Plivo API +13

Plivo API 90

Statuspage at status.plivo.com with components and a readable history feed (20). From 6 August the feed posts announced India carrier maintenance (13 to 14 August, announced on 5 August), voice call webhooks degraded for a subset of calls (25 August), intermittent call failures to India (11 September, 10 October) and announced Plivo CX console and flows maintenance (23 October). None touches messaging, so a clean record for this listing (30). API limit published, 300 requests per 5 seconds, with a 429 above it (15). The API overview's error table answers 429 with "Implement exponential backoff", backoff guidance with no Retry-After or safe-retry guidance for sends (10 of 15). Plivo's Platform Service Levels document covers support response times only, with no availability figure or credits (5 of 10). Messaging API is generally available (10). 20 + 30 + 15 + 10 + 5 + 10 = 90.

Vonage Messages API + MCP 77

Statuspage at vonageapi.statuspage.io with components and history (20). Its history pages, read on 1 November, list 565 entries from 3 August, 444 of them maintenance, 101 minor and 20 with no impact set, and none major or critical. Messaging incidents hit one carrier, country or region, such as outbound SMS in the APAC region for 19 minutes on 21 October and T-Mobile delivery on a subset of 10DLC numbers on 1 October, so partial and minor (20). The earlier IsDown count is struck, since a third-party copy of a status page isn't evidence in this run. The Messages API allows 75 requests a second per API key by default, and exceeding it returns 429 (15). The OpenAPI spec documents 429 with Retry-After and X-RateLimit headers, without backoff or safe-retry guidance (12 of 15). No SLA found on the legal hub or security page, per the 2 October check, not re-read on 1 November (0). The Messages API is generally available (10). 20 + 20 + 15 + 12 + 0 + 10 = 77.

Agent ergonomics Plivo API +7

Plivo API 57

List endpoints take limit and offset, with no field selection (15 of 25). Message list filters weren't rechecked this run (15 of 20). HTTP status errors, and we didn't recheck the messaging error-code list this run (12 of 20). No idempotency key or safe-retry guidance for sends found (0 of 20). Official SDKs in Node, Python and other languages, and a send needs src, dst and text (15).

Vonage Messages API + MCP 50

The Messages API sends and updates messages and returns a message_uuid. Lists and searches live in the separate Reports API (15 of 25). Filtering only through Reports (10 of 20). A shared error catalogue with codes an agent can look up (15 of 20). No idempotency key on sends, and channel-level rejections arrive later by status webhook after a 202 (0 of 20). SDKs in Node, Python and four more languages. Basic auth works for sends, but application webhooks need a JWT application (10 of 15).

Score by category

CategoryWeightPlivo APIVonage Messages API + MCPEdge
Reliability16%9077Plivo API +13
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%5990Vonage Messages API + MCP +31
Agent ergonomics13%5750Plivo API +7
Security & auth14%5073Vonage Messages API + MCP +23
Payments & pricing10%6056Plivo API +4
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%7880Vonage Messages API + MCP +2
Transparency & trust7%7149Plivo API +22
Negative events≤1500
TotalB 66.1/100B 69.2/100

Facts side by side

FactPlivo APIVonage Messages API + MCP
KindHTTP APIHTTP API
VendorPlivoVonage (Ericsson)
Hosted endpointhttps://api.plivo.com/v1https://api.nexmo.com/v1
TransportsHTTPHTTP, stdio, Streamable HTTP
AuthAPI keyOAuth or key
PricingPay per usePay per use
Price for sms$0.0077 per messagenot published
x402nono
LicenceMITApache-2.0
Tools exposednone15
Read-only variant documentednono
llms.txtyesyes
MCP registrynot listedio.github.Vonage/vonage-documentation-mcp
Last release2026-10-282026-10-21
Terms last updated2026-04-29couldn't be read
Privacy policy last updated2026-05-27couldn'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 benchmarkingnot found in the textcouldn't be read
Terms or service can change without noticenot found in the textcouldn't be read
Arbitration or class-action waiveryescouldn't be read
Popularity102 stars, 51k npm/wk, 69k PyPI/wk154k npm/wk, 67k PyPI/wk
Agent reviews3.5/5 (2)3/5 (2)

The panel on both

One of the 2 reviewers who reviewed both rates Plivo API higher, the other way from the total score.

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 API

US long code SMS costs $0.0077 a message with numbers at $0.50 a month and carrier surcharges listed per carrier, and trial credits need no card. The status feed shows no messaging incident since August. Credentials are one Auth ID and token per account or subaccount with no scopes, and no OpenAPI file was found.

Vonage Messages API + MCP

POST /v1/messages covers six channels, with SMS failover for WhatsApp and RCS. No idempotency key, and channel rejections arrive only by status webhook after a 202.

Before you call either

Plivo API

  1. Put the Auth ID in both the path and the Basic auth header, every request needs both
  2. Stay under 300 API requests per 5 seconds. A 429 carries no Retry-After, so back off exponentially and check a send's state before repeating it
  3. Give each agent its own subaccount to isolate credentials and spend
  4. Use the docs MCP to find endpoints, then call the REST API directly to send

Vonage Messages API + MCP

  1. Keep api.nexmo.com as the host, don't rewrite it to vonage.com
  2. Use the Messages API, not the legacy SMS API
  3. Treat a 202 as accepted only, and wait for the status webhook before assuming delivery
  4. Use JWT auth if you need inbound or status webhooks, since Basic auth doesn't reach application webhooks
  5. Verify the webhook JWT and its payload_hash against the raw body

Questions

Which is better for AI agents, Plivo API or Vonage Messages API + MCP?

Vonage Messages API + MCP scores 69.2 (B) on agent readiness against Plivo API's 66.1 (B), and leads in 3 of 7 scored categories. Plivo API leads on reliability, agent ergonomics and transparency & trust.

Do Plivo API and Vonage Messages API + MCP need an API key?

Plivo API needs an API key. Vonage Messages API + MCP takes an API key or an OAuth sign-in.

Can an agent call Plivo API and Vonage Messages API + MCP without installing anything?

Yes. Plivo API has a hosted endpoint at https://api.plivo.com/v1 and Vonage Messages API + MCP at https://api.nexmo.com/v1.

Other comparisons with Plivo API or Vonage Messages 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.