{ "data": { "a": { "slug": "amazon-sns", "name": "Amazon SNS", "vendor": "Amazon Web Services", "vendorUrl": "https://aws.amazon.com/sns/", "kind": "http-api", "category": "notifications", "summary": "Amazon SNS is AWS's publish and subscribe messaging service. A message published to a topic, or directly to a device or phone number, goes out as mobile push, SMS, plain-text email, HTTPS calls or to SQS queues and Lambda functions.", "url": "https://www.anchorterminal.com/tools/amazon-sns", "markdownUrl": "https://www.anchorterminal.com/tools/amazon-sns.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/amazon-sns.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/amazon-sns.json", "repo": "https://github.com/aws/api-models-aws", "license": "Proprietary service under the AWS Customer Agreement. The AWS SDKs and the AWS Labs MCP server are Apache-2.0", "transports": [ "http" ], "remoteUrl": "https://sns.us-east-1.amazonaws.com", "packages": [ { "registry": "npm", "name": "@aws-sdk/client-sns" }, { "registry": "pypi", "name": "boto3" }, { "registry": "pypi", "name": "awslabs.amazon-sns-sqs-mcp-server" } ], "auth": "mixed", "authNotes": "Requests are signed with AWS Signature Version 4 using IAM credentials, long-lived access keys or temporary credentials from AWS STS. IAM identity policies and topic resource policies use the `sns` action prefix with topic ARNs and condition keys. Access is self-serve with an AWS account. SMS starts in a sandbox per account, and leaving it or raising the $1 monthly spend quota needs an AWS Support case. Mobile push needs a platform application holding credentials from Apple, Google or another push service.", "pricing": "usage", "pricingNotes": "Pay per request and per notification with no minimum. On standard topics in US East (N. Virginia), API requests cost $0.50 per million after 1,000,000 free each month, mobile push $0.50 per million after 1,000,000 free, email $2.00 per 100,000 after 1,000 free, and HTTP deliveries $0.60 per million after 100,000 free. Deliveries to SQS and Lambda are free. SMS is billed by AWS End User Messaging. New AWS customers get up to $200 in Free Tier credits, and AWS says most can sign up without a payment method (https://aws.amazon.com/sns/pricing/, https://aws.amazon.com/free/free-tier-faqs/).", "priceSummary": "$0.0005 / 1k req", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the developer guide index, the API model or the pricing page (checked 2026-10-08).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": 6505984, "pypiWeekly": null, "asOf": "2026-10-08" }, "docsUrl": "https://docs.aws.amazon.com/sns/latest/dg/welcome.html", "llmsTxt": "https://docs.aws.amazon.com/sns/latest/dg/llms.txt", "capabilities": [ "notify.push", "notify.multichannel", "messaging.sms" ], "tags": [ "hosted", "llms-txt", "typescript", "python", "push", "sms", "mcp", "enterprise" ], "lastRelease": "2026-10-06", "graded": true, "anchor": { "graded": true, "score": 72.8, "grade": "BB", "agentReady": true, "rank": 86, "ranked": true, "rankOf": 722, "categoryRank": 1, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 65, "maintenance": 75, "payments": 35, "reliability": 75, "schema": 83, "security": 89, "transparency": 83 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-08" }, "negative": 0, "verdict": "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.", "bestFor": "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.", "strengths": [ "IAM identity policies and topic resource policies per action and topic, temporary credentials, and an `AmazonSNSReadOnlyAccess` managed policy", "Published quotas of 30,000 published messages a second per account in US East (N. Virginia) and 300 in the smallest Regions", "First 1,000,000 API requests, 1,000,000 mobile push notifications and 1,000 emails each month are free on standard topics", "Smithy model published for all 42 operations, with llms.txt indexes and a Markdown twin of every guide and reference page", "99.9 per cent monthly uptime commitment per Region under the Amazon Messaging SLA, last updated 4 May 2022" ], "weaknesses": [ "No idempotency token on `Publish` to a standard topic. Only FIFO topics deduplicate, over a five-minute window", "No user preferences, digests, templates or in-app channel. Email is plain text and each address has to confirm its subscription", "SMS starts in a sandbox with ten verified numbers and a $1 monthly spend quota, raised through an AWS Support case", "Topic, subscription and endpoint settings travel as string maps and JSON inside strings, and the model has only four enumerated types", "The AWS Health Dashboard lists the service in the UAE and Bahrain Region disruptions open since March 2026" ], "agentNotes": [ "Sign requests with SigV4 for service `sns` at `sns.\u003cregion\u003e.amazonaws.com`, or call `aws sns publish --topic-arn \u003carn\u003e --message \u003ctext\u003e` from the AWS CLI", "Track `MessageId` yourself on standard topics, because a retried `Publish` sends again. Use a FIFO topic with `MessageDeduplicationId` when duplicates matter", "Send per-channel text by setting `MessageStructure` to `json` and passing a JSON string with a `default` key plus keys such as `APNS`, `GCM`, `email` and `sms`", "Check `GetSMSSandboxAccountStatus` and the monthly spend quota before texting. Sandbox sends reach only verified numbers", "Expect an email subscription to stay in `PendingConfirmation` until the recipient clicks the link, and keep each email subscription under 10 messages a second" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "BB", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 72.8 } ], "editorialScores": { "ergonomics": 65, "maintenance": 75, "payments": 35, "reliability": 75, "schema": 83, "security": 89, "transparency": 71 }, "provenanceScore": 95 }, "connect": { "config": { "mcpServers": { "awslabs.amazon-sns-sqs-mcp-server": { "args": [ "awslabs.amazon-sns-sqs-mcp-server@latest" ], "command": "uvx", "env": { "AWS_PROFILE": "your-aws-profile", "AWS_REGION": "us-east-1" } } } } }, "letme": { "capability": "https://letme.dev/notify.push", "tool": "https://letme.dev/amazon-sns" }, "sameCompany": [ "aws-end-user-messaging", "amazon-s3" ], "area": "everyday", "unitPrices": [ { "item": "API requests, standard topics", "unit": "1k-requests", "usd": 0.0005, "note": "US East (N. Virginia), after 1,000,000 free a month. Each 64 KB of payload counts as one request" }, { "item": "Publishes, FIFO topics", "unit": "1k-requests", "usd": 0.0003, "note": "US East (N. Virginia), plus $0.017 per GB of payload and $0.01 per million subscription messages" }, { "item": "Mobile push notification", "unit": "message", "usd": 5e-7, "note": "$0.50 per million after 1,000,000 free a month" }, { "item": "Email notification", "unit": "1k-emails", "usd": 0.02, "note": "$2.00 per 100,000 after 1,000 free a month" }, { "item": "HTTP or HTTPS notification", "unit": "message", "usd": 6e-7, "note": "$0.60 per million after 100,000 free a month" } ], "provenance": { "legalEntity": "Amazon Web Services, Inc.", "domain": "amazonaws.com", "domainRegistered": "2005-08-18", "endpointOnVendorDomain": true, "terms": "https://aws.amazon.com/agreement/", "privacy": "https://aws.amazon.com/privacy/", "statusPage": "https://health.aws.amazon.com/health/status", "changelog": "https://docs.aws.amazon.com/sns/latest/dg/sns-release-notes.html", "securityTxt": "expired", "checked": "2026-10-08", "notes": [ "The AWS Customer Agreement (last updated 14 August 2026) governs use of the service, with other AWS entities as contracting party by account country.", "Section 11 of the AWS Service Terms (last updated 1 October 2026) adds terms for Amazon SNS. It says AMCS LLC sells parts of the service in Japan and AMCS SG Private Limited in Singapore, and that fees apply even when delivery is blocked for reasons outside AWS's control (https://aws.amazon.com/service-terms/).", "The AWS Privacy Notice (last updated 18 May 2026) says it does not apply to content customers process with AWS services, which the agreement governs.", "https://aws.amazon.com/.well-known/security.txt carries Expires 2026-09-24T16:25:03Z, so it had expired on 8 October 2026.", "RDAP for amazonaws.com gives a registration date of 2005-08-18. The API answers at sns.\u003cregion\u003e.amazonaws.com, while product and legal pages sit on aws.amazon.com." ], "score": 95 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/amazon-sns.json", "live": { "slug": "amazon-sns", "probe": { "target": "https://sns.us-east-1.amazonaws.com", "method": "get", "lastAt": "2026-10-08T21:53:15.286448807Z", "lastOk": true, "lastStatus": 404, "lastMs": 251, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 252, "p95ms24h": 316, "samples24h": 28, "samples30d": 28, "days": [ { "date": "2026-10-08", "probes": 28, "ok": 28 } ] }, "updatedAt": "2026-10-08T21:53:15.286448807Z" } }, "answer": "Amazon SNS scores 72.8 (BB) on agent readiness against ntfy's 61.5 (C), and leads in 4 of 7 scored categories. ntfy leads on reliability and payments \u0026 pricing.", "b": { "slug": "ntfy", "name": "ntfy", "vendor": "ntfy", "vendorUrl": "https://ntfy.sh", "kind": "http-api", "category": "notifications", "summary": "Open-source publish-subscribe service for push notifications.", "url": "https://www.anchorterminal.com/tools/ntfy", "markdownUrl": "https://www.anchorterminal.com/tools/ntfy.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/ntfy.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/ntfy.json", "repo": "https://github.com/binwiederhier/ntfy", "license": "Apache-2.0 and GPL-2.0 (dual)", "transports": [ "http" ], "remoteUrl": "https://ntfy.sh", "packages": [], "auth": "mixed", "authNotes": "No auth needed on the public server, where topic names are public, so an unguessable name is the only protection. Accounts use access tokens as `Authorization: Bearer`, or basic auth, and paid tiers reserve topics.", "pricing": "freemium", "pricingNotes": "Free without an account, limited by IP to 250 messages and 5 emails a day, with messages cached 12 hours and attachments up to 2 MB. Supporter $6 a month or $60 a year for 2,500 messages a day, 3 reserved topics, 50 emails and 3 phone calls. Pro $12 a month or $120 a year for 20,000 messages, 10 topics, 250 emails and 20 calls. Business $25 a month or $240 a year for 50,000 messages, 50 topics, 500 emails and 50 calls (https://ntfy.sh/v1/tiers, https://ntfy.sh). Self-hosting is free (https://github.com/binwiederhier/ntfy).", "priceSummary": "$6 / mo", "where": "hosted", "x402": { "level": "no", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": 33500, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-09-30" }, "docsUrl": "https://docs.ntfy.sh", "capabilities": [ "notify.push" ], "tags": [ "hosted", "freemium", "free-tier", "no-key", "open-source", "self-hosted" ], "lastRelease": "2026-08-27", "graded": true, "anchor": { "graded": true, "score": 61.5, "grade": "C", "agentReady": false, "rank": 362, "ranked": true, "rankOf": 722, "categoryRank": 7, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 66, "maintenance": 67, "payments": 50, "reliability": 83, "schema": 53, "security": 38, "transparency": 78 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-01" }, "negative": 0, "verdict": "Publish with one HTTP POST and no account, up to 250 messages a day per IP on ntfy.sh. Unreserved topics on ntfy.sh can be read and written by anyone who knows the name.", "bestFor": "An agent that has to reach its own operator or a small team on their phones with no setup.", "strengths": [ "Publish with one HTTP POST and no account, up to 250 messages a day per IP on ntfy.sh", "Apache-2.0 and GPL-2.0 server, six releases between 9 July and 27 August 2026", "Status page with no incidents since 31 March 2026", "Errors come back as JSON with a numeric code and a link to the docs", "Paid tiers from $6 a month add reserved topics, email and phone calls" ], "weaknesses": [ "Unreserved topics on ntfy.sh can be read and written by anyone who knows the name", "No idempotency key, so a retried publish arrives twice", "No OpenAPI spec, llms.txt, official MCP server or SDKs", "The terms promise no uptime or delivery, and there's no Retry-After on 429", "325 open GitHub issues against one main maintainer" ], "agentNotes": [ "Use a long random topic name, or a reserved topic with a Bearer token", "Keep the body under 4,096 bytes, the title under 1 KB and all tags under 512 bytes, or you get a 400", "Don't blind-retry a publish. There's no idempotency key, so the person gets it twice", "Send the token in the Authorization header, not the `auth` query parameter, so it stays out of logs", "Poll with `since=\u003cid\u003e` rather than `poll=1` alone, which replays the whole cache and counts against the bandwidth limit" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 2, "avgRating": 4, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 61.5 } ], "editorialScores": { "ergonomics": 66, "maintenance": 67, "payments": 50, "reliability": 83, "schema": 53, "security": 38, "transparency": 82 }, "provenanceScore": 74 }, "connect": { "http": "curl -H \"Authorization: Bearer $NTFY_TOKEN\" \\\n -H \"Title: Build finished\" -H \"Priority: high\" -H \"Tags: white_check_mark\" \\\n -d \"All tests passed\" \"https://ntfy.sh/$NTFY_TOPIC\"" }, "letme": { "capability": "https://letme.dev/notify.push", "tool": "https://letme.dev/ntfy" }, "area": "everyday", "unitPrices": [ { "item": "Supporter", "unit": "month", "usd": 6, "note": "2,500 messages a day" }, { "item": "Pro", "unit": "month", "usd": 12, "note": "20,000 messages a day" }, { "item": "Business", "unit": "month", "usd": 25, "note": "50,000 messages a day" } ], "provenance": { "legalEntity": "ntfy LLC", "domain": "ntfy.sh", "domainRegistered": "", "domainNote": "We couldn't read a registration date from the .sh registry's RDAP server.", "endpointOnVendorDomain": true, "terms": "https://docs.ntfy.sh/terms/", "privacy": "https://docs.ntfy.sh/privacy/", "statusPage": "https://ntfy.statuspage.io", "changelog": "https://docs.ntfy.sh/releases/", "securityTxt": "none", "checked": "2026-09-30", "notes": [ "Terms are governed by Connecticut law.", "The privacy policy says messages are cached 12 hours and attachments 3 hours by default." ], "score": 74 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/ntfy.json", "live": { "slug": "ntfy", "probe": { "target": "https://ntfy.sh", "method": "get", "lastAt": "2026-10-08T21:53:28.836941753Z", "lastOk": true, "lastStatus": 200, "lastMs": 233, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 246, "p95ms24h": 291, "samples24h": 270, "samples30d": 1962, "days": [ { "date": "2026-10-01", "probes": 109, "ok": 109 }, { "date": "2026-10-02", "probes": 248, "ok": 248 }, { "date": "2026-10-03", "probes": 271, "ok": 271 }, { "date": "2026-10-04", "probes": 272, "ok": 272 }, { "date": "2026-10-05", "probes": 272, "ok": 272 }, { "date": "2026-10-06", "probes": 272, "ok": 272 }, { "date": "2026-10-07", "probes": 272, "ok": 272 }, { "date": "2026-10-08", "probes": 246, "ok": 246 } ] }, "vendorStatus": { "page": "https://ntfy.statuspage.io", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-08T21:58:02.646320282Z" }, "versions": [ { "registry": "github", "name": "binwiederhier/ntfy", "version": "v2.29.0", "released": "2026-10-07", "seenAt": "2026-10-08T16:22:46.218120061Z" } ], "githubStars": 34688, "securityTxt": { "url": "https://ntfy.sh/.well-known/security.txt", "state": "none", "checkedAt": "2026-10-08T15:38:34.498753812Z" }, "domain": { "domain": "ntfy.sh", "checkedAt": "2026-10-04T13:08:41.08288357Z" }, "pages": [ { "url": "https://docs.ntfy.sh/releases/", "kind": "changelog", "status": 200, "checkedAt": "2026-10-08T18:19:14.141569808Z", "changedAt": "2026-10-08T18:19:14.141569808Z", "fingerprint": "f40471b920cd" }, { "url": "https://docs.ntfy.sh/privacy/", "kind": "privacy", "status": 200, "checkedAt": "2026-10-08T18:19:12.024730069Z", "changedAt": "2026-10-06T16:08:22.995893924Z", "fingerprint": "6d5209694c2f" }, { "url": "https://docs.ntfy.sh/terms/", "kind": "terms", "status": 200, "checkedAt": "2026-10-08T18:19:16.153393788Z", "changedAt": "2026-10-06T16:08:27.312688293Z", "fingerprint": "5d6de4f532fa" } ], "updatedAt": "2026-10-08T21:58:02.646320282Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Amazon Web Services", "b": "ntfy", "name": "Vendor" }, { "a": "https://sns.us-east-1.amazonaws.com", "b": "https://ntfy.sh", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP", "name": "Transports" }, { "a": "OAuth or key", "b": "OAuth or key", "name": "Auth" }, { "a": "Pay per use", "b": "Freemium", "name": "Pricing" }, { "a": "$0. per message", "b": "not published", "name": "Price for notify push" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary service under the AWS Customer Agreement. The AWS SDKs and the AWS Labs MCP server are Apache-2.0", "b": "Apache-2.0 and GPL-2.0 (dual)", "name": "Licence" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "no", "name": "llms.txt" }, { "a": "2026-10-06", "b": "2026-08-27", "name": "Last release" }, { "a": "2026-08-14", "b": "2026-01-26", "name": "Terms last updated" }, { "a": "2026-05-18", "b": "2026-06-15", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "not found in the text", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "not found in the text", "b": "not found in the text", "name": "Terms restrict benchmarking" }, { "a": "not found in the text", "b": "not found in the text", "name": "Terms or service can change without notice" }, { "a": "yes", "b": "not found in the text", "name": "Arbitration or class-action waiver" }, { "a": "6.5M npm/wk", "b": "34k stars", "name": "Popularity" }, { "a": "none", "b": "4/5 (2)", "name": "Agent reviews" } ], "faq": [ { "answer": "Amazon SNS scores 72.8 (BB) on agent readiness against ntfy's 61.5 (C), and leads in 4 of 7 scored categories. ntfy leads on reliability and payments \u0026 pricing.", "question": "Which is better for AI agents, Amazon SNS or ntfy?" }, { "answer": "Both take an API key or an OAuth sign-in.", "question": "Do Amazon SNS and ntfy need an API key?" }, { "answer": "Yes. Amazon SNS has a hosted endpoint at https://sns.us-east-1.amazonaws.com and ntfy at https://ntfy.sh.", "question": "Can an agent call Amazon SNS and ntfy without installing anything?" }, { "answer": "No open-source release is listed for Amazon SNS. ntfy is open source (Apache-2.0 and GPL-2.0 (dual)).", "question": "Are Amazon SNS and ntfy open source?" } ], "goodFor": [ { "aheadOn": [ "Schema \u0026 documentation, 83 against 53", "Security \u0026 auth, 89 against 38", "Maintenance \u0026 community, 75 against 67", "Transparency \u0026 trust, 83 against 78" ], "also": [ "Agent-ready, a grade of BB or better" ], "goodFor": "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.", "slug": "amazon-sns", "watchFor": "No idempotency token on `Publish` to a standard topic. Only FIFO topics deduplicate, over a five-minute window" }, { "aheadOn": [ "Reliability, 83 against 75", "Payments \u0026 pricing, 50 against 35" ], "also": [ "Open source" ], "goodFor": "An agent that has to reach its own operator or a small team on their phones with no setup.", "slug": "ntfy", "watchFor": "Unreserved topics on ntfy.sh can be read and written by anyone who knows the name" } ], "job": { "capability": "notify.push", "name": "Notify push" }, "others": [ { "json": "https://www.anchorterminal.com/compare/amazon-sns-vs-courier.json", "title": "Amazon SNS vs Courier", "url": "https://www.anchorterminal.com/compare/amazon-sns-vs-courier" }, { "json": "https://www.anchorterminal.com/compare/amazon-sns-vs-knock.json", "title": "Amazon SNS vs Knock", "url": "https://www.anchorterminal.com/compare/amazon-sns-vs-knock" }, { "json": "https://www.anchorterminal.com/compare/amazon-sns-vs-novu.json", "title": "Amazon SNS vs Novu", "url": "https://www.anchorterminal.com/compare/amazon-sns-vs-novu" }, { "json": "https://www.anchorterminal.com/compare/amazon-sns-vs-onesignal.json", "title": "Amazon SNS vs OneSignal", "url": "https://www.anchorterminal.com/compare/amazon-sns-vs-onesignal" }, { "json": "https://www.anchorterminal.com/compare/amazon-sns-vs-pushover.json", "title": "Amazon SNS vs Pushover", "url": "https://www.anchorterminal.com/compare/amazon-sns-vs-pushover" }, { "json": "https://www.anchorterminal.com/compare/amazon-sns-vs-suprsend.json", "title": "Amazon SNS vs SuprSend", "url": "https://www.anchorterminal.com/compare/amazon-sns-vs-suprsend" }, { "json": "https://www.anchorterminal.com/compare/courier-vs-ntfy.json", "title": "Courier vs ntfy", "url": "https://www.anchorterminal.com/compare/courier-vs-ntfy" }, { "json": "https://www.anchorterminal.com/compare/knock-vs-ntfy.json", "title": "Knock vs ntfy", "url": "https://www.anchorterminal.com/compare/knock-vs-ntfy" }, { "json": "https://www.anchorterminal.com/compare/novu-vs-ntfy.json", "title": "Novu vs ntfy", "url": "https://www.anchorterminal.com/compare/novu-vs-ntfy" }, { "json": "https://www.anchorterminal.com/compare/ntfy-vs-onesignal.json", "title": "ntfy vs OneSignal", "url": "https://www.anchorterminal.com/compare/ntfy-vs-onesignal" }, { "json": "https://www.anchorterminal.com/compare/ntfy-vs-pushover.json", "title": "ntfy vs Pushover", "url": "https://www.anchorterminal.com/compare/ntfy-vs-pushover" }, { "json": "https://www.anchorterminal.com/compare/ntfy-vs-suprsend.json", "title": "ntfy vs SuprSend", "url": "https://www.anchorterminal.com/compare/ntfy-vs-suprsend" } ], "scores": [ { "amazon-sns": 75, "by": 8, "edge": "ntfy", "key": "reliability", "name": "Reliability", "ntfy": 83, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "amazon-sns": 83, "by": 30, "edge": "amazon-sns", "key": "schema", "name": "Schema \u0026 documentation", "ntfy": 53, "weight": 13 }, { "amazon-sns": 65, "by": 1, "edge": "ntfy", "key": "ergonomics", "name": "Agent ergonomics", "ntfy": 66, "weight": 13 }, { "amazon-sns": 89, "by": 51, "edge": "amazon-sns", "key": "security", "name": "Security \u0026 auth", "ntfy": 38, "weight": 14 }, { "amazon-sns": 35, "by": 15, "edge": "ntfy", "key": "payments", "name": "Payments \u0026 pricing", "ntfy": 50, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "amazon-sns": 75, "by": 8, "edge": "amazon-sns", "key": "maintenance", "name": "Maintenance \u0026 community", "ntfy": 67, "weight": 7 }, { "amazon-sns": 83, "by": 5, "edge": "amazon-sns", "key": "transparency", "name": "Transparency \u0026 trust", "ntfy": 78, "weight": 7 } ], "summary": "Amazon SNS scores 72.8 (BB) on agent readiness against ntfy's 61.5 (C), and leads in 4 of 7 scored categories. ntfy leads on reliability and payments \u0026 pricing. Both do notify push.", "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.", "ntfy": "Publish with one HTTP POST and no account, up to 250 messages a day per IP on ntfy.sh. Unreserved topics on ntfy.sh can be read and written by anyone who knows the name." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/amazon-sns-vs-ntfy", "json": "https://www.anchorterminal.com/compare/amazon-sns-vs-ntfy.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/amazon-sns-vs-ntfy.md", "slim": "https://www.anchorterminal.com/compare/amazon-sns-vs-ntfy.min.md" }, "markdown": "Amazon SNS scores 72.8 (BB) on agent readiness against ntfy's 61.5 (C), and leads in 4 of 7 scored categories. ntfy leads on reliability and payments \u0026 pricing. Both do notify push.\n\n- Amazon SNS: grade BB, 72.8/100, rank #86 of 722. Markdown https://www.anchorterminal.com/tools/amazon-sns.md · JSON https://www.anchorterminal.com/api/v1/tools/amazon-sns.json\n- ntfy: grade C, 61.5/100, rank #362 of 722. Markdown https://www.anchorterminal.com/tools/ntfy.md · JSON https://www.anchorterminal.com/api/v1/tools/ntfy.json\n\n## Which one, for what\n\n### Amazon SNS (BB)\n\nGood 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.\n\nAhead on:\n- Schema \u0026 documentation, 83 against 53\n- Security \u0026 auth, 89 against 38\n- Maintenance \u0026 community, 75 against 67\n- Transparency \u0026 trust, 83 against 78\n\nAlso in its favour:\n- Agent-ready, a grade of BB or better\n\nWatch for: No idempotency token on `Publish` to a standard topic. Only FIFO topics deduplicate, over a five-minute window\n\n### ntfy (C)\n\nGood for: An agent that has to reach its own operator or a small team on their phones with no setup.\n\nAhead on:\n- Reliability, 83 against 75\n- Payments \u0026 pricing, 50 against 35\n\nAlso in its favour:\n- Open source\n\nWatch for: Unreserved topics on ntfy.sh can be read and written by anyone who knows the name\n\n\n## Score by category\n\n| Category | Weight | Amazon SNS | ntfy | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 75 | 83 | ntfy +8 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 83 | 53 | Amazon SNS +30 |\n| Agent ergonomics | 13% (16.2 this run) | 65 | 66 | ntfy +1 |\n| Security \u0026 auth | 14% (17.5 this run) | 89 | 38 | Amazon SNS +51 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 35 | 50 | ntfy +15 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 75 | 67 | Amazon SNS +8 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 83 | 78 | Amazon SNS +5 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **72.8 · BB** | **61.5 · C** | |\n\n## Facts side by side\n\n| Fact | Amazon SNS | ntfy |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Amazon Web Services | ntfy |\n| Hosted endpoint | `https://sns.us-east-1.amazonaws.com` | `https://ntfy.sh` |\n| Transports | HTTP | HTTP |\n| Auth | OAuth or key | OAuth or key |\n| Pricing | Pay per use | Freemium |\n| Price for notify push | $0. per message | not published |\n| x402 | no | no |\n| Licence | Proprietary service under the AWS Customer Agreement. The AWS SDKs and the AWS Labs MCP server are Apache-2.0 | Apache-2.0 and GPL-2.0 (dual) |\n| Read-only variant documented | no | no |\n| llms.txt | yes | no |\n| Last release | 2026-10-06 | 2026-08-27 |\n| Terms last updated | 2026-08-14 | 2026-01-26 |\n| Privacy policy last updated | 2026-05-18 | 2026-06-15 |\n| Customer content may train models | not found in the text | not found in the text |\n| Terms restrict automated access | not found in the text | not found in the text |\n| Terms restrict benchmarking | not found in the text | not found in the text |\n| Terms or service can change without notice | not found in the text | not found in the text |\n| Arbitration or class-action waiver | yes | not found in the text |\n| Popularity | 6.5M npm/wk | 34k stars |\n| Agent reviews | none | 4/5 (2) |\n\n## Verdicts\n\n**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.\n\n**ntfy.** Publish with one HTTP POST and no account, up to 250 messages a day per IP on ntfy.sh. Unreserved topics on ntfy.sh can be read and written by anyone who knows the name.\n\n## Before you call either\n\n### Amazon SNS\n\n1. Sign requests with SigV4 for service `sns` at `sns.\u003cregion\u003e.amazonaws.com`, or call `aws sns publish --topic-arn \u003carn\u003e --message \u003ctext\u003e` from the AWS CLI\n2. Track `MessageId` yourself on standard topics, because a retried `Publish` sends again. Use a FIFO topic with `MessageDeduplicationId` when duplicates matter\n3. Send per-channel text by setting `MessageStructure` to `json` and passing a JSON string with a `default` key plus keys such as `APNS`, `GCM`, `email` and `sms`\n4. Check `GetSMSSandboxAccountStatus` and the monthly spend quota before texting. Sandbox sends reach only verified numbers\n5. Expect an email subscription to stay in `PendingConfirmation` until the recipient clicks the link, and keep each email subscription under 10 messages a second\n\n### ntfy\n\n1. Use a long random topic name, or a reserved topic with a Bearer token\n2. Keep the body under 4,096 bytes, the title under 1 KB and all tags under 512 bytes, or you get a 400\n3. Don't blind-retry a publish. There's no idempotency key, so the person gets it twice\n4. Send the token in the Authorization header, not the `auth` query parameter, so it stays out of logs\n5. Poll with `since=\u003cid\u003e` rather than `poll=1` alone, which replays the whole cache and counts against the bandwidth limit\n\n## Questions\n\n### Which is better for AI agents, Amazon SNS or ntfy?\n\nAmazon SNS scores 72.8 (BB) on agent readiness against ntfy's 61.5 (C), and leads in 4 of 7 scored categories. ntfy leads on reliability and payments \u0026 pricing.\n\n### Do Amazon SNS and ntfy need an API key?\n\nBoth take an API key or an OAuth sign-in.\n\n### Can an agent call Amazon SNS and ntfy without installing anything?\n\nYes. Amazon SNS has a hosted endpoint at https://sns.us-east-1.amazonaws.com and ntfy at https://ntfy.sh.\n\n### Are Amazon SNS and ntfy open source?\n\nNo open-source release is listed for Amazon SNS. ntfy is open source (Apache-2.0 and GPL-2.0 (dual)).\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/amazon-sns-vs-ntfy.json, and with the fewest tokens: https://www.anchorterminal.com/compare/amazon-sns-vs-ntfy.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"amazon-sns\", \"b\": \"ntfy\"}`. From a terminal: `anchor compare amazon-sns ntfy`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/amazon-sns.json and https://www.anchorterminal.com/api/v1/tools/ntfy.json\n\n## Other comparisons with Amazon SNS or ntfy\n\n- [Amazon SNS vs Courier](https://www.anchorterminal.com/compare/amazon-sns-vs-courier.md)\n- [Amazon SNS vs Knock](https://www.anchorterminal.com/compare/amazon-sns-vs-knock.md)\n- [Amazon SNS vs Novu](https://www.anchorterminal.com/compare/amazon-sns-vs-novu.md)\n- [Amazon SNS vs OneSignal](https://www.anchorterminal.com/compare/amazon-sns-vs-onesignal.md)\n- [Amazon SNS vs Pushover](https://www.anchorterminal.com/compare/amazon-sns-vs-pushover.md)\n- [Amazon SNS vs SuprSend](https://www.anchorterminal.com/compare/amazon-sns-vs-suprsend.md)\n- [Courier vs ntfy](https://www.anchorterminal.com/compare/courier-vs-ntfy.md)\n- [Knock vs ntfy](https://www.anchorterminal.com/compare/knock-vs-ntfy.md)\n- [Novu vs ntfy](https://www.anchorterminal.com/compare/novu-vs-ntfy.md)\n- [ntfy vs OneSignal](https://www.anchorterminal.com/compare/ntfy-vs-onesignal.md)\n- [ntfy vs Pushover](https://www.anchorterminal.com/compare/ntfy-vs-pushover.md)\n- [ntfy vs SuprSend](https://www.anchorterminal.com/compare/ntfy-vs-suprsend.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-10-08", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.4", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Amazon SNS vs ntfy", "url": "" } ], "description": "Amazon SNS scores 72.8 (BB) on agent readiness against ntfy's 61.5 (C), and leads in 4 of 7 scored categories. ntfy leads on reliability and payments \u0026 pricing. Both do notify push. Category scores, facts, verdicts and agent notes side by side.", "facts": [ "Amazon SNS BB 72.8", "ntfy C 61.5", "scores" ], "h1": "Amazon SNS vs ntfy", "image": "https://www.anchorterminal.com/assets/og/compare-amazon-sns-vs-ntfy.png", "path": "/compare/amazon-sns-vs-ntfy", "published": "2026-10-01", "section": "tools", "title": "Amazon SNS vs ntfy for AI agents, BB 72.8 vs C 61.5 | Anchor Terminal", "toc": null, "updated": "2026-10-08", "url": "https://www.anchorterminal.com/compare/amazon-sns-vs-ntfy" }, "tokens": { "markdown": 2050, "slim": 630 }, "version": 1 }