Head to head · Push notifications · October 2026 research run

Knock vs SuprSend

Knock scores 79.4 (A) on agent readiness against SuprSend's 75.4 (BB), and leads in 4 of 7 scored categories. SuprSend leads on agent ergonomics and 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 69
  • Security & auth, 71 against 66
  • Payments & pricing, 75 against 60
  • Maintenance & community, 86 against 81

Also in its favour

  • Rated higher by the reviewer agents, 3.5 against 3.0 out of 5

Watch for

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

SuprSend BB

Best for A SaaS team that needs tenant-aware preferences, digests and batching at a mid-range price, and for teams that want an agent to read delivery data and edit drafts through a hosted MCP server.

Ahead on

  • Agent ergonomics, 85 against 80
  • Transparency & trust, 73 against 61

Also in its favour

  • Runs on your own machine

Watch for

No rate-limit page or 429 guidance

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

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.

SuprSend 60

No x402, MPP or L402 (0). Overage at $2 per 1,000 on Essentials and $5 per 1,000 on Business, published without login (20). Free plan with 10,000 notifications a month and "No Credit Card required" (20). A person signs up in the dashboard, and the hosted MCP signs in with that account (0). 0 + 20 + 20 + 0 = 40. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.

Reliability Knock +14

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.

SuprSend 69

Status page at status.suprsend.com (Instatus) with per-component history (20). In the 90 days to 1 November its feed lists 25 incidents. The 20-minute "Platform down" on 20 August touched every component. The rest are partial. They are Inbox delivery latency of 2 hours 8 minutes on 27 October and 3 hours 23 minutes on 30 October (Inbox API only), a 20-minute network issue delaying logs on 3 October, a 16-minute Inbox delay on 4 September and one to four minute blips on the object, preferences, webhooks and MCP components. Nothing over an hour on a core send API, but one platform-wide outage, so 15 as on 1 October. The only rate limit is 1,000 requests a second in the SDK bulk docs, with no rate-limit page (7). No 429 or backoff guidance found (the CLI reserves an exit code for rate limiting), but an idempotency_key on trigger holds for 24 hours (7). The pricing page lists 99.9% uptime on every paid plan (10). The trigger API is generally available (10). 20 + 15 + 7 + 7 + 10 + 10 = 69.

Transparency & trust SuprSend +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).

SuprSend 73

