{ "data": { "a": { "slug": "expo-push-notifications", "name": "Expo Push Notifications", "vendor": "Expo", "vendorUrl": "https://expo.dev", "kind": "http-api", "category": "notifications", "summary": "Hosted push service from Expo that takes one HTTPS request and relays it to Apple's APNs and Google's FCM for apps built with Expo. It issues push tickets and receipts, and sending is free.", "url": "https://www.anchorterminal.com/tools/expo-push-notifications", "markdownUrl": "https://www.anchorterminal.com/tools/expo-push-notifications.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/expo-push-notifications.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/expo-push-notifications.json", "repo": "https://github.com/expo/expo-server-sdk-node", "license": "Proprietary service under Expo's terms of service. The Node.js server SDK is MIT", "transports": [ "http" ], "remoteUrl": "https://exp.host/--/api/v2/push/send", "packages": [ { "registry": "npm", "name": "expo-server-sdk" } ], "auth": "mixed", "authNotes": "No credential by default. The docs say the API \"currently does not require any authentication\", and a send needs only an Expo push token. An owner can turn on enhanced push security in the EAS dashboard, after which every call needs `Authorization: Bearer \u003caccess token\u003e` or fails with `UNAUTHORIZED`. Tokens are personal access tokens, which act on everything the person can reach, or robot user tokens limited by role. Both are created and revoked by a person in the dashboard.", "pricing": "free", "pricingNotes": "Free. The push FAQ says there is no cost for sending through the service, and the pricing page lists no push charge. A send needs an Expo project with APNs and FCM credentials, which a person sets up on an Expo account. The Free plan is $0 a month, Starter $19 and Production $199, and those prices buy builds and updates, not push. Whether signup asks for a card was not stated.", "priceSummary": "Free", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the push docs, the pricing page or the Node SDK source (checked 2026-10-09).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": 1037, "npmWeekly": 1348515, "pypiWeekly": null, "asOf": "2026-10-09" }, "docsUrl": "https://docs.expo.dev/push-notifications/sending-notifications/", "llmsTxt": "https://docs.expo.dev/llms.txt", "capabilities": [ "notify.push" ], "tags": [ "hosted", "free", "push", "no-key", "llms-txt", "typescript", "closed-source", "status-page", "soc2" ], "lastRelease": "2026-08-24", "graded": true, "anchor": { "graded": true, "score": 58.8, "grade": "C", "agentReady": false, "rank": 571, "ranked": true, "rankOf": 950, "categoryRank": 9, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 63, "maintenance": 74, "payments": 40, "reliability": 65, "schema": 60, "security": 48, "transparency": 68 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-09" }, "negative": 0, "verdict": "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.", "bestFor": "An agent that must push to an app already built with Expo, at no cost and with one call for both platforms.", "strengths": [ "One POST to `https://exp.host/--/api/v2/push/send` reaches both APNs and FCM, with up to 100 messages a request", "Sending is free, per the push FAQ, and the Free plan costs $0 a month", "Limits are published. 600 notifications a second per project, 100 messages a request, 1,000 receipt IDs a request", "Docs are served as Markdown with an `llms.txt` index, and every message field is mapped to its APNs or FCM equivalent", "Expo states notification content is held only in memory and queues until handed to Apple or Google" ], "weaknesses": [ "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", "No idempotency key. Expo says a notification may reach Apple or Google more than once, or not at all", "No SLA for the push service, stated in the docs", "Three iOS push incidents on the status page since 4 August 2026, one a partial outage of 83 minutes and one a backlog of 4 hours 41 minutes", "No OpenAPI file or push API changelog was found, and only the Node.js SDK is maintained by Expo", "Expo's terms say accounts registered by bots, agents or other automated means are not permitted. This matters before any probe is run" ], "agentNotes": [ "Send an array of up to 100 messages per request, all for one project, and stay under 600 notifications a second", "Keep each ticket `id` and POST them to `/--/api/v2/push/getReceipts` about 15 minutes later. Receipts are cleared after 24 hours", "Stop sending to a token when a ticket or receipt returns `DeviceNotRegistered`", "If the project has enhanced push security on, send `Authorization: Bearer \u003caccess token\u003e` or the call fails with `UNAUTHORIZED`", "Retry 429 and 5xx with exponential backoff, and expect an occasional duplicate because there is no idempotency key" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 58.8 } ], "editorialScores": { "ergonomics": 63, "maintenance": 74, "payments": 40, "reliability": 65, "schema": 60, "security": 48, "transparency": 60 }, "provenanceScore": 76 }, "connect": { "install": "yarn add expo-server-sdk", "http": "curl -H \"Content-Type: application/json\" -X POST \"https://exp.host/--/api/v2/push/send\" -d '{\n \"to\": \"ExponentPushToken[xxxxxxxxxxxxxxxxxxxxxx]\",\n \"title\":\"hello\",\n \"body\": \"world\"\n}'" }, "letme": { "capability": "https://letme.dev/notify.push", "tool": "https://letme.dev/expo-push-notifications" }, "area": "everyday", "provenance": { "legalEntity": "650 Industries, Inc.", "domain": "expo.dev", "domainRegistered": "2019-02-22", "endpointOnVendorDomain": false, "terms": "https://expo.dev/terms", "privacy": "https://expo.dev/privacy", "statusPage": "https://status.expo.dev", "changelog": "https://github.com/expo/expo-server-sdk-node/blob/main/CHANGELOG.md", "securityTxt": "valid", "checked": "2026-10-09", "notes": [ "The terms (last updated 29 May 2025, effective 30 June 2025) are a contract with 650 Industries, Inc. and cover any product or service Expo makes available. They list EAS Build, Update, Submit, Hosting and Workflows by name and do not name the push service.", "The push API answers at exp.host, a second domain. Expo's docs and its Node SDK source name that host.", "expo.dev/.well-known/security.txt gives vulnerability-disclosures@expo.dev and a Canonical line and has no Expires field, which RFC 9116 requires.", "The privacy policy (last updated 21 October 2025) says Expo may collect end users' push tokens when the push service is used.", "expo.dev/robots.txt disallows `/expo-subscription-agreement`, so that agreement was not read.", "The registry's RDAP record for expo.dev gives a registration date of 2019-02-22. The changelog link is the Node SDK's, because no changelog for the push API itself was found." ], "score": 76 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/expo-push-notifications.json", "live": { "slug": "expo-push-notifications", "probe": { "target": "https://exp.host/--/api/v2/push/send", "method": "get", "lastAt": "2026-10-10T02:54:55.058129772Z", "lastOk": true, "lastStatus": 405, "lastMs": 121, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 127, "p95ms24h": 197, "samples24h": 115, "samples30d": 115, "days": [ { "date": "2026-10-09", "probes": 85, "ok": 85 }, { "date": "2026-10-10", "probes": 30, "ok": 30 } ] }, "vendorStatus": { "page": "https://status.expo.dev", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-10T02:50:18.829667993Z" }, "versions": [ { "registry": "github", "name": "expo/expo-server-sdk-node", "version": "v7.2.0", "released": "2026-08-24", "seenAt": "2026-10-09T16:52:32.455380467Z" }, { "registry": "npm", "name": "expo-server-sdk", "version": "7.2.0", "seenAt": "2026-10-09T16:52:31.59453516Z" } ], "githubStars": 1037, "npmWeekly": 1348515, "pages": [ { "url": "https://raw.githubusercontent.com/expo/expo-server-sdk-node/main/CHANGELOG.md", "kind": "changelog", "status": 200, "checkedAt": "2026-10-09T18:45:09.224081599Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "851125e2dd50" }, { "url": "https://expo.dev/privacy", "kind": "privacy", "status": 200, "checkedAt": "2026-10-09T18:39:14.02772659Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "42bd6fab5bc9" }, { "url": "https://expo.dev/terms", "kind": "terms", "status": 200, "checkedAt": "2026-10-09T18:39:16.223165435Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "d061e1a55580" } ], "updatedAt": "2026-10-10T02:54:55.058129772Z" } }, "answer": "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 \u0026 documentation.", "b": { "slug": "magicbell", "name": "MagicBell", "vendor": "MagicBell, Inc.", "vendorUrl": "https://www.magicbell.com", "kind": "http-api", "category": "notifications", "summary": "MagicBell is a hosted notification service that sends one broadcast to users across an in-app inbox, mobile and web push, email, SMS, Slack and Teams. Agents reach it through a REST API, a CLI and typed clients.", "url": "https://www.anchorterminal.com/tools/magicbell", "markdownUrl": "https://www.anchorterminal.com/tools/magicbell.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/magicbell.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/magicbell.json", "repo": "https://github.com/magicbell/magicbell-js", "license": "Proprietary service under MagicBell's terms. The Go client and the CLI are MIT. The JavaScript client carries MagicBell's own Licence Agreement", "transports": [ "http" ], "remoteUrl": "https://api.magicbell.com/v2", "packages": [ { "registry": "npm", "name": "magicbell-js" }, { "registry": "npm", "name": "magicbell-cli" }, { "registry": "go", "name": "github.com/magicbell/magicbell-go" } ], "auth": "api-key", "authNotes": "Self-serve. Every call takes a JWT as a Bearer token. A Project JWT is created in the dashboard under Project Auth with a name and an expiry, is shown once and can be discarded. It covers the whole project (broadcasts, users, integrations, workflows, events). A User JWT is signed by the customer's backend with HS256 from the project's API key and secret key, and covers one user's inbox, channel tokens and preferences. No scopes on either.", "pricing": "freemium", "pricingNotes": "Builder is $0 a month with 1,000 deliveries and one project, so an agent's owner can start without a contract. Startup is $249 a month with 50,000 deliveries and five projects, then $0.0025 a delivery and $99 a month per extra project. Enterprise is custom. A delivery is one notification on one channel for one user. Whether sign-up asks for a card was not checked (https://www.magicbell.com/pricing, checked 2026-10-09).", "priceSummary": "$249 / mo", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the docs, the OpenAPI file or the pricing page (checked 2026-10-09).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": 31, "npmWeekly": 48674, "pypiWeekly": null, "asOf": "2026-10-09" }, "docsUrl": "https://www.magicbell.com/docs", "openapi": "https://www.magicbell.com/docs/api/openapi.json", "capabilities": [ "notify.push", "notify.in-app", "notify.multichannel", "notify.preferences" ], "tags": [ "hosted", "freemium", "openapi", "typescript", "go", "swift", "java", "cli", "webhooks", "status-page" ], "lastRelease": "2026-07-29", "graded": true, "anchor": { "graded": true, "score": 58.8, "grade": "C", "agentReady": false, "rank": 572, "ranked": true, "rankOf": 950, "categoryRank": 10, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 63, "maintenance": 49, "payments": 35, "reliability": 75, "schema": 68, "security": 50, "transparency": 58 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-09" }, "negative": 0, "verdict": "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.", "bestFor": "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.", "strengths": [ "OpenAPI 3.1 file with 144 operations, published at `/docs/api/openapi.json` without a login", "`Idempotency-Key` header caches the first response for 24 hours on some endpoints", "Status page shows 100 per cent for the API and dashboard over 180 days to 7 October 2026", "Project tokens are named, take an expiry and can be discarded in the dashboard", "Builder plan at $0 with 1,000 deliveries a month, and overage on Startup at $0.0025 a delivery" ], "weaknesses": [ "No batching or digest step found. Workflows have four commands (broadcast, wait, pause, abort)", "No llms.txt or Markdown docs, and the OpenAPI file documents no error responses", "Project tokens are project-wide with no scopes or read-only mode", "No SLA, SOC 2 or ISO 27001 statement, security.txt or sub-processor list found", "The Trust Centre says data is never sold or shared, while the privacy policy of 2 July 2024 marks account data as sold or shared" ], "agentNotes": [ "Ask the owner for a Project JWT from the dashboard's Project Auth page. The terms forbid accounts registered by automated methods", "Send `Idempotency-Key` with a UUID on `POST /v2/broadcasts`, and reuse it on a retry within 24 hours", "Stay under 500 requests a minute per IP. A 429 blocks the address for 60 seconds, so put many recipients in one broadcast", "Use a Project JWT for broadcasts, users, integrations and workflows, and a User JWT for one user's inbox, tokens and preferences", "Read delivery failures from `GET /v2/events` and the broadcast's `status`, since email, SMS and push go through providers the owner connects" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 58.8 } ], "editorialScores": { "ergonomics": 63, "maintenance": 49, "payments": 35, "reliability": 75, "schema": 68, "security": 50, "transparency": 30 }, "provenanceScore": 86 }, "connect": { "install": "npm install magicbell-js", "http": "curl --request POST \\\n --url 'https://api.magicbell.com/v2/broadcasts' \\\n --header 'content-type: application/json' \\\n --header \"authorization: Bearer $TOKEN\" \\\n --data '{\"title\":\"Build finished\",\"recipients\":[{\"email\":\"test@example.com\"}]}'" }, "letme": { "capability": "https://letme.dev/notify.push", "tool": "https://letme.dev/magicbell" }, "area": "everyday", "unitPrices": [ { "item": "Startup", "unit": "month", "usd": 249, "note": "50,000 deliveries and five projects included" }, { "item": "Startup overage, per delivery", "unit": "message", "usd": 0.0025 }, { "item": "Additional project", "unit": "month", "usd": 99 } ], "provenance": { "legalEntity": "MagicBell, Inc.", "domain": "magicbell.com", "domainRegistered": "2004-04-17", "endpointOnVendorDomain": true, "terms": "https://www.magicbell.com/terms-and-conditions", "privacy": "https://www.magicbell.com/privacy-policy", "statusPage": "https://status.magicbell.com", "changelog": "https://github.com/orgs/magicbell/discussions/categories/changelog", "securityTxt": "none", "checked": "2026-10-09", "notes": [ "The terms and the privacy policy name MagicBell, Inc., 2261 Market Street #4311, San Francisco, California 94114. Both are dated 2 July 2024.", "The terms cover the website, the service and the API in one document, with a short section of API usage terms. They are governed by the law of the place where the owner is based.", "www.magicbell.com/.well-known/security.txt returns 404. The footer's vulnerability disclosure link is a contact form.", "RDAP for magicbell.com gives a registration date of 2004-04-17.", "The changelog is a category of GitHub Discussions, reached from magicbell.to/changelog." ], "score": 86 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/magicbell.json", "live": { "slug": "magicbell", "probe": { "target": "https://api.magicbell.com/v2", "method": "get", "lastAt": "2026-10-10T02:55:01.073978663Z", "lastOk": true, "lastStatus": 405, "lastMs": 83, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 75, "p95ms24h": 146, "samples24h": 199, "samples30d": 199, "days": [ { "date": "2026-10-09", "probes": 169, "ok": 169 }, { "date": "2026-10-10", "probes": 30, "ok": 30 } ] }, "vendorStatus": { "page": "https://status.magicbell.com", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-10-10T00:50:46.758560844Z" }, "versions": [ { "registry": "github", "name": "magicbell/magicbell-js", "version": "magicbell-js@1.8.0", "released": "2026-07-29", "seenAt": "2026-10-09T17:03:21.634893251Z" }, { "registry": "npm", "name": "magicbell-cli", "version": "1.4.0", "seenAt": "2026-10-09T17:03:20.318744385Z" }, { "registry": "npm", "name": "magicbell-js", "version": "1.8.0", "seenAt": "2026-10-09T17:03:19.39275514Z" } ], "githubStars": 31, "npmWeekly": 37252, "securityTxt": { "url": "https://magicbell.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-10-09T15:39:38.125987859Z" }, "pages": [ { "url": "https://www.magicbell.com/pricing", "kind": "pricing", "status": 200, "checkedAt": "2026-10-09T18:51:48.970314458Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "4cd91f59fc38" }, { "url": "https://www.magicbell.com/privacy-policy", "kind": "privacy", "status": 200, "checkedAt": "2026-10-09T18:51:52.097131207Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "bb8aafa9a2a2" }, { "url": "https://www.magicbell.com/terms-and-conditions", "kind": "terms", "status": 200, "checkedAt": "2026-10-09T18:51:53.094681634Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "b24be5d72a74" } ], "updatedAt": "2026-10-10T02:55:01.073978663Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Expo", "b": "MagicBell, Inc.", "name": "Vendor" }, { "a": "https://exp.host/--/api/v2/push/send", "b": "https://api.magicbell.com/v2", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP", "name": "Transports" }, { "a": "OAuth or key", "b": "API key", "name": "Auth" }, { "a": "Free", "b": "Freemium", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary service under Expo's terms of service. The Node.js server SDK is MIT", "b": "Proprietary service under MagicBell's terms. The Go client and the CLI are MIT. The JavaScript client carries MagicBell's own Licence Agreement", "name": "Licence" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "no", "name": "llms.txt" }, { "a": "2026-08-24", "b": "2026-07-29", "name": "Last release" }, { "a": "2025-05-29", "b": "no date given", "name": "Terms last updated" }, { "a": "2025-10-21", "b": "no date given", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "yes", "b": "yes", "name": "Terms restrict automated access" }, { "a": "not found in the text", "b": "not found in the text", "name": "Terms restrict benchmarking" }, { "a": "yes", "b": "not found in the text", "name": "Terms or service can change without notice" }, { "a": "yes", "b": "not found in the text", "name": "Arbitration or class-action waiver" }, { "a": "1k stars, 1.3M npm/wk", "b": "31 stars, 49k npm/wk", "name": "Popularity" } ], "faq": [ { "answer": "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 \u0026 documentation.", "question": "Which is better for AI agents, Expo Push Notifications or MagicBell?" }, { "answer": "Expo Push Notifications takes an API key or an OAuth sign-in. MagicBell needs an API key.", "question": "Do Expo Push Notifications and MagicBell need an API key?" }, { "answer": "Yes. Expo Push Notifications has a hosted endpoint at https://exp.host/--/api/v2/push/send and MagicBell at https://api.magicbell.com/v2.", "question": "Can an agent call Expo Push Notifications and MagicBell without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Payments \u0026 pricing, 40 against 35", "Maintenance \u0026 community, 74 against 49", "Transparency \u0026 trust, 68 against 58" ], "also": null, "goodFor": "An agent that must push to an app already built with Expo, at no cost and with one call for both platforms.", "slug": "expo-push-notifications", "watchFor": "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" }, { "aheadOn": [ "Reliability, 75 against 65", "Schema \u0026 documentation, 68 against 60" ], "also": null, "goodFor": "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.", "slug": "magicbell", "watchFor": "No batching or digest step found. Workflows have four commands (broadcast, wait, pause, abort)" } ], "job": { "capability": "notify.push", "name": "Push notifications" }, "others": [ { "json": "https://www.anchorterminal.com/compare/amazon-sns-vs-expo-push-notifications.json", "title": "Amazon SNS vs Expo Push Notifications", "url": "https://www.anchorterminal.com/compare/amazon-sns-vs-expo-push-notifications" }, { "json": "https://www.anchorterminal.com/compare/amazon-sns-vs-magicbell.json", "title": "Amazon SNS vs MagicBell", "url": "https://www.anchorterminal.com/compare/amazon-sns-vs-magicbell" }, { "json": "https://www.anchorterminal.com/compare/courier-vs-expo-push-notifications.json", "title": "Courier vs Expo Push Notifications", "url": "https://www.anchorterminal.com/compare/courier-vs-expo-push-notifications" }, { "json": "https://www.anchorterminal.com/compare/courier-vs-magicbell.json", "title": "Courier vs MagicBell", "url": "https://www.anchorterminal.com/compare/courier-vs-magicbell" }, { "json": "https://www.anchorterminal.com/compare/expo-push-notifications-vs-firebase-cloud-messaging.json", "title": "Expo Push Notifications vs Firebase Cloud Messaging", "url": "https://www.anchorterminal.com/compare/expo-push-notifications-vs-firebase-cloud-messaging" }, { "json": "https://www.anchorterminal.com/compare/expo-push-notifications-vs-knock.json", "title": "Expo Push Notifications vs Knock", "url": "https://www.anchorterminal.com/compare/expo-push-notifications-vs-knock" }, { "json": "https://www.anchorterminal.com/compare/expo-push-notifications-vs-novu.json", "title": "Expo Push Notifications vs Novu", "url": "https://www.anchorterminal.com/compare/expo-push-notifications-vs-novu" }, { "json": "https://www.anchorterminal.com/compare/expo-push-notifications-vs-ntfy.json", "title": "Expo Push Notifications vs ntfy", "url": "https://www.anchorterminal.com/compare/expo-push-notifications-vs-ntfy" }, { "json": "https://www.anchorterminal.com/compare/expo-push-notifications-vs-onesignal.json", "title": "Expo Push Notifications vs OneSignal", "url": "https://www.anchorterminal.com/compare/expo-push-notifications-vs-onesignal" }, { "json": "https://www.anchorterminal.com/compare/expo-push-notifications-vs-pingram.json", "title": "Expo Push Notifications vs Pingram", "url": "https://www.anchorterminal.com/compare/expo-push-notifications-vs-pingram" }, { "json": "https://www.anchorterminal.com/compare/expo-push-notifications-vs-pushover.json", "title": "Expo Push Notifications vs Pushover", "url": "https://www.anchorterminal.com/compare/expo-push-notifications-vs-pushover" }, { "json": "https://www.anchorterminal.com/compare/expo-push-notifications-vs-suprsend.json", "title": "Expo Push Notifications vs SuprSend", "url": "https://www.anchorterminal.com/compare/expo-push-notifications-vs-suprsend" }, { "json": "https://www.anchorterminal.com/compare/firebase-cloud-messaging-vs-magicbell.json", "title": "Firebase Cloud Messaging vs MagicBell", "url": "https://www.anchorterminal.com/compare/firebase-cloud-messaging-vs-magicbell" }, { "json": "https://www.anchorterminal.com/compare/knock-vs-magicbell.json", "title": "Knock vs MagicBell", "url": "https://www.anchorterminal.com/compare/knock-vs-magicbell" }, { "json": "https://www.anchorterminal.com/compare/magicbell-vs-novu.json", "title": "MagicBell vs Novu", "url": "https://www.anchorterminal.com/compare/magicbell-vs-novu" }, { "json": "https://www.anchorterminal.com/compare/magicbell-vs-ntfy.json", "title": "MagicBell vs ntfy", "url": "https://www.anchorterminal.com/compare/magicbell-vs-ntfy" }, { "json": "https://www.anchorterminal.com/compare/magicbell-vs-onesignal.json", "title": "MagicBell vs OneSignal", "url": "https://www.anchorterminal.com/compare/magicbell-vs-onesignal" }, { "json": "https://www.anchorterminal.com/compare/magicbell-vs-pingram.json", "title": "MagicBell vs Pingram", "url": "https://www.anchorterminal.com/compare/magicbell-vs-pingram" }, { "json": "https://www.anchorterminal.com/compare/magicbell-vs-pushover.json", "title": "MagicBell vs Pushover", "url": "https://www.anchorterminal.com/compare/magicbell-vs-pushover" }, { "json": "https://www.anchorterminal.com/compare/magicbell-vs-suprsend.json", "title": "MagicBell vs SuprSend", "url": "https://www.anchorterminal.com/compare/magicbell-vs-suprsend" } ], "scores": [ { "by": 10, "edge": "magicbell", "expo-push-notifications": 65, "key": "reliability", "magicbell": 75, "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 8, "edge": "magicbell", "expo-push-notifications": 60, "key": "schema", "magicbell": 68, "name": "Schema \u0026 documentation", "weight": 13 }, { "by": 0, "edge": "", "expo-push-notifications": 63, "key": "ergonomics", "magicbell": 63, "name": "Agent ergonomics", "weight": 13 }, { "by": 2, "edge": "magicbell", "expo-push-notifications": 48, "key": "security", "magicbell": 50, "name": "Security \u0026 auth", "weight": 14 }, { "by": 5, "edge": "expo-push-notifications", "expo-push-notifications": 40, "key": "payments", "magicbell": 35, "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 25, "edge": "expo-push-notifications", "expo-push-notifications": 74, "key": "maintenance", "magicbell": 49, "name": "Maintenance \u0026 community", "weight": 7 }, { "by": 10, "edge": "expo-push-notifications", "expo-push-notifications": 68, "key": "transparency", "magicbell": 58, "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "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 \u0026 documentation. Both do push notifications.", "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." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/expo-push-notifications-vs-magicbell", "json": "https://www.anchorterminal.com/compare/expo-push-notifications-vs-magicbell.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/expo-push-notifications-vs-magicbell.md", "slim": "https://www.anchorterminal.com/compare/expo-push-notifications-vs-magicbell.min.md" }, "markdown": "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 \u0026 documentation. Both do push notifications.\n\n- 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\n- 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\n- Best notification APIs for AI agents: https://www.anchorterminal.com/best/notifications/index.md\n- All 66 notifications comparisons: https://www.anchorterminal.com/compare/notifications/index.md\n\n## Which one, for what\n\n### Expo Push Notifications (C)\n\nGood for: An agent that must push to an app already built with Expo, at no cost and with one call for both platforms.\n\nAhead on:\n- Payments \u0026 pricing, 40 against 35\n- Maintenance \u0026 community, 74 against 49\n- Transparency \u0026 trust, 68 against 58\n\nWatch 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\n\n### MagicBell (C)\n\nGood 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.\n\nAhead on:\n- Reliability, 75 against 65\n- Schema \u0026 documentation, 68 against 60\n\nWatch for: No batching or digest step found. Workflows have four commands (broadcast, wait, pause, abort)\n\n\n## Score by category\n\n| Category | Weight | Expo Push Notifications | MagicBell | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 65 | 75 | MagicBell +10 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 60 | 68 | MagicBell +8 |\n| Agent ergonomics | 13% (16.2 this run) | 63 | 63 | even |\n| Security \u0026 auth | 14% (17.5 this run) | 48 | 50 | MagicBell +2 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 40 | 35 | Expo Push Notifications +5 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 74 | 49 | Expo Push Notifications +25 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 68 | 58 | Expo Push Notifications +10 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **58.8 · C** | **58.8 · C** | |\n\n## Facts side by side\n\n| Fact | Expo Push Notifications | MagicBell |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Expo | MagicBell, Inc. |\n| Hosted endpoint | `https://exp.host/--/api/v2/push/send` | `https://api.magicbell.com/v2` |\n| Transports | HTTP | HTTP |\n| Auth | OAuth or key | API key |\n| Pricing | Free | Freemium |\n| x402 | no | no |\n| 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 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | no |\n| Last release | 2026-08-24 | 2026-07-29 |\n| Terms last updated | 2025-05-29 | no date given |\n| Privacy policy last updated | 2025-10-21 | no date given |\n| Customer content may train models | not found in the text | not found in the text |\n| Terms restrict automated access | yes | yes |\n| Terms restrict benchmarking | not found in the text | not found in the text |\n| Terms or service can change without notice | yes | not found in the text |\n| Arbitration or class-action waiver | yes | not found in the text |\n| Popularity | 1k stars, 1.3M npm/wk | 31 stars, 49k npm/wk |\n\n## Verdicts\n\n**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.\n\n**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.\n\n## Before you call either\n\n### Expo Push Notifications\n\n1. Send an array of up to 100 messages per request, all for one project, and stay under 600 notifications a second\n2. Keep each ticket `id` and POST them to `/--/api/v2/push/getReceipts` about 15 minutes later. Receipts are cleared after 24 hours\n3. Stop sending to a token when a ticket or receipt returns `DeviceNotRegistered`\n4. If the project has enhanced push security on, send `Authorization: Bearer \u003caccess token\u003e` or the call fails with `UNAUTHORIZED`\n5. Retry 429 and 5xx with exponential backoff, and expect an occasional duplicate because there is no idempotency key\n\n### MagicBell\n\n1. Ask the owner for a Project JWT from the dashboard's Project Auth page. The terms forbid accounts registered by automated methods\n2. Send `Idempotency-Key` with a UUID on `POST /v2/broadcasts`, and reuse it on a retry within 24 hours\n3. Stay under 500 requests a minute per IP. A 429 blocks the address for 60 seconds, so put many recipients in one broadcast\n4. Use a Project JWT for broadcasts, users, integrations and workflows, and a User JWT for one user's inbox, tokens and preferences\n5. Read delivery failures from `GET /v2/events` and the broadcast's `status`, since email, SMS and push go through providers the owner connects\n\n## Questions\n\n### Which is better for AI agents, Expo Push Notifications or MagicBell?\n\nExpo 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 \u0026 documentation.\n\n### Do Expo Push Notifications and MagicBell need an API key?\n\nExpo Push Notifications takes an API key or an OAuth sign-in. MagicBell needs an API key.\n\n### Can an agent call Expo Push Notifications and MagicBell without installing anything?\n\nYes. Expo Push Notifications has a hosted endpoint at https://exp.host/--/api/v2/push/send and MagicBell at https://api.magicbell.com/v2.\n\n\n## For agents\n\n- 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\n- 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`\n- 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\n\n## Other comparisons with Expo Push Notifications or MagicBell\n\n- [Amazon SNS vs Expo Push Notifications](https://www.anchorterminal.com/compare/amazon-sns-vs-expo-push-notifications.md)\n- [Amazon SNS vs MagicBell](https://www.anchorterminal.com/compare/amazon-sns-vs-magicbell.md)\n- [Courier vs Expo Push Notifications](https://www.anchorterminal.com/compare/courier-vs-expo-push-notifications.md)\n- [Courier vs MagicBell](https://www.anchorterminal.com/compare/courier-vs-magicbell.md)\n- [Expo Push Notifications vs Firebase Cloud Messaging](https://www.anchorterminal.com/compare/expo-push-notifications-vs-firebase-cloud-messaging.md)\n- [Expo Push Notifications vs Knock](https://www.anchorterminal.com/compare/expo-push-notifications-vs-knock.md)\n- [Expo Push Notifications vs Novu](https://www.anchorterminal.com/compare/expo-push-notifications-vs-novu.md)\n- [Expo Push Notifications vs ntfy](https://www.anchorterminal.com/compare/expo-push-notifications-vs-ntfy.md)\n- [Expo Push Notifications vs OneSignal](https://www.anchorterminal.com/compare/expo-push-notifications-vs-onesignal.md)\n- [Expo Push Notifications vs Pingram](https://www.anchorterminal.com/compare/expo-push-notifications-vs-pingram.md)\n- [Expo Push Notifications vs Pushover](https://www.anchorterminal.com/compare/expo-push-notifications-vs-pushover.md)\n- [Expo Push Notifications vs SuprSend](https://www.anchorterminal.com/compare/expo-push-notifications-vs-suprsend.md)\n- [Firebase Cloud Messaging vs MagicBell](https://www.anchorterminal.com/compare/firebase-cloud-messaging-vs-magicbell.md)\n- [Knock vs MagicBell](https://www.anchorterminal.com/compare/knock-vs-magicbell.md)\n- [MagicBell vs Novu](https://www.anchorterminal.com/compare/magicbell-vs-novu.md)\n- [MagicBell vs ntfy](https://www.anchorterminal.com/compare/magicbell-vs-ntfy.md)\n- [MagicBell vs OneSignal](https://www.anchorterminal.com/compare/magicbell-vs-onesignal.md)\n- [MagicBell vs Pingram](https://www.anchorterminal.com/compare/magicbell-vs-pingram.md)\n- [MagicBell vs Pushover](https://www.anchorterminal.com/compare/magicbell-vs-pushover.md)\n- [MagicBell vs SuprSend](https://www.anchorterminal.com/compare/magicbell-vs-suprsend.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-10-10", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.4", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Expo Push Notifications vs MagicBell", "url": "" } ], "description": "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.", "facts": [ "Expo Push Notifications C 58.8", "MagicBell C 58.8", "scores" ], "h1": "Expo Push Notifications vs MagicBell", "image": "https://www.anchorterminal.com/assets/og/compare-expo-push-notifications-vs-magicbell.png", "path": "/compare/expo-push-notifications-vs-magicbell", "published": "2026-10-01", "section": "tools", "title": "Expo Push Notifications vs MagicBell for AI agents (2026)", "toc": null, "updated": "2026-10-09", "url": "https://www.anchorterminal.com/compare/expo-push-notifications-vs-magicbell" }, "tokens": { "markdown": 2450, "slim": 680 }, "version": 1 }