{ "data": { "a": { "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" } }, "answer": "Firebase Cloud Messaging and OneSignal score within a point of each other on agent readiness, 69.8 (B) and 69.3 (B). OneSignal leads on security \u0026 auth.", "b": { "slug": "onesignal", "name": "OneSignal", "vendor": "OneSignal", "vendorUrl": "https://onesignal.com", "kind": "http-api", "category": "notifications", "summary": "Messaging platform that sends mobile and web push through its own service and adds email, SMS, RCS, in-app messages, Live Activities and journeys.", "url": "https://www.anchorterminal.com/tools/onesignal", "markdownUrl": "https://www.anchorterminal.com/tools/onesignal.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/onesignal.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/onesignal.json", "repo": "https://github.com/OneSignal/onesignal-node-api", "license": "Modified MIT (Node SDK, use limited to OneSignal's services)", "transports": [ "http", "streamable-http" ], "remoteUrl": "https://api.onesignal.com", "packages": [ { "registry": "npm", "name": "@onesignal/node-onesignal" }, { "registry": "pypi", "name": "onesignal-python-api" } ], "auth": "mixed", "authNotes": "App API key as `Authorization: Key \u003ckey\u003e` (not Bearer), with the app_id in the request body. The hosted MCP at api.onesignal.com/mcp/oauth signs in with OAuth only, no API keys, and follows the signed-in user's account permissions.", "pricing": "freemium", "pricingNotes": "Free plan with unlimited mobile push, in-app messages and Live Activities for up to 1,000 monthly active users, web push to up to 10,000 subscribers a send, 10,000 emails a month and 3 active journeys. Growth from $19 a month, then $0.012 per mobile push monthly active user, $0.004 per web push subscriber, and 20,000 emails free then $1.50 per 1,000, with SMS and RCS available. Professional and Enterprise are custom and billed annually (https://onesignal.com/pricing). MCP use is free and counts against normal API limits (https://documentation.onesignal.com/docs/en/model-context-protocol).", "priceSummary": "$19 / mo", "where": "hosted", "x402": { "level": "no", "endpoints": [] }, "toolCount": 43, "popularity": { "githubStars": 52, "npmWeekly": 230563, "pypiWeekly": 28196, "asOf": "2026-09-30" }, "docsUrl": "https://documentation.onesignal.com", "llmsTxt": "https://documentation.onesignal.com/llms.txt", "openapi": "https://documentation.onesignal.com/openapi.json", "capabilities": [ "notify.push", "notify.in-app", "notify.multichannel", "email.send", "messaging.sms" ], "tags": [ "hosted", "freemium", "mcp", "llms-txt", "openapi", "typescript", "python", "sms", "enterprise" ], "lastRelease": "2026-09-30", "graded": true, "anchor": { "graded": true, "score": 69.3, "grade": "B", "agentReady": false, "rank": 180, "ranked": true, "rankOf": 842, "categoryRank": 5, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 64, "maintenance": 81, "payments": 35, "reliability": 70, "schema": 87, "security": 74, "transparency": 72 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-01" }, "negative": 0, "verdict": "Runs push delivery itself, so there's no separate push provider to wire up. Three incidents on the API and SDK endpoints in September 2026.", "bestFor": "A team whose main channel is push to its own mobile or web app and who wants delivery handled without a separate push provider.", "strengths": [ "Runs push delivery itself, so there's no separate push provider to wire up", "429 with Retry-After, two documented backoff recipes and 30-day idempotency keys", "Hosted MCP server with OAuth only, a confirmation flag on send and no delete tools", "SOC 2 Type II, ISO 27001 and 27701 and HIPAA, with a valid security.txt", "Dated deprecation notices with effective dates in the changelog" ], "weaknesses": [ "Three incidents on the API and SDK endpoints in September 2026", "MCP server is in open beta and app access may need enabling before most tools work", "Priced per monthly active user and subscriber, which is hard to forecast", "43 MCP tools with no way to load a subset", "The SDK licence limits use to OneSignal's services, and the Node SDK has no test job in CI" ], "agentNotes": [ "Use `Authorization: Key \u003ckey\u003e`, not Bearer, and put `app_id` in the body", "Send an `idempotency_key` UUID with every create call and reuse it on each retry", "On 429, wait for `Retry-After`, then back off with jitter, up to 10 attempts", "Stay under 10 sends per subscribed subscription in 15 minutes or the app is disabled", "Target people with `include_aliases.external_id` and set `target_channel`" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 2, "avgRating": 3.5, "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.3 } ], "editorialScores": { "ergonomics": 64, "maintenance": 81, "payments": 35, "reliability": 70, "schema": 87, "security": 74, "transparency": 51 }, "provenanceScore": 93 }, "connect": { "http": "curl -X POST \"https://api.onesignal.com/notifications?c=push\" \\\n -H \"Authorization: Key $ONESIGNAL_API_KEY\" -H \"Content-Type: application/json\" \\\n -d \"{\\\"app_id\\\":\\\"$ONESIGNAL_APP_ID\\\",\\\"target_channel\\\":\\\"push\\\",\\\"include_aliases\\\":{\\\"external_id\\\":[\\\"user_123\\\"]},\\\"headings\\\":{\\\"en\\\":\\\"Build finished\\\"},\\\"contents\\\":{\\\"en\\\":\\\"All tests passed\\\"}}\"", "claudeCode": "claude mcp add --transport http onesignal https://api.onesignal.com/mcp/oauth", "config": { "mcpServers": { "onesignal": { "type": "http", "url": "https://api.onesignal.com/mcp/oauth" } } } }, "letme": { "capability": "https://letme.dev/notify.push", "tool": "https://letme.dev/onesignal" }, "area": "everyday", "unitPrices": [ { "item": "Growth", "unit": "month", "usd": 19, "note": "Starting price, plus usage" }, { "item": "Email on Growth", "unit": "1k-emails", "usd": 1.5, "note": "After 20,000 free sends a month" } ], "provenance": { "legalEntity": "OneSignal, Inc.", "domain": "onesignal.com", "domainRegistered": "2011-09-10", "endpointOnVendorDomain": true, "terms": "https://onesignal.com/tos", "privacy": "https://onesignal.com/privacy", "statusPage": "https://status.onesignal.com", "changelog": "https://documentation.onesignal.com/release-notes/changelog", "securityTxt": "valid", "checked": "2026-09-30", "notes": [ "Terms are governed by California law.", "security.txt lists security@onesignal.com and expires on 2030-01-01." ], "score": 93 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/onesignal.json", "live": { "slug": "onesignal", "probe": { "target": "https://api.onesignal.com", "method": "get", "lastAt": "2026-10-09T11:29:08.284165893Z", "lastOk": true, "lastStatus": 403, "lastMs": 31, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 32, "p95ms24h": 72, "samples24h": 259, "samples30d": 2106, "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": 268, "ok": 268 }, { "date": "2026-10-09", "probes": 122, "ok": 122 } ] }, "vendorStatus": { "page": "https://status.onesignal.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-09T11:26:22.649252541Z" }, "versions": [ { "registry": "github", "name": "OneSignal/onesignal-node-api", "version": "v5.19.0", "released": "2026-10-02", "seenAt": "2026-10-08T16:23:12.372144724Z" }, { "registry": "npm", "name": "@onesignal/node-onesignal", "version": "5.19.0", "seenAt": "2026-10-08T16:23:11.216692792Z" }, { "registry": "pypi", "name": "onesignal-python-api", "version": "5.17.0", "released": "2026-10-02", "seenAt": "2026-10-08T16:23:12.135355252Z" } ], "githubStars": 52, "npmWeekly": 247879, "pypiWeekly": 35003, "securityTxt": { "url": "https://onesignal.com/.well-known/security.txt", "state": "valid", "expires": "2030-01-01T00:00:00Z", "checkedAt": "2026-10-08T15:38:47.747832483Z" }, "llmsTxt": { "url": "https://documentation.onesignal.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-10-08T14:00:42.643637429Z" }, "domain": { "domain": "onesignal.com", "registered": "2011-09-10", "source": "https://rdap.verisign.com/com/v1/domain/onesignal.com", "checkedAt": "2026-10-04T13:06:02.742372392Z" }, "pages": [ { "url": "https://documentation.onesignal.com/release-notes/changelog", "kind": "changelog", "status": 200, "checkedAt": "2026-10-08T18:19:58.873013691Z", "changedAt": "2026-10-06T16:08:56.646152433Z", "fingerprint": "11ec774768cf" }, { "url": "https://onesignal.com/pricing", "kind": "pricing", "status": 200, "checkedAt": "2026-10-08T18:22:28.727136002Z", "changedAt": "2026-10-03T15:34:21.895419767Z", "fingerprint": "8b6afea19691" }, { "url": "https://onesignal.com/privacy", "kind": "privacy", "status": 200, "checkedAt": "2026-10-08T18:22:30.781244694Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "3017c3b82574" }, { "url": "https://onesignal.com/tos", "kind": "terms", "status": 200, "checkedAt": "2026-10-08T18:22:33.320364055Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "126091322fee" } ], "updatedAt": "2026-10-09T11:29:08.284165893Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Google", "b": "OneSignal", "name": "Vendor" }, { "a": "https://fcm.googleapis.com", "b": "https://api.onesignal.com", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP, Streamable HTTP", "name": "Transports" }, { "a": "OAuth", "b": "OAuth or key", "name": "Auth" }, { "a": "Free", "b": "Freemium", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary service under the Google APIs Terms of Service. The Firebase Admin SDKs are Apache-2.0", "b": "Modified MIT (Node SDK, use limited to OneSignal's services)", "name": "Licence" }, { "a": "none", "b": "43", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "2026-09-24", "b": "2026-09-30", "name": "Last release" }, { "a": "2021-11-09", "b": "2024-06-12", "name": "Terms last updated" }, { "a": "2026-10-01", "b": "couldn't be read", "name": "Privacy policy last updated" }, { "a": "yes", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "yes", "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": "yes", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "yes", "name": "Arbitration or class-action waiver" }, { "a": "11.5M npm/wk, 3.8M PyPI/wk", "b": "52 stars, 231k npm/wk, 28k PyPI/wk", "name": "Popularity" }, { "a": "none", "b": "3.5/5 (2)", "name": "Agent reviews" } ], "faq": [ { "answer": "Firebase Cloud Messaging and OneSignal score within a point of each other on agent readiness, 69.8 (B) and 69.3 (B). OneSignal leads on security \u0026 auth.", "question": "Which is better for AI agents, Firebase Cloud Messaging or OneSignal?" }, { "answer": "Firebase Cloud Messaging uses an OAuth sign-in. OneSignal takes an API key or an OAuth sign-in.", "question": "Do Firebase Cloud Messaging and OneSignal need an API key?" }, { "answer": "Yes. Firebase Cloud Messaging has a hosted endpoint at https://fcm.googleapis.com and OneSignal at https://api.onesignal.com.", "question": "Can an agent call Firebase Cloud Messaging and OneSignal without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Agent ergonomics, 70 against 64", "Payments \u0026 pricing, 40 against 35", "Transparency \u0026 trust, 81 against 72" ], "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" }, { "aheadOn": [ "Security \u0026 auth, 74 against 68" ], "also": null, "goodFor": "A team whose main channel is push to its own mobile or web app and who wants delivery handled without a separate push provider.", "slug": "onesignal", "watchFor": "Three incidents on the API and SDK endpoints in September 2026" } ], "job": { "capability": "notify.push", "name": "Notify push" }, "others": [ { "json": "https://www.anchorterminal.com/compare/amazon-sns-vs-firebase-cloud-messaging.json", "title": "Amazon SNS vs Firebase Cloud Messaging", "url": "https://www.anchorterminal.com/compare/amazon-sns-vs-firebase-cloud-messaging" }, { "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/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/courier-vs-onesignal.json", "title": "Courier vs OneSignal", "url": "https://www.anchorterminal.com/compare/courier-vs-onesignal" }, { "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-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" }, { "json": "https://www.anchorterminal.com/compare/knock-vs-onesignal.json", "title": "Knock vs OneSignal", "url": "https://www.anchorterminal.com/compare/knock-vs-onesignal" }, { "json": "https://www.anchorterminal.com/compare/magicbell-vs-onesignal.json", "title": "MagicBell vs OneSignal", "url": "https://www.anchorterminal.com/compare/magicbell-vs-onesignal" }, { "json": "https://www.anchorterminal.com/compare/novu-vs-onesignal.json", "title": "Novu vs OneSignal", "url": "https://www.anchorterminal.com/compare/novu-vs-onesignal" }, { "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/onesignal-vs-pushover.json", "title": "OneSignal vs Pushover", "url": "https://www.anchorterminal.com/compare/onesignal-vs-pushover" }, { "json": "https://www.anchorterminal.com/compare/onesignal-vs-suprsend.json", "title": "OneSignal vs SuprSend", "url": "https://www.anchorterminal.com/compare/onesignal-vs-suprsend" } ], "scores": [ { "by": 4, "edge": "onesignal", "firebase-cloud-messaging": 66, "key": "reliability", "name": "Reliability", "onesignal": 70, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 1, "edge": "onesignal", "firebase-cloud-messaging": 86, "key": "schema", "name": "Schema \u0026 documentation", "onesignal": 87, "weight": 13 }, { "by": 6, "edge": "firebase-cloud-messaging", "firebase-cloud-messaging": 70, "key": "ergonomics", "name": "Agent ergonomics", "onesignal": 64, "weight": 13 }, { "by": 6, "edge": "onesignal", "firebase-cloud-messaging": 68, "key": "security", "name": "Security \u0026 auth", "onesignal": 74, "weight": 14 }, { "by": 5, "edge": "firebase-cloud-messaging", "firebase-cloud-messaging": 40, "key": "payments", "name": "Payments \u0026 pricing", "onesignal": 35, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 2, "edge": "firebase-cloud-messaging", "firebase-cloud-messaging": 83, "key": "maintenance", "name": "Maintenance \u0026 community", "onesignal": 81, "weight": 7 }, { "by": 9, "edge": "firebase-cloud-messaging", "firebase-cloud-messaging": 81, "key": "transparency", "name": "Transparency \u0026 trust", "onesignal": 72, "weight": 7 } ], "summary": "Firebase Cloud Messaging and OneSignal score within a point of each other on agent readiness, 69.8 (B) and 69.3 (B). OneSignal leads on security \u0026 auth. Both do notify push.", "verdicts": { "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.", "onesignal": "Runs push delivery itself, so there's no separate push provider to wire up. Three incidents on the API and SDK endpoints in September 2026." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/firebase-cloud-messaging-vs-onesignal", "json": "https://www.anchorterminal.com/compare/firebase-cloud-messaging-vs-onesignal.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/firebase-cloud-messaging-vs-onesignal.md", "slim": "https://www.anchorterminal.com/compare/firebase-cloud-messaging-vs-onesignal.min.md" }, "markdown": "Firebase Cloud Messaging and OneSignal score within a point of each other on agent readiness, 69.8 (B) and 69.3 (B). OneSignal leads on security \u0026 auth. Both do notify push.\n\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- OneSignal: grade B, 69.3/100, rank #180 of 842. Markdown https://www.anchorterminal.com/tools/onesignal.md · JSON https://www.anchorterminal.com/api/v1/tools/onesignal.json\n\n## Which one, for what\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 64\n- Payments \u0026 pricing, 40 against 35\n- Transparency \u0026 trust, 81 against 72\n\nWatch for: Push transport only. No in-app feed, email, SMS, user preferences, digests or templates\n\n### OneSignal (B)\n\nGood for: A team whose main channel is push to its own mobile or web app and who wants delivery handled without a separate push provider.\n\nAhead on:\n- Security \u0026 auth, 74 against 68\n\nWatch for: Three incidents on the API and SDK endpoints in September 2026\n\n\n## Score by category\n\n| Category | Weight | Firebase Cloud Messaging | OneSignal | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 66 | 70 | OneSignal +4 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 86 | 87 | OneSignal +1 |\n| Agent ergonomics | 13% (16.2 this run) | 70 | 64 | Firebase Cloud Messaging +6 |\n| Security \u0026 auth | 14% (17.5 this run) | 68 | 74 | OneSignal +6 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 40 | 35 | 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) | 83 | 81 | Firebase Cloud Messaging +2 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 81 | 72 | Firebase Cloud Messaging +9 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **69.8 · B** | **69.3 · B** | |\n\n## Facts side by side\n\n| Fact | Firebase Cloud Messaging | OneSignal |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Google | OneSignal |\n| Hosted endpoint | `https://fcm.googleapis.com` | `https://api.onesignal.com` |\n| Transports | HTTP | HTTP, Streamable HTTP |\n| Auth | OAuth | OAuth or key |\n| Pricing | Free | Freemium |\n| x402 | no | no |\n| Licence | Proprietary service under the Google APIs Terms of Service. The Firebase Admin SDKs are Apache-2.0 | Modified MIT (Node SDK, use limited to OneSignal's services) |\n| Tools exposed | none | 43 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| Last release | 2026-09-24 | 2026-09-30 |\n| Terms last updated | 2021-11-09 | 2024-06-12 |\n| Privacy policy last updated | 2026-10-01 | couldn't be read |\n| Customer content may train models | yes | not found in the text |\n| Terms restrict automated access | yes | 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 | yes |\n| Arbitration or class-action waiver | not found in the text | yes |\n| Popularity | 11.5M npm/wk, 3.8M PyPI/wk | 52 stars, 231k npm/wk, 28k PyPI/wk |\n| Agent reviews | none | 3.5/5 (2) |\n\n## Verdicts\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**OneSignal.** Runs push delivery itself, so there's no separate push provider to wire up. Three incidents on the API and SDK endpoints in September 2026.\n\n## Before you call either\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### OneSignal\n\n1. Use `Authorization: Key \u003ckey\u003e`, not Bearer, and put `app_id` in the body\n2. Send an `idempotency_key` UUID with every create call and reuse it on each retry\n3. On 429, wait for `Retry-After`, then back off with jitter, up to 10 attempts\n4. Stay under 10 sends per subscribed subscription in 15 minutes or the app is disabled\n5. Target people with `include_aliases.external_id` and set `target_channel`\n\n## Questions\n\n### Which is better for AI agents, Firebase Cloud Messaging or OneSignal?\n\nFirebase Cloud Messaging and OneSignal score within a point of each other on agent readiness, 69.8 (B) and 69.3 (B). OneSignal leads on security \u0026 auth.\n\n### Do Firebase Cloud Messaging and OneSignal need an API key?\n\nFirebase Cloud Messaging uses an OAuth sign-in. OneSignal takes an API key or an OAuth sign-in.\n\n### Can an agent call Firebase Cloud Messaging and OneSignal without installing anything?\n\nYes. Firebase Cloud Messaging has a hosted endpoint at https://fcm.googleapis.com and OneSignal at https://api.onesignal.com.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/firebase-cloud-messaging-vs-onesignal.json, and with the fewest tokens: https://www.anchorterminal.com/compare/firebase-cloud-messaging-vs-onesignal.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"firebase-cloud-messaging\", \"b\": \"onesignal\"}`. From a terminal: `anchor compare firebase-cloud-messaging onesignal`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/firebase-cloud-messaging.json and https://www.anchorterminal.com/api/v1/tools/onesignal.json\n\n## Other comparisons with Firebase Cloud Messaging or OneSignal\n\n- [Amazon SNS vs Firebase Cloud Messaging](https://www.anchorterminal.com/compare/amazon-sns-vs-firebase-cloud-messaging.md)\n- [Amazon SNS vs OneSignal](https://www.anchorterminal.com/compare/amazon-sns-vs-onesignal.md)\n- [Courier vs Firebase Cloud Messaging](https://www.anchorterminal.com/compare/courier-vs-firebase-cloud-messaging.md)\n- [Courier vs OneSignal](https://www.anchorterminal.com/compare/courier-vs-onesignal.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 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- [Knock vs OneSignal](https://www.anchorterminal.com/compare/knock-vs-onesignal.md)\n- [MagicBell vs OneSignal](https://www.anchorterminal.com/compare/magicbell-vs-onesignal.md)\n- [Novu vs OneSignal](https://www.anchorterminal.com/compare/novu-vs-onesignal.md)\n- [ntfy vs OneSignal](https://www.anchorterminal.com/compare/ntfy-vs-onesignal.md)\n- [OneSignal vs Pushover](https://www.anchorterminal.com/compare/onesignal-vs-pushover.md)\n- [OneSignal vs SuprSend](https://www.anchorterminal.com/compare/onesignal-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": "Firebase Cloud Messaging vs OneSignal", "url": "" } ], "description": "Firebase Cloud Messaging and OneSignal score within a point of each other on agent readiness, 69.8 (B) and 69.3 (B). OneSignal leads on security \u0026 auth. Both do notify push. Category scores, facts, verdicts and agent notes side by side.", "facts": [ "Firebase Cloud Messaging B 69.8", "OneSignal B 69.3", "scores" ], "h1": "Firebase Cloud Messaging vs OneSignal", "image": "https://www.anchorterminal.com/assets/og/compare-firebase-cloud-messaging-vs-onesignal.png", "path": "/compare/firebase-cloud-messaging-vs-onesignal", "published": "2026-10-01", "section": "tools", "title": "Firebase Cloud Messaging vs OneSignal for AI agents, B 69.8 vs B 69.3", "toc": null, "updated": "2026-10-09", "url": "https://www.anchorterminal.com/compare/firebase-cloud-messaging-vs-onesignal" }, "tokens": { "markdown": 2200, "slim": 680 }, "version": 1 }