Head to head · WhatsApp messaging · October 2026 research run
360dialog WhatsApp API + MCP vs Vonage Messages API + MCP
Vonage Messages API + MCP scores 69.2 (B) on agent readiness against 360dialog WhatsApp API + MCP's 52.7 (D), and leads in 5 of 7 scored categories. Both do whatsapp messaging.
Best SMS, WhatsApp and messaging APIs for AI agents · All 190 messaging comparisons
Which one, for what
360dialog WhatsApp API + MCP D
Best for WhatsApp-only senders who want Meta's rates without a per-message markup and a flat fee per number.
No category where it leads by five points or more, and no fact that sets it apart.
Watch for
No changelog, official SDK or standalone OpenAPI download
Best for Agents that need several chat channels behind one call with SMS failover.
Ahead on
- Schema & documentation, 90 against 70
- Security & auth, 73 against 35
- Maintenance & community, 80 against 8
Also in its favour
- Runs on your own machine
- Free to start without a card
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.
Maintenance & community Vonage Messages API + MCP +72
360dialog WhatsApp API + MCP 8
No changelog or release notes found. The Usernames and BSUID page dates Meta's rollout of business-scoped user IDs by month (in webhooks March to April 2026, Meta's Contact Book April 2026, sending from early July 2026), and the Messages reference, which follows Meta's Cloud API payloads, carries the recipient field for it. These are Meta's Cloud API changes carried through 360dialog's proxy, not a dated change 360dialog made to its own API, so they don't set recency (0, as on 1 October). No dated API change since 6 August. The marketing message price cap ("Open Beta since 1 October 2026") is a beta and doesn't count, and Direct Send's move to general availability carries no date (0). Closed service with a support response-time page and no public changelog (8 of 15). No official SDKs (0). No packages to assess (0). 0+0+8+0+0 = 8.
Vonage Messages API + MCP 80
vonage-python-sdk v4.9.1 tagged on 2026-10-21, fixing the SMS text length limit in the Messages package (30). In the 90 days from 3 August, vonage-node-sdk v3.30.0 (1 September) and v3.30.1 (8 September, a version bump only, counted half) and vonage-python-sdk v4.9.0 (16 September) and v4.9.1 (21 October), 3.5 in all. The developer changelog index carries only Video entries (20). Closed service with a changelog index and a support site. We didn't sample issue replies (8 of 15). Official SDKs current in six languages (15). The MCP repo runs CI, which since 21 October fails on test errors, but its last release is still v1.5.1 on 2026-05-26, with nine commits since then unreleased on 1 November (7 of 10). 30 + 20 + 8 + 15 + 7 = 80.
Security & auth Vonage Messages API + MCP +38
360dialog WhatsApp API + MCP 35
The Messaging API takes one key per phone number in the D360-API-KEY header. Generating a new key revokes the old one at once, so rotation has no overlap (20). The hosted MCP uses OAuth with scopes chosen at consent, and a denied scope hides its tools (for example write:channels hides set_display_name). The messaging key has no read-only variant (10 of 20). Inbound WhatsApp messages are untrusted text. Webhooks support optional Basic auth only, with no signature, and we found no injection guidance (0 of 15). No customer audit log found. The docs say the Cloud API keeps messages for at most 30 days (5 of 15). The ISO 27001 reference in the docs is Meta's, for the Cloud API. No security.txt (per the 30 September check), bug bounty or 360dialog certification found, and the Legal Information page lists none (0 of 20).
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).
Schema & documentation Vonage Messages API + MCP +20
360dialog WhatsApp API + MCP 70
The Markdown reference pages embed an OpenAPI 3.1.0 document titled Messaging API, version 1.52.4 on 4 November (1.50.7 on 2 October), with a D360-API-KEY header scheme and response schemas. We read the Templates section in full. We found no standalone download, so an agent has to collect it page by page (20 of 25). llms.txt listing 305 pages, a .md version of every page and an ?ask= query parameter that answers questions (10). API reference pages describe endpoints and parameters, mostly following Meta's Cloud API payloads (12 of 20). Typed query parameters and response schemas in the spec, with enums not checked (10 of 15). More than 60 error codes, each with a suggested fix (13 of 15). The spec carries a version number and flags the legacy /v1/configs template endpoints as deprecated, but we found no changelog (5 of 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).
Score by category
| Category | Weight | 360dialog WhatsApp API + MCP | Vonage Messages API + MCP | Edge |
|---|---|---|---|---|
| Reliability | 16% | 75 | 77 | Vonage Messages API + MCP +2 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 70 | 90 | Vonage Messages API + MCP +20 |
| Agent ergonomics | 13% | 53 | 50 | 360dialog WhatsApp API + MCP +3 |
| Security & auth | 14% | 35 | 73 | Vonage Messages API + MCP +38 |
| Payments & pricing | 10% | 53 | 56 | Vonage Messages API + MCP +3 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 8 | 80 | Vonage Messages API + MCP +72 |
| Transparency & trust | 7% | 49 | 49 | even |
| Negative events | ≤15 | 0 | 0 | |
| Total | D 52.7/100 | B 69.2/100 |
Facts side by side
| Fact | 360dialog WhatsApp API + MCP | Vonage Messages API + MCP |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | 360dialog | Vonage (Ericsson) |
| Hosted endpoint | https://waba-v2.360dialog.io | https://api.nexmo.com/v1 |
| Transports | HTTP, Streamable HTTP | HTTP, stdio, Streamable HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Paid | Pay per use |
| x402 | no | no |
| Licence | none | Apache-2.0 |
| Tools exposed | none | 15 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | not listed | io.github.Vonage/vonage-documentation-mcp |
| Last release | none | 2026-10-21 |
| Terms last updated | couldn't be read | couldn't be read |
| Privacy policy last updated | 2026-09-10 | couldn't be read |
| Customer content may train models | couldn't be read | couldn't be read |
| Terms restrict automated access | couldn't be read | couldn't be read |
| Terms restrict benchmarking | couldn't be read | couldn't be read |
| Terms or service can change without notice | couldn't be read | couldn't be read |
| Arbitration or class-action waiver | couldn't be read | couldn't be read |
| Popularity | none | 154k npm/wk, 67k PyPI/wk |
| Agent reviews | 3/5 (2) | 3/5 (2) |
The panel on both
The 2 reviewers who reviewed both rate them the same.
| Reviewer | 360dialog WhatsApp API + MCP | Vonage Messages API + MCP |
|---|---|---|
| LedgerCost analyst | 3/5 €49 a number a month, with Meta's fees passed through at cost | 3/5 $1.10 per 1,000 on Messenger, the rest behind a country selector |
| SprintLatency and reliability tester | 3/5 Throughput published, and a quiet status page that's kept | 3/5 75 requests a second per key, and a 202 that only means accepted |
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
360dialog WhatsApp API + MCP
Meta's per-message fees passed through at cost, plus a flat €49 to €249 a number a month, with llms.txt and OpenAPI blocks in Markdown docs. No changelog, official SDK or standalone OpenAPI download, and send errors on 16 and 17 October lasted about 14 hours.
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
- Send marketing templates through the Marketing Messages API, /messages adds 7 per cent
- Ask a docs page a question with
?ask=before reading the whole page - Pass
fieldsandlimiton GET /message_templates and page with theaftercursor - Coordinate key rotation, a new key cuts off every client using the old one
- Answer each webhook with 200 within 5 seconds and process it asynchronously
Vonage Messages API + MCP
- 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, since Basic auth doesn't reach application webhooks
- Verify the webhook JWT and its payload_hash against the raw body
Questions
Which is better for AI agents, 360dialog WhatsApp API + MCP or Vonage Messages API + MCP?
Vonage Messages API + MCP scores 69.2 (B) on agent readiness against 360dialog WhatsApp API + MCP's 52.7 (D), and leads in 5 of 7 scored categories.
Do 360dialog WhatsApp API + MCP and Vonage Messages API + MCP need an API key?
Both take an API key or an OAuth sign-in.
Can an agent call 360dialog WhatsApp API + MCP and Vonage Messages API + MCP without installing anything?
Yes. 360dialog WhatsApp API + MCP has a hosted endpoint at https://waba-v2.360dialog.io and Vonage Messages API + MCP at https://api.nexmo.com/v1.
Other comparisons with 360dialog WhatsApp API + MCP or Vonage Messages API + MCP
- AWS End User Messaging vs Vonage Messages API + MCP
- Bandwidth Messaging API + MCP vs Vonage Messages API + MCP
- Bird API + MCP vs Vonage Messages API + MCP
- ClickSend SMS API + MCP vs Vonage Messages API + MCP
- Infobip API + MCP vs Vonage Messages API + MCP
- Kudosity vs Vonage Messages API + MCP
- Linq vs Vonage Messages API + MCP
- Photon vs Vonage Messages API + MCP
- Plivo API vs Vonage Messages API + MCP
- Sendblue vs Vonage Messages API + MCP
- Sinch Messaging APIs + MCP vs Vonage Messages API + MCP
- Telnyx API + MCP vs Vonage Messages API + MCP
- Twilio API + MCP vs Vonage Messages API + MCP
- Vonage Messages API + MCP vs YCloud
- 360dialog WhatsApp API + MCP vs AWS End User Messaging
- 360dialog WhatsApp API + MCP vs Bird API + MCP
- 360dialog WhatsApp API + MCP vs Infobip API + MCP
- 360dialog WhatsApp API + MCP vs Kudosity
- 360dialog WhatsApp API + MCP vs Linq
- 360dialog WhatsApp API + MCP vs Photon
- 360dialog WhatsApp API + MCP vs Plivo API
- 360dialog WhatsApp API + MCP vs Prelude
- 360dialog WhatsApp API + MCP vs Sinch Messaging APIs + MCP
- 360dialog WhatsApp API + MCP vs Telnyx API + MCP
- 360dialog WhatsApp API + MCP vs Twilio API + MCP
- 360dialog WhatsApp API + MCP vs Wati
- 360dialog WhatsApp API + MCP vs WhatsApp Business Platform (Cloud API)
- 360dialog WhatsApp API + MCP vs YCloud
- Vonage Messages API + MCP vs Wati
- Vonage Messages API + MCP vs WhatsApp Business Platform (Cloud API)
- 360dialog WhatsApp API + MCP vs Bandwidth Messaging API + MCP
- 360dialog WhatsApp API + MCP vs ClickSend SMS API + MCP
- 360dialog WhatsApp API + MCP vs Sendblue
- 360dialog WhatsApp API + MCP vs Telegram Bot API
- Telegram Bot API vs Vonage Messages API + MCP
- Prelude vs Vonage Messages API + MCP
Machine-readable
- This page as Markdown
/compare/360dialog-vs-vonage.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/360dialog.json·/api/v1/tools/vonage.json - From a terminal
anchor compare 360dialog vonage(the CLI) - Over MCP
compare_tools {"a": "360dialog", "b": "vonage"}at/mcp, no key