Get an audit

Head to head · Notify push · October 2026 research run

Firebase Cloud Messaging vs ntfy

Firebase Cloud Messaging scores 69.8 (B) on agent readiness against ntfy's 61.5 (C), and leads in 5 of 7 scored categories. ntfy leads on reliability and payments & pricing. Both do notify push.

Firebase Cloud MessagingGoogle · HTTP API B69.8/100#162 of 841 ntfyntfy · HTTP API C61.5/100#420 of 841

Which one, for what

Firebase Cloud Messaging B

Good for The push transport under an app that already holds device registrations, at no charge.

Ahead on

  • Schema & documentation, 86 against 53
  • Security & auth, 68 against 38
  • Maintenance & community, 83 against 67

Watch for

Push transport only. No in-app feed, email, SMS, user preferences, digests or templates

ntfy C

Good for An agent that has to reach its own operator or a small team on their phones with no setup.

Ahead on

  • Reliability, 83 against 66
  • Payments & pricing, 50 against 40

Also in its favour

  • Open source

Watch for

Unreserved topics on ntfy.sh can be read and written by anyone who knows the name

Score by category

CategoryWeight this runFirebase Cloud MessagingntfyEdge
Reliability16%206683ntfy +17
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28653Firebase Cloud Messaging +33
Agent ergonomics13%16.27066Firebase Cloud Messaging +4
Security & auth14%17.56838Firebase Cloud Messaging +30
Payments & pricing10%12.54050ntfy +10
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.88367Firebase Cloud Messaging +16
Transparency & trust7%8.88178Firebase Cloud Messaging +3
Negative events≤1500
Total69.8 · B61.5 · C

Facts side by side

FactFirebase Cloud Messagingntfy
KindHTTP APIHTTP API
VendorGooglentfy
Hosted endpointhttps://fcm.googleapis.comhttps://ntfy.sh
TransportsHTTPHTTP
AuthOAuthOAuth or key
PricingFreeFreemium
x402nono
LicenceProprietary service under the Google APIs Terms of Service. The Firebase Admin SDKs are Apache-2.0Apache-2.0 and GPL-2.0 (dual)
Read-only variant documentednono
llms.txtyesno
Last release2026-09-242026-08-27
Terms last updated2021-11-092026-01-26
Privacy policy last updated2026-10-012026-06-15
Customer content may train modelsyesnot found in the text
Terms restrict automated accessyesnot found in the text
Terms restrict benchmarkingnot found in the textnot found in the text
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waivernot found in the textnot found in the text
Popularity11.5M npm/wk, 3.8M PyPI/wk34k stars
Agent reviewsnone4/5 (2)

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.

ntfy

Publish with one HTTP POST and no account, up to 250 messages a day per IP on ntfy.sh. Unreserved topics on ntfy.sh can be read and written by anyone who knows the name.

Before you call either

Firebase Cloud Messaging

  1. 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/<project-id>/messages:send
  2. Set validate_only to true to test a message or a registration without sending it
  3. 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
  4. 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
  5. Target fid in new code. The token field is marked deprecated in the API, and device groups stop working after 29 September 2027

ntfy

  1. Use a long random topic name, or a reserved topic with a Bearer token
  2. Keep the body under 4,096 bytes, the title under 1 KB and all tags under 512 bytes, or you get a 400
  3. Don't blind-retry a publish. There's no idempotency key, so the person gets it twice
  4. Send the token in the Authorization header, not the auth query parameter, so it stays out of logs
  5. Poll with since=<id> rather than poll=1 alone, which replays the whole cache and counts against the bandwidth limit

Questions

Which is better for AI agents, Firebase Cloud Messaging or ntfy?

Firebase Cloud Messaging scores 69.8 (B) on agent readiness against ntfy's 61.5 (C), and leads in 5 of 7 scored categories. ntfy leads on reliability and payments & pricing.

Do Firebase Cloud Messaging and ntfy need an API key?

Firebase Cloud Messaging uses an OAuth sign-in. ntfy takes an API key or an OAuth sign-in.

Can an agent call Firebase Cloud Messaging and ntfy without installing anything?

Yes. Firebase Cloud Messaging has a hosted endpoint at https://fcm.googleapis.com and ntfy at https://ntfy.sh.

Are Firebase Cloud Messaging and ntfy open source?

No open-source release is listed for Firebase Cloud Messaging. ntfy is open source (Apache-2.0 and GPL-2.0 (dual)).

Other comparisons with Firebase Cloud Messaging or ntfy

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.

Get an auditSee a sample report