# AWS End User Messaging vs WhatsApp Business Platform (Cloud API)

> AWS End User Messaging scores 74.3 (BB) on agent readiness against WhatsApp Business Platform (Cloud API)'s 67.1 (B), and leads in 5 of 7 scored categories. WhatsApp Business Platform (Cloud API) leads on reliability and payments & pricing. Both do messaging whatsapp. Category…

- Canonical: https://www.anchorterminal.com/compare/aws-end-user-messaging-vs-whatsapp-cloud-api
- Markdown: https://www.anchorterminal.com/compare/aws-end-user-messaging-vs-whatsapp-cloud-api.md (~2,850 tokens)
- Slim: https://www.anchorterminal.com/compare/aws-end-user-messaging-vs-whatsapp-cloud-api.min.md (~780 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/aws-end-user-messaging-vs-whatsapp-cloud-api.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

AWS End User Messaging scores 74.3 (BB) on agent readiness against WhatsApp Business Platform (Cloud API)'s 67.1 (B), and leads in 5 of 7 scored categories. WhatsApp Business Platform (Cloud API) leads on reliability and payments & pricing. Both do messaging whatsapp.

- AWS End User Messaging: grade BB, 74.3/100, rank #64 of 722. Markdown https://www.anchorterminal.com/tools/aws-end-user-messaging.md · JSON https://www.anchorterminal.com/api/v1/tools/aws-end-user-messaging.json
- WhatsApp Business Platform (Cloud API): grade B, 67.1/100, rank #218 of 722. Markdown https://www.anchorterminal.com/tools/whatsapp-cloud-api.md · JSON https://www.anchorterminal.com/api/v1/tools/whatsapp-cloud-api.json

## 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:
- Schema & documentation, 88 against 82
- Security & auth, 88 against 67
- Maintenance & community, 85 against 34

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

### WhatsApp Business Platform (Cloud API) (B)

Good for: The direct route to WhatsApp for a business messaging its own customers, with no reseller fee.

Ahead on:
- Reliability, 80 against 73
- Payments & pricing, 40 against 30

Watch for: A person has to create a Meta account, a developer app, a business portfolio and a system user in a browser before any token exists


## Score by category

| Category | Weight | AWS End User Messaging | WhatsApp Business Platform (Cloud API) | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 73 | 80 | WhatsApp Business Platform (Cloud API) +7 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 88 | 82 | AWS End User Messaging +6 |
| Agent ergonomics | 13% (16.2 this run) | 71 | 67 | AWS End User Messaging +4 |
| Security & auth | 14% (17.5 this run) | 88 | 67 | AWS End User Messaging +21 |
| Payments & pricing | 10% (12.5 this run) | 30 | 40 | WhatsApp Business Platform (Cloud API) +10 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 85 | 34 | AWS End User Messaging +51 |
| Transparency & trust | 7% (8.8 this run) | 83 | 82 | AWS End User Messaging +1 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **74.3 · BB** | **67.1 · B** | |

## Facts side by side

| Fact | AWS End User Messaging | WhatsApp Business Platform (Cloud API) |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | Amazon Web Services | Meta Platforms, Inc. |
| Hosted endpoint | `https://sms-voice.us-east-1.amazonaws.com` | `https://graph.facebook.com` |
| Transports | HTTP | HTTP |
| Auth | OAuth or key | OAuth |
| Pricing | Pay per use | Pay per use |
| Price for messaging whatsapp | $0.005 per message | not published |
| x402 | no | no |
| Licence | Proprietary service under the AWS Customer Agreement. The AWS SDKs are Apache-2.0 | Proprietary service under the Meta Terms for WhatsApp Business Platform. The OpenAPI document in facebook/openapi is MIT |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-10-06 | 2026-08-11 |
| Terms last updated | 2026-08-14 | couldn't be read |
| Privacy policy last updated | 2026-05-18 | 2025-08-22 |
| 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 | 407k npm/wk | none |

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

**WhatsApp Business Platform (Cloud API).** The first-party WhatsApp API has a public OpenAPI document, Markdown docs with llms.txt, numeric rate limits and a test number that sends without a payment method. Setup needs a person in three Meta dashboards, no idempotency key was found for sends, and Meta's terms restrict general-purpose AI assistants on the platform.

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

### WhatsApp Business Platform (Cloud API)

1. Check when the user last wrote. Free-form messages are accepted only within 24 hours of the user's last message. After that, send an approved template.
2. Record the message id from each send and match it to `messages` webhook statuses. Many failures arrive only by webhook, and no idempotency key was found.
3. On error 130429 or 131056 wait and retry. Meta's guidance for the per-recipient limit is 4^X seconds, with X rising by one per failure.
4. Verify `X-Hub-Signature-256` with the app secret on every webhook, and deduplicate, because failed deliveries are retried for up to 7 days.
5. Request `health_status` on the phone number before a campaign to see whether the app, business, account, number and template can send.

## Questions

### Which is better for AI agents, AWS End User Messaging or WhatsApp Business Platform (Cloud API)?

AWS End User Messaging scores 74.3 (BB) on agent readiness against WhatsApp Business Platform (Cloud API)'s 67.1 (B), and leads in 5 of 7 scored categories. WhatsApp Business Platform (Cloud API) leads on reliability and payments & pricing.

### Do AWS End User Messaging and WhatsApp Business Platform (Cloud API) need an API key?

AWS End User Messaging takes an API key or an OAuth sign-in. WhatsApp Business Platform (Cloud API) uses an OAuth sign-in.

### Can an agent call AWS End User Messaging and WhatsApp Business Platform (Cloud API) without installing anything?

Yes. AWS End User Messaging has a hosted endpoint at https://sms-voice.us-east-1.amazonaws.com and WhatsApp Business Platform (Cloud API) at https://graph.facebook.com.


## For agents

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

## Other comparisons with AWS End User Messaging or WhatsApp Business Platform (Cloud API)

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