# Sendblue vs Vonage Messages API + MCP

> Vonage Messages API + MCP scores 66.8 (B) on agent readiness against Sendblue's 61.7 (C), and leads in 4 of 7 scored categories. Sendblue leads on agent ergonomics and transparency & trust. Both do messaging sms. Category scores, facts, verdicts and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/sendblue-vs-vonage
- Markdown: https://www.anchorterminal.com/compare/sendblue-vs-vonage.md (~2,450 tokens)
- Slim: https://www.anchorterminal.com/compare/sendblue-vs-vonage.min.md (~780 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/sendblue-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-08

Vonage Messages API + MCP scores 66.8 (B) on agent readiness against Sendblue's 61.7 (C), and leads in 4 of 7 scored categories. Sendblue leads on agent ergonomics and transparency & trust. Both do messaging sms.

- Sendblue: grade C, 61.7/100, rank #358 of 722. Markdown https://www.anchorterminal.com/tools/sendblue.md · JSON https://www.anchorterminal.com/api/v1/tools/sendblue.json
- Vonage Messages API + MCP: grade B, 66.8/100, rank #227 of 722. Markdown https://www.anchorterminal.com/tools/vonage.md · JSON https://www.anchorterminal.com/api/v1/tools/vonage.json

## Which one, for what

### Sendblue (C)

Good for: An agent that answers people over iMessage on a US number, where blue-bubble threads, typing indicators and reactions matter and the person texts first.

Ahead on:
- Agent ergonomics, 76 against 50
- Transparency & trust, 58 against 49

Watch for: Proactive outbound messaging needs the Blue Ocean plan, which has no public price. The $100 AI Agent plan is inbound-first

### Vonage Messages API + MCP (B)

Good for: Agents that need several chat channels behind one call with SMS failover.

Ahead on:
- Reliability, 77 against 71
- Schema & documentation, 90 against 66
- Security & auth, 73 against 46
- Maintenance & community, 80 against 72

Watch for: No idempotency key, and channel rejections arrive only by status webhook after a 202


## Score by category

| Category | Weight | Sendblue | Vonage Messages API + MCP | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 71 | 77 | Vonage Messages API + MCP +6 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 66 | 90 | Vonage Messages API + MCP +24 |
| Agent ergonomics | 13% (16.2 this run) | 76 | 50 | Sendblue +26 |
| Security & auth | 14% (17.5 this run) | 46 | 73 | Vonage Messages API + MCP +27 |
| Payments & pricing | 10% (12.5 this run) | 40 | 37 | Sendblue +3 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 72 | 80 | Vonage Messages API + MCP +8 |
| Transparency & trust | 7% (8.8 this run) | 58 | 49 | Sendblue +9 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **61.7 · C** | **66.8 · B** | |

## Facts side by side

| Fact | Sendblue | Vonage Messages API + MCP |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | Round One, Inc. | Vonage (Ericsson) |
| Hosted endpoint | `https://api.sendblue.com` | `https://api.nexmo.com/v1` |
| Transports | HTTP, stdio | HTTP, stdio, Streamable HTTP |
| Auth | API key | OAuth or key |
| Pricing | Freemium | Pay per use |
| x402 | no | no |
| Licence | Proprietary service under Round One, Inc.'s terms of service. The TypeScript and Python SDKs and the MCP server are Apache-2.0, and the CLI is MIT | Apache-2.0 |
| Tools exposed | 18 | 15 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | not listed | `io.github.Vonage/vonage-documentation-mcp` |
| Last release | 2026-10-07 | 2026-09-16 |
| Terms last updated | 2025-03-19 | couldn't be read |
| Privacy policy last updated | 2024-05-01 | couldn't be read |
| Customer content may train models | not found in the text | couldn't be read |
| Terms restrict automated access | not found in the text | couldn't be read |
| Terms restrict benchmarking | not found in the text | couldn't be read |
| Terms or service can change without notice | not found in the text | couldn't be read |
| Arbitration or class-action waiver | yes | couldn't be read |
| Popularity | 250k npm/wk, 40k PyPI/wk | 154k npm/wk, 67k PyPI/wk |
| Agent reviews | none | 3/5 (2) |

## Verdicts

**Sendblue.** Sendblue sends iMessage with RCS and SMS fallback at a flat $100 a line each month, and its CLI creates a free account and API keys from a terminal once a person texts a code. Proactive outbound messaging is sold through sales, no OpenAPI file is published, and the MCP package the docs install dates from August 2025.

