# Expo Push Notifications vs MagicBell

> Expo Push Notifications and MagicBell score within a point of each other for push notifications, 58.8 and 58.8 out of 100. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/expo-push-notifications-vs-magicbell
- Markdown: https://www.anchorterminal.com/compare/expo-push-notifications-vs-magicbell.md (~2,450 tokens)
- Slim: https://www.anchorterminal.com/compare/expo-push-notifications-vs-magicbell.min.md (~680 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/expo-push-notifications-vs-magicbell.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

Expo Push Notifications and MagicBell score within a point of each other on agent readiness, 58.8 (C) and 58.8 (C). MagicBell leads on reliability and schema & documentation. Both do push notifications.

- Expo Push Notifications: grade C, 58.8/100, rank #571 of 950. Markdown https://www.anchorterminal.com/tools/expo-push-notifications.md · JSON https://www.anchorterminal.com/api/v1/tools/expo-push-notifications.json
- MagicBell: grade C, 58.8/100, rank #572 of 950. Markdown https://www.anchorterminal.com/tools/magicbell.md · JSON https://www.anchorterminal.com/api/v1/tools/magicbell.json
- Best notification APIs for AI agents: https://www.anchorterminal.com/best/notifications/index.md
- All 66 notifications comparisons: https://www.anchorterminal.com/compare/notifications/index.md

## Which one, for what

### Expo Push Notifications (C)

Good for: An agent that must push to an app already built with Expo, at no cost and with one call for both platforms.

Ahead on:
- Payments & pricing, 40 against 35
- Maintenance & community, 74 against 49
- Transparency & trust, 68 against 58

Watch for: The send API needs no authentication by default, so anyone holding a push token can send to that device until the owner enables access tokens

### 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 65
- Schema & documentation, 68 against 60

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


## Score by category

| Category | Weight | Expo Push Notifications | MagicBell | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 65 | 75 | MagicBell +10 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 60 | 68 | MagicBell +8 |
| Agent ergonomics | 13% (16.2 this run) | 63 | 63 | even |
| Security & auth | 14% (17.5 this run) | 48 | 50 | MagicBell +2 |
| Payments & pricing | 10% (12.5 this run) | 40 | 35 | Expo Push Notifications +5 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 74 | 49 | Expo Push Notifications +25 |
| Transparency & trust | 7% (8.8 this run) | 68 | 58 | Expo Push Notifications +10 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **58.8 · C** | **58.8 · C** | |

## Facts side by side

| Fact | Expo Push Notifications | MagicBell |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | Expo | MagicBell, Inc. |
| Hosted endpoint | `https://exp.host/--/api/v2/push/send` | `https://api.magicbell.com/v2` |
| Transports | HTTP | HTTP |
| Auth | OAuth or key | API key |
| Pricing | Free | Freemium |
| x402 | no | no |
| Licence | Proprietary service under Expo's terms of service. The Node.js server SDK is MIT | Proprietary service under MagicBell's terms. The Go client and the CLI are MIT. The JavaScript client carries MagicBell's own Licence Agreement |
| Read-only variant documented | no | no |
| llms.txt | yes | no |
| Last release | 2026-08-24 | 2026-07-29 |
| Terms last updated | 2025-05-29 | no date given |
| Privacy policy last updated | 2025-10-21 | no date given |
| 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 | not found in the text |
| Terms or service can change without notice | yes | not found in the text |
| Arbitration or class-action waiver | yes | not found in the text |
| Popularity | 1k stars, 1.3M npm/wk | 31 stars, 49k npm/wk |

## Verdicts

**Expo Push Notifications.** A free push relay with a small, well documented HTTP API, published limits of 600 notifications a second and written error codes. Sending needs no credential unless the owner turns on access tokens, there is no idempotency key or SLA, and the status page records three iOS push incidents since 4 August 2026.

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

### Expo Push Notifications

1. Send an array of up to 100 messages per request, all for one project, and stay under 600 notifications a second
2. Keep each ticket `id` and POST them to `/--/api/v2/push/getReceipts` about 15 minutes later. Receipts are cleared after 24 hours
3. Stop sending to a token when a ticket or receipt returns `DeviceNotRegistered`
4. If the project has enhanced push security on, send `Authorization: Bearer <access token>` or the call fails with `UNAUTHORIZED`
5. Retry 429 and 5xx with exponential backoff, and expect an occasional duplicate because there is no idempotency key

### 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, Expo Push Notifications or MagicBell?

Expo Push Notifications and MagicBell score within a point of each other on agent readiness, 58.8 (C) and 58.8 (C). MagicBell leads on reliability and schema & documentation.

### Do Expo Push Notifications and MagicBell need an API key?

Expo Push Notifications takes an API key or an OAuth sign-in. MagicBell needs an API key.

### Can an agent call Expo Push Notifications and MagicBell without installing anything?

Yes. Expo Push Notifications has a hosted endpoint at https://exp.host/--/api/v2/push/send and MagicBell at https://api.magicbell.com/v2.


## For agents

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

## Other comparisons with Expo Push Notifications or MagicBell

- [Amazon SNS vs Expo Push Notifications](https://www.anchorterminal.com/compare/amazon-sns-vs-expo-push-notifications.md)
- [Amazon SNS vs MagicBell](https://www.anchorterminal.com/compare/amazon-sns-vs-magicbell.md)
- [Courier vs Expo Push Notifications](https://www.anchorterminal.com/compare/courier-vs-expo-push-notifications.md)
- [Courier vs MagicBell](https://www.anchorterminal.com/compare/courier-vs-magicbell.md)
- [Expo Push Notifications vs Firebase Cloud Messaging](https://www.anchorterminal.com/compare/expo-push-notifications-vs-firebase-cloud-messaging.md)
- [Expo Push Notifications vs Knock](https://www.anchorterminal.com/compare/expo-push-notifications-vs-knock.md)
- [Expo Push Notifications vs Novu](https://www.anchorterminal.com/compare/expo-push-notifications-vs-novu.md)
- [Expo Push Notifications vs ntfy](https://www.anchorterminal.com/compare/expo-push-notifications-vs-ntfy.md)
- [Expo Push Notifications vs OneSignal](https://www.anchorterminal.com/compare/expo-push-notifications-vs-onesignal.md)
- [Expo Push Notifications vs Pingram](https://www.anchorterminal.com/compare/expo-push-notifications-vs-pingram.md)
- [Expo Push Notifications vs Pushover](https://www.anchorterminal.com/compare/expo-push-notifications-vs-pushover.md)
- [Expo Push Notifications vs SuprSend](https://www.anchorterminal.com/compare/expo-push-notifications-vs-suprsend.md)
- [Firebase Cloud Messaging vs MagicBell](https://www.anchorterminal.com/compare/firebase-cloud-messaging-vs-magicbell.md)
- [Knock vs MagicBell](https://www.anchorterminal.com/compare/knock-vs-magicbell.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 Pingram](https://www.anchorterminal.com/compare/magicbell-vs-pingram.md)
- [MagicBell vs Pushover](https://www.anchorterminal.com/compare/magicbell-vs-pushover.md)
- [MagicBell vs SuprSend](https://www.anchorterminal.com/compare/magicbell-vs-suprsend.md)