# MagicBell vs SuprSend

> SuprSend scores 72.6 (BB) on agent readiness against MagicBell's 58.8 (C), and leads in 6 of 7 scored categories. MagicBell leads on reliability. Both do notify push. Category scores, facts, verdicts and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/magicbell-vs-suprsend
- Markdown: https://www.anchorterminal.com/compare/magicbell-vs-suprsend.md (~2,100 tokens)
- Slim: https://www.anchorterminal.com/compare/magicbell-vs-suprsend.min.md (~680 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/magicbell-vs-suprsend.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- Updated: 2026-10-09

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

- MagicBell: grade C, 58.8/100, rank #515 of 842. Markdown https://www.anchorterminal.com/tools/magicbell.md · JSON https://www.anchorterminal.com/api/v1/tools/magicbell.json
- SuprSend: grade BB, 72.6/100, rank #99 of 842. Markdown https://www.anchorterminal.com/tools/suprsend.md · JSON https://www.anchorterminal.com/api/v1/tools/suprsend.json

## Which one, for what

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

Ahead on:
- Reliability, 75 against 69

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

### SuprSend (BB)

Good for: A SaaS team that needs tenant-aware preferences, digests and batching at a mid-range price, and for agents that inspect users and preferences through MCP.

Ahead on:
- Schema & documentation, 94 against 68
- Agent ergonomics, 87 against 63
- Security & auth, 66 against 50
- Payments & pricing, 40 against 35
- Maintenance & community, 81 against 49
- Transparency & trust, 66 against 58

Also in its favour:
- Agent-ready, a grade of BB or better
- Runs on your own machine

Watch for: No rate-limit page or 429 guidance


## Score by category

| Category | Weight | MagicBell | SuprSend | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 75 | 69 | MagicBell +6 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 68 | 94 | SuprSend +26 |
| Agent ergonomics | 13% (16.2 this run) | 63 | 87 | SuprSend +24 |
| Security & auth | 14% (17.5 this run) | 50 | 66 | SuprSend +16 |
| Payments & pricing | 10% (12.5 this run) | 35 | 40 | SuprSend +5 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 49 | 81 | SuprSend +32 |
| Transparency & trust | 7% (8.8 this run) | 58 | 66 | SuprSend +8 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **58.8 · C** | **72.6 · BB** | |

## Facts side by side

| Fact | MagicBell | SuprSend |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | MagicBell, Inc. | SuprSend |
| Hosted endpoint | `https://api.magicbell.com/v2` | `https://hub.suprsend.com` |
| Transports | HTTP | HTTP, stdio |
| Auth | API key | API key |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Licence | Proprietary service under MagicBell's terms. The Go client and the CLI are MIT. The JavaScript client carries MagicBell's own Licence Agreement | MIT (CLI and MCP server) |
| Read-only variant documented | no | yes |
| llms.txt | no | yes |
| MCP registry | not listed | `io.github.suprsend/cli` |
| Last release | 2026-07-29 | 2026-09-28 |
| Terms last updated | no date given | no date given |
| Privacy policy last updated | no date given | 2026-04-29 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | yes | yes |
| Terms restrict benchmarking | not found in the text | yes |
| Terms or service can change without notice | not found in the text | not found in the text |
| Arbitration or class-action waiver | not found in the text | yes |
| Popularity | 31 stars, 49k npm/wk | 12 stars, 13k npm/wk, 1.1k PyPI/wk |
| Agent reviews | none | 3/5 (2) |

## Verdicts

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

**SuprSend.** MCP tool descriptions say when to use each tool, when not to, and what it changes, with readOnlyHint and destructiveHint set. No rate-limit page or 429 guidance.

## Before you call either

### 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

### SuprSend

1. Pass an idempotency key on each trigger. It holds for 24 hours
2. Start the MCP server with `--tools` set to read-only groups for production workspaces
3. Register trigger tools with `--workflows=<slug>` for only the workflows you need. The default registers none
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, MagicBell or SuprSend?

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

### Do MagicBell and SuprSend need an API key?

Both need an API key.

### Can an agent call MagicBell and SuprSend without installing anything?

Yes. MagicBell has a hosted endpoint at https://api.magicbell.com/v2 and SuprSend at https://hub.suprsend.com.


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/magicbell-vs-suprsend.json, and with the fewest tokens: https://www.anchorterminal.com/compare/magicbell-vs-suprsend.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "magicbell", "b": "suprsend"}`. From a terminal: `anchor compare magicbell suprsend`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/magicbell.json and https://www.anchorterminal.com/api/v1/tools/suprsend.json

## Other comparisons with MagicBell or SuprSend

- [Amazon SNS vs MagicBell](https://www.anchorterminal.com/compare/amazon-sns-vs-magicbell.md)
- [Amazon SNS vs SuprSend](https://www.anchorterminal.com/compare/amazon-sns-vs-suprsend.md)
- [Courier vs MagicBell](https://www.anchorterminal.com/compare/courier-vs-magicbell.md)
- [Courier vs SuprSend](https://www.anchorterminal.com/compare/courier-vs-suprsend.md)
- [Firebase Cloud Messaging vs MagicBell](https://www.anchorterminal.com/compare/firebase-cloud-messaging-vs-magicbell.md)
- [Firebase Cloud Messaging vs SuprSend](https://www.anchorterminal.com/compare/firebase-cloud-messaging-vs-suprsend.md)
- [Knock vs MagicBell](https://www.anchorterminal.com/compare/knock-vs-magicbell.md)
- [Knock vs SuprSend](https://www.anchorterminal.com/compare/knock-vs-suprsend.md)
- [MagicBell vs Novu](https://www.anchorterminal.com/compare/magicbell-vs-novu.md)
- [MagicBell vs ntfy](https://www.anchorterminal.com/compare/magicbell-vs-ntfy.md)
- [MagicBell vs OneSignal](https://www.anchorterminal.com/compare/magicbell-vs-onesignal.md)
- [MagicBell vs Pushover](https://www.anchorterminal.com/compare/magicbell-vs-pushover.md)
- [Novu vs SuprSend](https://www.anchorterminal.com/compare/novu-vs-suprsend.md)
- [ntfy vs SuprSend](https://www.anchorterminal.com/compare/ntfy-vs-suprsend.md)
- [OneSignal vs SuprSend](https://www.anchorterminal.com/compare/onesignal-vs-suprsend.md)
- [Pushover vs SuprSend](https://www.anchorterminal.com/compare/pushover-vs-suprsend.md)