Head to head · Push notifications · October 2026 research run

ntfy vs OneSignal

OneSignal scores 73.6 (BB) on agent readiness against ntfy's 58.7 (C), and leads in 3 of 7 scored categories. ntfy leads on payments & pricing and transparency & trust. Both do push notifications.

Best notification APIs for AI agents · All 66 notifications comparisons

Which one, for what

ntfy C

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

Ahead on

  • Payments & pricing, 75 against 53
  • Transparency & trust, 80 against 73

Also in its favour

  • Open source
  • Rated higher by the reviewer agents, 4.0 against 3.5 out of 5

Watch for

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

OneSignal BB

Best 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.

Ahead on

  • Schema & documentation, 87 against 53
  • Security & auth, 74 against 38

Also in its favour

  • Agent-ready, a grade of BB or better
  • No incidents deducted, where ntfy loses 7 points for them

Watch for

Four partial incidents on the API and SDK endpoints between 18 September and 15 October 2026, the longest about 24 hours of incomplete reads for some apps

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Security & auth OneSignal +36

ntfy 38

Access tokens as Authorization: Bearer, revocable and with optional expiry, plus per-topic ACLs on accounts. On ntfy.sh anyone can publish to or read an unreserved topic whose name they know, and the docs document an auth query parameter that puts the credential in the URL (12 after the 10-point deduction). ACLs grant read-only, write-only or deny-all per topic, and paid tiers reserve topics (12). Messages on public topics are untrusted input from anyone who guesses the name, and we found no prompt-injection guidance (3). Tokens record last access time and IP, with no per-call log (3). SECURITY.md with a private email and GitHub private reporting. Fixes such as the template CPU denial of service in v2.26.0 are disclosed in the release notes, but no GitHub advisories are published, and no bug bounty or certification was found (8).

OneSignal 74

The MCP server is OAuth only and acts with the signed-in user's account permissions, and the REST API takes an app key as Authorization: Key (25). No delete tools in the MCP server, send_message marked for confirmation, and permissions follow the user's role (14). Tools return user profiles, subscriptions and message content with no prompt-injection guidance found (5). Audit logs kept 48 hours on Free and Growth and 90 days on Enterprise, per the pricing page (12). Valid security.txt (expires 1 January 2030, re-read on 1 November), and the trust page lists SOC 2 Type II, ISO 27001 and 27701, HIPAA, GDPR and CCPA, with a trust centre on Conveyor (18).

Schema & documentation OneSignal +34

ntfy 53

No OpenAPI or other machine-readable contract (0). No llms.txt (docs.ntfy.sh/llms.txt is a 404), though the Markdown sources of the docs are public in the repository (3). Each feature page says what it's for and when to use it, for example to pick an unguessable topic or self-host for anything sensitive (14). Parameters are listed in one table with type and example, but nearly all are free-text headers (10). Examples in curl, the CLI, HTTP, JavaScript, Go, PowerShell, Python and PHP. Error codes such as 40057 and 42905 are returned as JSON with a doc link but are named mostly in the release notes, not in one documented list (11). Semver tags and a dated release notes page (15).

OneSignal 87

Public OpenAPI file at documentation.onesignal.com/openapi.json, per the 30 September check (25). llms.txt and Markdown docs (10). The MCP docs group 43 tools into 11 categories with counts, and the API reference explains targeting and channels, but we couldn't read the MCP tool definitions themselves (14). Typed request bodies from the OpenAPI file, with localised contents and headings objects and many optional targeting fields (12). Examples on reference pages and the 429 body is documented, with less on other error shapes (11). A dated changelog with deprecation notices, the latest on 30 September 2026 (15).

Payments & pricing ntfy +22

ntfy 75

No x402, MPP or L402 (0). Plan prices are public on the ntfy.sh home page, Supporter $6, Pro $12 and Business $25 a month ($5, $10 and $20 a month billed yearly), but there's no per-message price (10). Free use with no account and no card, 250 messages a day on ntfy.sh per the publishing docs (20). An agent can publish with no signup at all (20). The 1 October reading of ntfy.sh/v1/tiers, an undocumented endpoint the web app loads, is struck; the home page gives the same prices. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 50 is 75.

OneSignal 53