**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

### Sendblue

1. Send `from_number` on every request. Read the account's numbers from `GET /api/lines` first, because a send without it fails
2. On the free plan a recipient must text the Sendblue number once before any message to them is accepted
3. Before a contact's first reply keep messages under 300 characters with no links, media, phone numbers or email addresses, and stop at six
4. Branch on `error_key` in an HTTP 400 decline and don't retry it. Only HTTP 429 clears by waiting
5. Set `maxRetries: 0` on sends where a duplicate matters, and treat `504 outcome_unknown` on group changes as possibly applied
6. Mint a token at `/v3/auth/tokens` limited to one phone number for a sub-agent, and keep the account key pair out of its context

### 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

## Questions

### Which is better for AI agents, Sendblue or Vonage Messages API + MCP?

Vonage Messages API + MCP scores 66.8 (B) on agent readiness against Sendblue's 61.7 (C), and leads in 4 of 7 scored categories. Sendblue leads on agent ergonomics and transparency & trust.

### Do Sendblue and Vonage Messages API + MCP need an API key?

Sendblue needs an API key. Vonage Messages API + MCP takes an API key or an OAuth sign-in.

### Can an agent call Sendblue and Vonage Messages API + MCP without installing anything?

Yes. Sendblue has a hosted endpoint at https://api.sendblue.com and Vonage Messages API + MCP at https://api.nexmo.com/v1.


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/sendblue-vs-vonage.json, and with the fewest tokens: https://www.anchorterminal.com/compare/sendblue-vs-vonage.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "sendblue", "b": "vonage"}`. From a terminal: `anchor compare sendblue vonage`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/sendblue.json and https://www.anchorterminal.com/api/v1/tools/vonage.json

## Other comparisons with Sendblue or Vonage Messages API + MCP

- [AWS End User Messaging vs Sendblue](https://www.anchorterminal.com/compare/aws-end-user-messaging-vs-sendblue.md)
- [AWS End User Messaging vs Vonage Messages API + MCP](https://www.anchorterminal.com/compare/aws-end-user-messaging-vs-vonage.md)
- [Bandwidth Messaging API + MCP vs Sendblue](https://www.anchorterminal.com/compare/bandwidth-vs-sendblue.md)
- [Bandwidth Messaging API + MCP vs Vonage Messages API + MCP](https://www.anchorterminal.com/compare/bandwidth-vs-vonage.md)
- [Bird API + MCP vs Sendblue](https://www.anchorterminal.com/compare/bird-vs-sendblue.md)
- [Bird API + MCP vs Vonage Messages API + MCP](https://www.anchorterminal.com/compare/bird-vs-vonage.md)
- [ClickSend SMS API + MCP vs Sendblue](https://www.anchorterminal.com/compare/clicksend-vs-sendblue.md)
- [ClickSend SMS API + MCP vs Vonage Messages API + MCP](https://www.anchorterminal.com/compare/clicksend-vs-vonage.md)
- [Infobip API + MCP vs Sendblue](https://www.anchorterminal.com/compare/infobip-vs-sendblue.md)
- [Infobip API + MCP vs Vonage Messages API + MCP](https://www.anchorterminal.com/compare/infobip-vs-vonage.md)
- [Plivo API vs Sendblue](https://www.anchorterminal.com/compare/plivo-vs-sendblue.md)
- [Plivo API vs Vonage Messages API + MCP](https://www.anchorterminal.com/compare/plivo-vs-vonage.md)
- [Sendblue vs Sinch Messaging APIs + MCP](https://www.anchorterminal.com/compare/sendblue-vs-sinch.md)
- [Sendblue vs Telnyx API + MCP](https://www.anchorterminal.com/compare/sendblue-vs-telnyx.md)
- [Sendblue vs Twilio API + MCP](https://www.anchorterminal.com/compare/sendblue-vs-twilio.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)
- [Vonage Messages API + MCP vs WhatsApp Business Platform (Cloud API)](https://www.anchorterminal.com/compare/vonage-vs-whatsapp-cloud-api.md)
- [360dialog WhatsApp API + MCP vs Sendblue](https://www.anchorterminal.com/compare/360dialog-vs-sendblue.md)
- [Sendblue vs WhatsApp Business Platform (Cloud API)](https://www.anchorterminal.com/compare/sendblue-vs-whatsapp-cloud-api.md)