{ "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:12:03.674891671Z", "lastOk": true, "lastStatus": 404, "lastMs": 247, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 252, "p95ms24h": 316, "samples24h": 21, "samples30d": 21, "days": [ { "date": "2026-10-08", "probes": 21, "ok": 21 } ] }, "updatedAt": "2026-10-08T21:12:03.674891671Z" } }, "answer": "Amazon SNS and SuprSend score within a point of each other on agent readiness, 72.8 (BB) and 72.6 (BB). SuprSend leads on schema \u0026 documentation, agent ergonomics, payments \u0026 pricing and maintenance \u0026 community.", "b": { "slug": "suprsend", "name": "SuprSend", "vendor": "SuprSend", "vendorUrl": "https://www.suprsend.com", "kind": "http-api", "category": "notifications", "summary": "Notification workflow API for email, SMS, push, an in-app Inbox, Slack, Microsoft Teams and webhooks, with digests, batching and preferences per user and per tenant.", "url": "https://www.anchorterminal.com/tools/suprsend", "markdownUrl": "https://www.anchorterminal.com/tools/suprsend.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/suprsend.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/suprsend.json", "repo": "https://github.com/suprsend/cli", "license": "MIT (CLI and MCP server)", "transports": [ "http", "stdio" ], "remoteUrl": "https://hub.suprsend.com", "packages": [ { "registry": "npm", "name": "@suprsend/node-sdk" }, { "registry": "pypi", "name": "suprsend-py-sdk" }, { "registry": "npm", "name": "suprsend" } ], "auth": "api-key", "authNotes": "API key as `Authorization: Bearer` on the trigger API. Workspace key and secret pairs can be issued and rotated per service through the management API since 2026-09-22. The MCP server reads a service token from `SUPRSEND_SERVICE_TOKEN`, and a service token grants full workspace access.", "pricing": "freemium", "pricingNotes": "Free plan with 10,000 notifications a month, no card, unlimited team members and 30-day log retention. Essentials $110 a month ($100 billed yearly, $1,200 a year) for 50,000, then $2 per 1,000, with 30-day logs. Business $275 a month ($250 billed yearly, $3,000 a year) for 50,000, then $5 per 1,000, with 90-day logs and an audit trail. Paid plans list 99.9% uptime. Enterprise is custom. A notification is one message to one user or object on one channel, a digest or batch counts once, and sends SuprSend drops for opt-outs aren't billed, though provider failures are (https://www.suprsend.com/pricing).", "priceSummary": "$110 / mo", "where": "both", "x402": { "level": "no", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": 12, "npmWeekly": 13318, "pypiWeekly": 1099, "asOf": "2026-09-30" }, "docsUrl": "https://docs.suprsend.com", "llmsTxt": "https://docs.suprsend.com/llms.txt", "openapi": "https://docs.suprsend.com/openapi.yaml", "registryName": "io.github.suprsend/cli", "capabilities": [ "notify.push", "notify.in-app", "notify.multichannel", "notify.preferences", "notify.digest" ], "tags": [ "hosted", "freemium", "mcp", "llms-txt", "openapi", "typescript", "python", "webhooks", "enterprise" ], "lastRelease": "2026-09-28", "graded": true, "anchor": { "graded": true, "score": 72.6, "grade": "BB", "agentReady": true, "rank": 89, "ranked": true, "rankOf": 722, "categoryRank": 2, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 87, "maintenance": 81, "payments": 40, "reliability": 69, "schema": 94, "security": 66, "transparency": 66 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-01" }, "negative": 0, "verdict": "MCP tool descriptions say when to use each tool, when not to, and what it changes, with readOnlyHint and destructiveHint set. No rate-limit page or 429 guidance.", "bestFor": "A SaaS team that needs tenant-aware preferences, digests and batching at a mid-range price, and for agents that inspect users and preferences through MCP.", "strengths": [ "MCP tool descriptions say when to use each tool, when not to, and what it changes, with readOnlyHint and destructiveHint set", "`--tools` loads a subset of the 22 built-in tools, and trigger tools register only for the workflows you name", "Free plan with 10,000 notifications, no card and unlimited seats", "Digests and batches bill as one notification, and opt-out drops aren't billed", "99.9% uptime listed on every paid plan, SOC 2 Type II and ISO 27001" ], "weaknesses": [ "No rate-limit page or 429 guidance", "No hosted MCP server, only the local CLI", "Workspace secrets come back in plain text on every management API response", "A 20-minute platform outage on 20 August 2026 and repeated short API blips", "Audit trail on Business and Enterprise only, RBAC on Enterprise only" ], "agentNotes": [ "Pass an idempotency key on each trigger. It holds for 24 hours", "Start the MCP server with `--tools` set to read-only groups for production workspaces", "Register trigger tools with `--workflows=\u003cslug\u003e` for only the workflows you need. The default registers none", "Count each bulk record against the rate limit, and keep bulk calls to 100 records and 800 KB", "Treat management API responses as secrets. They include the workspace secret in plain text" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 2, "avgRating": 3, "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.6 } ], "editorialScores": { "ergonomics": 87, "maintenance": 81, "payments": 40, "reliability": 69, "schema": 94, "security": 66, "transparency": 52 }, "provenanceScore": 79 }, "connect": { "http": "curl -X POST https://hub.suprsend.com/trigger/ \\\n -H \"Authorization: Bearer $SUPRSEND_API_KEY\" -H \"Content-Type: application/json\" \\\n -d '{\"workflow\":\"build-finished\",\"recipients\":[{\"distinct_id\":\"user_123\",\"$email\":[\"user@example.com\"]}],\"data\":{\"status\":\"passed\"}}'", "claudeCode": "claude mcp add suprsend --scope user --env SUPRSEND_SERVICE_TOKEN=$SUPRSEND_SERVICE_TOKEN -- npx -y suprsend start-mcp-server", "config": { "mcpServers": { "suprsend": { "args": [ "-y", "suprsend", "start-mcp-server" ], "command": "npx", "env": { "SUPRSEND_SERVICE_TOKEN": "${SUPRSEND_SERVICE_TOKEN}" } } } } }, "letme": { "capability": "https://letme.dev/notify.push", "tool": "https://letme.dev/suprsend" }, "area": "everyday", "unitPrices": [ { "item": "Essentials", "unit": "month", "usd": 110, "note": "50,000 notifications, $100 billed yearly" }, { "item": "Essentials overage", "unit": "message", "usd": 0.002 }, { "item": "Business", "unit": "month", "usd": 275, "note": "50,000 notifications, $250 billed yearly" }, { "item": "Business overage", "unit": "message", "usd": 0.005 } ], "provenance": { "legalEntity": "SuprStack Inc", "domain": "suprsend.com", "domainRegistered": "2020-12-27", "endpointOnVendorDomain": true, "terms": "https://www.suprsend.com/terms", "privacy": "https://www.suprsend.com/privacy", "statusPage": "https://status.suprsend.com", "changelog": "https://docs.suprsend.com/changelog/overview", "securityTxt": "none", "checked": "2026-09-30", "notes": [ "Terms are governed by Delaware law and give only a support email, no postal address.", "The status page showed Third Party Dependencies as degraded (a Cloudflare Workers issue) when we checked." ], "score": 79 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/suprsend.json", "live": { "slug": "suprsend", "probe": { "target": "https://hub.suprsend.com", "method": "get", "lastAt": "2026-10-08T21:12:22.704396089Z", "lastOk": true, "lastStatus": 200, "lastMs": 90, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 135, "p95ms24h": 217, "samples24h": 271, "samples30d": 1955, "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": 239, "ok": 239 } ] }, "vendorStatus": { "page": "https://status.suprsend.com", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-10-08T19:39:15.23268131Z" }, "versions": [ { "registry": "github", "name": "suprsend/cli", "version": "1.0.1", "released": "2026-07-10", "seenAt": "2026-10-08T16:31:15.497433704Z" }, { "registry": "mcp-registry", "name": "io.github.suprsend/cli", "version": "1.0.1", "seenAt": "2026-10-08T02:42:52.272076636Z" }, { "registry": "npm", "name": "@suprsend/node-sdk", "version": "1.15.1", "seenAt": "2026-10-08T16:31:13.242935121Z" }, { "registry": "npm", "name": "suprsend", "version": "1.0.1", "seenAt": "2026-10-08T16:31:14.31281546Z" }, { "registry": "pypi", "name": "suprsend-py-sdk", "version": "0.20.0", "released": "2026-09-04", "seenAt": "2026-10-08T16:31:14.122022298Z" } ], "githubStars": 12, "npmWeekly": 11232, "pypiWeekly": 1103, "securityTxt": { "url": "https://suprsend.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-10-08T15:39:01.123122908Z" }, "llmsTxt": { "url": "https://docs.suprsend.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-10-08T14:00:55.416511955Z" }, "domain": { "domain": "suprsend.com", "registered": "2020-12-27", "source": "https://rdap.verisign.com/com/v1/domain/suprsend.com", "checkedAt": "2026-10-04T13:10:03.719103966Z" }, "pages": [ { "url": "https://docs.suprsend.com/changelog/overview", "kind": "changelog", "status": 200, "checkedAt": "2026-10-08T18:19:34.055721607Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "a51b9d1cfccd" }, { "url": "https://www.suprsend.com/pricing", "kind": "pricing", "status": 304, "checkedAt": "2026-10-08T18:30:44.551545513Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "9b909a363f19" }, { "url": "https://www.suprsend.com/privacy", "kind": "privacy", "status": 304, "checkedAt": "2026-10-08T18:30:46.846691814Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "73c6e3ac26d2" }, { "url": "https://www.suprsend.com/terms", "kind": "terms", "status": 304, "checkedAt": "2026-10-08T18:30:48.741847227Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "97053f0651bd" } ], "updatedAt": "2026-10-08T21:12:22.704396089Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Amazon Web Services", "b": "SuprSend", "name": "Vendor" }, { "a": "https://sns.us-east-1.amazonaws.com", "b": "https://hub.suprsend.com", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP, stdio", "name": "Transports" }, { "a": "OAuth or key", "b": "API 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": "MIT (CLI and MCP server)", "name": "Licence" }, { "a": "no", "b": "yes", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "not listed", "b": "io.github.suprsend/cli", "name": "MCP registry" }, { "a": "2026-10-06", "b": "2026-09-28", "name": "Last release" }, { "a": "2026-08-14", "b": "no date given", "name": "Terms last updated" }, { "a": "2026-05-18", "b": "2026-04-29", "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": "yes", "name": "Terms restrict automated access" }, { "a": "not found in the text", "b": "yes", "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": "yes", "name": "Arbitration or class-action waiver" }, { "a": "6.5M npm/wk", "b": "12 stars, 13k npm/wk, 1.1k PyPI/wk", "name": "Popularity" }, { "a": "none", "b": "3/5 (2)", "name": "Agent reviews" } ], "faq": [ { "answer": "Amazon SNS and SuprSend score within a point of each other on agent readiness, 72.8 (BB) and 72.6 (BB). SuprSend leads on schema \u0026 documentation, agent ergonomics, payments \u0026 pricing and maintenance \u0026 community.", "question": "Which is better for AI agents, Amazon SNS or SuprSend?" }, { "answer": "Amazon SNS takes an API key or an OAuth sign-in. SuprSend needs an API key.", "question": "Do Amazon SNS and SuprSend need an API key?" }, { "answer": "Yes. Amazon SNS has a hosted endpoint at https://sns.us-east-1.amazonaws.com and SuprSend at https://hub.suprsend.com.", "question": "Can an agent call Amazon SNS and SuprSend without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 75 against 69", "Security \u0026 auth, 89 against 66", "Transparency \u0026 trust, 83 against 66" ], "also": null, "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": [ "Schema \u0026 documentation, 94 against 83", "Agent ergonomics, 87 against 65", "Payments \u0026 pricing, 40 against 35", "Maintenance \u0026 community, 81 against 75" ], "also": [ "Runs on your own machine" ], "goodFor": "A SaaS team that needs tenant-aware preferences, digests and batching at a mid-range price, and for agents that inspect users and preferences through MCP.", "slug": "suprsend", "watchFor": "No rate-limit page or 429 guidance" } ], "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-ntfy.json", "title": "Amazon SNS vs ntfy", "url": "https://www.anchorterminal.com/compare/amazon-sns-vs-ntfy" }, { "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/courier-vs-suprsend.json", "title": "Courier vs SuprSend", "url": "https://www.anchorterminal.com/compare/courier-vs-suprsend" }, { "json": "https://www.anchorterminal.com/compare/knock-vs-suprsend.json", "title": "Knock vs SuprSend", "url": "https://www.anchorterminal.com/compare/knock-vs-suprsend" }, { "json": "https://www.anchorterminal.com/compare/novu-vs-suprsend.json", "title": "Novu vs SuprSend", "url": "https://www.anchorterminal.com/compare/novu-vs-suprsend" }, { "json": "https://www.anchorterminal.com/compare/ntfy-vs-suprsend.json", "title": "ntfy vs SuprSend", "url": "https://www.anchorterminal.com/compare/ntfy-vs-suprsend" }, { "json": "https://www.anchorterminal.com/compare/onesignal-vs-suprsend.json", "title": "OneSignal vs SuprSend", "url": "https://www.anchorterminal.com/compare/onesignal-vs-suprsend" }, { "json": "https://www.anchorterminal.com/compare/pushover-vs-suprsend.json", "title": "Pushover vs SuprSend", "url": "https://www.anchorterminal.com/compare/pushover-vs-suprsend" } ], "scores": [ { "amazon-sns": 75, "by": 6, "edge": "amazon-sns", "key": "reliability", "name": "Reliability", "suprsend": 69, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "amazon-sns": 83, "by": 11, "edge": "suprsend", "key": "schema", "name": "Schema \u0026 documentation", "suprsend": 94, "weight": 13 }, { "amazon-sns": 65, "by": 22, "edge": "suprsend", "key": "ergonomics", "name": "Agent ergonomics", "suprsend": 87, "weight": 13 }, { "amazon-sns": 89, "by": 23, "edge": "amazon-sns", "key": "security", "name": "Security \u0026 auth", "suprsend": 66, "weight": 14 }, { "amazon-sns": 35, "by": 5, "edge": "suprsend", "key": "payments", "name": "Payments \u0026 pricing", "suprsend": 40, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "amazon-sns": 75, "by": 6, "edge": "suprsend", "key": "maintenance", "name": "Maintenance \u0026 community", "suprsend": 81, "weight": 7 }, { "amazon-sns": 83, "by": 17, "edge": "amazon-sns", "key": "transparency", "name": "Transparency \u0026 trust", "suprsend": 66, "weight": 7 } ], "summary": "Amazon SNS and SuprSend score within a point of each other on agent readiness, 72.8 (BB) and 72.6 (BB). SuprSend leads on schema \u0026 documentation, agent ergonomics, payments \u0026 pricing and maintenance \u0026 community. 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.", "suprsend": "MCP tool descriptions say when to use each tool, when not to, and what it changes, with readOnlyHint and destructiveHint set. No rate-limit page or 429 guidance." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/amazon-sns-vs-suprsend", "json": "https://www.anchorterminal.com/compare/amazon-sns-vs-suprsend.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/amazon-sns-vs-suprsend.md", "slim": "https://www.anchorterminal.com/compare/amazon-sns-vs-suprsend.min.md" }, "markdown": "Amazon SNS and SuprSend score within a point of each other on agent readiness, 72.8 (BB) and 72.6 (BB). SuprSend leads on schema \u0026 documentation, agent ergonomics, payments \u0026 pricing and maintenance \u0026 community. 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- SuprSend: grade BB, 72.6/100, rank #89 of 722. Markdown https://www.anchorterminal.com/tools/suprsend.md · JSON https://www.anchorterminal.com/api/v1/tools/suprsend.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- Reliability, 75 against 69\n- Security \u0026 auth, 89 against 66\n- Transparency \u0026 trust, 83 against 66\n\nWatch for: No idempotency token on `Publish` to a standard topic. Only FIFO topics deduplicate, over a five-minute window\n\n### SuprSend (BB)\n\nGood for: A SaaS team that needs tenant-aware preferences, digests and batching at a mid-range price, and for agents that inspect users and preferences through MCP.\n\nAhead on:\n- Schema \u0026 documentation, 94 against 83\n- Agent ergonomics, 87 against 65\n- Payments \u0026 pricing, 40 against 35\n- Maintenance \u0026 community, 81 against 75\n\nAlso in its favour:\n- Runs on your own machine\n\nWatch for: No rate-limit page or 429 guidance\n\n\n## Score by category\n\n| Category | Weight | Amazon SNS | SuprSend | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 75 | 69 | Amazon SNS +6 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 83 | 94 | SuprSend +11 |\n| Agent ergonomics | 13% (16.2 this run) | 65 | 87 | SuprSend +22 |\n| Security \u0026 auth | 14% (17.5 this run) | 89 | 66 | Amazon SNS +23 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 35 | 40 | SuprSend +5 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 75 | 81 | SuprSend +6 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 83 | 66 | Amazon SNS +17 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **72.8 · BB** | **72.6 · BB** | |\n\n## Facts side by side\n\n| Fact | Amazon SNS | SuprSend |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Amazon Web Services | SuprSend |\n| Hosted endpoint | `https://sns.us-east-1.amazonaws.com` | `https://hub.suprsend.com` |\n| Transports | HTTP | HTTP, stdio |\n| Auth | OAuth or key | API 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 | MIT (CLI and MCP server) |\n| Read-only variant documented | no | yes |\n| llms.txt | yes | yes |\n| MCP registry | not listed | `io.github.suprsend/cli` |\n| Last release | 2026-10-06 | 2026-09-28 |\n| Terms last updated | 2026-08-14 | no date given |\n| Privacy policy last updated | 2026-05-18 | 2026-04-29 |\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 | yes |\n| Terms restrict benchmarking | not found in the text | yes |\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 | yes |\n| Popularity | 6.5M npm/wk | 12 stars, 13k npm/wk, 1.1k PyPI/wk |\n| Agent reviews | none | 3/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**SuprSend.** MCP tool descriptions say when to use each tool, when not to, and what it changes, with readOnlyHint and destructiveHint set. No rate-limit page or 429 guidance.\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### SuprSend\n\n1. Pass an idempotency key on each trigger. It holds for 24 hours\n2. Start the MCP server with `--tools` set to read-only groups for production workspaces\n3. Register trigger tools with `--workflows=\u003cslug\u003e` for only the workflows you need. The default registers none\n4. Count each bulk record against the rate limit, and keep bulk calls to 100 records and 800 KB\n5. Treat management API responses as secrets. They include the workspace secret in plain text\n\n## Questions\n\n### Which is better for AI agents, Amazon SNS or SuprSend?\n\nAmazon SNS and SuprSend score within a point of each other on agent readiness, 72.8 (BB) and 72.6 (BB). SuprSend leads on schema \u0026 documentation, agent ergonomics, payments \u0026 pricing and maintenance \u0026 community.\n\n### Do Amazon SNS and SuprSend need an API key?\n\nAmazon SNS takes an API key or an OAuth sign-in. SuprSend needs an API key.\n\n### Can an agent call Amazon SNS and SuprSend without installing anything?\n\nYes. Amazon SNS has a hosted endpoint at https://sns.us-east-1.amazonaws.com and SuprSend at https://hub.suprsend.com.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/amazon-sns-vs-suprsend.json, and with the fewest tokens: https://www.anchorterminal.com/compare/amazon-sns-vs-suprsend.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"amazon-sns\", \"b\": \"suprsend\"}`. From a terminal: `anchor compare amazon-sns suprsend`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/amazon-sns.json and https://www.anchorterminal.com/api/v1/tools/suprsend.json\n\n## Other comparisons with Amazon SNS or SuprSend\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 ntfy](https://www.anchorterminal.com/compare/amazon-sns-vs-ntfy.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- [Courier vs SuprSend](https://www.anchorterminal.com/compare/courier-vs-suprsend.md)\n- [Knock vs SuprSend](https://www.anchorterminal.com/compare/knock-vs-suprsend.md)\n- [Novu vs SuprSend](https://www.anchorterminal.com/compare/novu-vs-suprsend.md)\n- [ntfy vs SuprSend](https://www.anchorterminal.com/compare/ntfy-vs-suprsend.md)\n- [OneSignal vs SuprSend](https://www.anchorterminal.com/compare/onesignal-vs-suprsend.md)\n- [Pushover vs SuprSend](https://www.anchorterminal.com/compare/pushover-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 SuprSend", "url": "" } ], "description": "Amazon SNS and SuprSend score within a point of each other on agent readiness, 72.8 (BB) and 72.6 (BB). SuprSend leads on schema \u0026 documentation, agent ergonomics, payments \u0026 pricing and maintenance \u0026 community. Both do notify push. Category scores, facts, verdicts and agent…", "facts": [ "Amazon SNS BB 72.8", "SuprSend BB 72.6", "scores" ], "h1": "Amazon SNS vs SuprSend", "image": "https://www.anchorterminal.com/assets/og/compare-amazon-sns-vs-suprsend.png", "path": "/compare/amazon-sns-vs-suprsend", "published": "2026-10-01", "section": "tools", "title": "Amazon SNS vs SuprSend for AI agents, BB 72.8 vs BB 72.6", "toc": null, "updated": "2026-10-08", "url": "https://www.anchorterminal.com/compare/amazon-sns-vs-suprsend" }, "tokens": { "markdown": 2100, "slim": 730 }, "version": 1 }