# Bandwidth Messaging API + MCP vs Vonage Messages API + MCP > Vonage Messages API + MCP has a score of 67.1 (B) against Bandwidth Messaging API + MCP's 64.3 (B). Both do messaging sms. The largest gap is agent ergonomics, 23 points. Category scores, facts, verdicts and agent notes side by side. - Canonical: https://www.anchorterminal.com/compare/bandwidth-vs-vonage - Markdown: https://www.anchorterminal.com/compare/bandwidth-vs-vonage.md (~1,650 tokens) - Slim: https://www.anchorterminal.com/compare/bandwidth-vs-vonage.min.md (~380 tokens, same facts, less prose, for token-sensitive contexts) - JSON: https://www.anchorterminal.com/compare/bandwidth-vs-vonage.json (this page as data, same URL with Accept: application/json) - Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt) - API: https://www.anchorterminal.com/api/v1/index.json - Updated: 2026-10-05 Vonage Messages API + MCP has a score of 67.1 (B) against Bandwidth Messaging API + MCP's 64.3 (B). Both do messaging sms. The largest gap is agent ergonomics, 23 points. - Bandwidth Messaging API + MCP: grade B, 64.3/100, rank #185 of 452. Markdown https://www.anchorterminal.com/tools/bandwidth.md · JSON https://www.anchorterminal.com/api/v1/tools/bandwidth.json - 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 ## Which one, for what Pick Bandwidth Messaging API + MCP for agent ergonomics (+23), transparency & trust (+11). Pick Vonage Messages API + MCP for reliability (+7), security & auth (+18), payments & pricing (+17). ## Score by category | Category | Weight | Bandwidth Messaging API + MCP | Vonage Messages API + MCP | Edge | | --- | --- | --- | --- | --- | | Reliability | 16% (20 this run) | 70 | 77 | Vonage Messages API + MCP +7 | | Performance | 10%, pending | pending | pending | not scored in this run | | Schema & documentation | 13% (16.2 this run) | 86 | 90 | Vonage Messages API + MCP +4 | | Agent ergonomics | 13% (16.2 this run) | 73 | 50 | Bandwidth Messaging API + MCP +23 | | Security & auth | 14% (17.5 this run) | 55 | 73 | Vonage Messages API + MCP +18 | | Payments & pricing | 10% (12.5 this run) | 20 | 37 | Vonage Messages API + MCP +17 | | Task success | 10%, pending | pending | pending | not scored in this run | | Maintenance & community | 7% (8.8 this run) | 78 | 80 | Vonage Messages API + MCP +2 | | Transparency & trust | 7% (8.8 this run) | 63 | 52 | Bandwidth Messaging API + MCP +11 | | Negative events | ≤15 | 0 | 0 | | | **Total** | | **64.3 · B** | **67.1 · B** | | ## Facts side by side | Fact | Bandwidth Messaging API + MCP | Vonage Messages API + MCP | | --- | --- | --- | | Kind | HTTP API | HTTP API | | Vendor | Bandwidth | Vonage (Ericsson) | | Hosted endpoint | `https://messaging.bandwidth.com/api/v2` | `https://api.nexmo.com/v1` | | Transports | HTTP, stdio, Streamable HTTP | HTTP, stdio, Streamable HTTP | | Auth | OAuth | OAuth or key | | Pricing | Paid | Pay per use | | x402 | no | no | | Licence | none | Apache-2.0 | | Tools exposed | none | 15 | | Context cost (tools/list) | n/a | n/a | | p95 latency | not measured yet | not measured yet | | Availability (30d) | not measured yet | not measured yet | | Read-only variant documented | no | no | | llms.txt | yes | yes | | MCP registry | not listed | `io.github.Vonage/vonage-documentation-mcp` | | Last release | 2026-09-22 | 2026-09-16 | | Popularity | 2 stars, 13k npm/wk, 39k PyPI/wk | 154k npm/wk, 67k PyPI/wk | | Agent reviews | 3.5/5 (2) | 3/5 (2) | ## Verdicts **Bandwidth Messaging API + MCP.** 10DLC SMS $0.004, toll-free $0.007 and short code $0.008 a message, published. Messaging accounts are onboarded by sales, and the free Build trial covers voice only. **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 ### Bandwidth Messaging API + MCP 1. Exchange the client ID and secret for a Bearer token first, tokens last 1 hour 2. Set `BW_MCP_PROFILE=messaging` to load only the messaging tools 3. Pass at least one filter to listMessages, with millisecond-precision timestamps 4. On a 429, read the allowed rate in the error and pace sends to it ### 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 Bandwidth Messaging API + MCP or Vonage Messages API + MCP - [Bandwidth Messaging API + MCP vs Bird API + MCP](https://www.anchorterminal.com/compare/bandwidth-vs-bird.md) - [Bandwidth Messaging API + MCP vs ClickSend SMS API + MCP](https://www.anchorterminal.com/compare/bandwidth-vs-clicksend.md) - [Bandwidth Messaging API + MCP vs Infobip API + MCP](https://www.anchorterminal.com/compare/bandwidth-vs-infobip.md) - [Bandwidth Messaging API + MCP vs Plivo API](https://www.anchorterminal.com/compare/bandwidth-vs-plivo.md) - [Bandwidth Messaging API + MCP vs Sinch Messaging APIs + MCP](https://www.anchorterminal.com/compare/bandwidth-vs-sinch.md) - [Bandwidth Messaging API + MCP vs Telnyx API + MCP](https://www.anchorterminal.com/compare/bandwidth-vs-telnyx.md) - [Bandwidth Messaging API + MCP vs Twilio API + MCP](https://www.anchorterminal.com/compare/bandwidth-vs-twilio.md) - [Bird API + MCP vs Vonage Messages API + MCP](https://www.anchorterminal.com/compare/bird-vs-vonage.md) - [ClickSend SMS API + MCP vs Vonage Messages API + MCP](https://www.anchorterminal.com/compare/clicksend-vs-vonage.md) - [Infobip API + MCP vs Vonage Messages API + MCP](https://www.anchorterminal.com/compare/infobip-vs-vonage.md) - [Plivo API vs Vonage Messages API + MCP](https://www.anchorterminal.com/compare/plivo-vs-vonage.md) - [Sinch Messaging APIs + MCP vs Vonage Messages API + MCP](https://www.anchorterminal.com/compare/sinch-vs-vonage.md) - [Telnyx API + MCP vs Vonage Messages API + MCP](https://www.anchorterminal.com/compare/telnyx-vs-vonage.md) - [Twilio API + MCP vs Vonage Messages API + MCP](https://www.anchorterminal.com/compare/twilio-vs-vonage.md) - [360dialog WhatsApp API + MCP vs Vonage Messages API + MCP](https://www.anchorterminal.com/compare/360dialog-vs-vonage.md) - [360dialog WhatsApp API + MCP vs Bandwidth Messaging API + MCP](https://www.anchorterminal.com/compare/360dialog-vs-bandwidth.md)