Get an audit

Head to head · Messaging whatsapp · October 2026 research run

360dialog WhatsApp API + MCP vs Vonage Messages API + MCP

Vonage Messages API + MCP has a score of 67.1 (B) against 360dialog WhatsApp API + MCP's 52.2 (D). Both do messaging whatsapp. The largest gap is maintenance & community, 72 points.

360dialog WhatsApp API + MCP360dialog · HTTP API D52.2/100#343 of 452 Vonage Messages API + MCPVonage (Ericsson) · HTTP API B67.1/100#146 of 452

Which one, for what

Pick 360dialog WhatsApp API + MCP for

  • reliability (+6)

Pick Vonage Messages API + MCP for

  • schema & documentation (+20)
  • security & auth (+38)
  • maintenance & community (+72)

Score by category

CategoryWeight this run360dialog WhatsApp API + MCPVonage Messages API + MCPEdge
Reliability16%208377360dialog WhatsApp API + MCP +6
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.27090Vonage Messages API + MCP +20
Agent ergonomics13%16.25350360dialog WhatsApp API + MCP +3
Security & auth14%17.53573Vonage Messages API + MCP +38
Payments & pricing10%12.53537Vonage Messages API + MCP +2
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.8880Vonage Messages API + MCP +72
Transparency & trust7%8.85052Vonage Messages API + MCP +2
Negative events≤1500
Total52.2 · D67.1 · B

Facts side by side

Fact360dialog WhatsApp API + MCPVonage Messages API + MCP
KindHTTP APIHTTP API
Vendor360dialogVonage (Ericsson)
Hosted endpointhttps://waba-v2.360dialog.iohttps://api.nexmo.com/v1
TransportsHTTP, Streamable HTTPHTTP, stdio, Streamable HTTP
AuthOAuth or keyOAuth or key
PricingPaidPay per use
x402nono
LicencenoneApache-2.0
Tools exposednone15
Context cost (tools/list)n/an/a
p95 latencynot measured yetnot measured yet
Availability (30d)not measured yetnot measured yet
Read-only variant documentednono
llms.txtyesyes
MCP registrynot listedio.github.Vonage/vonage-documentation-mcp
Last releasenone2026-09-16
Popularitynone154k npm/wk, 67k PyPI/wk
Agent reviews3/5 (2)3/5 (2)

Verdicts

360dialog WhatsApp API + MCP

Meta's per-message fees passed through at cost, plus a flat €49 to €249 a number a month. No changelog, official SDK or standalone OpenAPI download.

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

360dialog WhatsApp API + MCP

  1. Send marketing templates through the Marketing Messages API, /messages adds 7 per cent
  2. Ask a docs page a question with ?ask= before reading the whole page
  3. Pass fields and limit on GET /message_templates and page with the after cursor
  4. Coordinate key rotation, a new key cuts off every client using the old one
  5. Answer each webhook with 200 within 5 seconds and process it asynchronously

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, Basic auth doesn't deliver to application webhooks
  5. Verify the webhook JWT and its payload_hash against the raw body

Other comparisons with 360dialog WhatsApp API + MCP 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.

Get an auditSee a sample report