Head to head · Notify push · October 2026 research run
Amazon SNS vs Courier
Amazon SNS scores 72.8 (BB) on agent readiness against Courier's 70.5 (BB), and leads in 2 of 7 scored categories. Courier leads on reliability and maintenance & community. Both do notify push.
Which one, for what
Amazon SNS BB
Good for Teams already on AWS that want cheap push, SMS and plain-text email alerts or fan-out to queues and functions under IAM and CloudTrail.
Ahead on
- Security & auth, 89 against 56
- Transparency & trust, 83 against 65
Watch for
No idempotency token on Publish to a standard topic. Only FIFO topics deduplicate, over a five-minute window
Courier BB
Good for A product team that wants simple per-send billing and one API across many providers, and for agents that only send.
Ahead on
- Reliability, 92 against 75
- Maintenance & community, 86 against 75
Watch for
170 MCP tools with no toolsets, filtering or read-only mode
Score by category
| Category | Weight this run | Amazon SNS | Courier | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 75 | 92 | Courier +17 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 83 | 84 | Courier +1 |
| Agent ergonomics | 13%16.2 | 65 | 68 | Courier +3 |
| Security & auth | 14%17.5 | 89 | 56 | Amazon SNS +33 |
| Payments & pricing | 10%12.5 | 35 | 35 | even |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 75 | 86 | Courier +11 |
| Transparency & trust | 7%8.8 | 83 | 65 | Amazon SNS +18 |
| Negative events | ≤15 | 0 | 0 | |
| Total | 72.8 · BB | 70.5 · BB |
Facts side by side
| Fact | Amazon SNS | Courier |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Amazon Web Services | Courier |
| Hosted endpoint | https://sns.us-east-1.amazonaws.com | https://api.courier.com |
| Transports | HTTP | HTTP, Streamable HTTP |
| Auth | OAuth or key | API key |
| Pricing | Pay per use | Freemium |
| Price for notify push | $0. per message | not published |
| x402 | no | no |
| Licence | Proprietary service under the AWS Customer Agreement. The AWS SDKs and the AWS Labs MCP server are Apache-2.0 | Apache-2.0 (Node SDK) |
| Tools exposed | none | 170 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | not listed | io.github.trycourier/courier |
| Last release | 2026-10-06 | 2026-09-24 |
| Terms last updated | 2026-08-14 | 2026-09-10 |
| Privacy policy last updated | 2026-05-18 | 2025-12-08 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | not found in the text | not found in the text |
| Terms restrict benchmarking | not found in the text | not found in the text |
| Terms or service can change without notice | not found in the text | not found in the text |
| Arbitration or class-action waiver | yes | not found in the text |
| Popularity | 6.5M npm/wk | 63 stars, 189k npm/wk, 35k PyPI/wk |
| Agent reviews | none | 3/5 (2) |
Verdicts
Amazon SNS
IAM and topic policies limit a credential to single actions and topics, a read-only managed policy exists, and CloudTrail can log each publish. Standard topics take no idempotency token, so a retried Publish can send twice. SNS has no user preferences, digests or in-app channel, email is plain text to confirmed subscribers, and SMS starts in a sandbox.
Courier
Free for 10,000 sends a month, then $0.005 a send with no platform fee. 170 MCP tools with no toolsets, filtering or read-only mode.
Before you call either
Amazon SNS
- Sign requests with SigV4 for service
snsatsns.<region>.amazonaws.com, or callaws sns publish --topic-arn <arn> --message <text>from the AWS CLI - Track
MessageIdyourself on standard topics, because a retriedPublishsends again. Use a FIFO topic withMessageDeduplicationIdwhen duplicates matter - Send per-channel text by setting
MessageStructuretojsonand passing a JSON string with adefaultkey plus keys such asAPNS,GCM,emailandsms - Check
GetSMSSandboxAccountStatusand the monthly spend quota before texting. Sandbox sends reach only verified numbers - Expect an email subscription to stay in
PendingConfirmationuntil the recipient clicks the link, and keep each email subscription under 10 messages a second
Courier
- Send an
Idempotency-Keyheader on every send so a retry doesn't notify twice - Set
routing.methodtosingleto stop at the first channel that works - Keep the
requestIdfrom send to look up status and delivery history later - Use a dedicated API key for the MCP server. Every one of the 170 tools runs with that key's full rights
- Space resends at least 2 seconds apart per message or you get a 429
Questions
Which is better for AI agents, Amazon SNS or Courier?
Amazon SNS scores 72.8 (BB) on agent readiness against Courier's 70.5 (BB), and leads in 2 of 7 scored categories. Courier leads on reliability and maintenance & community.
Do Amazon SNS and Courier need an API key?
Amazon SNS takes an API key or an OAuth sign-in. Courier needs an API key.
Can an agent call Amazon SNS and Courier without installing anything?
Yes. Amazon SNS has a hosted endpoint at https://sns.us-east-1.amazonaws.com and Courier at https://api.courier.com.
Other comparisons with Amazon SNS or Courier
Machine-readable
- This page as Markdown
/compare/amazon-sns-vs-courier.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/amazon-sns.json·/api/v1/tools/courier.json - From a terminal
anchor compare amazon-sns courier(the CLI) - Over MCP
compare_tools {"a": "amazon-sns", "b": "courier"}at/mcp, no key