{ "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": "OneSignal scores 69.3 (B) on agent readiness against Expo Push Notifications's 58.8 (C), and leads in 6 of 7 scored categories. Expo Push Notifications leads on payments \u0026 pricing.", "b": { "slug": "onesignal", "name": "OneSignal", "vendor": "OneSignal", "vendorUrl": "https://onesignal.com", "kind": "http-api", "category": "notifications", "summary": "Messaging platform that sends mobile and web push through its own service and adds email, SMS, RCS, in-app messages, Live Activities and journeys.", "url": "https://www.anchorterminal.com/tools/onesignal", "markdownUrl": "https://www.anchorterminal.com/tools/onesignal.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/onesignal.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/onesignal.json", "repo": "https://github.com/OneSignal/onesignal-node-api", "license": "Modified MIT (Node SDK, use limited to OneSignal's services)", "transports": [ "http", "streamable-http" ], "remoteUrl": "https://api.onesignal.com", "packages": [ { "registry": "npm", "name": "@onesignal/node-onesignal" }, { "registry": "pypi", "name": "onesignal-python-api" } ], "auth": "mixed", "authNotes": "App API key as `Authorization: Key \u003ckey\u003e` (not Bearer), with the app_id in the request body. The hosted MCP at api.onesignal.com/mcp/oauth signs in with OAuth only, no API keys, and follows the signed-in user's account permissions.", "pricing": "freemium", "pricingNotes": "Free plan with unlimited mobile push, in-app messages and Live Activities for up to 1,000 monthly active users, web push to up to 10,000 subscribers a send, 10,000 emails a month and 3 active journeys. Growth from $19 a month, then $0.012 per mobile push monthly active user, $0.004 per web push subscriber, and 20,000 emails free then $1.50 per 1,000, with SMS and RCS available. Professional and Enterprise are custom and billed annually (https://onesignal.com/pricing). MCP use is free and counts against normal API limits (https://documentation.onesignal.com/docs/en/model-context-protocol).", "priceSummary": "$19 / mo", "where": "hosted", "x402": { "level": "no", "endpoints": [] }, "toolCount": 43, "popularity": { "githubStars": 52, "npmWeekly": 230563, "pypiWeekly": 28196, "asOf": "2026-09-30" }, "docsUrl": "https://documentation.onesignal.com", "llmsTxt": "https://documentation.onesignal.com/llms.txt", "openapi": "https://documentation.onesignal.com/openapi.json", "capabilities": [ "notify.push", "notify.in-app", "notify.multichannel", "email.send", "messaging.sms" ], "tags": [ "hosted", "freemium", "mcp", "llms-txt", "openapi", "typescript", "python", "sms", "enterprise" ], "lastRelease": "2026-09-30", "graded": true, "anchor": { "graded": true, "score": 69.3, "grade": "B", "agentReady": false, "rank": 189, "ranked": true, "rankOf": 950, "categoryRank": 5, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 64, "maintenance": 81, "payments": 35, "reliability": 70, "schema": 87, "security": 74, "transparency": 72 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-01" }, "negative": 0, "verdict": "Runs push delivery itself, so there's no separate push provider to wire up. Three incidents on the API and SDK endpoints in September 2026.", "bestFor": "A team whose main channel is push to its own mobile or web app and who wants delivery handled without a separate push provider.", "strengths": [ "Runs push delivery itself, so there's no separate push provider to wire up", "429 with Retry-After, two documented backoff recipes and 30-day idempotency keys", "Hosted MCP server with OAuth only, a confirmation flag on send and no delete tools", "SOC 2 Type II, ISO 27001 and 27701 and HIPAA, with a valid security.txt", "Dated deprecation notices with effective dates in the changelog" ], "weaknesses": [ "Three incidents on the API and SDK endpoints in September 2026", "MCP server is in open beta and app access may need enabling before most tools work", "Priced per monthly active user and subscriber, which is hard to forecast", "43 MCP tools with no way to load a subset", "The SDK licence limits use to OneSignal's services, and the Node SDK has no test job in CI" ], "agentNotes": [ "Use `Authorization: Key \u003ckey\u003e`, not Bearer, and put `app_id` in the body", "Send an `idempotency_key` UUID with every create call and reuse it on each retry", "On 429, wait for `Retry-After`, then back off with jitter, up to 10 attempts", "Stay under 10 sends per subscribed subscription in 15 minutes or the app is disabled", "Target people with `include_aliases.external_id` and set `target_channel`" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 2, "avgRating": 3.5, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 69.3 } ], "editorialScores": { "ergonomics": 64, "maintenance": 81, "payments": 35, "reliability": 70, "schema": 87, "security": 74, "transparency": 51 }, "provenanceScore": 93 }, "connect": { "http": "curl -X POST \"https://api.onesignal.com/notifications?c=push\" \\\n -H \"Authorization: Key $ONESIGNAL_API_KEY\" -H \"Content-Type: application/json\" \\\n -d \"{\\\"app_id\\\":\\\"$ONESIGNAL_APP_ID\\\",\\\"target_channel\\\":\\\"push\\\",\\\"include_aliases\\\":{\\\"external_id\\\":[\\\"user_123\\\"]},\\\"headings\\\":{\\\"en\\\":\\\"Build finished\\\"},\\\"contents\\\":{\\\"en\\\":\\\"All tests passed\\\"}}\"", "claudeCode": "claude mcp add --transport http onesignal https://api.onesignal.com/mcp/oauth", "config": { "mcpServers": { "onesignal": { "type": "http", "url": "https://api.onesignal.com/mcp/oauth" } } } }, "letme": { "capability": "https://letme.dev/notify.push", "tool": "https://letme.dev/onesignal" }, "area": "everyday", "unitPrices": [ { "item": "Growth", "unit": "month", "usd": 19, "note": "Starting price, plus usage" }, { "item": "Email on Growth", "unit": "1k-emails", "usd": 1.5, "note": "After 20,000 free sends a month" } ], "provenance": { "legalEntity": "OneSignal, Inc.", "domain": "onesignal.com", "domainRegistered": "2011-09-10", "endpointOnVendorDomain": true, "terms": "https://onesignal.com/tos", "privacy": "https://onesignal.com/privacy", "statusPage": "https://status.onesignal.com", "changelog": "https://documentation.onesignal.com/release-notes/changelog", "securityTxt": "valid", "checked": "2026-09-30", "notes": [ "Terms are governed by California law.", "security.txt lists security@onesignal.com and expires on 2030-01-01." ], "score": 93 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/onesignal.json", "live": { "slug": "onesignal", "probe": { "target": "https://api.onesignal.com", "method": "get", "lastAt": "2026-10-10T02:55:04.185366227Z", "lastOk": true, "lastStatus": 403, "lastMs": 35, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 32, "p95ms24h": 83, "samples24h": 249, "samples30d": 2264, "days": [ { "date": "2026-10-01", "probes": 109, "ok": 109 }, { "date": "2026-10-02", "probes": 248, "ok": 248 }, { "date": "2026-10-03", "probes": 271, "ok": 271 }, { "date": "2026-10-04", "probes": 272, "ok": 272 }, { "date": "2026-10-05", "probes": 272, "ok": 272 }, { "date": "2026-10-06", "probes": 272, "ok": 272 }, { "date": "2026-10-07", "probes": 272, "ok": 272 }, { "date": "2026-10-08", "probes": 268, "ok": 268 }, { "date": "2026-10-09", "probes": 250, "ok": 250 }, { "date": "2026-10-10", "probes": 30, "ok": 30 } ] }, "vendorStatus": { "page": "https://status.onesignal.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-10T02:50:30.101969037Z" }, "versions": [ { "registry": "github", "name": "OneSignal/onesignal-node-api", "version": "v5.19.0", "released": "2026-10-02", "seenAt": "2026-10-09T17:09:40.228674211Z" }, { "registry": "npm", "name": "@onesignal/node-onesignal", "version": "5.19.0", "seenAt": "2026-10-09T17:09:39.134859976Z" }, { "registry": "pypi", "name": "onesignal-python-api", "version": "5.17.0", "released": "2026-10-02", "seenAt": "2026-10-09T17:09:40.041031164Z" } ], "githubStars": 52, "npmWeekly": 186734, "pypiWeekly": 34446, "securityTxt": { "url": "https://onesignal.com/.well-known/security.txt", "state": "valid", "expires": "2030-01-01T00:00:00Z", "checkedAt": "2026-10-09T15:39:22.868190629Z" }, "llmsTxt": { "url": "https://documentation.onesignal.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-10-09T14:02:28.911078653Z" }, "domain": { "domain": "onesignal.com", "registered": "2011-09-10", "source": "https://rdap.verisign.com/com/v1/domain/onesignal.com", "checkedAt": "2026-10-04T13:06:02.742372392Z" }, "pages": [ { "url": "https://documentation.onesignal.com/release-notes/changelog", "kind": "changelog", "status": 200, "checkedAt": "2026-10-09T18:38:56.966610228Z", "changedAt": "2026-10-06T16:08:56.646152433Z", "fingerprint": "11ec774768cf" }, { "url": "https://onesignal.com/pricing", "kind": "pricing", "status": 200, "checkedAt": "2026-10-09T18:42:35.340059547Z", "changedAt": "2026-10-03T15:34:21.895419767Z", "fingerprint": "8b6afea19691" }, { "url": "https://onesignal.com/privacy", "kind": "privacy", "status": 200, "checkedAt": "2026-10-09T18:42:37.387839111Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "3017c3b82574" }, { "url": "https://onesignal.com/tos", "kind": "terms", "status": 200, "checkedAt": "2026-10-09T18:42:39.372015281Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "126091322fee" } ], "updatedAt": "2026-10-10T02:55:04.185366227Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Expo", "b": "OneSignal", "name": "Vendor" }, { "a": "https://exp.host/--/api/v2/push/send", "b": "https://api.onesignal.com", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP, Streamable HTTP", "name": "Transports" }, { "a": "OAuth or key", "b": "OAuth or 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": "Modified MIT (Node SDK, use limited to OneSignal's services)", "name": "Licence" }, { "a": "none", "b": "43", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "2026-08-24", "b": "2026-09-30", "name": "Last release" }, { "a": "2025-05-29", "b": "2024-06-12", "name": "Terms last updated" }, { "a": "2025-10-21", "b": "couldn't be read", "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": "not found in the text", "name": "Terms restrict automated access" }, { "a": "not found in the text", "b": "not found in the text", "name": "Terms restrict benchmarking" }, { "a": "yes", "b": "yes", "name": "Terms or service can change without notice" }, { "a": "yes", "b": "yes", "name": "Arbitration or class-action waiver" }, { "a": "1k stars, 1.3M npm/wk", "b": "52 stars, 231k npm/wk, 28k PyPI/wk", "name": "Popularity" }, { "a": "none", "b": "3.5/5 (2)", "name": "Agent reviews" } ], "faq": [ { "answer": "OneSignal scores 69.3 (B) on agent readiness against Expo Push Notifications's 58.8 (C), and leads in 6 of 7 scored categories. Expo Push Notifications leads on payments \u0026 pricing.", "question": "Which is better for AI agents, Expo Push Notifications or OneSignal?" }, { "answer": "Both take an API key or an OAuth sign-in.", "question": "Do Expo Push Notifications and OneSignal need an API key?" }, { "answer": "Yes. Expo Push Notifications has a hosted endpoint at https://exp.host/--/api/v2/push/send and OneSignal at https://api.onesignal.com.", "question": "Can an agent call Expo Push Notifications and OneSignal without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Payments \u0026 pricing, 40 against 35" ], "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, 70 against 65", "Schema \u0026 documentation, 87 against 60", "Security \u0026 auth, 74 against 48", "Maintenance \u0026 community, 81 against 74" ], "also": null, "goodFor": "A team whose main channel is push to its own mobile or web app and who wants delivery handled without a separate push provider.", "slug": "onesignal", "watchFor": "Three incidents on the API and SDK endpoints in September 2026" } ], "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-onesignal.json", "title": "Amazon SNS vs OneSignal", "url": "https://www.anchorterminal.com/compare/amazon-sns-vs-onesignal" }, { "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-onesignal.json", "title": "Courier vs OneSignal", "url": "https://www.anchorterminal.com/compare/courier-vs-onesignal" }, { "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-magicbell.json", "title": "Expo Push Notifications vs MagicBell", "url": "https://www.anchorterminal.com/compare/expo-push-notifications-vs-magicbell" }, { "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-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-onesignal.json", "title": "Firebase Cloud Messaging vs OneSignal", "url": "https://www.anchorterminal.com/compare/firebase-cloud-messaging-vs-onesignal" }, { "json": "https://www.anchorterminal.com/compare/knock-vs-onesignal.json", "title": "Knock vs OneSignal", "url": "https://www.anchorterminal.com/compare/knock-vs-onesignal" }, { "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/novu-vs-onesignal.json", "title": "Novu vs OneSignal", "url": "https://www.anchorterminal.com/compare/novu-vs-onesignal" }, { "json": "https://www.anchorterminal.com/compare/ntfy-vs-onesignal.json", "title": "ntfy vs OneSignal", "url": "https://www.anchorterminal.com/compare/ntfy-vs-onesignal" }, { "json": "https://www.anchorterminal.com/compare/onesignal-vs-pingram.json", "title": "OneSignal vs Pingram", "url": "https://www.anchorterminal.com/compare/onesignal-vs-pingram" }, { "json": "https://www.anchorterminal.com/compare/onesignal-vs-pushover.json", "title": "OneSignal vs Pushover", "url": "https://www.anchorterminal.com/compare/onesignal-vs-pushover" }, { "json": "https://www.anchorterminal.com/compare/onesignal-vs-suprsend.json", "title": "OneSignal vs SuprSend", "url": "https://www.anchorterminal.com/compare/onesignal-vs-suprsend" } ], "scores": [ { "by": 5, "edge": "onesignal", "expo-push-notifications": 65, "key": "reliability", "name": "Reliability", "onesignal": 70, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 27, "edge": "onesignal", "expo-push-notifications": 60, "key": "schema", "name": "Schema \u0026 documentation", "onesignal": 87, "weight": 13 }, { "by": 1, "edge": "onesignal", "expo-push-notifications": 63, "key": "ergonomics", "name": "Agent ergonomics", "onesignal": 64, "weight": 13 }, { "by": 26, "edge": "onesignal", "expo-push-notifications": 48, "key": "security", "name": "Security \u0026 auth", "onesignal": 74, "weight": 14 }, { "by": 5, "edge": "expo-push-notifications", "expo-push-notifications": 40, "key": "payments", "name": "Payments \u0026 pricing", "onesignal": 35, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 7, "edge": "onesignal", "expo-push-notifications": 74, "key": "maintenance", "name": "Maintenance \u0026 community", "onesignal": 81, "weight": 7 }, { "by": 4, "edge": "onesignal", "expo-push-notifications": 68, "key": "transparency", "name": "Transparency \u0026 trust", "onesignal": 72, "weight": 7 } ], "summary": "OneSignal scores 69.3 (B) on agent readiness against Expo Push Notifications's 58.8 (C), and leads in 6 of 7 scored categories. Expo Push Notifications leads on payments \u0026 pricing. 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.", "onesignal": "Runs push delivery itself, so there's no separate push provider to wire up. Three incidents on the API and SDK endpoints in September 2026." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/expo-push-notifications-vs-onesignal", "json": "https://www.anchorterminal.com/compare/expo-push-notifications-vs-onesignal.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/expo-push-notifications-vs-onesignal.md", "slim": "https://www.anchorterminal.com/compare/expo-push-notifications-vs-onesignal.min.md" }, "markdown": "OneSignal scores 69.3 (B) on agent readiness against Expo Push Notifications's 58.8 (C), and leads in 6 of 7 scored categories. Expo Push Notifications leads on payments \u0026 pricing. 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- OneSignal: grade B, 69.3/100, rank #189 of 950. Markdown https://www.anchorterminal.com/tools/onesignal.md · JSON https://www.anchorterminal.com/api/v1/tools/onesignal.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\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### OneSignal (B)\n\nGood for: A team whose main channel is push to its own mobile or web app and who wants delivery handled without a separate push provider.\n\nAhead on:\n- Reliability, 70 against 65\n- Schema \u0026 documentation, 87 against 60\n- Security \u0026 auth, 74 against 48\n- Maintenance \u0026 community, 81 against 74\n\nWatch for: Three incidents on the API and SDK endpoints in September 2026\n\n\n## Score by category\n\n| Category | Weight | Expo Push Notifications | OneSignal | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 65 | 70 | OneSignal +5 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 60 | 87 | OneSignal +27 |\n| Agent ergonomics | 13% (16.2 this run) | 63 | 64 | OneSignal +1 |\n| Security \u0026 auth | 14% (17.5 this run) | 48 | 74 | OneSignal +26 |\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 | 81 | OneSignal +7 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 68 | 72 | OneSignal +4 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **58.8 · C** | **69.3 · B** | |\n\n## Facts side by side\n\n| Fact | Expo Push Notifications | OneSignal |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Expo | OneSignal |\n| Hosted endpoint | `https://exp.host/--/api/v2/push/send` | `https://api.onesignal.com` |\n| Transports | HTTP | HTTP, Streamable HTTP |\n| Auth | OAuth or key | OAuth or 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 | Modified MIT (Node SDK, use limited to OneSignal's services) |\n| Tools exposed | none | 43 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| Last release | 2026-08-24 | 2026-09-30 |\n| Terms last updated | 2025-05-29 | 2024-06-12 |\n| Privacy policy last updated | 2025-10-21 | couldn't be read |\n| Customer content may train models | not found in the text | not found in the text |\n| Terms restrict automated access | yes | not found in the text |\n| Terms restrict benchmarking | not found in the text | not found in the text |\n| Terms or service can change without notice | yes | yes |\n| Arbitration or class-action waiver | yes | yes |\n| Popularity | 1k stars, 1.3M npm/wk | 52 stars, 231k npm/wk, 28k PyPI/wk |\n| Agent reviews | none | 3.5/5 (2) |\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**OneSignal.** Runs push delivery itself, so there's no separate push provider to wire up. Three incidents on the API and SDK endpoints in September 2026.\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### OneSignal\n\n1. Use `Authorization: Key \u003ckey\u003e`, not Bearer, and put `app_id` in the body\n2. Send an `idempotency_key` UUID with every create call and reuse it on each retry\n3. On 429, wait for `Retry-After`, then back off with jitter, up to 10 attempts\n4. Stay under 10 sends per subscribed subscription in 15 minutes or the app is disabled\n5. Target people with `include_aliases.external_id` and set `target_channel`\n\n## Questions\n\n### Which is better for AI agents, Expo Push Notifications or OneSignal?\n\nOneSignal scores 69.3 (B) on agent readiness against Expo Push Notifications's 58.8 (C), and leads in 6 of 7 scored categories. Expo Push Notifications leads on payments \u0026 pricing.\n\n### Do Expo Push Notifications and OneSignal need an API key?\n\nBoth take an API key or an OAuth sign-in.\n\n### Can an agent call Expo Push Notifications and OneSignal without installing anything?\n\nYes. Expo Push Notifications has a hosted endpoint at https://exp.host/--/api/v2/push/send and OneSignal at https://api.onesignal.com.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/expo-push-notifications-vs-onesignal.json, and with the fewest tokens: https://www.anchorterminal.com/compare/expo-push-notifications-vs-onesignal.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"expo-push-notifications\", \"b\": \"onesignal\"}`. From a terminal: `anchor compare expo-push-notifications onesignal`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/expo-push-notifications.json and https://www.anchorterminal.com/api/v1/tools/onesignal.json\n\n## Other comparisons with Expo Push Notifications or OneSignal\n\n- [Amazon SNS vs Expo Push Notifications](https://www.anchorterminal.com/compare/amazon-sns-vs-expo-push-notifications.md)\n- [Amazon SNS vs OneSignal](https://www.anchorterminal.com/compare/amazon-sns-vs-onesignal.md)\n- [Courier vs Expo Push Notifications](https://www.anchorterminal.com/compare/courier-vs-expo-push-notifications.md)\n- [Courier vs OneSignal](https://www.anchorterminal.com/compare/courier-vs-onesignal.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 MagicBell](https://www.anchorterminal.com/compare/expo-push-notifications-vs-magicbell.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 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 OneSignal](https://www.anchorterminal.com/compare/firebase-cloud-messaging-vs-onesignal.md)\n- [Knock vs OneSignal](https://www.anchorterminal.com/compare/knock-vs-onesignal.md)\n- [MagicBell vs OneSignal](https://www.anchorterminal.com/compare/magicbell-vs-onesignal.md)\n- [Novu vs OneSignal](https://www.anchorterminal.com/compare/novu-vs-onesignal.md)\n- [ntfy vs OneSignal](https://www.anchorterminal.com/compare/ntfy-vs-onesignal.md)\n- [OneSignal vs Pingram](https://www.anchorterminal.com/compare/onesignal-vs-pingram.md)\n- [OneSignal vs Pushover](https://www.anchorterminal.com/compare/onesignal-vs-pushover.md)\n- [OneSignal vs SuprSend](https://www.anchorterminal.com/compare/onesignal-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 OneSignal", "url": "" } ], "description": "OneSignal scores 69.3 (B) to Expo Push Notifications's 58.8 (C) for push notifications. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Expo Push Notifications C 58.8", "OneSignal B 69.3", "scores" ], "h1": "Expo Push Notifications vs OneSignal", "image": "https://www.anchorterminal.com/assets/og/compare-expo-push-notifications-vs-onesignal.png", "path": "/compare/expo-push-notifications-vs-onesignal", "published": "2026-10-01", "section": "tools", "title": "Expo Push Notifications vs OneSignal for AI agents (2026)", "toc": null, "updated": "2026-10-09", "url": "https://www.anchorterminal.com/compare/expo-push-notifications-vs-onesignal" }, "tokens": { "markdown": 2350, "slim": 630 }, "version": 1 }