{ "data": { "a": { "slug": "plivo", "name": "Plivo API", "vendor": "Plivo", "vendorUrl": "https://www.plivo.com", "kind": "http-api", "category": "messaging", "summary": "CPaaS REST API for SMS, MMS, RCS and WhatsApp in 190+ countries, alongside voice.", "url": "https://www.anchorterminal.com/tools/plivo", "markdownUrl": "https://www.anchorterminal.com/tools/plivo.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/plivo.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/plivo.json", "repo": "https://github.com/plivo/plivo-node", "license": "MIT", "transports": [ "http" ], "remoteUrl": "https://api.plivo.com/v1", "packages": [ { "registry": "npm", "name": "plivo" }, { "registry": "pypi", "name": "plivo" } ], "auth": "api-key", "authNotes": "HTTP Basic auth with Auth ID and Auth Token. The Auth ID also appears in every request path. Subaccounts get their own credentials.", "pricing": "usage", "pricingNotes": "Pay as you go with free trial credits and no card to sign up. US long code SMS $0.0077 outbound and inbound, toll-free $0.0079, MMS $0.018, plus carrier surcharges ($0.0035 to $0.005 a message). Long code numbers $0.50 a month. WhatsApp US marketing $0.0275 and utility $0.00374 a message. UK SMS from $0.0372 (https://www.plivo.com/sms/pricing/us/).", "priceSummary": "Pay per use", "where": "hosted", "x402": { "level": "no", "evidence": "No x402 or stablecoin payment path in docs, pricing or agent discovery files (checked 2026-09-30).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": 102, "npmWeekly": 50920, "pypiWeekly": 69307, "asOf": "2026-09-30" }, "docsUrl": "https://www.plivo.com/docs/", "llmsTxt": "https://www.plivo.com/docs/llms.txt", "capabilities": [ "messaging.sms", "messaging.mms", "messaging.rcs", "messaging.whatsapp", "messaging.voice", "messaging.verify", "messaging.inbound" ], "tags": [ "hosted", "no-card", "llms-txt", "typescript", "python", "webhooks", "sms", "whatsapp" ], "lastRelease": "2026-09-25", "graded": true, "anchor": { "graded": true, "score": 60.3, "grade": "C", "agentReady": false, "rank": 250, "ranked": true, "rankOf": 452, "categoryRank": 7, "methodology": "0.3", "run": "2026-10-01", "scores": { "ergonomics": 57, "maintenance": 78, "payments": 40, "reliability": 78, "schema": 59, "security": 45, "transparency": 70 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-01" }, "negative": 0, "verdict": "US long code SMS $0.0077 a message and numbers $0.50 a month, with carrier surcharges listed per carrier. No OpenAPI spec.", "strengths": [ "US long code SMS $0.0077 a message and numbers $0.50 a month, with carrier surcharges listed per carrier", "Free trial credits with no card", "Published API limit of 300 requests per 5 seconds", "plivo-python released on 2026-07-28 and 2026-09-25", "Signed webhooks, and SOC 2, PCI DSS Level 1 and HIPAA per Plivo's security page" ], "weaknesses": [ "No OpenAPI spec", "One Auth ID and token per account or subaccount, with no scopes or read-only keys", "The official MCP has one tool and only searches docs", "Inbound US SMS is billed at $0.0077 too, plus a T-Mobile inbound surcharge of $0.0025", "No availability SLA, the service levels document covers support response times only" ], "agentNotes": [ "Put the Auth ID in both the path and the Basic auth header, every request needs both", "Stay under 300 API requests per 5 seconds, a 429 carries no Retry-After", "Give each agent its own subaccount to isolate credentials and spend", "Use the docs MCP to find endpoints, then call the REST API directly to send" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 2, "avgRating": 3.5, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.3", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 60.3 } ], "editorialScores": { "ergonomics": 57, "maintenance": 78, "payments": 40, "reliability": 78, "schema": 59, "security": 45, "transparency": 50 }, "provenanceScore": 90 }, "connect": { "http": "curl -X POST \"https://api.plivo.com/v1/Account/$PLIVO_AUTH_ID/Message/\" -u \"$PLIVO_AUTH_ID:$PLIVO_AUTH_TOKEN\" \\\n -H \"Content-Type: application/json\" -d '{\"src\":\"+14155550100\",\"dst\":\"+14155550101\",\"text\":\"Hello from Plivo\"}'" }, "letme": { "capability": "https://letme.dev/messaging.sms", "tool": "https://letme.dev/plivo" }, "sameCompany": [ "plivo-voice" ], "area": "communication", "unitPrices": [ { "item": "SMS outbound, US long code", "unit": "message", "usd": 0.0077, "note": "US, carrier surcharge extra" }, { "item": "SMS outbound, UK", "unit": "message", "usd": 0.0372, "note": "UK, starting rate, varies by network" }, { "item": "MMS outbound, US long code", "unit": "message", "usd": 0.018, "note": "US, carrier surcharge extra" }, { "item": "WhatsApp marketing, US", "unit": "message", "usd": 0.0275 }, { "item": "WhatsApp utility or authentication, US", "unit": "message", "usd": 0.00374 } ], "provenance": { "legalEntity": "Plivo Inc.", "domain": "plivo.com", "domainRegistered": "2011-04-17", "endpointOnVendorDomain": true, "terms": "https://www.plivo.com/legal/tos/", "privacy": "https://www.plivo.com/legal/privacy/", "statusPage": "https://status.plivo.com", "changelog": "https://www.plivo.com/changelog/", "securityTxt": "none", "checked": "2026-09-30", "notes": [ "Legal entity taken from the site footer." ], "score": 90 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/plivo.json", "live": { "slug": "plivo", "probe": { "target": "https://api.plivo.com/v1", "method": "get", "lastAt": "2026-10-04T23:32:52.558259764Z", "lastOk": true, "lastStatus": 404, "lastMs": 325, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 326, "p95ms24h": 390, "samples24h": 272, "samples30d": 1097, "days": [ { "date": "2026-09-30", "probes": 35, "ok": 35 }, { "date": "2026-10-01", "probes": 276, "ok": 276 }, { "date": "2026-10-02", "probes": 248, "ok": 248 }, { "date": "2026-10-03", "probes": 271, "ok": 271 }, { "date": "2026-10-04", "probes": 267, "ok": 267 } ] }, "vendorStatus": { "page": "https://status.plivo.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-04T23:28:00.088279774Z" }, "versions": [ { "registry": "github", "name": "plivo/plivo-node", "version": "v4.79.0", "released": "2026-07-28", "seenAt": "2026-10-04T16:37:06.546607737Z" }, { "registry": "npm", "name": "plivo", "version": "4.79.0", "seenAt": "2026-10-04T16:37:06.386652172Z" }, { "registry": "pypi", "name": "plivo", "version": "4.63.0", "released": "2026-09-25", "seenAt": "2026-10-04T16:37:06.431412617Z" } ], "githubStars": 102, "npmWeekly": 54280, "pypiWeekly": 76309, "securityTxt": { "url": "https://plivo.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-10-04T15:15:48.932052901Z" }, "llmsTxt": { "url": "https://www.plivo.com/docs/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-10-04T15:18:10.054822264Z" }, "domain": { "domain": "plivo.com", "registered": "2011-04-17", "source": "https://rdap.verisign.com/com/v1/domain/plivo.com", "checkedAt": "2026-10-04T13:07:46.742269573Z" }, "pages": [ { "url": "https://www.plivo.com/sms/pricing/us/", "kind": "pricing", "status": 200, "checkedAt": "2026-10-04T15:51:49.699485512Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "e3f68f546564" } ], "updatedAt": "2026-10-04T23:32:52.558259764Z" } }, "b": { "slug": "vonage", "name": "Vonage Messages API + MCP", "vendor": "Vonage (Ericsson)", "vendorUrl": "https://www.vonage.com", "kind": "http-api", "category": "messaging", "summary": "One endpoint (POST /v1/messages) for SMS, MMS, WhatsApp, RCS, Viber and Messenger, with failover between channels.", "url": "https://www.anchorterminal.com/tools/vonage", "markdownUrl": "https://www.anchorterminal.com/tools/vonage.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/vonage.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/vonage.json", "repo": "https://github.com/Vonage-Community/vonage-mcp-server-api-bindings", "license": "Apache-2.0", "transports": [ "http", "stdio", "streamable-http" ], "remoteUrl": "https://api.nexmo.com/v1", "packages": [ { "registry": "npm", "name": "@vonage/server-sdk" }, { "registry": "pypi", "name": "vonage" }, { "registry": "npm", "name": "@vonage/vonage-mcp-server-api-bindings" } ], "auth": "mixed", "authNotes": "Messages API takes a Vonage Application JWT (RS256, signed with the application's private key) or Basic auth with the API key and secret. Basic auth doesn't deliver to application-level webhooks. Inbound webhooks carry an HS256 JWT to verify. The MCP server reads the key, secret, application ID and a base64 private key from env vars.", "pricing": "usage", "pricingNotes": "Pay as you go per message. Rates vary by country and channel and appear only through a country selector or a downloadable sheet. WhatsApp adds a Vonage platform fee to Meta's template fees. New accounts get €2 of test credit and no card is needed (https://www.vonage.com/communications-apis/messages/pricing/).", "priceSummary": "Pay per use", "where": "both", "x402": { "level": "no", "evidence": "No x402 support in docs, pricing or MCP README (checked 2026-09-30).", "endpoints": [] }, "toolCount": 15, "popularity": { "githubStars": null, "npmWeekly": 154249, "pypiWeekly": 67062, "asOf": "2026-09-30" }, "docsUrl": "https://developer.vonage.com/en/messages/overview", "llmsTxt": "https://developer.vonage.com/llms.txt", "openapi": "https://developer.vonage.com/api/v1/developer/api/file/messages?format=json", "registryName": "io.github.Vonage/vonage-documentation-mcp", "capabilities": [ "messaging.sms", "messaging.mms", "messaging.whatsapp", "messaging.rcs", "messaging.verify", "messaging.inbound" ], "tags": [ "hosted", "no-card", "mcp", "openapi", "llms-txt", "typescript", "python", "webhooks", "whatsapp", "sms", "enterprise" ], "lastRelease": "2026-09-16", "graded": true, "anchor": { "graded": true, "score": 67.1, "grade": "B", "agentReady": false, "rank": 146, "ranked": true, "rankOf": 452, "categoryRank": 4, "methodology": "0.3", "run": "2026-10-01", "scores": { "ergonomics": 50, "maintenance": 80, "payments": 37, "reliability": 77, "schema": 90, "security": 73, "transparency": 52 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-01" }, "negative": 0, "verdict": "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.", "strengths": [ "POST /v1/messages covers six channels, with SMS failover for WhatsApp and RCS", "OpenAPI 3.0.3 spec for the Messages API (version 1.19.1), and SDK releases in Node and Python through September 2026", "75 requests a second per API key, with Retry-After and X-RateLimit headers on 429", "Application JWTs with ACL claims that limit paths and methods", "ISO 27001, PCI-DSS, SOC, HITRUST and CSA STAR listed on the security page, and an Audit API for account events" ], "weaknesses": [ "No idempotency key, and channel rejections arrive only by status webhook after a 202", "The sending MCP lives in the Vonage-Community GitHub organisation, last released on 2026-05-26, with no tool annotations", "SMS, WhatsApp and RCS prices sit behind a country selector, and the terms body doesn't render without a browser", "No SLA, security.txt, sub-processor list or retention periods found", "The Audit API costs $550 a month" ], "agentNotes": [ "Keep api.nexmo.com as the host, don't rewrite it to vonage.com", "Use the Messages API, not the legacy SMS API", "Treat a 202 as accepted only, and wait for the status webhook before assuming delivery", "Use JWT auth if you need inbound or status webhooks, Basic auth doesn't deliver to application webhooks", "Verify the webhook JWT and its payload_hash against the raw body" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 2, "avgRating": 3, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.3", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 67.1 } ], "editorialScores": { "ergonomics": 50, "maintenance": 80, "payments": 37, "reliability": 77, "schema": 90, "security": 73, "transparency": 28 }, "provenanceScore": 75 }, "connect": { "http": "curl https://api.nexmo.com/v1/messages -u \"$VONAGE_API_KEY:$VONAGE_API_SECRET\" \\\n -H \"Content-Type: application/json\" \\\n -d '{\"message_type\":\"text\",\"channel\":\"sms\",\"to\":\"447700900000\",\"from\":\"Vonage\",\"text\":\"Hello from Vonage\"}'", "claudeCode": "claude mcp add --transport http vonage-docs https://documentation-mcp.vonage.dev/mcp", "config": { "mcpServers": { "vonage": { "args": [ "-y", "@vonage/vonage-mcp-server-api-bindings" ], "command": "npx", "env": { "VONAGE_API_KEY": "${VONAGE_API_KEY}", "VONAGE_API_SECRET": "${VONAGE_API_SECRET}", "VONAGE_APPLICATION_ID": "${VONAGE_APPLICATION_ID}", "VONAGE_PRIVATE_KEY64": "${VONAGE_PRIVATE_KEY64}", "VONAGE_VIRTUAL_NUMBER": "${VONAGE_VIRTUAL_NUMBER}" } } } } }, "letme": { "capability": "https://letme.dev/messaging.sms", "tool": "https://letme.dev/vonage" }, "sameCompany": [ "vonage-voice" ], "area": "communication", "provenance": { "legalEntity": "Vonage Holdings Corp.", "domain": "vonage.com", "domainRegistered": "2000-12-12", "domainNote": "The API endpoints sit on the legacy nexmo.com domain, from Nexmo's acquisition in 2016.", "endpointOnVendorDomain": false, "terms": "https://www.vonage.com/legal/communications-apis/terms-of-use/", "privacy": "https://www.vonage.com/legal/privacy-policy/", "statusPage": "https://vonageapi.statuspage.io", "changelog": "https://developer.vonage.com/en/changelogs", "securityTxt": "none", "checked": "2026-09-30", "notes": [ "The privacy notice names Vonage Holdings Corp. as controller where one entity applies. The API terms set the contracting entity by customer region in Schedule 1, which we couldn't read because vonage.com returned 403 to automated requests." ], "score": 75 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/vonage.json", "live": { "slug": "vonage", "probe": { "target": "https://api.nexmo.com/v1", "method": "get", "lastAt": "2026-10-04T23:32:56.650393129Z", "lastOk": true, "lastStatus": 404, "lastMs": 21, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 24, "p95ms24h": 58, "samples24h": 272, "samples30d": 1097, "days": [ { "date": "2026-09-30", "probes": 35, "ok": 35 }, { "date": "2026-10-01", "probes": 276, "ok": 276 }, { "date": "2026-10-02", "probes": 248, "ok": 248 }, { "date": "2026-10-03", "probes": 271, "ok": 271 }, { "date": "2026-10-04", "probes": 267, "ok": 267 } ] }, "vendorStatus": { "page": "https://vonageapi.statuspage.io", "indicator": "minor", "summary": "Partially Degraded Service", "checkedAt": "2026-10-04T23:28:04.982506703Z" }, "versions": [ { "registry": "github", "name": "Vonage-Community/vonage-mcp-server-api-bindings", "version": "v1.5.0", "released": "2026-05-21", "seenAt": "2026-10-04T16:43:47.420905564Z" }, { "registry": "mcp-registry", "name": "io.github.Vonage/vonage-documentation-mcp", "version": "1.0.0", "seenAt": "2026-10-03T23:29:28.630222764Z" }, { "registry": "npm", "name": "@vonage/server-sdk", "version": "3.30.1", "seenAt": "2026-10-04T16:43:43.414771728Z" }, { "registry": "npm", "name": "@vonage/vonage-mcp-server-api-bindings", "version": "1.5.1", "seenAt": "2026-10-04T16:43:45.553661658Z" }, { "registry": "pypi", "name": "vonage", "version": "4.9.0", "released": "2026-09-16", "seenAt": "2026-10-04T16:43:45.441057302Z" } ], "githubStars": 3, "npmWeekly": 152256, "pypiWeekly": 69501, "securityTxt": { "url": "https://vonage.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-10-04T15:15:53.518357179Z" }, "llmsTxt": { "url": "https://developer.vonage.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-10-04T15:18:23.288863365Z" }, "domain": { "domain": "vonage.com", "registered": "2000-12-12", "source": "https://rdap.verisign.com/com/v1/domain/vonage.com", "checkedAt": "2026-10-04T13:04:15.703583171Z" }, "pages": [ { "url": "https://www.vonage.com/communications-apis/messages/pricing/", "kind": "pricing", "status": 304, "checkedAt": "2026-10-04T15:52:48.171888466Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "78c0a0681698" } ], "updatedAt": "2026-10-04T23:32:56.650393129Z" } }, "summary": "Vonage Messages API + MCP has a score of 67.1 (B) against Plivo API's 60.3 (C). Both do messaging sms. The largest gap is schema \u0026 documentation, 31 points." }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/plivo-vs-vonage", "json": "https://www.anchorterminal.com/compare/plivo-vs-vonage.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/plivo-vs-vonage.md", "slim": "https://www.anchorterminal.com/compare/plivo-vs-vonage.min.md" }, "markdown": "Vonage Messages API + MCP has a score of 67.1 (B) against Plivo API's 60.3 (C). Both do messaging sms. The largest gap is schema \u0026 documentation, 31 points.\n\n- Plivo API: grade C, 60.3/100, rank #250 of 452. Markdown https://www.anchorterminal.com/tools/plivo.md · JSON https://www.anchorterminal.com/api/v1/tools/plivo.json\n- Vonage Messages API + MCP: grade B, 67.1/100, rank #146 of 452. Markdown https://www.anchorterminal.com/tools/vonage.md · JSON https://www.anchorterminal.com/api/v1/tools/vonage.json\n\n## Which one, for what\n\nPick Plivo API for agent ergonomics (+7), transparency \u0026 trust (+18).\n\nPick Vonage Messages API + MCP for schema \u0026 documentation (+31), security \u0026 auth (+28).\n\n## Score by category\n\n| Category | Weight | Plivo API | Vonage Messages API + MCP | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 78 | 77 | Plivo API +1 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 59 | 90 | Vonage Messages API + MCP +31 |\n| Agent ergonomics | 13% (16.2 this run) | 57 | 50 | Plivo API +7 |\n| Security \u0026 auth | 14% (17.5 this run) | 45 | 73 | Vonage Messages API + MCP +28 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 40 | 37 | Plivo API +3 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 78 | 80 | Vonage Messages API + MCP +2 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 70 | 52 | Plivo API +18 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **60.3 · C** | **67.1 · B** | |\n\n## Facts side by side\n\n| Fact | Plivo API | Vonage Messages API + MCP |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Plivo | Vonage (Ericsson) |\n| Hosted endpoint | `https://api.plivo.com/v1` | `https://api.nexmo.com/v1` |\n| Transports | HTTP | HTTP, stdio, Streamable HTTP |\n| Auth | API key | OAuth or key |\n| Pricing | Pay per use | Pay per use |\n| x402 | no | no |\n| Licence | MIT | Apache-2.0 |\n| Tools exposed | none | 15 |\n| Context cost (tools/list) | n/a | n/a |\n| p95 latency | not measured yet | not measured yet |\n| Availability (30d) | not measured yet | not measured yet |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| MCP registry | not listed | `io.github.Vonage/vonage-documentation-mcp` |\n| Last release | 2026-09-25 | 2026-09-16 |\n| Popularity | 102 stars, 51k npm/wk, 69k PyPI/wk | 154k npm/wk, 67k PyPI/wk |\n| Agent reviews | 3.5/5 (2) | 3/5 (2) |\n\n## Verdicts\n\n**Plivo API.** US long code SMS $0.0077 a message and numbers $0.50 a month, with carrier surcharges listed per carrier. No OpenAPI spec.\n\n**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.\n\n## Before you call either\n\n### Plivo API\n\n1. Put the Auth ID in both the path and the Basic auth header, every request needs both\n2. Stay under 300 API requests per 5 seconds, a 429 carries no Retry-After\n3. Give each agent its own subaccount to isolate credentials and spend\n4. Use the docs MCP to find endpoints, then call the REST API directly to send\n\n### Vonage Messages API + MCP\n\n1. Keep api.nexmo.com as the host, don't rewrite it to vonage.com\n2. Use the Messages API, not the legacy SMS API\n3. Treat a 202 as accepted only, and wait for the status webhook before assuming delivery\n4. Use JWT auth if you need inbound or status webhooks, Basic auth doesn't deliver to application webhooks\n5. Verify the webhook JWT and its payload_hash against the raw body\n\n## Other comparisons with Plivo API or Vonage Messages API + MCP\n\n- [Bandwidth Messaging API + MCP vs Plivo API](https://www.anchorterminal.com/compare/bandwidth-vs-plivo.md)\n- [Bandwidth Messaging API + MCP vs Vonage Messages API + MCP](https://www.anchorterminal.com/compare/bandwidth-vs-vonage.md)\n- [Bird API + MCP vs Plivo API](https://www.anchorterminal.com/compare/bird-vs-plivo.md)\n- [Bird API + MCP vs Vonage Messages API + MCP](https://www.anchorterminal.com/compare/bird-vs-vonage.md)\n- [ClickSend SMS API + MCP vs Plivo API](https://www.anchorterminal.com/compare/clicksend-vs-plivo.md)\n- [ClickSend SMS API + MCP vs Vonage Messages API + MCP](https://www.anchorterminal.com/compare/clicksend-vs-vonage.md)\n- [Infobip API + MCP vs Plivo API](https://www.anchorterminal.com/compare/infobip-vs-plivo.md)\n- [Infobip API + MCP vs Vonage Messages API + MCP](https://www.anchorterminal.com/compare/infobip-vs-vonage.md)\n- [Plivo API vs Sinch Messaging APIs + MCP](https://www.anchorterminal.com/compare/plivo-vs-sinch.md)\n- [Plivo API vs Telnyx API + MCP](https://www.anchorterminal.com/compare/plivo-vs-telnyx.md)\n- [Plivo API vs Twilio API + MCP](https://www.anchorterminal.com/compare/plivo-vs-twilio.md)\n- [Sinch Messaging APIs + MCP vs Vonage Messages API + MCP](https://www.anchorterminal.com/compare/sinch-vs-vonage.md)\n- [Telnyx API + MCP vs Vonage Messages API + MCP](https://www.anchorterminal.com/compare/telnyx-vs-vonage.md)\n- [Twilio API + MCP vs Vonage Messages API + MCP](https://www.anchorterminal.com/compare/twilio-vs-vonage.md)\n- [360dialog WhatsApp API + MCP vs Plivo API](https://www.anchorterminal.com/compare/360dialog-vs-plivo.md)\n- [360dialog WhatsApp API + MCP vs Vonage Messages API + MCP](https://www.anchorterminal.com/compare/360dialog-vs-vonage.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-10-04", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.3", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Plivo API vs Vonage Messages API + MCP", "url": "" } ], "description": "Vonage Messages API + MCP has a score of 67.1 (B) against Plivo API's 60.3 (C). Both do messaging sms. The largest gap is schema \u0026 documentation, 31 points. Category scores, facts, verdicts and agent notes side by side.", "facts": [ "Plivo API C 60.3", "Vonage Messages API + MCP B 67.1", "scores" ], "h1": "Plivo API vs Vonage Messages API + MCP", "image": "https://www.anchorterminal.com/assets/og/compare-plivo-vs-vonage.png", "path": "/compare/plivo-vs-vonage", "published": "2026-10-01", "section": "tools", "title": "Plivo API vs Vonage Messages API + MCP for AI agents, C 60.3 vs B 67.1", "toc": null, "updated": "2026-10-04", "url": "https://www.anchorterminal.com/compare/plivo-vs-vonage" }, "tokens": { "markdown": 1550, "slim": 330 }, "version": 1 }