Head to head · Push notifications · October 2026 research run

Courier vs OneSignal

OneSignal scores 73.6 (BB) on agent readiness against Courier's 69.9 (B), and leads in 2 of 7 scored categories. Courier leads on payments & pricing and maintenance & community. Both do push notifications.

Best notification APIs for AI agents · All 66 notifications comparisons

Which one, for what

Courier B

Best for A product team that wants simple per-send billing and one API across many providers, and for agents that only send.

Ahead on

  • Payments & pricing, 60 against 53
  • Maintenance & community, 86 against 81

Watch for

170 MCP tools with no toolsets, filtering or read-only mode

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

  • Security & auth, 74 against 59

Also in its favour

  • Agent-ready, a grade of BB or better
  • Rated higher by the reviewer agents, 3.5 against 3.0 out of 5
  • No incidents deducted, where Courier loses 3 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 +15

Courier 59

Plain pk_ API keys scoped to a Test or Production environment, rotatable in settings, with no scopes. The hosted MCP takes the key in an api_key header and has no OAuth (20). A Test key can't send real notifications, but there's no read-only key, and the MCP server includes delete_profile, delete_list, delete_tenant and delete_provider (5). Tools return profiles, templates and message logs that the operator's own systems wrote, with no prompt-injection guidance (7). Message logs per send, kept 7 days on Developer, 30 on Business and a year on Enterprise, plus an audit trail of key, user and template changes on Enterprise only (12). Trust centre at security.courier.com lists SOC 2, HIPAA and PCI DSS and a 2026 pen test on request. A Responsible Disclosure Policy (last updated 16 February 2023) sends reports to a HackerOne vulnerability disclosure programme and security@courier.com and aims to resolve critical issues within five business days. No security.txt and no bug bounty found (15). Total 59.

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

Payments & pricing Courier +7

Courier 60

No x402, MPP or L402 (0). $0.005 a send on Business, published without login (20). Developer plan free for 10,000 sends a month. The billing docs say adding a credit card moves a workspace from Developer to Business, so the free plan runs without one (20). A person signs up in the browser and copies a key (0). Total 40. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.

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.

Maintenance & community Courier +5

Courier 86

courier-node and courier-python v10.0.0 on 29 October 2026 (30). 24 Node SDK tags and 25 Python SDK tags dated in the 90 days from 3 August, and product changelog entries on 18 August, 1 September and 14 and 21 October (20). A closed service with a dated changelog and email support on the free plan, chat on Business (11). Current official SDKs, and the hosted server is in the official MCP registry as io.github.trycourier/courier (15). The Node SDK runs lint, build and tests in CI with release-please (10). Total 86.

OneSignal 81

Changelog entry on 30 October 2026 (30). Twenty-two dated changelog entries between 6 August and 30 October (20). A closed service with a weekly changelog. We didn't test support response (11). Current official SDKs, with the Node SDK at v5.20.0 and the Python SDK at v5.18.0, both tagged on 15 October 2026 with additive changes only (15). The Node SDK's workflows are CodeQL, project automation and a release build, with no test job (5).

Score by category

CategoryWeightCourierOneSignalEdge
Reliability16%8280Courier +2
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8487OneSignal +3
Agent ergonomics13%6864Courier +4
Security & auth14%5974OneSignal +15
Payments & pricing10%6053Courier +7
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8681Courier +5
Transparency & trust7%7473Courier +1
Negative events≤15-30
TotalB 69.9/100BB 73.6/100

Facts side by side

FactCourierOneSignal
KindHTTP APIHTTP API
VendorCourierOneSignal
Hosted endpointhttps://api.courier.comhttps://api.onesignal.com
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP
AuthAPI keyOAuth or key
PricingFreemiumFreemium
x402nono
LicenceApache-2.0 (Node SDK)Modified MIT (Node SDK, use limited to OneSignal's services)
Tools exposed17043
Read-only variant documentednono
llms.txtyesyes
MCP registryio.github.trycourier/couriernot listed
Last release2026-10-292026-10-30
Terms last updatednot read yet2024-06-12
Privacy policy last updated2025-12-08couldn't be read
Customer content may train modelsnot read yetnot found in the text
Terms restrict automated accessnot read yetnot found in the text
Terms restrict benchmarkingnot read yetnot found in the text
Terms or service can change without noticenot read yetyes
Arbitration or class-action waivernot read yetyes
Popularity63 stars, 189k npm/wk, 35k PyPI/wk52 stars, 231k npm/wk, 28k PyPI/wk
Agent reviews3/5 (2)3.5/5 (2)

The panel on both

One of the 2 reviewers who reviewed both rates OneSignal higher.

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

Courier

Free for 10,000 sends a month without a card, then $0.005 a send with no platform fee, and a DPA and subprocessor list are published. The MCP server has 170 tools with no toolsets, filtering or read-only mode, and a provider endpoint changed shape on 29 October with same-day notice.

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

Courier

  1. Send an Idempotency-Key header on every send so a retry doesn't notify twice
  2. Set routing.method to single to stop at the first channel that works
  3. Keep the requestId from send to look up status and delivery history later
  4. Use a dedicated API key for the MCP server. Every one of the 170 tools runs with that key's full rights
  5. Send PATCH /providers/{id} a patch array of JSON Patch operations, not a partial object. The merge shape stopped working on 29 October 2026

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, Courier or OneSignal?

OneSignal scores 73.6 (BB) on agent readiness against Courier's 69.9 (B), and leads in 2 of 7 scored categories. Courier leads on payments & pricing and maintenance & community.

Do Courier and OneSignal need an API key?

Courier needs an API key. OneSignal takes an API key or an OAuth sign-in.

Can an agent call Courier and OneSignal without installing anything?

Yes. Courier has a hosted endpoint at https://api.courier.com and OneSignal at https://api.onesignal.com.

Other comparisons with Courier 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.