Get an audit

Head to head · Notify push · October 2026 research run

Courier vs MagicBell

Courier scores 70.5 (BB) on agent readiness against MagicBell's 58.8 (C), and leads in 6 of 7 scored categories. Both do notify push.

CourierCourier · HTTP API BB70.5/100#146 of 841 MagicBellMagicBell, Inc. · HTTP API C58.8/100#515 of 841

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 75
  • Schema & documentation, 84 against 68
  • Agent ergonomics, 68 against 63
  • Security & auth, 56 against 50
  • Maintenance & community, 86 against 49
  • Transparency & trust, 65 against 58

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

MagicBell C

Good for A product team that wants an embeddable in-app inbox with push, email, SMS, Slack and Teams behind one broadcast call, and an agent that sends notifications with a project token it was given.

No category where it leads by five points or more, and no fact that sets it apart.

Watch for

No batching or digest step found. Workflows have four commands (broadcast, wait, pause, abort)

Score by category

CategoryWeight this runCourierMagicBellEdge
Reliability16%209275Courier +17
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28468Courier +16
Agent ergonomics13%16.26863Courier +5
Security & auth14%17.55650Courier +6
Payments & pricing10%12.53535even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.88649Courier +37
Transparency & trust7%8.86558Courier +7
Negative events≤1500
Total70.5 · BB58.8 · C

Facts side by side

FactCourierMagicBell
KindHTTP APIHTTP API
VendorCourierMagicBell, Inc.
Hosted endpointhttps://api.courier.comhttps://api.magicbell.com/v2
TransportsHTTP, Streamable HTTPHTTP
AuthAPI keyAPI key
PricingFreemiumFreemium
x402nono
LicenceApache-2.0 (Node SDK)Proprietary service under MagicBell's terms. The Go client and the CLI are MIT. The JavaScript client carries MagicBell's own Licence Agreement
Tools exposed170none
Read-only variant documentednono
llms.txtyesno
MCP registryio.github.trycourier/couriernot listed
Last release2026-09-242026-07-29
Terms last updated2026-09-10no date given
Privacy policy last updated2025-12-08no date given
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textyes
Terms restrict benchmarkingnot found in the textnot found in the text
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waivernot found in the textnot found in the text
Popularity63 stars, 189k npm/wk, 35k PyPI/wk31 stars, 49k npm/wk
Agent reviews3/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.

MagicBell

A public OpenAPI 3.1 file covers all 144 operations, with idempotency keys and a status page showing no API downtime in 180 days. No batching or digest step, llms.txt, error code list, SLA or sub-processor list was found, and project tokens carry no scopes.

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. Space resends at least 2 seconds apart per message or you get a 429

MagicBell

  1. Ask the owner for a Project JWT from the dashboard's Project Auth page. The terms forbid accounts registered by automated methods
  2. Send Idempotency-Key with a UUID on POST /v2/broadcasts, and reuse it on a retry within 24 hours
  3. Stay under 500 requests a minute per IP. A 429 blocks the address for 60 seconds, so put many recipients in one broadcast
  4. Use a Project JWT for broadcasts, users, integrations and workflows, and a User JWT for one user's inbox, tokens and preferences
  5. Read delivery failures from GET /v2/events and the broadcast's status, since email, SMS and push go through providers the owner connects

Questions

Which is better for AI agents, Courier or MagicBell?

Courier scores 70.5 (BB) on agent readiness against MagicBell's 58.8 (C), and leads in 6 of 7 scored categories.

Do Courier and MagicBell need an API key?

Both need an API key.

Can an agent call Courier and MagicBell without installing anything?

Yes. Courier has a hosted endpoint at https://api.courier.com and MagicBell at https://api.magicbell.com/v2.

Other comparisons with Courier or MagicBell

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.

Get an auditSee a sample report