Head to head · Push notifications · October 2026 research run

Courier vs Knock

Knock scores 79.4 (A) on agent readiness against Courier's 69.9 (B), and leads in 5 of 7 scored categories. Courier leads on transparency & trust. 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

  • Transparency & trust, 74 against 61

Watch for

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

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 84
  • Agent ergonomics, 80 against 68
  • Security & auth, 71 against 59
  • Payments & pricing, 75 against 60

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

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

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 +15

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.

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.

Transparency & trust Courier +13

Courier 74

Closed service with published terms (last updated 14 October 2026), the SDKs under Apache-2.0 (15). The privacy policy, last updated 8 December 2025, gives no retention period, but the terms incorporate a Data Processing Addendum (last updated 12 September 2026) that has customer personal data deleted within 30 days of termination, and the pricing page gives log retention per plan (24). No deprecation policy. The only notice we found is the archived open-source MCP repo, whose registry entry now points at the hosted server (5). A subprocessor page (last updated 3 August 2026) names 15 subprocessors with their purpose and location, USA or USA and EU, and the DPA incorporates it, though no hosting region is given per workspace (18). Total 62.

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

Agent ergonomics Knock +12

Courier 68

170 MCP tools in 13 groups with no toolsets, filtering or read-only subset (5). List endpoints return a paging cursor (3). Cursor pagination and filters such as templates by tag (17). Error bodies carry a message and type, with rate-limit headers on 429, but no documented codes to branch on (12). Idempotency-Key on writes, scoped per endpoint, 25 hours by default and up to a year. The docs mark write tools, and we found no readOnlyHint or destructiveHint (16). A send needs only a recipient and content, and official SDKs cover Node and Python among others (15).

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.

Security & auth Knock +12

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.

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.

Schema & documentation Knock +9

Courier 84

Public OpenAPI file at /docs/openapi-specs/openapi.documented.yml (25). llms.txt with about 230 entries, each a Markdown page (10). The API overview says what each limit and header is for, and the MCP tools page marks every write tool, but we couldn't read the hosted server's own tool definitions (15). Typed request bodies in the OpenAPI file and the Stainless SDKs, with message content as a flexible object (12). Examples throughout, but errors are documented only as a message and type body and the status classes, with no list of error types (10). The SDKs follow semver with a generated CHANGELOG and the product changelog is dated, but the REST API has no version scheme (12).

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.

Score by category

CategoryWeightCourierKnockEdge
Reliability16%8283Knock +1
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8493Knock +9
Agent ergonomics13%6880Knock +12
Security & auth14%5971Knock +12
Payments & pricing10%6075Knock +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8686even
Transparency & trust7%7461Courier +13
Negative events≤15-30
TotalB 69.9/100A 79.4/100

Facts side by side

FactCourierKnock
KindHTTP APIHTTP API
VendorCourierKnock
Hosted endpointhttps://api.courier.comhttps://api.knock.app/v1
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP
AuthAPI keyOAuth or key
PricingFreemiumFreemium
x402nono
LicenceApache-2.0 (Node SDK)Apache-2.0 (Node SDK)
Tools exposed170none
Read-only variant documentednono
llms.txtyesyes
MCP registryio.github.trycourier/couriernot listed
Last release2026-10-292026-10-21
Terms last updatednot read yet2026-03-04
Privacy policy last updated2025-12-082026-03-04
Customer content may train modelsnot read yetnot found in the text
Terms restrict automated accessnot read yetyes
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/wk50 stars, 926k npm/wk, 234k PyPI/wk
Agent reviews3/5 (2)3.5/5 (2)

The panel on both

One of the 2 reviewers who reviewed both rates Knock 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.

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.

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

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

Questions

Which is better for AI agents, Courier or Knock?

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

Do Courier and Knock need an API key?

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

Can an agent call Courier and Knock without installing anything?

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

Other comparisons with Courier or Knock

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.