{ "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-09T09:26:50.167166367Z", "lastOk": true, "lastStatus": 404, "lastMs": 99, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 39, "p95ms24h": 99, "samples24h": 20, "samples30d": 20, "days": [ { "date": "2026-10-09", "probes": 20, "ok": 20 } ] }, "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-09T09:26:50.167166367Z" } }, "answer": "Firebase Cloud Messaging scores 69.8 (B) on agent readiness against Knock's 66.5 (B), and leads in 3 of 7 scored categories.", "b": { "slug": "knock", "name": "Knock", "vendor": "Knock", "vendorUrl": "https://knock.app", "kind": "http-api", "category": "notifications", "summary": "Notification workflow API.", "url": "https://www.anchorterminal.com/tools/knock", "markdownUrl": "https://www.anchorterminal.com/tools/knock.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/knock.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/knock.json", "repo": "https://github.com/knocklabs/knock-node", "license": "Apache-2.0 (Node SDK)", "transports": [ "http", "streamable-http" ], "remoteUrl": "https://api.knock.app/v1", "packages": [ { "registry": "npm", "name": "@knocklabs/node" }, { "registry": "pypi", "name": "knockapi" } ], "auth": "mixed", "authNotes": "Secret API key per environment as a Bearer token for server calls, and a public key plus signed user tokens for client feeds. The hosted MCP signs in with OAuth or takes a service token (`knock_st_...`) as a Bearer credential for headless use.", "pricing": "freemium", "pricingNotes": "Developer plan free with 10,000 messages a month, 500 guide active users and 500 AI agent credits. Starter $250 a month with 50,000 messages prepaid, then $0.005 a message, 2,500 guide active users ($0.05 each after) and 2,000 agent credits ($0.01 each after). Enterprise is priced by volume or by notified users. A message is one delivery to one user on one channel, and bounced or failed messages aren't billed. No setup fee, billed monthly in arrears (https://knock.app/pricing).", "priceSummary": "$250 / mo", "where": "hosted", "x402": { "level": "no", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": 50, "npmWeekly": 926382, "pypiWeekly": 233669, "asOf": "2026-09-30" }, "docsUrl": "https://docs.knock.app", "llmsTxt": "https://docs.knock.app/llms.txt", "openapi": "https://docs.knock.app/openapi.json", "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-29", "graded": true, "anchor": { "graded": true, "score": 66.5, "grade": "B", "agentReady": false, "rank": 265, "ranked": true, "rankOf": 842, "categoryRank": 6, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 64, "maintenance": 86, "payments": 40, "reliability": 58, "schema": 88, "security": 71, "transparency": 60 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-01" }, "negative": 0, "verdict": "Hosted MCP server with OAuth, six capability toggles and no delete tools. Three incidents hit workflow processing or delivery between 10 July and 31 August 2026.", "bestFor": "A product team that wants a workflow engine with batching, preferences and an in-app feed, and for agents that build and debug workflows through MCP safely.", "strengths": [ "Hosted MCP server with OAuth, six capability toggles and no delete tools", "Idempotency keys on trigger for 24 hours, plus cancellation keys for delayed runs", "Rate limits published in five tiers from 1 to 1,000 requests a second", "Audit logs attribute management API changes to the service token that made them", "Free plan with 10,000 messages a month and no card" ], "weaknesses": [ "Three incidents hit workflow processing or delivery between 10 July and 31 August 2026", "No SLA, Retry-After header or backoff guidance found", "Service tokens carry the creator's full privileges with no expiry, and skip MCP consent", "Starter jumps from free to $250 a month", "Email, SMS and push go through providers you configure and pay for separately" ], "agentNotes": [ "Create the workflow in the dashboard or through the MCP server before you trigger it. Triggers reference it by key", "Send an `Idempotency-Key` on every trigger. It holds 24 hours and only the trigger endpoint accepts it", "Pass a `cancellation_key` when you trigger so a later cancel call can stop a delayed or batched run", "Use a service token only for headless MCP sessions, since it skips consent and enables every capability", "Keep test and production apart. Rate limits and keys are scoped to an environment" ], "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": 66.5 } ], "editorialScores": { "ergonomics": 64, "maintenance": 86, "payments": 40, "reliability": 58, "schema": 88, "security": 71, "transparency": 39 }, "provenanceScore": 81 }, "connect": { "http": "curl -X POST https://api.knock.app/v1/workflows/new-comment/trigger \\\n -H \"Authorization: Bearer $KNOCK_SECRET_API_KEY\" -H \"Content-Type: application/json\" \\\n -d '{\"recipients\":[\"user_123\"],\"data\":{\"message\":\"Build finished\"}}'", "claudeCode": "claude mcp add --transport http knock https://mcp.knock.app/mcp", "config": { "mcpServers": { "knock": { "headers": { "Authorization": "Bearer ${KNOCK_SERVICE_TOKEN}" }, "type": "http", "url": "https://mcp.knock.app/mcp" } } } }, "letme": { "capability": "https://letme.dev/notify.push", "tool": "https://letme.dev/knock" }, "area": "everyday", "unitPrices": [ { "item": "Starter", "unit": "month", "usd": 250, "note": "50,000 messages included" }, { "item": "Starter overage", "unit": "message", "usd": 0.005 }, { "item": "AI agent credit overage", "unit": "credit", "usd": 0.01 } ], "provenance": { "legalEntity": "Knock Labs, Inc.", "domain": "knock.app", "domainRegistered": "2020-08-28", "endpointOnVendorDomain": true, "terms": "https://knock.app/terms", "privacy": "https://knock.app/legal/privacy-policy", "statusPage": "https://status.knock.app", "changelog": "https://knock.app/changelog", "securityTxt": "none", "checked": "2026-09-30", "notes": [ "Terms are governed by New York law. A separate data processing addendum is published at knock.app/legal/data-processing-addendum.", "The status page tracks the in-dashboard agent as its own component." ], "score": 81 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/knock.json", "live": { "slug": "knock", "probe": { "target": "https://api.knock.app/v1", "method": "get", "lastAt": "2026-10-09T09:26:54.116605287Z", "lastOk": true, "lastStatus": 404, "lastMs": 308, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 297, "p95ms24h": 330, "samples24h": 261, "samples30d": 2085, "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": 101, "ok": 101 } ] }, "vendorStatus": { "page": "https://status.knock.app", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-09T09:25:16.708318188Z" }, "versions": [ { "registry": "github", "name": "knocklabs/knock-node", "version": "v1.36.0", "released": "2026-09-30", "seenAt": "2026-10-08T16:17:59.410254776Z" }, { "registry": "npm", "name": "@knocklabs/node", "version": "1.36.0", "seenAt": "2026-10-08T16:17:55.433846604Z" }, { "registry": "pypi", "name": "knockapi", "version": "1.31.0", "released": "2026-09-30", "seenAt": "2026-10-08T16:17:59.212196523Z" } ], "githubStars": 50, "npmWeekly": 950212, "pypiWeekly": 196946, "securityTxt": { "url": "https://knock.app/.well-known/security.txt", "state": "none", "checkedAt": "2026-10-08T15:38:33.618077645Z" }, "llmsTxt": { "url": "https://docs.knock.app/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-10-08T14:00:33.752054984Z" }, "domain": { "domain": "knock.app", "registered": "2020-08-28", "source": "https://pubapi.registry.google/rdap/domain/knock.app", "checkedAt": "2026-10-04T13:04:01.050922733Z" }, "pages": [ { "url": "https://knock.app/changelog", "kind": "changelog", "status": 200, "checkedAt": "2026-10-08T18:21:08.063606233Z", "changedAt": "2026-10-07T18:06:43.405248203Z", "fingerprint": "c223a15a4932" }, { "url": "https://knock.app/pricing", "kind": "pricing", "status": 200, "checkedAt": "2026-10-08T18:21:12.284491595Z", "changedAt": "2026-10-07T18:06:47.972051612Z", "fingerprint": "88884ef8f29a" }, { "url": "https://knock.app/legal/privacy-policy", "kind": "privacy", "status": 200, "checkedAt": "2026-10-08T18:21:10.384869361Z", "changedAt": "2026-10-07T18:06:45.716206824Z", "fingerprint": "8b88939fcacf" }, { "url": "https://knock.app/terms", "kind": "terms", "status": 200, "checkedAt": "2026-10-08T18:21:14.116260889Z", "changedAt": "2026-10-07T18:06:49.489482879Z", "fingerprint": "2855cc420ae7" } ], "updatedAt": "2026-10-09T09:26:54.116605287Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Google", "b": "Knock", "name": "Vendor" }, { "a": "https://fcm.googleapis.com", "b": "https://api.knock.app/v1", "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": "Apache-2.0 (Node SDK)", "name": "Licence" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "2026-09-24", "b": "2026-09-29", "name": "Last release" }, { "a": "2021-11-09", "b": "2026-03-04", "name": "Terms last updated" }, { "a": "2026-10-01", "b": "2026-03-04", "name": "Privacy policy last updated" }, { "a": "yes", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "yes", "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": "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": "50 stars, 926k npm/wk, 234k PyPI/wk", "name": "Popularity" }, { "a": "none", "b": "3.5/5 (2)", "name": "Agent reviews" } ], "faq": [ { "answer": "Firebase Cloud Messaging scores 69.8 (B) on agent readiness against Knock's 66.5 (B), and leads in 3 of 7 scored categories.", "question": "Which is better for AI agents, Firebase Cloud Messaging or Knock?" }, { "answer": "Firebase Cloud Messaging uses an OAuth sign-in. Knock takes an API key or an OAuth sign-in.", "question": "Do Firebase Cloud Messaging and Knock need an API key?" }, { "answer": "Yes. Firebase Cloud Messaging has a hosted endpoint at https://fcm.googleapis.com and Knock at https://api.knock.app/v1.", "question": "Can an agent call Firebase Cloud Messaging and Knock without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 66 against 58", "Agent ergonomics, 70 against 64", "Transparency \u0026 trust, 81 against 60" ], "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": null, "also": null, "goodFor": "A product team that wants a workflow engine with batching, preferences and an in-app feed, and for agents that build and debug workflows through MCP safely.", "slug": "knock", "watchFor": "Three incidents hit workflow processing or delivery between 10 July and 31 August 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-knock.json", "title": "Amazon SNS vs Knock", "url": "https://www.anchorterminal.com/compare/amazon-sns-vs-knock" }, { "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-knock.json", "title": "Courier vs Knock", "url": "https://www.anchorterminal.com/compare/courier-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" }, { "json": "https://www.anchorterminal.com/compare/knock-vs-magicbell.json", "title": "Knock vs MagicBell", "url": "https://www.anchorterminal.com/compare/knock-vs-magicbell" }, { "json": "https://www.anchorterminal.com/compare/knock-vs-novu.json", "title": "Knock vs Novu", "url": "https://www.anchorterminal.com/compare/knock-vs-novu" }, { "json": "https://www.anchorterminal.com/compare/knock-vs-ntfy.json", "title": "Knock vs ntfy", "url": "https://www.anchorterminal.com/compare/knock-vs-ntfy" }, { "json": "https://www.anchorterminal.com/compare/knock-vs-onesignal.json", "title": "Knock vs OneSignal", "url": "https://www.anchorterminal.com/compare/knock-vs-onesignal" }, { "json": "https://www.anchorterminal.com/compare/knock-vs-pushover.json", "title": "Knock vs Pushover", "url": "https://www.anchorterminal.com/compare/knock-vs-pushover" }, { "json": "https://www.anchorterminal.com/compare/knock-vs-suprsend.json", "title": "Knock vs SuprSend", "url": "https://www.anchorterminal.com/compare/knock-vs-suprsend" } ], "scores": [ { "by": 8, "edge": "firebase-cloud-messaging", "firebase-cloud-messaging": 66, "key": "reliability", "knock": 58, "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 2, "edge": "knock", "firebase-cloud-messaging": 86, "key": "schema", "knock": 88, "name": "Schema \u0026 documentation", "weight": 13 }, { "by": 6, "edge": "firebase-cloud-messaging", "firebase-cloud-messaging": 70, "key": "ergonomics", "knock": 64, "name": "Agent ergonomics", "weight": 13 }, { "by": 3, "edge": "knock", "firebase-cloud-messaging": 68, "key": "security", "knock": 71, "name": "Security \u0026 auth", "weight": 14 }, { "by": 0, "edge": "", "firebase-cloud-messaging": 40, "key": "payments", "knock": 40, "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 3, "edge": "knock", "firebase-cloud-messaging": 83, "key": "maintenance", "knock": 86, "name": "Maintenance \u0026 community", "weight": 7 }, { "by": 21, "edge": "firebase-cloud-messaging", "firebase-cloud-messaging": 81, "key": "transparency", "knock": 60, "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "Firebase Cloud Messaging scores 69.8 (B) on agent readiness against Knock's 66.5 (B), and leads in 3 of 7 scored categories. 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.", "knock": "Hosted MCP server with OAuth, six capability toggles and no delete tools. Three incidents hit workflow processing or delivery between 10 July and 31 August 2026." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/firebase-cloud-messaging-vs-knock", "json": "https://www.anchorterminal.com/compare/firebase-cloud-messaging-vs-knock.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/firebase-cloud-messaging-vs-knock.md", "slim": "https://www.anchorterminal.com/compare/firebase-cloud-messaging-vs-knock.min.md" }, "markdown": "Firebase Cloud Messaging scores 69.8 (B) on agent readiness against Knock's 66.5 (B), and leads in 3 of 7 scored categories. 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- Knock: grade B, 66.5/100, rank #265 of 842. Markdown https://www.anchorterminal.com/tools/knock.md · JSON https://www.anchorterminal.com/api/v1/tools/knock.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- Reliability, 66 against 58\n- Agent ergonomics, 70 against 64\n- Transparency \u0026 trust, 81 against 60\n\nWatch for: Push transport only. No in-app feed, email, SMS, user preferences, digests or templates\n\n### Knock (B)\n\nGood for: A product team that wants a workflow engine with batching, preferences and an in-app feed, and for agents that build and debug workflows through MCP safely.\n\nWatch for: Three incidents hit workflow processing or delivery between 10 July and 31 August 2026\n\n\n## Score by category\n\n| Category | Weight | Firebase Cloud Messaging | Knock | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 66 | 58 | Firebase Cloud Messaging +8 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 86 | 88 | Knock +2 |\n| Agent ergonomics | 13% (16.2 this run) | 70 | 64 | Firebase Cloud Messaging +6 |\n| Security \u0026 auth | 14% (17.5 this run) | 68 | 71 | Knock +3 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 40 | 40 | even |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 83 | 86 | Knock +3 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 81 | 60 | Firebase Cloud Messaging +21 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **69.8 · B** | **66.5 · B** | |\n\n## Facts side by side\n\n| Fact | Firebase Cloud Messaging | Knock |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Google | Knock |\n| Hosted endpoint | `https://fcm.googleapis.com` | `https://api.knock.app/v1` |\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 | Apache-2.0 (Node SDK) |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| Last release | 2026-09-24 | 2026-09-29 |\n| Terms last updated | 2021-11-09 | 2026-03-04 |\n| Privacy policy last updated | 2026-10-01 | 2026-03-04 |\n| Customer content may train models | yes | not found in the text |\n| Terms restrict automated access | yes | 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 | yes |\n| Arbitration or class-action waiver | not found in the text | yes |\n| Popularity | 11.5M npm/wk, 3.8M PyPI/wk | 50 stars, 926k npm/wk, 234k 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**Knock.** Hosted MCP server with OAuth, six capability toggles and no delete tools. Three incidents hit workflow processing or delivery between 10 July and 31 August 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### Knock\n\n1. Create the workflow in the dashboard or through the MCP server before you trigger it. Triggers reference it by key\n2. Send an `Idempotency-Key` on every trigger. It holds 24 hours and only the trigger endpoint accepts it\n3. Pass a `cancellation_key` when you trigger so a later cancel call can stop a delayed or batched run\n4. Use a service token only for headless MCP sessions, since it skips consent and enables every capability\n5. Keep test and production apart. Rate limits and keys are scoped to an environment\n\n## Questions\n\n### Which is better for AI agents, Firebase Cloud Messaging or Knock?\n\nFirebase Cloud Messaging scores 69.8 (B) on agent readiness against Knock's 66.5 (B), and leads in 3 of 7 scored categories.\n\n### Do Firebase Cloud Messaging and Knock need an API key?\n\nFirebase Cloud Messaging uses an OAuth sign-in. Knock takes an API key or an OAuth sign-in.\n\n### Can an agent call Firebase Cloud Messaging and Knock without installing anything?\n\nYes. Firebase Cloud Messaging has a hosted endpoint at https://fcm.googleapis.com and Knock at https://api.knock.app/v1.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/firebase-cloud-messaging-vs-knock.json, and with the fewest tokens: https://www.anchorterminal.com/compare/firebase-cloud-messaging-vs-knock.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"firebase-cloud-messaging\", \"b\": \"knock\"}`. From a terminal: `anchor compare firebase-cloud-messaging knock`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/firebase-cloud-messaging.json and https://www.anchorterminal.com/api/v1/tools/knock.json\n\n## Other comparisons with Firebase Cloud Messaging or Knock\n\n- [Amazon SNS vs Firebase Cloud Messaging](https://www.anchorterminal.com/compare/amazon-sns-vs-firebase-cloud-messaging.md)\n- [Amazon SNS vs Knock](https://www.anchorterminal.com/compare/amazon-sns-vs-knock.md)\n- [Courier vs Firebase Cloud Messaging](https://www.anchorterminal.com/compare/courier-vs-firebase-cloud-messaging.md)\n- [Courier vs Knock](https://www.anchorterminal.com/compare/courier-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- [Knock vs MagicBell](https://www.anchorterminal.com/compare/knock-vs-magicbell.md)\n- [Knock vs Novu](https://www.anchorterminal.com/compare/knock-vs-novu.md)\n- [Knock vs ntfy](https://www.anchorterminal.com/compare/knock-vs-ntfy.md)\n- [Knock vs OneSignal](https://www.anchorterminal.com/compare/knock-vs-onesignal.md)\n- [Knock vs Pushover](https://www.anchorterminal.com/compare/knock-vs-pushover.md)\n- [Knock vs SuprSend](https://www.anchorterminal.com/compare/knock-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 Knock", "url": "" } ], "description": "Firebase Cloud Messaging scores 69.8 (B) on agent readiness against Knock's 66.5 (B), and leads in 3 of 7 scored categories. Both do notify push. Category scores, facts, verdicts and agent notes side by side.", "facts": [ "Firebase Cloud Messaging B 69.8", "Knock B 66.5", "scores" ], "h1": "Firebase Cloud Messaging vs Knock", "image": "https://www.anchorterminal.com/assets/og/compare-firebase-cloud-messaging-vs-knock.png", "path": "/compare/firebase-cloud-messaging-vs-knock", "published": "2026-10-01", "section": "tools", "title": "Firebase Cloud Messaging vs Knock for AI agents, B 69.8 vs B 66.5", "toc": null, "updated": "2026-10-09", "url": "https://www.anchorterminal.com/compare/firebase-cloud-messaging-vs-knock" }, "tokens": { "markdown": 2150, "slim": 630 }, "version": 1 }