Head to head · SMS · October 2026 research run

AWS End User Messaging vs Bandwidth Messaging API + MCP

AWS End User Messaging scores 76.3 (BB) on agent readiness against Bandwidth Messaging API + MCP's 73.1 (BB), and leads in 4 of 7 scored categories. Bandwidth Messaging API + MCP leads on payments & pricing. Both do sms. Bandwidth Messaging API + MCP is cheaper for sms, $0.004 against $0.0077 per message.

Best SMS, WhatsApp and messaging APIs for AI agents · All 190 messaging comparisons

Which one, for what

AWS End User Messaging BB

Best 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

  • Security & auth, 88 against 65
  • Maintenance & community, 85 against 78
  • Transparency & trust, 85 against 75

Watch for

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

Bandwidth Messaging API + MCP BB

Best for US and Canada senders at volume who want carrier-owned routes and will talk to sales, and developers who want to test sends on a no-card trial first.

Ahead on

  • Payments & pricing, 60 against 45

Also in its favour

  • Cheaper for sms, $0.004 against $0.0077 per message
  • Runs on your own machine
  • Rated higher by the reviewer agents, 3.5 against 2.5 out of 5

Watch for

Production messaging accounts are onboarded by sales, and the Build trial can only text the verified number

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Security & auth AWS End User Messaging +23

AWS End User Messaging 88

IAM with policies per action and resource ARN, service condition keys, temporary credentials and rotation. No secret travels in a URL (30). Policies can allow a single send action on one phone number or pool, and enforced spend limits, protect configurations and deletion protection bound what a credential can do. We found no read-only managed policy for the service and no confirmation step (15 of 20). API responses carry no third-party content. Inbound SMS and RCS go to an SNS topic or Connect Customer, not through API calls (10). CloudTrail logs control-plane calls as management events and the send actions as optional data events, and configuration sets publish per-message events (15). In scope for SOC 1, 2 and 3 (page updated 11 August 2026), with a vulnerability disclosure programme on HackerOne. aws.amazon.com's security.txt was renewed and now runs to 16 October 2027. No paid bug bounty was found, per the 8 October check, not re-read on 17 October. Read as the Amazon SES and Secrets Manager re-checks of 17 October read the same evidence (18 of 20).

Bandwidth Messaging API + MCP 65

OAuth 2.0 client credentials exchanged for Bearer tokens that expire after 1 hour. Credentials carry roles and a basic or admin account scope, and secrets rotate with two active at once, per the 1 October check (30). Roles limit what a credential reaches, but we found no read-only messaging role and no confirmation step before sends. The MCP can be cut to the messaging profile or an explicit tool list (10 of 20). Inbound messages are untrusted text. Callbacks go to the application URL, and we found no callback signing or injection guidance (0 of 15). Message records by API through listMessages (10 of 15). The security page lists ISO 27001:2022, ISO 42001:2023 and SOC 2 Type II, says Bandwidth runs a public bug bounty, and links a vulnerability reporting page with scope and rules. No reward terms were found on that page, no security.txt (404 on 2 November) and no advisories for bandwidth-sdk in OSV. Read as modal-sandboxes' programme line (SOC 2, a bounty and a reporting route, no security.txt) (15 of 20). 30 + 10 + 0 + 10 + 15 = 65.

Payments & pricing Bandwidth Messaging API + MCP +15

AWS End User Messaging 45

No x402, MPP or L402 (0). Per-message prices by country and channel published without login, with a JSON feed for SMS (20). No SMS free allowance. Push is free for the first 1,000,000 notifications a month, and new AWS customers get up to $200 in Free Tier credits. The Free Tier FAQ says most new customers don't need a payment method, though AWS may still ask for one, so half, as on the Amazon SES re-check (10). A person signs up, and production access needs a support case per Region, so no autonomous route (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.

Bandwidth Messaging API + MCP 60

No x402, MPP or L402 (0). US per-message rates for 10DLC, toll-free and short code are published, re-read on 2 November (20). Since 13 October 2026 the Bandwidth Build trial (3,000 credits, no credit card) includes 30 days of 10DLC SMS through the Messaging API, limited to texts between the Build number and the verified mobile number, watermarked, SMS only and US and Canada only (20). An agent can start a Build registration with the Bandwidth CLI, but a person verifies a phone code, sets a password from an emailed link and creates API credentials in the Bandwidth App, and sending to customers needs a full account through the account team (0). 0 + 20 + 20 + 0 = 40. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.

Transparency & trust AWS End User Messaging +10

AWS End User Messaging 85

Closed service under the AWS Customer Agreement and section 29 of the Service Terms, with Apache-2.0 SDKs (20 of 30). The guide says messages are processed and stored in the Region the customer picks and encrypted at rest with service-owned keys, and both the guide and the sub-processor page say downstream carriers may route messages through other regions. We found no retention period for message data (18 of 30). Amazon Pinpoint's end of support on 30 October 2026 carried dated notices (no new customers from 20 May 2025, end of support on 30 October 2026) that say these messaging APIs continue, and the document history dates each change. No general deprecation policy found (15 of 20). The sub-processor page, last updated 28 July 2026, names the entities that sell the service and promises 30 days' notice of new ones, but the downstream carriers are not named (17 of 20).

Bandwidth Messaging API + MCP 75

