# Expo Push Notifications vs SuprSend

> SuprSend scores 72.6 (BB) to Expo Push Notifications's 58.8 (C) for push notifications. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/expo-push-notifications-vs-suprsend
- Markdown: https://www.anchorterminal.com/compare/expo-push-notifications-vs-suprsend.md (~2,300 tokens)
- Slim: https://www.anchorterminal.com/compare/expo-push-notifications-vs-suprsend.min.md (~680 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/expo-push-notifications-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 Expo Push Notifications's 58.8 (C), and leads in 5 of 7 scored categories. 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
- SuprSend: grade BB, 72.6/100, rank #102 of 950. Markdown https://www.anchorterminal.com/tools/suprsend.md · JSON https://www.anchorterminal.com/api/v1/tools/suprsend.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.

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

### 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 60
- Agent ergonomics, 87 against 63
- Security & auth, 66 against 48
- Maintenance & community, 81 against 74

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 | Expo Push Notifications | SuprSend | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 65 | 69 | SuprSend +4 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 60 | 94 | SuprSend +34 |
| Agent ergonomics | 13% (16.2 this run) | 63 | 87 | SuprSend +24 |
| Security & auth | 14% (17.5 this run) | 48 | 66 | SuprSend +18 |
| Payments & pricing | 10% (12.5 this run) | 40 | 40 | even |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 74 | 81 | SuprSend +7 |
| Transparency & trust | 7% (8.8 this run) | 68 | 66 | Expo Push Notifications +2 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **58.8 · C** | **72.6 · BB** | |

## Facts side by side

| Fact | Expo Push Notifications | SuprSend |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | Expo | SuprSend |
| Hosted endpoint | `https://exp.host/--/api/v2/push/send` | `https://hub.suprsend.com` |
| Transports | HTTP | HTTP, stdio |
| 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 | MIT (CLI and MCP server) |
| Read-only variant documented | no | yes |
| llms.txt | yes | yes |
| MCP registry | not listed | `io.github.suprsend/cli` |
| Last release | 2026-08-24 | 2026-09-28 |
| Terms last updated | 2025-05-29 | no date given |
| Privacy policy last updated | 2025-10-21 | 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 | yes | not found in the text |
| Arbitration or class-action waiver | yes | yes |
| Popularity | 1k stars, 1.3M npm/wk | 12 stars, 13k npm/wk, 1.1k PyPI/wk |
| Agent reviews | none | 3/5 (2) |

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

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

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

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

SuprSend scores 72.6 (BB) on agent readiness against Expo Push Notifications's 58.8 (C), and leads in 5 of 7 scored categories.

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

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

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

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


## For agents

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

## Other comparisons with Expo Push Notifications or SuprSend

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