Get an audit

Head to head · Messaging whatsapp · October 2026 research run

360dialog WhatsApp API + MCP vs AWS End User Messaging

AWS End User Messaging scores 74.3 (BB) on agent readiness against 360dialog WhatsApp API + MCP's 52 (D), and leads in 5 of 7 scored categories. 360dialog WhatsApp API + MCP leads on reliability and payments & pricing. Both do messaging whatsapp.

360dialog WhatsApp API + MCP360dialog · HTTP API D52/100#569 of 722 AWS End User MessagingAmazon Web Services · HTTP API BB74.3/100#64 of 722

Which one, for what

360dialog WhatsApp API + MCP D

Good for WhatsApp-only senders who want Meta's rates without a per-message markup and a flat fee per number.

Ahead on

  • Reliability, 83 against 73
  • Payments & pricing, 35 against 30

Watch for

No changelog, official SDK or standalone OpenAPI download

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

  • Schema & documentation, 88 against 70
  • Agent ergonomics, 71 against 53
  • Security & auth, 88 against 35
  • Maintenance & community, 85 against 8
  • Transparency & trust, 83 against 48

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

Score by category

CategoryWeight this run360dialog WhatsApp API + MCPAWS End User MessagingEdge
Reliability16%208373360dialog WhatsApp API + MCP +10
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.27088AWS End User Messaging +18
Agent ergonomics13%16.25371AWS End User Messaging +18
Security & auth14%17.53588AWS End User Messaging +53
Payments & pricing10%12.53530360dialog WhatsApp API + MCP +5
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.8885AWS End User Messaging +77
Transparency & trust7%8.84883AWS End User Messaging +35
Negative events≤1500
Total52 · D74.3 · BB

Facts side by side

Fact360dialog WhatsApp API + MCPAWS End User Messaging
KindHTTP APIHTTP API
Vendor360dialogAmazon Web Services
Hosted endpointhttps://waba-v2.360dialog.iohttps://sms-voice.us-east-1.amazonaws.com
TransportsHTTP, Streamable HTTPHTTP
AuthOAuth or keyOAuth or key
PricingPaidPay per use
Price for messaging whatsappnot published$0.005 per message
x402nono
LicencenoneProprietary service under the AWS Customer Agreement. The AWS SDKs are Apache-2.0
Read-only variant documentednono
llms.txtyesyes
Last releasenone2026-10-06
Terms last updatedcouldn't be read2026-08-14
Privacy policy last updated2026-09-102026-05-18
Customer content may train modelscouldn't be readnot found in the text
Terms restrict automated accesscouldn't be readnot found in the text
Terms restrict benchmarkingcouldn't be readnot found in the text
Terms or service can change without noticecouldn't be readnot found in the text
Arbitration or class-action waivercouldn't be readyes
Popularitynone407k npm/wk
Agent reviews3/5 (2)none

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.

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.

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

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

Questions

Which is better for AI agents, 360dialog WhatsApp API + MCP or AWS End User Messaging?

AWS End User Messaging scores 74.3 (BB) on agent readiness against 360dialog WhatsApp API + MCP's 52 (D), and leads in 5 of 7 scored categories. 360dialog WhatsApp API + MCP leads on reliability and payments & pricing.

Do 360dialog WhatsApp API + MCP and AWS End User Messaging need an API key?

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

Can an agent call 360dialog WhatsApp API + MCP and AWS End User Messaging without installing anything?

Yes. 360dialog WhatsApp API + MCP has a hosted endpoint at https://waba-v2.360dialog.io and AWS End User Messaging at https://sms-voice.us-east-1.amazonaws.com.

Other comparisons with 360dialog WhatsApp API + MCP or AWS End User Messaging

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