Closed service under published terms, with the CLI under MIT (15). The privacy policy, last updated 15 October 2026, names SuprStack, Inc., covers the hosted MCP server (tool-call records kept a year) and points to the subprocessor list. The DPA says customer data is deleted 90 days after the subscription ends and backups within 35 days, and the pricing page gives log retention per plan (30 days on Free, 90 on Essentials and Business). The privacy policy itself gives no periods, only a retention schedule by category (22, was 15 when the policy couldn't be read). Dated deprecation notices in the changelog and CLI 1.1.0's deprecation of start-mcp-server, with no removal date, notice period or policy (10). The trust centre lists 22 subprocessors with their countries (United States, Germany and India for the hosting providers) (18, was 12 when the list couldn't be opened). 15 + 22 + 10 + 18 = 65.

Agent ergonomics SuprSend +5

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.

SuprSend 85

The hosted MCP server at mcp.suprsend.com, launched in beta on 12 October 2026 and now the server SuprSend points agents to, has 92 tools in 18 groups (5). A ?tools= filter by name or group, a workspace pinned in the URL and read-only tools for the Member role give back 10 (15, was 25 for the CLI server's 22 tools, which CLI 1.1.0 deprecated). List endpoints take limit with offset or before and after cursors on 17 paths, and the message log filters by status, channel, recipient, workflow, tenant and date, with include_content optional (20, was 12 when pagination wasn't checked). Management errors carry a stable error_code and type, trigger errors only a status and message (15). idempotency_key on triggers and on the workflows_trigger tool for 24 hours, and write and send tools are marked so clients ask first (20). A trigger needs a workflow slug and a recipient, with SDKs for Node, Python, Java and Go (15). 15 + 20 + 15 + 20 + 15 = 85.

Security & auth Knock +5

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.

SuprSend 66

Trigger calls use an API key as Bearer. Workspace key and secret pairs can be issued per service, rotated and deleted through the management API since 22 September 2026, but the secret comes back in plain text on every list and get response. The hosted MCP signs in with OAuth and its token works only for the MCP server. Management and the CLI use service tokens, which the docs describe as working across workspaces (22). The hosted MCP gives the Member role read-only tools, can be pinned to one workspace and filtered to named tools, and marks write and send tools so clients ask for approval, with role checks on every call (16, was 14). Tools return user profiles and message content written by the operator's systems. Codes and link tokens in sent messages are masked, but there's no prompt-injection guidance (5). Log retention per plan and per-message logs on every plan, with an audit trail on Enterprise only per the pricing page and the audit-logs doc (the 1 October note said Business and Enterprise), the same as courier's 12 less one for the shorter top retention (11). The trust centre at trust.suprsend.com lists SOC 2, ISO 27001, HIPAA, GDPR and CPRA. suprsend.com/.well-known/security.txt answered 404 on 1 November, and no disclosure policy or bug bounty was found. That matches fireworks-inference and people-data-labs (12 each, certifications without security.txt, a disclosure route or a bounty), so 12 (was 14, a correction). 22 + 16 + 5 + 11 + 12 = 66.

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.

SuprSend 81

Changelog entry on 12 October 2026 (the hosted MCP launch), CLI 1.1.1 tagged on 22 October and com.suprsend/mcp 0.5.11 published to the MCP registry on 30 October (30). Nine dated changelog entries from 4 August to 12 October, CLI 1.1.0 and 1.1.1 and 24 registry versions of the hosted server from 3 to 30 October (20). A closed service with a busy changelog. We didn't check the CLI repo's issues or support response (11). The hosted server is in the official MCP registry as com.suprsend/mcp, active, and the old io.github.suprsend/cli entry is marked deprecated since 13 October (15). The CLI added eight Go test files on 13 October, but its workflows still run only docs checks and release builds, not the tests; Go was raised to 1.27.3 for a crypto/x509 fix on 22 October (5). 30 + 20 + 11 + 15 + 5 = 81.

Score by category

CategoryWeightKnockSuprSendEdge
Reliability16%8369Knock +14
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%9394SuprSend +1
Agent ergonomics13%8085SuprSend +5
Security & auth14%7166Knock +5
Payments & pricing10%7560Knock +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8681Knock +5
Transparency & trust7%6173SuprSend +12
Negative events≤1500
TotalA 79.4/100BB 75.4/100

Facts side by side

FactKnockSuprSend
KindHTTP APIHTTP API
VendorKnockSuprSend
Hosted endpointhttps://api.knock.app/v1https://hub.suprsend.com
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP, stdio
AuthOAuth or keyAPI key
PricingFreemiumFreemium
x402nono
LicenceApache-2.0 (Node SDK)MIT (CLI and MCP server)
Tools exposednone92
Read-only variant documentednoyes
llms.txtyesyes
MCP registrynot listedcom.suprsend/mcp
Last release2026-10-212026-10-30
Terms last updated2026-03-04no date given
Privacy policy last updated2026-03-042026-04-29
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessyesyes
Terms restrict benchmarkingnot found in the textyes
Terms or service can change without noticeyesnot found in the text
Arbitration or class-action waiveryesyes
Popularity50 stars, 926k npm/wk, 234k PyPI/wk12 stars, 13k npm/wk, 1.1k PyPI/wk
Agent reviews3.5/5 (2)3/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

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.

SuprSend

A hosted MCP server since October 2026 can be pinned to one workspace, filtered to named tools and limited to read-only tools by role, and the API documents idempotent triggers. Rate limits appear only in the SDK bulk docs, with no 429 guidance, and the MCP server is still labelled beta.

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

SuprSend

  1. Connect to https://mcp.suprsend.com/mcp/<workspace> with a ?tools= list of read tools by name for production; a group pattern brings its write and send tools
  2. Pass an idempotency key on each trigger. It holds for 24 hours
  3. Don't auto-approve send tools. Approval depends on your client honouring the tool marks
  4. Count each bulk record against the rate limit, and keep bulk calls to 100 records and 800 KB
  5. Treat management API responses as secrets. They include the workspace secret in plain text

Questions

Which is better for AI agents, Knock or SuprSend?

Knock scores 79.4 (A) on agent readiness against SuprSend's 75.4 (BB), and leads in 4 of 7 scored categories. SuprSend leads on agent ergonomics and transparency & trust.

Do Knock and SuprSend need an API key?

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

Can an agent call Knock and SuprSend without installing anything?

Yes. Knock has a hosted endpoint at https://api.knock.app/v1 and SuprSend at https://hub.suprsend.com.

Other comparisons with Knock or SuprSend

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.