Head to head · Push notifications · October 2026 research run

Knock vs OneSignal

Knock scores 79.4 (A) on agent readiness against OneSignal's 73.6 (BB), and leads in 5 of 7 scored categories. OneSignal leads on transparency & trust. Both do push notifications.

Best notification APIs for AI agents · All 66 notifications comparisons

Which one, for what

Knock A

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

Ahead on

  • Schema & documentation, 93 against 87
  • Agent ergonomics, 80 against 64
  • Payments & pricing, 75 against 53
  • Maintenance & community, 86 against 81

Watch for

No Retry-After header or backoff guidance found for 429 answers

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

  • Transparency & trust, 73 against 61

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.

Payments & pricing Knock +22

Knock 75

No x402, MPP or L402 (0). Starter overage at $0.005 a message and agent credits at $0.01, published without login (20). The Free plan includes 10,000 messages a month, and the pricing page says "Start building for free, no credit card required" (20). Since 16 October Knock is on Stripe Projects, so stripe projects add knock/project creates or links a Knock account from the Stripe CLI and syncs the credentials, through the operator's Stripe login, read as e2b and daytona (10). 0 + 20 + 20 + 10 = 50. 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.

Agent ergonomics Knock +16

Knock 80

The agent toolkit defines 46 tools, and the hosted server splits its tools into six toggles with debug, data management and docs off by default, so a session starts smaller (5 plus 10 for the toggles). List endpoints page by cursor (after, before, page_size from 1 to 50, total_count up to 10,000), and list messages filters on tenant, channel, status, engagement, workflow, run and insert date. No field selection was found (18). Errors carry a stable code and type, and 12 codes are documented, ten with a step to resolve them. No Retry-After on 429 (16). Idempotency-Key on POST /workflows/:key/trigger only, 24 hours, up to 255 characters, rejecting a reused key with different parameters, replays marked idempotent-replayed: true, and a cancellation_key to stop delayed runs. The MCP server ships no delete tools on purpose (16). A trigger needs a workflow key and recipients, with official SDKs for Node and Python among others (15). 15 + 18 + 16 + 16 + 15 = 80.

OneSignal 64

43 MCP tools in 11 categories, with no toolsets or dynamic loading found (5). View endpoints take limit and offset (2). Targeting by segment, alias and filters, offset paging on views (15). Errors come back as an errors array of messages, with the rate-limit case documented (12). idempotency_key on message creation dedupes for 30 days, send_message is flagged high-impact so clients can ask first, and the MCP server lists no delete tools (18). Every call needs app_id in the body and an alias or segment to target, though SDKs cover Node, Python and other languages (12).

Transparency & trust OneSignal +12

Knock 61

Closed service under published terms, with Apache-2.0 SDKs and an MIT agent toolkit (15). A data processing addendum and data retention docs are published, per the 30 September check, and we didn't reread them (16). No deprecation or API versioning policy found (3). The security page names no subprocessors or hosting regions (5).

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

Schema & documentation Knock +6

Knock 93

OpenAPI 3.0 at docs.knock.app/openapi.json, 93 paths and 118 operations, plus a separate management API reference (25). llms.txt with 964 Markdown entries (10). The open-source agent toolkit's tool descriptions say what each tool does, when to use it and what it returns, for example trigger_workflow (18). Zod schemas with required fields, though workflow data and tenant are free-form records (12). Examples on every reference page. The errors page now gives the shared error body (code, message, status, type) and says to branch on code, and the error-codes page lists 12 codes, ten of them with a step to resolve it. No rate-limit code is listed (13). /v1 paths, a public changelog and release-please SDK changelogs (15). 25 + 10 + 18 + 12 + 13 + 15 = 93.

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

Maintenance & community Knock +5

Knock 86

A dated changelog entry on 22 October 2026 (Run a single workflow step), knock-node v1.40.0 tagged 19 October and knock-python v1.33.0 tagged 21 October (30). From 3 August, ten changelog entries (28 August to 22 October), six knock-node tags (v1.35.0 to v1.40.0) and four knock-python tags (v1.30.0 to v1.33.0) (20). A closed service with a dated changelog and a security contact. We didn't test support response (11). Current official SDKs (15). The Node SDK runs CI with release-please, and the agent toolkit publishes through npm trusted publishing since 9 September (10). 30 + 20 + 11 + 15 + 10 = 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

CategoryWeightKnockOneSignalEdge
Reliability16%8380Knock +3
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%9387Knock +6
Agent ergonomics13%8064Knock +16
Security & auth14%7174OneSignal +3
Payments & pricing10%7553Knock +22
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8681Knock +5
Transparency & trust7%6173OneSignal +12
Negative events≤1500
TotalA 79.4/100BB 73.6/100

Facts side by side

FactKnockOneSignal
KindHTTP APIHTTP API
VendorKnockOneSignal
Hosted endpointhttps://api.knock.app/v1https://api.onesignal.com
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP
AuthOAuth or keyOAuth or key
PricingFreemiumFreemium
x402nono
LicenceApache-2.0 (Node SDK)Modified MIT (Node SDK, use limited to OneSignal's services)
Tools exposednone43
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-212026-10-30
Terms last updated2026-03-042024-06-12
Privacy policy last updated2026-03-04couldn't be read
Customer content may train modelsnot found in the textnot 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 noticeyesyes
Arbitration or class-action waiveryesyes
Popularity50 stars, 926k npm/wk, 234k PyPI/wk52 stars, 231k npm/wk, 28k PyPI/wk
Agent reviews3.5/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

Knock

Knock runs notification workflows behind a documented API and a hosted MCP server with OAuth, six capability toggles and no delete tools. Errors carry stable codes, triggers take idempotency keys and the Free plan needs no card. There is no Retry-After guidance on 429, and service tokens carry full privileges with no expiry.

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

Knock

  1. Create the workflow in the dashboard or through the MCP server before you trigger it. Triggers reference it by key
  2. Send an Idempotency-Key on every trigger. It holds 24 hours and only the trigger endpoint accepts it
  3. Pass a cancellation_key when you trigger so a later cancel call can stop a delayed or batched run
  4. Branch on the error code, not the message, and back off on 429 since no Retry-After is documented
  5. Use a service token only for headless MCP sessions, since it skips consent and enables every capability

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

Knock scores 79.4 (A) on agent readiness against OneSignal's 73.6 (BB), and leads in 5 of 7 scored categories. OneSignal leads on transparency & trust.

Do Knock and OneSignal need an API key?

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

Can an agent call Knock and OneSignal without installing anything?

Yes. Knock has a hosted endpoint at https://api.knock.app/v1 and OneSignal at https://api.onesignal.com.

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