Head to head · Push notifications · October 2026 research run

Knock vs Pushover

Knock scores 79.4 (A) on agent readiness against Pushover's 55 (C), and leads in 6 of 7 scored categories. Pushover 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

  • Reliability, 83 against 62
  • Schema & documentation, 93 against 50
  • Agent ergonomics, 80 against 64
  • Security & auth, 71 against 52
  • Payments & pricing, 75 against 45
  • Maintenance & community, 86 against 20

Also in its favour

  • Agent-ready, a grade of BB or better

Watch for

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

Pushover C

Best for An agent that must reach its owner or an on-call team and get an acknowledgement.

Ahead on

  • Transparency & trust, 87 against 61

Watch for

Recipients need the app, $4.99 per platform after a 30-day trial

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.

Maintenance & community Knock +66

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.

Pushover 20

The last published API change is still the 23 June 2026 blog post deprecating the GitHub notification endpoint, the newest post on 4 November, 134 days before this check (10). No releases or dated changes in the 90 days from 6 August (0). A blog with dated product notices and a support site, with no public issue tracker (10). No official SDKs or MCP server (0). No packages to grade (0). 10+0+10+0+0 = 20.

Schema & documentation Knock +43

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.

Pushover 50

No OpenAPI or other machine-readable contract (0). No llms.txt and no Markdown docs (0). The single API page explains every parameter and when to use emergency priority, receipts and groups (16). Parameters are documented with limits (message 1,024 characters, title 250, URL 512, attachment 5 MB) and enumerated priorities and sounds, sent as form fields or JSON (11). Examples and an error example with status, errors and request fields (13). A /1/ version in the path and product changes announced on the blog, with no changelog as such (10). Re-read on the API and pricing pages on 4 November, unchanged.

Payments & pricing Knock +30

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.

Pushover 45

No x402, MPP or L402 (0). Prices are public but per licence and seat, $4.99 once per platform or $5 per user a month for Teams, and capacity upgrades aren't priced on the page (10). A 30-day trial of the app and 10,000 free messages a month without a card (20). A person has to create an account and install the app to get a user key (0). Re-read on the API and pricing pages on 4 November, unchanged. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.

Transparency & trust Pushover +26

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

Pushover 87

Closed service under published terms, last updated 1 May 2026 (15). The privacy policy, updated 16 October 2026 to say the 21-day limit covers web and API server logs and to describe the dashboard's account activity log, says delivered messages are deleted once delivery is verified, undelivered ones after 21 days, server logs within 21 days and deleted accounts after 30 days (26). Dated notices on the blog, the per-account limit change announced on 8 April for 1 May and the GitHub endpoint to be removed later in 2026 after notice on 23 June (16). Nine processors named, from Apple and Google to Vultr and rsync.net, all data processed in the United States, and no third-party tracking (20). 15+26+16+20 = 77.

Reliability Knock +21

Knock 83

