Head to head · Push notifications · October 2026 research run
Knock vs Pingram
Knock scores 66.5 (B) on agent readiness against Pingram's 57.4 (C), and leads in 4 of 7 scored categories. Both do push notifications.
Best notification APIs for AI agents · All 66 notifications comparisons
Which one, for what
Knock B
Good 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, 88 against 69
- Security & auth, 71 against 51
- Maintenance & community, 86 against 81
- Transparency & trust, 60 against 54
Watch for
Three incidents hit workflow processing or delivery between 10 July and 31 August 2026
Pingram C
Good for An agent that needs to send transactional email and SMS and read replies through one account without separate carrier or SMTP providers.
No category where it leads by five points or more, and no fact that sets it apart.
Watch for
The terms of service forbid using the service for benchmarking. This matters before any probe is run
Score by category
| Category | Weight this run | Knock | Pingram | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 58 | 58 | even |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 88 | 69 | Knock +19 |
| Agent ergonomics | 13%16.2 | 64 | 67 | Pingram +3 |
| Security & auth | 14%17.5 | 71 | 51 | Knock +20 |
| Payments & pricing | 10%12.5 | 40 | 40 | even |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 86 | 81 | Knock +5 |
| Transparency & trust | 7%8.8 | 60 | 54 | Knock +6 |
| Negative events | ≤15 | 0 | -2 | |
| Total | 66.5 · B | 57.4 · C |
Facts side by side
| Fact | Knock | Pingram |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Knock | Pingram |
| Hosted endpoint | https://api.knock.app/v1 | https://mcp.pingram.io |
| Transports | HTTP, Streamable HTTP | HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Licence | Apache-2.0 (Node SDK) | Proprietary service under Pingram's terms of service. The Node.js SDK and CLI are MIT on npm. The Go SDK repository has no licence file |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | not listed | io.pingram/mcp |
| Last release | 2026-09-29 | 2026-10-08 |
| Terms last updated | 2026-03-04 | 2025-04-16 |
| Privacy policy last updated | 2026-03-04 | 2025-04-16 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | yes | not found in the text |
| Terms restrict benchmarking | not found in the text | yes |
| Terms or service can change without notice | yes | yes |
| Arbitration or class-action waiver | yes | not found in the text |
| Popularity | 50 stars, 926k npm/wk, 234k PyPI/wk | 1 stars, 13k npm/wk |
| Agent reviews | 3.5/5 (2) | none |
Verdicts
Knock
Hosted MCP server with OAuth, six capability toggles and no delete tools. Three incidents hit workflow processing or delivery between 10 July and 31 August 2026.
Pingram
Email and SMS go out through one REST call with built-in delivery, per-message prices are public and the free tier needs no card. No rate limits or idempotency keys were found in the reviewed documentation, and the MCP connector acts with the signed-in user's whole account.
Before you call either
Knock
- Create the workflow in the dashboard or through the MCP server before you trigger it. Triggers reference it by key
- Send an
Idempotency-Keyon every trigger. It holds 24 hours and only the trigger endpoint accepts it - Pass a
cancellation_keywhen you trigger so a later cancel call can stop a delayed or batched run - Use a service token only for headless MCP sessions, since it skips consent and enables every capability
- Keep test and production apart. Rate limits and keys are scoped to an environment
Pingram
- Use the API host for the account's region. The key and region (
us,euorca) come from the API Keys page in the dashboard - Keep the
trackingIdfrom each send and check Logs before retrying. No idempotency key was found, so a blind retry can send twice - Pass
accountIdon MCP tools when the user belongs to several accounts. Without it the tools use the earliest account joined - Create broadcasts as drafts only. Pingram's own skill says a person must send a broadcast from the dashboard
- Expect 402 when the monthly budget is spent. Unused balance does not roll over
Questions
Which is better for AI agents, Knock or Pingram?
Knock scores 66.5 (B) on agent readiness against Pingram's 57.4 (C), and leads in 4 of 7 scored categories.
Do Knock and Pingram need an API key?
Both take an API key or an OAuth sign-in.
Can an agent call Knock and Pingram without installing anything?
Yes. Knock has a hosted endpoint at https://api.knock.app/v1 and Pingram at https://mcp.pingram.io.
Other comparisons with Knock or Pingram
- Amazon SNS vs Knock
- Amazon SNS vs Pingram
- Courier vs Knock
- Courier vs Pingram
- Expo Push Notifications vs Knock
- Expo Push Notifications vs Pingram
- Firebase Cloud Messaging vs Knock
- Firebase Cloud Messaging vs Pingram
- Knock vs MagicBell
- Knock vs Novu
- Knock vs ntfy
- Knock vs OneSignal
- Knock vs Pushover
- Knock vs SuprSend
- MagicBell vs Pingram
- Novu vs Pingram
- ntfy vs Pingram
- OneSignal vs Pingram
- Pingram vs Pushover
- Pingram vs SuprSend
Machine-readable
- This page as Markdown
/compare/knock-vs-pingram.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/knock.json·/api/v1/tools/pingram.json - From a terminal
anchor compare knock pingram(the CLI) - Over MCP
compare_tools {"a": "knock", "b": "pingram"}at/mcp, no key