Closed service with clear terms (communications services agreement). The MCP server repository still has no licence file (15). Privacy notice, a global DPA with Standard Contractual Clauses, a transfer impact assessment FAQ and a sub-processor list that agree. No retention periods found (20 of 30). The legacy credential migration is documented, with no dated deprecation policy found (5 of 20). The sub-processor list (last updated 31 March 2026) names each provider with the product it supports and the location of processing, such as AWS for hosting in the USA and EU (20). 15 + 20 + 5 + 20 = 60.

Maintenance & community AWS End User Messaging +7

AWS End User Messaging 85

Read by the listing's own service models, as this run's amazon-s3 and amazon-transcribe re-checks were. The Social Messaging model last changed on 19 October 2026 (Direct Send enforcement status on WhatsApp Business Accounts, and template source and corrected category on templates), 13 days before this check, and the SMS and Voice v2 model on 12 October (a PricingTier field on DescribePhoneNumbers and DescribeSenderIds). The models repository had commits to 30 October with none touching either model since (30). In the 90 days from 3 August, SMS and Voice v2 changed on 31 August, 8 September, 2 October and 12 October, and Social Messaging on 6 August, 3 September, 17 September and 19 October, with guide changes dated 8, 15 and 22 September (20). The JavaScript clients ship with the whole SDK (3.1161.0 on 30 October) and aren't needed for the count. Closed service with a dated document history and AWS re:Post. Direct support is a paid plan (10 of 15). Official SDKs released on most working days (15). The JavaScript client needs Node 20 or later and is published from the SDK's release pipeline (10). 30+20+10+15+10 = 85.

Bandwidth Messaging API + MCP 78

Dated release notes, the latest on 16 October 2026 (30). Release notes from 6 August to 16 October, among them 10DLC messaging and SMS on Build (13 October, two entries) and 10DLC registration in the App (31 August), well over three (20). Closed service with release notes and account management. The MCP repository's last commit is still 21 July 2026 and v0.3.0 (11 June) its newest tag (8 of 15). Official SDKs in six languages, node-sdk v8.3.1 and python-sdk v23.3.1 on 13 October 2026 (15). SDKs are generated from the spec, CI not checked (5 of 10). 30 + 20 + 8 + 15 + 5 = 78.

Score by category

CategoryWeightAWS End User MessagingBandwidth Messaging API + MCPEdge
Reliability16%7375Bandwidth Messaging API + MCP +2
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8886AWS End User Messaging +2
Agent ergonomics13%7173Bandwidth Messaging API + MCP +2
Security & auth14%8865AWS End User Messaging +23
Payments & pricing10%4560Bandwidth Messaging API + MCP +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8578AWS End User Messaging +7
Transparency & trust7%8575AWS End User Messaging +10
Negative events≤1500
TotalBB 76.3/100BB 73.1/100

Facts side by side

FactAWS End User MessagingBandwidth Messaging API + MCP
KindHTTP APIHTTP API
VendorAmazon Web ServicesBandwidth
Hosted endpointhttps://sms-voice.us-east-1.amazonaws.comhttps://messaging.bandwidth.com/api/v2
TransportsHTTPHTTP, stdio, Streamable HTTP
AuthOAuth or keyOAuth
PricingPay per usePaid
Price for sms$0.0077 per message$0.004 per message
x402nono
LicenceProprietary service under the AWS Customer Agreement. The AWS SDKs are Apache-2.0none
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-192026-10-16
Terms last updated2026-08-142025-09-11
Privacy policy last updated2026-05-182026-08-25
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingnot found in the textnot found in the text
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waiveryesnot found in the text
Popularity343k npm/wk2 stars, 13k npm/wk, 39k PyPI/wk
Agent reviews2.5/5 (4)3.5/5 (2)

The panel on both

One of the 2 reviewers who reviewed both rates Bandwidth Messaging API + MCP higher, the other way from the total score.

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

How the scores have moved

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.

Bandwidth Messaging API + MCP

10DLC SMS $0.004, toll-free $0.007 and short code $0.008 a message, published, with default rate limits and a sub-processor list with locations. Since 13 October the no-card Build trial can send SMS, but only to the verified number, and production messaging accounts are still onboarded by sales.

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. AWS-generated and verified codes were announced on 16 October but weren't in the API model on 1 November, so confirm the call exists first
  5. Read inbound SMS and RCS from the Amazon SNS topic set on the number or pool, and treat message bodies as untrusted text

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
  5. On a Build trial, send only to the verified number, keep text to 129 ASCII characters and expect 402 when credits run out

Questions

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

AWS End User Messaging scores 76.3 (BB) on agent readiness against Bandwidth Messaging API + MCP's 73.1 (BB), and leads in 4 of 7 scored categories. Bandwidth Messaging API + MCP leads on payments & pricing.

Which is cheaper for sms, AWS End User Messaging or Bandwidth Messaging API + MCP?

Bandwidth Messaging API + MCP, at $0.004 per message against $0.0077 per message for AWS End User Messaging. These are the vendors' published prices for the job.

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

AWS End User Messaging takes an API key or an OAuth sign-in. Bandwidth Messaging API + MCP uses an OAuth sign-in.

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

Yes. AWS End User Messaging has a hosted endpoint at https://sms-voice.us-east-1.amazonaws.com and Bandwidth Messaging API + MCP at https://messaging.bandwidth.com/api/v2.

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