{ "data": { "a": { "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": 66.8, "grade": "B", "agentReady": false, "rank": 209, "ranked": true, "rankOf": 629, "categoryRank": 5, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 50, "maintenance": 80, "payments": 37, "reliability": 77, "schema": 90, "security": 73, "transparency": 49 }, "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.", "bestFor": "Agents that need several chat channels behind one call with SMS failover.", "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.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 66.8 } ], "editorialScores": { "ergonomics": 50, "maintenance": 80, "payments": 37, "reliability": 77, "schema": 90, "security": 73, "transparency": 28 }, "provenanceScore": 69 }, "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": 69 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/vonage.json", "live": { "slug": "vonage", "probe": { "target": "https://api.nexmo.com/v1", "method": "get", "lastAt": "2026-10-08T19:09:02.122830972Z", "lastOk": true, "lastStatus": 404, "lastMs": 38, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 24, "p95ms24h": 64, "samples24h": 272, "samples30d": 2135, "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": 272, "ok": 272 }, { "date": "2026-10-05", "probes": 272, "ok": 272 }, { "date": "2026-10-06", "probes": 272, "ok": 272 }, { "date": "2026-10-07", "probes": 272, "ok": 272 }, { "date": "2026-10-08", "probes": 217, "ok": 217 } ] }, "vendorStatus": { "page": "https://vonageapi.statuspage.io", "indicator": "minor", "summary": "Partially Degraded Service", "checkedAt": "2026-10-08T19:07:04.034404547Z" }, "versions": [ { "registry": "github", "name": "Vonage-Community/vonage-mcp-server-api-bindings", "version": "v1.5.0", "released": "2026-05-21", "seenAt": "2026-10-08T16:34:38.629372145Z" }, { "registry": "mcp-registry", "name": "io.github.Vonage/vonage-documentation-mcp", "version": "1.0.0", "seenAt": "2026-10-08T02:42:52.272076636Z" }, { "registry": "npm", "name": "@vonage/server-sdk", "version": "3.30.1", "seenAt": "2026-10-08T16:34:34.591582249Z" }, { "registry": "npm", "name": "@vonage/vonage-mcp-server-api-bindings", "version": "1.5.1", "seenAt": "2026-10-08T16:34:36.752056116Z" }, { "registry": "pypi", "name": "vonage", "version": "4.9.0", "released": "2026-09-16", "seenAt": "2026-10-08T16:34:36.643960692Z" } ], "githubStars": 3, "npmWeekly": 151884, "pypiWeekly": 63193, "securityTxt": { "url": "https://vonage.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-10-08T15:38:38.377472768Z" }, "llmsTxt": { "url": "https://developer.vonage.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-10-08T14:01:01.755882378Z" }, "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": 200, "checkedAt": "2026-10-08T18:31:27.125076816Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "78c0a0681698" } ], "updatedAt": "2026-10-08T19:09:02.122830972Z" } }, "answer": "WhatsApp Business Platform (Cloud API) and Vonage Messages API + MCP score within a point of each other on agent readiness, 67.1 (B) and 66.8 (B). Vonage Messages API + MCP leads on schema \u0026 documentation, security \u0026 auth and maintenance \u0026 community.", "b": { "slug": "whatsapp-cloud-api", "name": "WhatsApp Business Platform (Cloud API)", "vendor": "Meta Platforms, Inc.", "vendorUrl": "https://developers.facebook.com", "kind": "http-api", "category": "messaging", "summary": "Meta's WhatsApp Business Platform Cloud API sends and receives WhatsApp messages for a business phone number through the Graph API, with inbound messages and status updates arriving by webhook. Access uses a Meta developer app and OAuth access tokens.", "url": "https://www.anchorterminal.com/tools/whatsapp-cloud-api", "markdownUrl": "https://www.anchorterminal.com/tools/whatsapp-cloud-api.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/whatsapp-cloud-api.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/whatsapp-cloud-api.json", "repo": "https://github.com/facebook/openapi", "license": "Proprietary service under the Meta Terms for WhatsApp Business Platform. The OpenAPI document in facebook/openapi is MIT", "transports": [ "http" ], "remoteUrl": "https://graph.facebook.com", "packages": [], "auth": "oauth", "authNotes": "Every call needs a Bearer access token from a Meta developer app with the WhatsApp use case. Access is self-serve for a business using its own account, with no App Review. A person creates the app, a business portfolio and a system user in Meta's dashboards, then generates a system user token with `whatsapp_business_messaging` and `whatsapp_business_management`. Apps that act for other businesses need Advanced access through App Review and onboard customers with Embedded Signup. Business verification raises the messaging limit above 250 recipients a day.", "pricing": "usage", "pricingNotes": "Charged per delivered message, by category (marketing, utility, authentication, service) and recipient country, with no platform or per-number fee found. Meta publishes rate cards as CSV and PDF in 16 currencies. We couldn't read the files, and the one rate we saw in prose is 0.68 US cents for a utility or authentication message to Brazil. Service messages are charged from 1 October 2026 per Meta's timeline. A test account and test number send without a payment method, so an agent can start without a contract (checked 2026-10-08).", "priceSummary": "Pay per use", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the WhatsApp documentation, the llms.txt indexes, the pricing pages or the OpenAPI document (checked 2026-10-08).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-08" }, "docsUrl": "https://developers.facebook.com/documentation/business-messaging/whatsapp/overview", "llmsTxt": "https://developers.facebook.com/documentation/business-messaging/whatsapp/llms.txt", "openapi": "https://raw.githubusercontent.com/facebook/openapi/main/business-messaging-api_v23.0.yaml", "capabilities": [ "messaging.whatsapp", "messaging.inbound" ], "tags": [ "hosted", "usage-based", "oauth", "openapi", "llms-txt", "webhooks", "whatsapp", "mcp", "sandbox", "status-page", "bug-bounty", "soc2" ], "lastRelease": "2026-08-11", "graded": true, "anchor": { "graded": true, "score": 67.1, "grade": "B", "agentReady": false, "rank": 201, "ranked": true, "rankOf": 629, "categoryRank": 4, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 67, "maintenance": 34, "payments": 40, "reliability": 80, "schema": 82, "security": 67, "transparency": 82 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-08" }, "negative": 0, "verdict": "The first-party WhatsApp API has a public OpenAPI document, Markdown docs with llms.txt, numeric rate limits and a test number that sends without a payment method. Setup needs a person in three Meta dashboards, no idempotency key was found for sends, and Meta's terms restrict general-purpose AI assistants on the platform.", "bestFor": "The direct route to WhatsApp for a business messaging its own customers, with no reseller fee.", "strengths": [ "A test WhatsApp Business account and test number are created with the app and send template messages with no payment method on file", "OpenAPI 3.1 document under MIT in facebook/openapi (78 paths, 113 operations), plus llms.txt indexes and a Markdown copy of each docs page", "Limits are published with numbers, including 80 messages a second per number, 5,000 requests an hour per active account and one message every 6 seconds per recipient", "Message data is kept for at most 30 days, with local storage and no-storage options per phone number, and SOC 2 Type II and ISO 27001 reports for Cloud API", "Webhook payloads are signed with HMAC-SHA256 in `X-Hub-Signature-256`, and mutual TLS is available" ], "weaknesses": [ "A person has to create a Meta account, a developer app, a business portfolio and a system user in a browser before any token exists", "No idempotency key for message sends was found in the reviewed documentation or the OpenAPI document, so a retried send can reach the user twice", "Meta's pricing page says the 15 January 2026 terms permit general-purpose AI assistants only where Meta is legally required to allow them", "Outside the 24-hour customer service window only pre-approved templates can be sent, and a new business portfolio is limited to 250 recipients in 24 hours", "Meta archived its Node.js SDK, and the published OpenAPI document is pinned to v23.0 while the Graph API is at v26.0" ], "agentNotes": [ "Check when the user last wrote. Free-form messages are accepted only within 24 hours of the user's last message. After that, send an approved template.", "Record the message id from each send and match it to `messages` webhook statuses. Many failures arrive only by webhook, and no idempotency key was found.", "On error 130429 or 131056 wait and retry. Meta's guidance for the per-recipient limit is 4^X seconds, with X rising by one per failure.", "Verify `X-Hub-Signature-256` with the app secret on every webhook, and deduplicate, because failed deliveries are retried for up to 7 days.", "Request `health_status` on the phone number before a campaign to see whether the app, business, account, number and template can send." ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 67.1 } ], "editorialScores": { "ergonomics": 67, "maintenance": 34, "payments": 40, "reliability": 80, "schema": 82, "security": 67, "transparency": 70 }, "provenanceScore": 94 }, "connect": { "http": "curl 'https://graph.facebook.com/v23.0/\u003cBUSINESS_PHONE_NUMBER_ID\u003e/messages' \\\n -H 'Content-Type: application/json' \\\n -H 'Authorization: Bearer \u003cSYSTEM_USER_ACCESS_TOKEN\u003e' \\\n -d '{\"messaging_product\":\"whatsapp\",\"recipient_type\":\"individual\",\"to\":\"\u003cWHATSAPP_USER_PHONE_NUMBER\u003e\",\"type\":\"text\",\"text\":{\"body\":\"Hello!\"}}'", "claudeCode": "claude mcp add --transport http whatsapp_business_tools https://mcp.facebook.com/whatsapp_business_tools" }, "letme": { "capability": "https://letme.dev/messaging.whatsapp", "tool": "https://letme.dev/whatsapp-cloud-api" }, "sameCompany": [ "meta-marketing-api" ], "area": "communication", "unitPrices": [ { "item": "Utility or authentication template, Brazil", "unit": "message", "usd": 0.0068, "note": "the one rate quoted in prose on Meta's non-template pricing page. Rates vary by country and category, and the rate card files weren't read" } ], "provenance": { "legalEntity": "Meta Platforms, Inc.", "domain": "facebook.com", "domainRegistered": "1997-03-29", "endpointOnVendorDomain": true, "terms": "https://www.facebook.com/legal/Meta-Terms-for-WhatsApp-Business-Platform", "privacy": "https://www.whatsapp.com/legal/business-data-processing-terms", "statusPage": "https://metastatus.com/whatsapp-business-api", "changelog": "https://developers.facebook.com/documentation/business-messaging/whatsapp/changelog", "securityTxt": "valid", "checked": "2026-10-08", "notes": [ "The API answers at graph.facebook.com and the MCP server at mcp.facebook.com, both facebook.com subdomains.", "www.whatsapp.com/legal/business-solution-terms and /legal/meta-terms-whatsapp-business both redirect to www.facebook.com/legal/Meta-Terms-for-WhatsApp-Business-Platform. That page and the Cloud API hosting terms at www.facebook.com/legal/WhatsApp-Business-Platform-Cloud-API render only with JavaScript, so their text wasn't read.", "The privacy field points at the WhatsApp Business Data Processing Terms (last updated 22 August 2025), which we read. Meta's docs name the Cloud API hosting terms as the other data document for Cloud API customers.", "The legal entity is taken from the copyright line of the MIT licence in facebook/openapi. The data processing terms name WhatsApp LLC and WhatsApp Ireland Limited as contracting entities.", "www.facebook.com/.well-known/security.txt and www.whatsapp.com/.well-known/security.txt name a contact, the bug bounty policy at bugbounty.meta.com and a disclosure policy, and expire on 7 November 2026.", "RDAP for facebook.com gives a registration date of 1997-03-29.", "The WhatsApp changelog's newest entry is 12 May 2026, and the one before it 8 December 2025." ], "score": 94 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/whatsapp-cloud-api.json", "live": { "slug": "whatsapp-cloud-api", "probe": { "target": "https://graph.facebook.com", "method": "get", "lastAt": "2026-10-08T19:09:02.278184818Z", "lastOk": true, "lastStatus": 400, "lastMs": 124, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 111, "p95ms24h": 124, "samples24h": 19, "samples30d": 19, "days": [ { "date": "2026-10-08", "probes": 19, "ok": 19 } ] }, "vendorStatus": { "page": "https://metastatus.com/whatsapp-business-api", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-10-08T17:51:19.274515472Z" }, "pages": [ { "url": "https://developers.facebook.com/documentation/business-messaging/whatsapp/changelog", "kind": "changelog", "status": 200, "checkedAt": "2026-10-08T18:17:37.55658412Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "c1607719e42e" }, { "url": "https://www.whatsapp.com/legal/business-data-processing-terms", "kind": "privacy", "status": 200, "checkedAt": "2026-10-08T18:31:35.269938621Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "3a883fb460c8" }, { "url": "https://www.facebook.com/legal/Meta-Terms-for-WhatsApp-Business-Platform", "kind": "terms", "status": 0, "checkedAt": "2026-10-08T18:27:43.250256264Z", "changedAt": "0001-01-01T00:00:00Z", "blockedByRobots": true } ], "updatedAt": "2026-10-08T19:09:02.278184818Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Vonage (Ericsson)", "b": "Meta Platforms, Inc.", "name": "Vendor" }, { "a": "https://api.nexmo.com/v1", "b": "https://graph.facebook.com", "name": "Hosted endpoint" }, { "a": "HTTP, stdio, Streamable HTTP", "b": "HTTP", "name": "Transports" }, { "a": "OAuth or key", "b": "OAuth", "name": "Auth" }, { "a": "Pay per use", "b": "Pay per use", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Apache-2.0", "b": "Proprietary service under the Meta Terms for WhatsApp Business Platform. The OpenAPI document in facebook/openapi is MIT", "name": "Licence" }, { "a": "15", "b": "none", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "io.github.Vonage/vonage-documentation-mcp", "b": "not listed", "name": "MCP registry" }, { "a": "2026-09-16", "b": "2026-08-11", "name": "Last release" }, { "a": "couldn't be read", "b": "couldn't be read", "name": "Terms last updated" }, { "a": "couldn't be read", "b": "2025-08-22", "name": "Privacy policy last updated" }, { "a": "couldn't be read", "b": "couldn't be read", "name": "Customer content may train models" }, { "a": "couldn't be read", "b": "couldn't be read", "name": "Terms restrict automated access" }, { "a": "couldn't be read", "b": "couldn't be read", "name": "Terms restrict benchmarking" }, { "a": "couldn't be read", "b": "couldn't be read", "name": "Terms or service can change without notice" }, { "a": "couldn't be read", "b": "couldn't be read", "name": "Arbitration or class-action waiver" }, { "a": "154k npm/wk, 67k PyPI/wk", "b": "none", "name": "Popularity" }, { "a": "3/5 (2)", "b": "none", "name": "Agent reviews" } ], "faq": [ { "answer": "WhatsApp Business Platform (Cloud API) and Vonage Messages API + MCP score within a point of each other on agent readiness, 67.1 (B) and 66.8 (B). Vonage Messages API + MCP leads on schema \u0026 documentation, security \u0026 auth and maintenance \u0026 community.", "question": "Which is better for AI agents, Vonage Messages API + MCP or WhatsApp Business Platform (Cloud API)?" }, { "answer": "Vonage Messages API + MCP takes an API key or an OAuth sign-in. WhatsApp Business Platform (Cloud API) uses an OAuth sign-in.", "question": "Do Vonage Messages API + MCP and WhatsApp Business Platform (Cloud API) need an API key?" }, { "answer": "Yes. Vonage Messages API + MCP has a hosted endpoint at https://api.nexmo.com/v1 and WhatsApp Business Platform (Cloud API) at https://graph.facebook.com.", "question": "Can an agent call Vonage Messages API + MCP and WhatsApp Business Platform (Cloud API) without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Schema \u0026 documentation, 90 against 82", "Security \u0026 auth, 73 against 67", "Maintenance \u0026 community, 80 against 34" ], "also": [ "Runs on your own machine", "Free to start without a card" ], "goodFor": "Agents that need several chat channels behind one call with SMS failover.", "slug": "vonage", "watchFor": "No idempotency key, and channel rejections arrive only by status webhook after a 202" }, { "aheadOn": [ "Agent ergonomics, 67 against 50", "Transparency \u0026 trust, 82 against 49" ], "also": null, "goodFor": "The direct route to WhatsApp for a business messaging its own customers, with no reseller fee.", "slug": "whatsapp-cloud-api", "watchFor": "A person has to create a Meta account, a developer app, a business portfolio and a system user in a browser before any token exists" } ], "job": { "capability": "messaging.whatsapp", "name": "Messaging whatsapp" }, "others": [ { "json": "https://www.anchorterminal.com/compare/bandwidth-vs-vonage.json", "title": "Bandwidth Messaging API + MCP vs Vonage Messages API + MCP", "url": "https://www.anchorterminal.com/compare/bandwidth-vs-vonage" }, { "json": "https://www.anchorterminal.com/compare/bird-vs-vonage.json", "title": "Bird API + MCP vs Vonage Messages API + MCP", "url": "https://www.anchorterminal.com/compare/bird-vs-vonage" }, { "json": "https://www.anchorterminal.com/compare/clicksend-vs-vonage.json", "title": "ClickSend SMS API + MCP vs Vonage Messages API + MCP", "url": "https://www.anchorterminal.com/compare/clicksend-vs-vonage" }, { "json": "https://www.anchorterminal.com/compare/infobip-vs-vonage.json", "title": "Infobip API + MCP vs Vonage Messages API + MCP", "url": "https://www.anchorterminal.com/compare/infobip-vs-vonage" }, { "json": "https://www.anchorterminal.com/compare/plivo-vs-vonage.json", "title": "Plivo API vs Vonage Messages API + MCP", "url": "https://www.anchorterminal.com/compare/plivo-vs-vonage" }, { "json": "https://www.anchorterminal.com/compare/sinch-vs-vonage.json", "title": "Sinch Messaging APIs + MCP vs Vonage Messages API + MCP", "url": "https://www.anchorterminal.com/compare/sinch-vs-vonage" }, { "json": "https://www.anchorterminal.com/compare/telnyx-vs-vonage.json", "title": "Telnyx API + MCP vs Vonage Messages API + MCP", "url": "https://www.anchorterminal.com/compare/telnyx-vs-vonage" }, { "json": "https://www.anchorterminal.com/compare/twilio-vs-vonage.json", "title": "Twilio API + MCP vs Vonage Messages API + MCP", "url": "https://www.anchorterminal.com/compare/twilio-vs-vonage" }, { "json": "https://www.anchorterminal.com/compare/360dialog-vs-vonage.json", "title": "360dialog WhatsApp API + MCP vs Vonage Messages API + MCP", "url": "https://www.anchorterminal.com/compare/360dialog-vs-vonage" }, { "json": "https://www.anchorterminal.com/compare/360dialog-vs-whatsapp-cloud-api.json", "title": "360dialog WhatsApp API + MCP vs WhatsApp Business Platform (Cloud API)", "url": "https://www.anchorterminal.com/compare/360dialog-vs-whatsapp-cloud-api" }, { "json": "https://www.anchorterminal.com/compare/bird-vs-whatsapp-cloud-api.json", "title": "Bird API + MCP vs WhatsApp Business Platform (Cloud API)", "url": "https://www.anchorterminal.com/compare/bird-vs-whatsapp-cloud-api" }, { "json": "https://www.anchorterminal.com/compare/infobip-vs-whatsapp-cloud-api.json", "title": "Infobip API + MCP vs WhatsApp Business Platform (Cloud API)", "url": "https://www.anchorterminal.com/compare/infobip-vs-whatsapp-cloud-api" }, { "json": "https://www.anchorterminal.com/compare/plivo-vs-whatsapp-cloud-api.json", "title": "Plivo API vs WhatsApp Business Platform (Cloud API)", "url": "https://www.anchorterminal.com/compare/plivo-vs-whatsapp-cloud-api" }, { "json": "https://www.anchorterminal.com/compare/sinch-vs-whatsapp-cloud-api.json", "title": "Sinch Messaging APIs + MCP vs WhatsApp Business Platform (Cloud API)", "url": "https://www.anchorterminal.com/compare/sinch-vs-whatsapp-cloud-api" }, { "json": "https://www.anchorterminal.com/compare/telnyx-vs-whatsapp-cloud-api.json", "title": "Telnyx API + MCP vs WhatsApp Business Platform (Cloud API)", "url": "https://www.anchorterminal.com/compare/telnyx-vs-whatsapp-cloud-api" }, { "json": "https://www.anchorterminal.com/compare/twilio-vs-whatsapp-cloud-api.json", "title": "Twilio API + MCP vs WhatsApp Business Platform (Cloud API)", "url": "https://www.anchorterminal.com/compare/twilio-vs-whatsapp-cloud-api" }, { "json": "https://www.anchorterminal.com/compare/bandwidth-vs-whatsapp-cloud-api.json", "title": "Bandwidth Messaging API + MCP vs WhatsApp Business Platform (Cloud API)", "url": "https://www.anchorterminal.com/compare/bandwidth-vs-whatsapp-cloud-api" }, { "json": "https://www.anchorterminal.com/compare/clicksend-vs-whatsapp-cloud-api.json", "title": "ClickSend SMS API + MCP vs WhatsApp Business Platform (Cloud API)", "url": "https://www.anchorterminal.com/compare/clicksend-vs-whatsapp-cloud-api" } ], "scores": [ { "by": 3, "edge": "whatsapp-cloud-api", "key": "reliability", "name": "Reliability", "vonage": 77, "weight": 16, "whatsapp-cloud-api": 80 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 8, "edge": "vonage", "key": "schema", "name": "Schema \u0026 documentation", "vonage": 90, "weight": 13, "whatsapp-cloud-api": 82 }, { "by": 17, "edge": "whatsapp-cloud-api", "key": "ergonomics", "name": "Agent ergonomics", "vonage": 50, "weight": 13, "whatsapp-cloud-api": 67 }, { "by": 6, "edge": "vonage", "key": "security", "name": "Security \u0026 auth", "vonage": 73, "weight": 14, "whatsapp-cloud-api": 67 }, { "by": 3, "edge": "whatsapp-cloud-api", "key": "payments", "name": "Payments \u0026 pricing", "vonage": 37, "weight": 10, "whatsapp-cloud-api": 40 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 46, "edge": "vonage", "key": "maintenance", "name": "Maintenance \u0026 community", "vonage": 80, "weight": 7, "whatsapp-cloud-api": 34 }, { "by": 33, "edge": "whatsapp-cloud-api", "key": "transparency", "name": "Transparency \u0026 trust", "vonage": 49, "weight": 7, "whatsapp-cloud-api": 82 } ], "summary": "WhatsApp Business Platform (Cloud API) and Vonage Messages API + MCP score within a point of each other on agent readiness, 67.1 (B) and 66.8 (B). Vonage Messages API + MCP leads on schema \u0026 documentation, security \u0026 auth and maintenance \u0026 community. Both do messaging whatsapp.", "verdicts": { "vonage": "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.", "whatsapp-cloud-api": "The first-party WhatsApp API has a public OpenAPI document, Markdown docs with llms.txt, numeric rate limits and a test number that sends without a payment method. Setup needs a person in three Meta dashboards, no idempotency key was found for sends, and Meta's terms restrict general-purpose AI assistants on the platform." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/vonage-vs-whatsapp-cloud-api", "json": "https://www.anchorterminal.com/compare/vonage-vs-whatsapp-cloud-api.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/vonage-vs-whatsapp-cloud-api.md", "slim": "https://www.anchorterminal.com/compare/vonage-vs-whatsapp-cloud-api.min.md" }, "markdown": "WhatsApp Business Platform (Cloud API) and Vonage Messages API + MCP score within a point of each other on agent readiness, 67.1 (B) and 66.8 (B). Vonage Messages API + MCP leads on schema \u0026 documentation, security \u0026 auth and maintenance \u0026 community. Both do messaging whatsapp.\n\n- Vonage Messages API + MCP: grade B, 66.8/100, rank #209 of 629. Markdown https://www.anchorterminal.com/tools/vonage.md · JSON https://www.anchorterminal.com/api/v1/tools/vonage.json\n- WhatsApp Business Platform (Cloud API): grade B, 67.1/100, rank #201 of 629. Markdown https://www.anchorterminal.com/tools/whatsapp-cloud-api.md · JSON https://www.anchorterminal.com/api/v1/tools/whatsapp-cloud-api.json\n\n## Which one, for what\n\n### Vonage Messages API + MCP (B)\n\nGood for: Agents that need several chat channels behind one call with SMS failover.\n\nAhead on:\n- Schema \u0026 documentation, 90 against 82\n- Security \u0026 auth, 73 against 67\n- Maintenance \u0026 community, 80 against 34\n\nAlso in its favour:\n- Runs on your own machine\n- Free to start without a card\n\nWatch for: No idempotency key, and channel rejections arrive only by status webhook after a 202\n\n### WhatsApp Business Platform (Cloud API) (B)\n\nGood for: The direct route to WhatsApp for a business messaging its own customers, with no reseller fee.\n\nAhead on:\n- Agent ergonomics, 67 against 50\n- Transparency \u0026 trust, 82 against 49\n\nWatch for: A person has to create a Meta account, a developer app, a business portfolio and a system user in a browser before any token exists\n\n\n## Score by category\n\n| Category | Weight | Vonage Messages API + MCP | WhatsApp Business Platform (Cloud API) | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 77 | 80 | WhatsApp Business Platform (Cloud API) +3 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 90 | 82 | Vonage Messages API + MCP +8 |\n| Agent ergonomics | 13% (16.2 this run) | 50 | 67 | WhatsApp Business Platform (Cloud API) +17 |\n| Security \u0026 auth | 14% (17.5 this run) | 73 | 67 | Vonage Messages API + MCP +6 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 37 | 40 | WhatsApp Business Platform (Cloud API) +3 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 80 | 34 | Vonage Messages API + MCP +46 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 49 | 82 | WhatsApp Business Platform (Cloud API) +33 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **66.8 · B** | **67.1 · B** | |\n\n## Facts side by side\n\n| Fact | Vonage Messages API + MCP | WhatsApp Business Platform (Cloud API) |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Vonage (Ericsson) | Meta Platforms, Inc. |\n| Hosted endpoint | `https://api.nexmo.com/v1` | `https://graph.facebook.com` |\n| Transports | HTTP, stdio, Streamable HTTP | HTTP |\n| Auth | OAuth or key | OAuth |\n| Pricing | Pay per use | Pay per use |\n| x402 | no | no |\n| Licence | Apache-2.0 | Proprietary service under the Meta Terms for WhatsApp Business Platform. The OpenAPI document in facebook/openapi is MIT |\n| Tools exposed | 15 | none |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| MCP registry | `io.github.Vonage/vonage-documentation-mcp` | not listed |\n| Last release | 2026-09-16 | 2026-08-11 |\n| Terms last updated | couldn't be read | couldn't be read |\n| Privacy policy last updated | couldn't be read | 2025-08-22 |\n| Customer content may train models | couldn't be read | couldn't be read |\n| Terms restrict automated access | couldn't be read | couldn't be read |\n| Terms restrict benchmarking | couldn't be read | couldn't be read |\n| Terms or service can change without notice | couldn't be read | couldn't be read |\n| Arbitration or class-action waiver | couldn't be read | couldn't be read |\n| Popularity | 154k npm/wk, 67k PyPI/wk | none |\n| Agent reviews | 3/5 (2) | none |\n\n## Verdicts\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**WhatsApp Business Platform (Cloud API).** The first-party WhatsApp API has a public OpenAPI document, Markdown docs with llms.txt, numeric rate limits and a test number that sends without a payment method. Setup needs a person in three Meta dashboards, no idempotency key was found for sends, and Meta's terms restrict general-purpose AI assistants on the platform.\n\n## Before you call either\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### WhatsApp Business Platform (Cloud API)\n\n1. Check when the user last wrote. Free-form messages are accepted only within 24 hours of the user's last message. After that, send an approved template.\n2. Record the message id from each send and match it to `messages` webhook statuses. Many failures arrive only by webhook, and no idempotency key was found.\n3. On error 130429 or 131056 wait and retry. Meta's guidance for the per-recipient limit is 4^X seconds, with X rising by one per failure.\n4. Verify `X-Hub-Signature-256` with the app secret on every webhook, and deduplicate, because failed deliveries are retried for up to 7 days.\n5. Request `health_status` on the phone number before a campaign to see whether the app, business, account, number and template can send.\n\n## Questions\n\n### Which is better for AI agents, Vonage Messages API + MCP or WhatsApp Business Platform (Cloud API)?\n\nWhatsApp Business Platform (Cloud API) and Vonage Messages API + MCP score within a point of each other on agent readiness, 67.1 (B) and 66.8 (B). Vonage Messages API + MCP leads on schema \u0026 documentation, security \u0026 auth and maintenance \u0026 community.\n\n### Do Vonage Messages API + MCP and WhatsApp Business Platform (Cloud API) need an API key?\n\nVonage Messages API + MCP takes an API key or an OAuth sign-in. WhatsApp Business Platform (Cloud API) uses an OAuth sign-in.\n\n### Can an agent call Vonage Messages API + MCP and WhatsApp Business Platform (Cloud API) without installing anything?\n\nYes. Vonage Messages API + MCP has a hosted endpoint at https://api.nexmo.com/v1 and WhatsApp Business Platform (Cloud API) at https://graph.facebook.com.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/vonage-vs-whatsapp-cloud-api.json, and with the fewest tokens: https://www.anchorterminal.com/compare/vonage-vs-whatsapp-cloud-api.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"vonage\", \"b\": \"whatsapp-cloud-api\"}`. From a terminal: `anchor compare vonage whatsapp-cloud-api`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/vonage.json and https://www.anchorterminal.com/api/v1/tools/whatsapp-cloud-api.json\n\n## Other comparisons with Vonage Messages API + MCP or WhatsApp Business Platform (Cloud API)\n\n- [Bandwidth Messaging API + MCP vs Vonage Messages API + MCP](https://www.anchorterminal.com/compare/bandwidth-vs-vonage.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 Vonage Messages API + MCP](https://www.anchorterminal.com/compare/clicksend-vs-vonage.md)\n- [Infobip API + MCP vs Vonage Messages API + MCP](https://www.anchorterminal.com/compare/infobip-vs-vonage.md)\n- [Plivo API vs Vonage Messages API + MCP](https://www.anchorterminal.com/compare/plivo-vs-vonage.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 Vonage Messages API + MCP](https://www.anchorterminal.com/compare/360dialog-vs-vonage.md)\n- [360dialog WhatsApp API + MCP vs WhatsApp Business Platform (Cloud API)](https://www.anchorterminal.com/compare/360dialog-vs-whatsapp-cloud-api.md)\n- [Bird API + MCP vs WhatsApp Business Platform (Cloud API)](https://www.anchorterminal.com/compare/bird-vs-whatsapp-cloud-api.md)\n- [Infobip API + MCP vs WhatsApp Business Platform (Cloud API)](https://www.anchorterminal.com/compare/infobip-vs-whatsapp-cloud-api.md)\n- [Plivo API vs WhatsApp Business Platform (Cloud API)](https://www.anchorterminal.com/compare/plivo-vs-whatsapp-cloud-api.md)\n- [Sinch Messaging APIs + MCP vs WhatsApp Business Platform (Cloud API)](https://www.anchorterminal.com/compare/sinch-vs-whatsapp-cloud-api.md)\n- [Telnyx API + MCP vs WhatsApp Business Platform (Cloud API)](https://www.anchorterminal.com/compare/telnyx-vs-whatsapp-cloud-api.md)\n- [Twilio API + MCP vs WhatsApp Business Platform (Cloud API)](https://www.anchorterminal.com/compare/twilio-vs-whatsapp-cloud-api.md)\n- [Bandwidth Messaging API + MCP vs WhatsApp Business Platform (Cloud API)](https://www.anchorterminal.com/compare/bandwidth-vs-whatsapp-cloud-api.md)\n- [ClickSend SMS API + MCP vs WhatsApp Business Platform (Cloud API)](https://www.anchorterminal.com/compare/clicksend-vs-whatsapp-cloud-api.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-10-08", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.4", "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": "Vonage Messages API + MCP vs WhatsApp Business Platform (Cloud API)", "url": "" } ], "description": "WhatsApp Business Platform (Cloud API) and Vonage Messages API + MCP score within a point of each other on agent readiness, 67.1 (B) and 66.8 (B). Vonage Messages API + MCP leads on schema \u0026 documentation, security \u0026 auth and maintenance \u0026 community. Both do messaging whatsapp.…", "facts": [ "Vonage Messages API + MCP B 66.8", "WhatsApp Business Platform (Cloud API) B 67.1", "scores" ], "h1": "Vonage Messages API + MCP vs WhatsApp Business Platform (Cloud API)", "image": "https://www.anchorterminal.com/assets/og/compare-vonage-vs-whatsapp-cloud-api.png", "path": "/compare/vonage-vs-whatsapp-cloud-api", "published": "2026-10-01", "section": "tools", "title": "Vonage Messages API + MCP vs WhatsApp Business Platform (Cloud API)", "toc": null, "updated": "2026-10-08", "url": "https://www.anchorterminal.com/compare/vonage-vs-whatsapp-cloud-api" }, "tokens": { "markdown": 2550, "slim": 680 }, "version": 1 }