Status page at status.knock.app, now on incident.io, with nine components including API, Notification delivery and Agent (20). The 90 days from 3 August hold four incidents. "Workflow processing and message delivery errors" on 31 August (16:42 to 18:26 UTC) said some customers might see errors in workflow run processing, a partial outage. Dashboard magic-link login failed on 21 September (Knock's own emails only), warehouse sync was delayed on 2 October, and new in-app feed connections failed on 29 and 30 October while "Normal API operations and notification delivery remain unaffected". All partial, so minor only (20). The 10 and 16 July incidents have left the window. Limits published in five tiers from 1 to 1,000 requests a second, scoped per environment (15). Over-limit calls get 429, with no Retry-After header or backoff guidance found, only an Idempotency-Key on trigger with a 24-hour window (8). The pricing page's plan table lists a 99.9% uptime SLA on Free and Starter, with Enterprise by contract (10). The trigger API is generally available (10). 20 + 20 + 15 + 8 + 10 + 10 = 83.

Pushover 62

A status page at status.pushover.net, titled Pushover Status, run on Site24x7 StatusIQ (20). On 4 November its robots.txt answered HTTP 404 with StatusIQ's generic error page, which says only that there was a problem with the request, so the host has no rules for us. The page renders its history in JavaScript, and its RSS feed lists only the current state of six components (Dashboard, Outbound Message Queue and four US regions, all operational on 4 November), so the incident history stays unread (5). Quotas published with numbers, 10,000 messages a month per account (25,000 for Teams) and at most 2 concurrent connections, re-read on the API page on 4 November (15). Over-quota sends get 429, every response carries X-Limit-App-Limit, X-Limit-App-Remaining and X-Limit-App-Reset, and the docs say never to repeat a 4xx and to wait at least 5 seconds after a 5xx. There's no idempotency key, so a retry after a timeout can send twice (12). No SLA found (0). The /1/ API is generally available, not beta (10). 20+5+15+12+0+10 = 62.

Security & auth Knock +19

Knock 71

The MCP server signs in with OAuth or a knock_st_ service token. Secret API keys are per environment, and client feeds use a public key plus signed user tokens. Service tokens inherit the creator's privileges, have full management API access and no expiry, but revoke immediately (22). No delete tools in the MCP server, data management off by default and an OAuth consent screen, though a service-token session skips consent and turns every capability on. The toolkit has human-in-the-loop helpers (15). Tools return message content and user data with no prompt-injection guidance found (5). Audit logs record management API changes with the token as author, and every message has delivery logs and events (14). The security page lists SOC 2 Type 2, HIPAA, GDPR and CCPA, third-party pen tests and a disclosure process at security@knock.app. No bug bounty found, and knock.app/.well-known/security.txt returned 404 on 1 November (15). The pricing table puts audit logs on Enterprise only.

Pushover 52

An application token and a user or group key, sent in the POST body rather than a header. An app token can only send, not read (18). No read access through the sending API, and group keys let you limit who receives (12). The sending API returns no untrusted content (10). Receipts for emergency messages and the limits endpoint, but no per-call log for the operator (6). security.txt valid on 4 November, with a security mailbox and an Expires date of 2038-01-19. No disclosure policy, bug bounty or certification found beyond it (6).

Score by category

CategoryWeightKnockPushoverEdge
Reliability16%8362Knock +21
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%9350Knock +43
Agent ergonomics13%8064Knock +16
Security & auth14%7152Knock +19
Payments & pricing10%7545Knock +30
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8620Knock +66
Transparency & trust7%6187Pushover +26
Negative events≤1500
TotalA 79.4/100C 55/100

Facts side by side

FactKnockPushover
KindHTTP APIHTTP API
VendorKnockPushover
Hosted endpointhttps://api.knock.app/v1https://api.pushover.net/1/messages.json
TransportsHTTP, Streamable HTTPHTTP
AuthOAuth or keyAPI key
PricingFreemiumPaid
x402nono
LicenceApache-2.0 (Node SDK)none
Read-only variant documentednono
llms.txtyesno
Last release2026-10-212026-06-23
Terms last updated2026-03-042026-05-01
Privacy policy last updated2026-03-042026-05-01
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 waiveryesnot found in the text
Popularity50 stars, 926k npm/wk, 234k PyPI/wknone
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.

Pushover

One POST with three required fields, form or JSON. Recipients need the app, $4.99 per platform after a 30-day trial.

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

Pushover

  1. Use priority 2 with retry (30 or more) and expire (10,800 or less) when a person must act, then poll the receipt
  2. Don't retry a 4xx. Fix the parameter named in errors. Wait at least 5 seconds before retrying a 5xx
  3. Read X-Limit-App-Remaining before a batch. Over the monthly quota every send returns 429
  4. Keep messages to 1,024 characters and titles to 250
  5. Send to a group key to reach several people in one call. Each person still counts against the quota

Questions

Which is better for AI agents, Knock or Pushover?

Knock scores 79.4 (A) on agent readiness against Pushover's 55 (C), and leads in 6 of 7 scored categories. Pushover leads on transparency & trust.

Do Knock and Pushover need an API key?

Knock takes an API key or an OAuth sign-in. Pushover needs an API key.

Can an agent call Knock and Pushover without installing anything?

Yes. Knock has a hosted endpoint at https://api.knock.app/v1 and Pushover at https://api.pushover.net/1/messages.json.

Other comparisons with Knock or Pushover

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.