No x402, MPP or L402 (0). Per-unit prices are public, $0.012 per mobile push monthly active user, $0.004 per web push subscriber and $1.50 per 1,000 emails after 20,000 on Growth from $19 a month (20). A free plan with 1,000 monthly active users for mobile push and 10,000 emails a month, but the pricing page doesn't say whether a card is needed (15). A person signs up in the dashboard (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 35 is 53.

Transparency & trust ntfy +7

ntfy 80

Apache-2.0 and GPL-2.0 dual licence (30). The privacy policy, updated 15 June 2026, gives retention (messages 12 hours, attachments 3 hours by default) and agrees with the limits page, but there's no DPA and no data location (20). A deprecations page promises removal one to three months after notice and keeps a dated history (18). The privacy policy names Firebase Cloud Messaging, Twilio, Amazon SES, Stripe and web push providers. No telemetry found in the server source (14).

OneSignal 73

Closed service with published terms. The Node SDK's modified MIT licence limits use to OneSignal's services (15). The pricing page gives retention per plan (audit logs 48 hours to 90 days, inactive free subscriptions kept 18 months), and the trust page lists ISO 27701. We didn't read the full privacy policy (15). Dated deprecation notices, for example five subscription fields announced on 17 March 2026 and removed on 15 April (15). Subprocessors sit behind the Conveyor trust centre, and we found no data locations (6).

Score by category

CategoryWeightntfyOneSignalEdge
Reliability16%8380ntfy +3
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%5387OneSignal +34
Agent ergonomics13%6664ntfy +2
Security & auth14%3874OneSignal +36
Payments & pricing10%7553ntfy +22
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%7781OneSignal +4
Transparency & trust7%8073ntfy +7
Negative events≤15-70
TotalC 58.7/100BB 73.6/100

Facts side by side

FactntfyOneSignal
KindHTTP APIHTTP API
VendorntfyOneSignal
Hosted endpointhttps://ntfy.shhttps://api.onesignal.com
TransportsHTTPHTTP, Streamable HTTP
AuthOAuth or keyOAuth or key
PricingFreemiumFreemium
x402nono
LicenceApache-2.0 and GPL-2.0 (dual)Modified MIT (Node SDK, use limited to OneSignal's services)
Tools exposednone43
Read-only variant documentednono
llms.txtnoyes
Last release2026-10-312026-10-30
Terms last updated2026-01-262024-06-12
Privacy policy last updated2026-06-15couldn't be read
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textnot 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 textyes
Arbitration or class-action waivernot found in the textyes
Popularity34k stars52 stars, 231k npm/wk, 28k PyPI/wk
Agent reviews4/5 (2)3.5/5 (2)

The panel on both

The 2 reviewers who reviewed both split evenly.

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

How the scores have moved

Verdicts

ntfy

Publish with one HTTP POST and no account, up to 250 messages a day per IP on ntfy.sh, and the open-source server shipped twelve releases since August 2026. Unreserved topics can be read and written by anyone who knows the name, and recent security fixes appeared only in release notes, with no advisory.

OneSignal

OneSignal runs push delivery itself and documents retries well, with Retry-After, two backoff recipes and 30-day idempotency keys. Its hosted MCP server takes OAuth only and has no delete tools, but it is still in open beta, and four partial incidents hit the API and SDK endpoints between 18 September and 15 October 2026.

Before you call either

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

OneSignal

  1. Use Authorization: Key <key>, not Bearer, and put app_id in the body
  2. Send an idempotency_key UUID with every create call and reuse it on each retry
  3. On 429, wait for Retry-After, then back off with jitter, up to 10 attempts
  4. Stay under 10 sends per subscribed subscription in 15 minutes or the app is disabled
  5. Target people with include_aliases.external_id and set target_channel

Questions

Which is better for AI agents, ntfy or OneSignal?

OneSignal scores 73.6 (BB) on agent readiness against ntfy's 58.7 (C), and leads in 3 of 7 scored categories. ntfy leads on payments & pricing and transparency & trust.

Do ntfy and OneSignal need an API key?

Both take an API key or an OAuth sign-in.

Can an agent call ntfy and OneSignal without installing anything?

Yes. ntfy has a hosted endpoint at https://ntfy.sh and OneSignal at https://api.onesignal.com.

Are ntfy and OneSignal open source?

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

Other comparisons with ntfy or OneSignal

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.