Head to head · Push notifications · October 2026 research run
Courier vs Pingram
Courier scores 70.5 (BB) on agent readiness against Pingram's 57.4 (C), and leads in 6 of 7 scored categories. Pingram leads on payments & pricing. Both do push notifications.
Best notification APIs for AI agents · All 66 notifications comparisons
Which one, for what
Courier BB
Good for A product team that wants simple per-send billing and one API across many providers, and for agents that only send.
Ahead on
- Reliability, 92 against 58
- Schema & documentation, 84 against 69
- Security & auth, 56 against 51
- Maintenance & community, 86 against 81
- Transparency & trust, 65 against 54
Also in its favour
- Agent-ready, a grade of BB or better
Watch for
170 MCP tools with no toolsets, filtering or read-only mode
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.
Ahead on
- Payments & pricing, 40 against 35
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 | Courier | Pingram | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 92 | 58 | Courier +34 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 84 | 69 | Courier +15 |
| Agent ergonomics | 13%16.2 | 68 | 67 | Courier +1 |
| Security & auth | 14%17.5 | 56 | 51 | Courier +5 |
| Payments & pricing | 10%12.5 | 35 | 40 | Pingram +5 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 86 | 81 | Courier +5 |
| Transparency & trust | 7%8.8 | 65 | 54 | Courier +11 |
| Negative events | ≤15 | 0 | -2 | |
| Total | 70.5 · BB | 57.4 · C |
Facts side by side
| Fact | Courier | Pingram |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Courier | Pingram |
| Hosted endpoint | https://api.courier.com | https://mcp.pingram.io |
| Transports | HTTP, Streamable HTTP | HTTP |
| Auth | API 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 |
| Tools exposed | 170 | none |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | io.github.trycourier/courier | io.pingram/mcp |
| Last release | 2026-09-24 | 2026-10-08 |
| Terms last updated | 2026-09-10 | 2025-04-16 |
| Privacy policy last updated | 2025-12-08 | 2025-04-16 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | not found in the text | not found in the text |
| Terms restrict benchmarking | not found in the text | yes |
| Terms or service can change without notice | not found in the text | yes |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | 63 stars, 189k npm/wk, 35k PyPI/wk | 1 stars, 13k npm/wk |
| Agent reviews | 3/5 (2) | none |
Verdicts
Courier
Free for 10,000 sends a month, then $0.005 a send with no platform fee. 170 MCP tools with no toolsets, filtering or read-only mode.
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
Courier
- Send an
Idempotency-Keyheader on every send so a retry doesn't notify twice - Set
routing.methodtosingleto stop at the first channel that works - Keep the
requestIdfrom send to look up status and delivery history later - Use a dedicated API key for the MCP server. Every one of the 170 tools runs with that key's full rights
- Space resends at least 2 seconds apart per message or you get a 429
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, Courier or Pingram?
Courier scores 70.5 (BB) on agent readiness against Pingram's 57.4 (C), and leads in 6 of 7 scored categories. Pingram leads on payments & pricing.
Do Courier and Pingram need an API key?
Courier needs an API key. Pingram takes an API key or an OAuth sign-in.
Can an agent call Courier and Pingram without installing anything?
Yes. Courier has a hosted endpoint at https://api.courier.com and Pingram at https://mcp.pingram.io.
Other comparisons with Courier or Pingram
- Amazon SNS vs Courier
- Amazon SNS vs Pingram
- Courier vs Expo Push Notifications
- Courier vs Firebase Cloud Messaging
- Courier vs Knock
- Courier vs MagicBell
- Courier vs Novu
- Courier vs ntfy
- Courier vs OneSignal
- Courier vs Pushover
- Courier vs SuprSend
- Expo Push Notifications vs Pingram
- Firebase Cloud Messaging vs Pingram
- Knock vs Pingram
- 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/courier-vs-pingram.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/courier.json·/api/v1/tools/pingram.json - From a terminal
anchor compare courier pingram(the CLI) - Over MCP
compare_tools {"a": "courier", "b": "pingram"}at/mcp, no key