{ "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": 96, "ranked": true, "rankOf": 842, "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": [ "amazon-bedrock-customization", "agentcore-code-interpreter", "amazon-textract", "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-09T11:28:53.536392453Z", "lastOk": true, "lastStatus": 404, "lastMs": 259, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 251, "p95ms24h": 281, "samples24h": 172, "samples30d": 172, "days": [ { "date": "2026-10-08", "probes": 50, "ok": 50 }, { "date": "2026-10-09", "probes": 122, "ok": 122 } ] }, "updatedAt": "2026-10-09T11:28:53.536392453Z" } }, "answer": "Amazon SNS scores 72.8 (BB) on agent readiness against Firebase Cloud Messaging's 69.8 (B), and leads in 3 of 7 scored categories. Firebase Cloud Messaging leads on agent ergonomics, payments \u0026 pricing and maintenance \u0026 community.", "b": { "slug": "firebase-cloud-messaging", "name": "Firebase Cloud Messaging", "vendor": "Google", "vendorUrl": "https://firebase.google.com/products/cloud-messaging", "kind": "http-api", "category": "notifications", "summary": "Google's push messaging service for Android, Apple and web apps. A server sends notification or data messages to devices, topics or conditions through the HTTP v1 API or the Firebase Admin SDKs.", "url": "https://www.anchorterminal.com/tools/firebase-cloud-messaging", "markdownUrl": "https://www.anchorterminal.com/tools/firebase-cloud-messaging.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/firebase-cloud-messaging.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/firebase-cloud-messaging.json", "repo": "https://github.com/firebase/firebase-admin-node", "license": "Proprietary service under the Google APIs Terms of Service. The Firebase Admin SDKs are Apache-2.0", "transports": [ "http" ], "remoteUrl": "https://fcm.googleapis.com", "packages": [ { "registry": "npm", "name": "firebase-admin" }, { "registry": "pypi", "name": "firebase-admin" } ], "auth": "oauth", "authNotes": "OAuth 2.0 bearer token minted from a service account key or Application Default Credentials, with the scope `https://www.googleapis.com/auth/firebase.messaging`. Sending needs the IAM permission `cloudmessaging.messages.create` on the project. Access is self-serve. A person creates the Firebase project and the service account in the console, with no review or sales step.", "pricing": "free", "pricingNotes": "No charge. The pricing page lists Cloud Messaging as no-cost on the Spark and Blaze plans, and Spark needs no billing account or card, so an agent's owner can start without a contract. The optional BigQuery export of delivery data is billed by BigQuery (https://firebase.google.com/pricing, checked 2026-10-08).", "priceSummary": "Free", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the FCM docs, the Discovery document or the pricing page (checked 2026-10-08).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": 11536195, "pypiWeekly": 3790113, "asOf": "2026-10-08" }, "docsUrl": "https://firebase.google.com/docs/cloud-messaging", "llmsTxt": "https://firebase.google.com/docs/llms.txt", "openapi": "https://fcm.googleapis.com/$discovery/rest?version=v1", "capabilities": [ "notify.push" ], "tags": [ "hosted", "free", "push", "oauth", "llms-txt", "typescript", "python", "java", "go", "dotnet", "mcp", "status-page", "soc2" ], "lastRelease": "2026-09-24", "graded": true, "anchor": { "graded": true, "score": 69.8, "grade": "B", "agentReady": false, "rank": 162, "ranked": true, "rankOf": 842, "categoryRank": 4, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 70, "maintenance": 83, "payments": 40, "reliability": 66, "schema": 86, "security": 68, "transparency": 81 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-08" }, "negative": 0, "verdict": "Sending is free at any volume, with a published quota of 600,000 messages a minute per project and documented 429 handling. FCM is push transport only. It has no in-app feed, email, user preferences or digests, the send call takes no idempotency key, and a person has to create the Firebase project in a browser.", "bestFor": "The push transport under an app that already holds device registrations, at no charge.", "strengths": [ "No charge for sending on either Firebase plan, and no billing account needed (https://firebase.google.com/pricing)", "Default quota of 600,000 messages a minute per project, with 429 responses that carry `retry-after` and written backoff guidance", "Short-lived OAuth 2.0 tokens with a `firebase.messaging` scope, and IAM permissions per action such as `cloudmessaging.messages.create`", "Public Discovery document (revision 20261006), a docs `llms.txt` and a Markdown twin of every docs page", "Dated deprecation notice in September 2026 that gives 12 months before the Instance ID server APIs and device groups stop on 29 September 2027" ], "weaknesses": [ "Push transport only. No in-app feed, email, SMS, user preferences, digests or templates", "No idempotency key on `messages:send`, so a retried request can reach the device twice", "One HTTP request per message. Only the Admin SDKs group up to 500 sends in a call", "FCM is absent from Google Cloud's list of services with audit logs, and per-message delivery data needs a BigQuery export", "One incident on 1 September 2026 lowered availability in North America for 3 hours 51 minutes, and no SLA names FCM" ], "agentNotes": [ "Mint an access token from a service account with the scope `https://www.googleapis.com/auth/firebase.messaging`, then POST to `https://fcm.googleapis.com/v1/projects/\u003cproject-id\u003e/messages:send`", "Set `validate_only` to true to test a message or a registration without sending it", "On 429 wait for the `retry-after` header, or 60 seconds if it is absent. Retry 500 and 503 with exponential backoff and jitter, and never retry 400, 401, 403 or 404", "Drop a registration when the error is `UNREGISTERED` (404). Keep your own record of sends, because a retry after a timeout can produce a duplicate", "Target `fid` in new code. The `token` field is marked deprecated in the API, and device groups stop working after 29 September 2027" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 69.8 } ], "editorialScores": { "ergonomics": 70, "maintenance": 83, "payments": 40, "reliability": 66, "schema": 86, "security": 68, "transparency": 68 }, "provenanceScore": 94 }, "connect": { "install": "npm install firebase-admin # or: pip install firebase-admin", "http": "curl -X POST \"https://fcm.googleapis.com/v1/projects/$FIREBASE_PROJECT_ID/messages:send\" \\\n -H \"Authorization: Bearer $ACCESS_TOKEN\" -H \"Content-Type: application/json\" \\\n -d '{\"message\":{\"topic\":\"news\",\"notification\":{\"title\":\"Build finished\",\"body\":\"All tests passed\"}}}'", "claudeCode": "claude mcp add firebase npx -- -y firebase-tools@latest mcp" }, "letme": { "capability": "https://letme.dev/notify.push", "tool": "https://letme.dev/firebase-cloud-messaging" }, "sameCompany": [ "gemini-api", "gemini-embedding", "vertex-ai-tuning", "google-model-armor", "google-imagen", "google-veo", "google-lyria", "google-speech-to-text", "gemini-live", "google-adk", "google-secret-manager", "google-weather-api", "chrome-devtools-mcp", "google-maps-platform", "google-cloud-translation", "google-calendar-api", "google-drive-api", "gemini-cli", "google-search-console", "google-ads-api", "google-forms", "google-sheets-api", "gmail-api" ], "area": "everyday", "provenance": { "legalEntity": "Google LLC", "domain": "google.com", "domainRegistered": "1997-09-15", "domainNote": "The endpoint is on googleapis.com, Google's API domain. The docs are on firebase.google.com.", "endpointOnVendorDomain": true, "terms": "https://developers.google.com/terms", "privacy": "https://policies.google.com/privacy", "statusPage": "https://status.firebase.google.com", "changelog": "https://firebase.google.com/support/releases", "securityTxt": "valid", "checked": "2026-10-08", "notes": [ "firebase.google.com/terms, last modified 24 September 2026, places Cloud Messaging under the Google APIs Terms of Service and the Firebase Data Processing and Security Terms.", "The Google APIs Terms of Service were last modified on 9 November 2021, name Google LLC of Mountain View, California, and choose California law.", "Google's privacy policy is effective 1 October 2026. Firebase's own privacy and security page, last modified 15 September 2026, gives the per-service data and retention table.", "www.google.com/.well-known/security.txt expires on 2030-04-01. firebase.google.com/.well-known/security.txt returns 404.", "The registration date of google.com is taken from our earlier Google listings and was not looked up again today." ], "score": 94 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/firebase-cloud-messaging.json", "live": { "slug": "firebase-cloud-messaging", "probe": { "target": "https://fcm.googleapis.com", "method": "get", "lastAt": "2026-10-09T11:29:00.774027159Z", "lastOk": true, "lastStatus": 404, "lastMs": 42, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 42, "p95ms24h": 72, "samples24h": 41, "samples30d": 41, "days": [ { "date": "2026-10-09", "probes": 41, "ok": 41 } ] }, "vendorStatus": { "page": "https://status.firebase.google.com", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-10-09T07:57:54.993043607Z" }, "updatedAt": "2026-10-09T11:29:00.774027159Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Amazon Web Services", "b": "Google", "name": "Vendor" }, { "a": "https://sns.us-east-1.amazonaws.com", "b": "https://fcm.googleapis.com", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP", "name": "Transports" }, { "a": "OAuth or key", "b": "OAuth", "name": "Auth" }, { "a": "Pay per use", "b": "Free", "name": "Pricing" }, { "a": "$0. per message", "b": "free", "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": "Proprietary service under the Google APIs Terms of Service. The Firebase Admin SDKs are Apache-2.0", "name": "Licence" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "2026-10-06", "b": "2026-09-24", "name": "Last release" }, { "a": "2026-08-14", "b": "2021-11-09", "name": "Terms last updated" }, { "a": "2026-05-18", "b": "2026-10-01", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "yes", "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": "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": "11.5M npm/wk, 3.8M PyPI/wk", "name": "Popularity" } ], "faq": [ { "answer": "Amazon SNS scores 72.8 (BB) on agent readiness against Firebase Cloud Messaging's 69.8 (B), and leads in 3 of 7 scored categories. Firebase Cloud Messaging leads on agent ergonomics, payments \u0026 pricing and maintenance \u0026 community.", "question": "Which is better for AI agents, Amazon SNS or Firebase Cloud Messaging?" }, { "answer": "Firebase Cloud Messaging, at free against $0. per message for Amazon SNS. These are the vendors' published prices for the job.", "question": "Which is cheaper for notify push, Amazon SNS or Firebase Cloud Messaging?" }, { "answer": "Amazon SNS takes an API key or an OAuth sign-in. Firebase Cloud Messaging uses an OAuth sign-in.", "question": "Do Amazon SNS and Firebase Cloud Messaging need an API key?" }, { "answer": "Yes. Amazon SNS has a hosted endpoint at https://sns.us-east-1.amazonaws.com and Firebase Cloud Messaging at https://fcm.googleapis.com.", "question": "Can an agent call Amazon SNS and Firebase Cloud Messaging without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 75 against 66", "Security \u0026 auth, 89 against 68" ], "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": [ "Agent ergonomics, 70 against 65", "Payments \u0026 pricing, 40 against 35", "Maintenance \u0026 community, 83 against 75" ], "also": null, "goodFor": "The push transport under an app that already holds device registrations, at no charge.", "slug": "firebase-cloud-messaging", "watchFor": "Push transport only. No in-app feed, email, SMS, user preferences, digests or templates" } ], "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-magicbell.json", "title": "Amazon SNS vs MagicBell", "url": "https://www.anchorterminal.com/compare/amazon-sns-vs-magicbell" }, { "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/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-firebase-cloud-messaging.json", "title": "Courier vs Firebase Cloud Messaging", "url": "https://www.anchorterminal.com/compare/courier-vs-firebase-cloud-messaging" }, { "json": "https://www.anchorterminal.com/compare/firebase-cloud-messaging-vs-knock.json", "title": "Firebase Cloud Messaging vs Knock", "url": "https://www.anchorterminal.com/compare/firebase-cloud-messaging-vs-knock" }, { "json": "https://www.anchorterminal.com/compare/firebase-cloud-messaging-vs-magicbell.json", "title": "Firebase Cloud Messaging vs MagicBell", "url": "https://www.anchorterminal.com/compare/firebase-cloud-messaging-vs-magicbell" }, { "json": "https://www.anchorterminal.com/compare/firebase-cloud-messaging-vs-novu.json", "title": "Firebase Cloud Messaging vs Novu", "url": "https://www.anchorterminal.com/compare/firebase-cloud-messaging-vs-novu" }, { "json": "https://www.anchorterminal.com/compare/firebase-cloud-messaging-vs-ntfy.json", "title": "Firebase Cloud Messaging vs ntfy", "url": "https://www.anchorterminal.com/compare/firebase-cloud-messaging-vs-ntfy" }, { "json": "https://www.anchorterminal.com/compare/firebase-cloud-messaging-vs-onesignal.json", "title": "Firebase Cloud Messaging vs OneSignal", "url": "https://www.anchorterminal.com/compare/firebase-cloud-messaging-vs-onesignal" }, { "json": "https://www.anchorterminal.com/compare/firebase-cloud-messaging-vs-pushover.json", "title": "Firebase Cloud Messaging vs Pushover", "url": "https://www.anchorterminal.com/compare/firebase-cloud-messaging-vs-pushover" }, { "json": "https://www.anchorterminal.com/compare/firebase-cloud-messaging-vs-suprsend.json", "title": "Firebase Cloud Messaging vs SuprSend", "url": "https://www.anchorterminal.com/compare/firebase-cloud-messaging-vs-suprsend" } ], "scores": [ { "amazon-sns": 75, "by": 9, "edge": "amazon-sns", "firebase-cloud-messaging": 66, "key": "reliability", "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "amazon-sns": 83, "by": 3, "edge": "firebase-cloud-messaging", "firebase-cloud-messaging": 86, "key": "schema", "name": "Schema \u0026 documentation", "weight": 13 }, { "amazon-sns": 65, "by": 5, "edge": "firebase-cloud-messaging", "firebase-cloud-messaging": 70, "key": "ergonomics", "name": "Agent ergonomics", "weight": 13 }, { "amazon-sns": 89, "by": 21, "edge": "amazon-sns", "firebase-cloud-messaging": 68, "key": "security", "name": "Security \u0026 auth", "weight": 14 }, { "amazon-sns": 35, "by": 5, "edge": "firebase-cloud-messaging", "firebase-cloud-messaging": 40, "key": "payments", "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "amazon-sns": 75, "by": 8, "edge": "firebase-cloud-messaging", "firebase-cloud-messaging": 83, "key": "maintenance", "name": "Maintenance \u0026 community", "weight": 7 }, { "amazon-sns": 83, "by": 2, "edge": "amazon-sns", "firebase-cloud-messaging": 81, "key": "transparency", "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "Amazon SNS scores 72.8 (BB) on agent readiness against Firebase Cloud Messaging's 69.8 (B), and leads in 3 of 7 scored categories. Firebase Cloud Messaging leads on 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.", "firebase-cloud-messaging": "Sending is free at any volume, with a published quota of 600,000 messages a minute per project and documented 429 handling. FCM is push transport only. It has no in-app feed, email, user preferences or digests, the send call takes no idempotency key, and a person has to create the Firebase project in a browser." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/amazon-sns-vs-firebase-cloud-messaging", "json": "https://www.anchorterminal.com/compare/amazon-sns-vs-firebase-cloud-messaging.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/amazon-sns-vs-firebase-cloud-messaging.md", "slim": "https://www.anchorterminal.com/compare/amazon-sns-vs-firebase-cloud-messaging.min.md" }, "markdown": "Amazon SNS scores 72.8 (BB) on agent readiness against Firebase Cloud Messaging's 69.8 (B), and leads in 3 of 7 scored categories. Firebase Cloud Messaging leads on agent ergonomics, payments \u0026 pricing and maintenance \u0026 community. Both do notify push.\n\n- Amazon SNS: grade BB, 72.8/100, rank #96 of 842. Markdown https://www.anchorterminal.com/tools/amazon-sns.md · JSON https://www.anchorterminal.com/api/v1/tools/amazon-sns.json\n- Firebase Cloud Messaging: grade B, 69.8/100, rank #162 of 842. Markdown https://www.anchorterminal.com/tools/firebase-cloud-messaging.md · JSON https://www.anchorterminal.com/api/v1/tools/firebase-cloud-messaging.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 66\n- Security \u0026 auth, 89 against 68\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### Firebase Cloud Messaging (B)\n\nGood for: The push transport under an app that already holds device registrations, at no charge.\n\nAhead on:\n- Agent ergonomics, 70 against 65\n- Payments \u0026 pricing, 40 against 35\n- Maintenance \u0026 community, 83 against 75\n\nWatch for: Push transport only. No in-app feed, email, SMS, user preferences, digests or templates\n\n\n## Score by category\n\n| Category | Weight | Amazon SNS | Firebase Cloud Messaging | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 75 | 66 | Amazon SNS +9 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 83 | 86 | Firebase Cloud Messaging +3 |\n| Agent ergonomics | 13% (16.2 this run) | 65 | 70 | Firebase Cloud Messaging +5 |\n| Security \u0026 auth | 14% (17.5 this run) | 89 | 68 | Amazon SNS +21 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 35 | 40 | Firebase Cloud Messaging +5 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 75 | 83 | Firebase Cloud Messaging +8 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 83 | 81 | Amazon SNS +2 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **72.8 · BB** | **69.8 · B** | |\n\n## Facts side by side\n\n| Fact | Amazon SNS | Firebase Cloud Messaging |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Amazon Web Services | Google |\n| Hosted endpoint | `https://sns.us-east-1.amazonaws.com` | `https://fcm.googleapis.com` |\n| Transports | HTTP | HTTP |\n| Auth | OAuth or key | OAuth |\n| Pricing | Pay per use | Free |\n| Price for notify push | $0. per message | free |\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 | Proprietary service under the Google APIs Terms of Service. The Firebase Admin SDKs are Apache-2.0 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| Last release | 2026-10-06 | 2026-09-24 |\n| Terms last updated | 2026-08-14 | 2021-11-09 |\n| Privacy policy last updated | 2026-05-18 | 2026-10-01 |\n| Customer content may train models | not found in the text | yes |\n| Terms restrict automated access | not found in the text | yes |\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 | 11.5M npm/wk, 3.8M PyPI/wk |\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**Firebase Cloud Messaging.** Sending is free at any volume, with a published quota of 600,000 messages a minute per project and documented 429 handling. FCM is push transport only. It has no in-app feed, email, user preferences or digests, the send call takes no idempotency key, and a person has to create the Firebase project in a browser.\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### Firebase Cloud Messaging\n\n1. Mint an access token from a service account with the scope `https://www.googleapis.com/auth/firebase.messaging`, then POST to `https://fcm.googleapis.com/v1/projects/\u003cproject-id\u003e/messages:send`\n2. Set `validate_only` to true to test a message or a registration without sending it\n3. On 429 wait for the `retry-after` header, or 60 seconds if it is absent. Retry 500 and 503 with exponential backoff and jitter, and never retry 400, 401, 403 or 404\n4. Drop a registration when the error is `UNREGISTERED` (404). Keep your own record of sends, because a retry after a timeout can produce a duplicate\n5. Target `fid` in new code. The `token` field is marked deprecated in the API, and device groups stop working after 29 September 2027\n\n## Questions\n\n### Which is better for AI agents, Amazon SNS or Firebase Cloud Messaging?\n\nAmazon SNS scores 72.8 (BB) on agent readiness against Firebase Cloud Messaging's 69.8 (B), and leads in 3 of 7 scored categories. Firebase Cloud Messaging leads on agent ergonomics, payments \u0026 pricing and maintenance \u0026 community.\n\n### Which is cheaper for notify push, Amazon SNS or Firebase Cloud Messaging?\n\nFirebase Cloud Messaging, at free against $0. per message for Amazon SNS. These are the vendors' published prices for the job.\n\n### Do Amazon SNS and Firebase Cloud Messaging need an API key?\n\nAmazon SNS takes an API key or an OAuth sign-in. Firebase Cloud Messaging uses an OAuth sign-in.\n\n### Can an agent call Amazon SNS and Firebase Cloud Messaging without installing anything?\n\nYes. Amazon SNS has a hosted endpoint at https://sns.us-east-1.amazonaws.com and Firebase Cloud Messaging at https://fcm.googleapis.com.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/amazon-sns-vs-firebase-cloud-messaging.json, and with the fewest tokens: https://www.anchorterminal.com/compare/amazon-sns-vs-firebase-cloud-messaging.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"amazon-sns\", \"b\": \"firebase-cloud-messaging\"}`. From a terminal: `anchor compare amazon-sns firebase-cloud-messaging`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/amazon-sns.json and https://www.anchorterminal.com/api/v1/tools/firebase-cloud-messaging.json\n\n## Other comparisons with Amazon SNS or Firebase Cloud Messaging\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 MagicBell](https://www.anchorterminal.com/compare/amazon-sns-vs-magicbell.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- [Amazon SNS vs SuprSend](https://www.anchorterminal.com/compare/amazon-sns-vs-suprsend.md)\n- [Courier vs Firebase Cloud Messaging](https://www.anchorterminal.com/compare/courier-vs-firebase-cloud-messaging.md)\n- [Firebase Cloud Messaging vs Knock](https://www.anchorterminal.com/compare/firebase-cloud-messaging-vs-knock.md)\n- [Firebase Cloud Messaging vs MagicBell](https://www.anchorterminal.com/compare/firebase-cloud-messaging-vs-magicbell.md)\n- [Firebase Cloud Messaging vs Novu](https://www.anchorterminal.com/compare/firebase-cloud-messaging-vs-novu.md)\n- [Firebase Cloud Messaging vs ntfy](https://www.anchorterminal.com/compare/firebase-cloud-messaging-vs-ntfy.md)\n- [Firebase Cloud Messaging vs OneSignal](https://www.anchorterminal.com/compare/firebase-cloud-messaging-vs-onesignal.md)\n- [Firebase Cloud Messaging vs Pushover](https://www.anchorterminal.com/compare/firebase-cloud-messaging-vs-pushover.md)\n- [Firebase Cloud Messaging vs SuprSend](https://www.anchorterminal.com/compare/firebase-cloud-messaging-vs-suprsend.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-10-09", "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 Firebase Cloud Messaging", "url": "" } ], "description": "Amazon SNS scores 72.8 (BB) on agent readiness against Firebase Cloud Messaging's 69.8 (B), and leads in 3 of 7 scored categories. Firebase Cloud Messaging leads on agent ergonomics, payments \u0026 pricing and maintenance \u0026 community. Both do notify push. Category scores, facts…", "facts": [ "Amazon SNS BB 72.8", "Firebase Cloud Messaging B 69.8", "scores" ], "h1": "Amazon SNS vs Firebase Cloud Messaging", "image": "https://www.anchorterminal.com/assets/og/compare-amazon-sns-vs-firebase-cloud-messaging.png", "path": "/compare/amazon-sns-vs-firebase-cloud-messaging", "published": "2026-10-01", "section": "tools", "title": "Amazon SNS vs Firebase Cloud Messaging for AI agents | Anchor Terminal", "toc": null, "updated": "2026-10-09", "url": "https://www.anchorterminal.com/compare/amazon-sns-vs-firebase-cloud-messaging" }, "tokens": { "markdown": 2500, "slim": 680 }, "version": 1 }