Get an audit

Head to head · Messaging sms · October 2026 research run

AWS End User Messaging vs Vonage Messages API + MCP

AWS End User Messaging scores 74.3 (BB) on agent readiness against Vonage Messages API + MCP's 66.8 (B), and leads in 4 of 7 scored categories. Vonage Messages API + MCP leads on payments & pricing. Both do messaging sms.

AWS End User MessagingAmazon Web Services · HTTP API BB74.3/100#64 of 722 Vonage Messages API + MCPVonage (Ericsson) · HTTP API B66.8/100#227 of 722

Which one, for what

AWS End User Messaging BB

Good for Teams already on AWS that want SMS, MMS, RCS and WhatsApp under IAM, CloudTrail and per-Region control at carrier-level prices.

Ahead on

  • Agent ergonomics, 71 against 50
  • Security & auth, 88 against 73
  • Maintenance & community, 85 against 80
  • Transparency & trust, 83 against 49

Also in its favour

  • Agent-ready, a grade of BB or better

Watch for

Sandbox limits new accounts to $1 of SMS a month and ten verified numbers until a support case per Region is approved

Vonage Messages API + MCP B

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

Ahead on

  • Payments & pricing, 37 against 30

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

Score by category

CategoryWeight this runAWS End User MessagingVonage Messages API + MCPEdge
Reliability16%207377Vonage Messages API + MCP +4
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28890Vonage Messages API + MCP +2
Agent ergonomics13%16.27150AWS End User Messaging +21
Security & auth14%17.58873AWS End User Messaging +15
Payments & pricing10%12.53037Vonage Messages API + MCP +7
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.88580AWS End User Messaging +5
Transparency & trust7%8.88349AWS End User Messaging +34
Negative events≤1500
Total74.3 · BB66.8 · B

Facts side by side

FactAWS End User MessagingVonage Messages API + MCP
KindHTTP APIHTTP API
VendorAmazon Web ServicesVonage (Ericsson)
Hosted endpointhttps://sms-voice.us-east-1.amazonaws.comhttps://api.nexmo.com/v1
TransportsHTTPHTTP, stdio, Streamable HTTP
AuthOAuth or keyOAuth or key
PricingPay per usePay per use
Price for messaging sms$0.0077 per messagenot published
x402nono
LicenceProprietary service under the AWS Customer Agreement. The AWS SDKs are Apache-2.0Apache-2.0
Tools exposednone15
Read-only variant documentednono
llms.txtyesyes
MCP registrynot listedio.github.Vonage/vonage-documentation-mcp
Last release2026-10-062026-09-16
Terms last updated2026-08-14couldn't be read
Privacy policy last updated2026-05-18couldn't be read
Customer content may train modelsnot found in the textcouldn't be read
Terms restrict automated accessnot found in the textcouldn't be read
Terms restrict benchmarkingnot found in the textcouldn't be read
Terms or service can change without noticenot found in the textcouldn't be read
Arbitration or class-action waiveryescouldn't be read
Popularity407k npm/wk154k npm/wk, 67k PyPI/wk
Agent reviewsnone3/5 (2)

Verdicts

AWS End User Messaging

IAM policies limit a credential to single actions and resources, CloudTrail can log every send, and enforced monthly spend limits cap cost. New accounts start in a sandbox with a $1 monthly SMS limit and ten verified recipients, production access needs a support case per Region, and the send actions take no idempotency token.

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

AWS End User Messaging

  1. Sign requests with SigV4 for service sms-voice at sms-voice.<region>.amazonaws.com. WhatsApp uses a separate API, social-messaging
  2. Check sandbox status and spend limits with describe-spend-limits before sending. Sandbox sends reach only verified destination numbers
  3. Pass DryRun on SendTextMessage to validate a request without sending, and track MessageId yourself because sends take no idempotency token
  4. Use Notify (SendNotifyTextMessage) for one-time passcodes without owning a number. Generate and check the code in your own application
  5. Read inbound SMS and RCS from the Amazon SNS topic set on the number or pool, and treat message bodies as untrusted text

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, AWS End User Messaging or Vonage Messages API + MCP?

AWS End User Messaging scores 74.3 (BB) on agent readiness against Vonage Messages API + MCP's 66.8 (B), and leads in 4 of 7 scored categories. Vonage Messages API + MCP leads on payments & pricing.

Do AWS End User Messaging and Vonage Messages API + MCP need an API key?

Both take an API key or an OAuth sign-in.

Can an agent call AWS End User Messaging and Vonage Messages API + MCP without installing anything?

Yes. AWS End User Messaging has a hosted endpoint at https://sms-voice.us-east-1.amazonaws.com and Vonage Messages API + MCP at https://api.nexmo.com/v1.

Other comparisons with AWS End User Messaging 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