{ "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 scores 58.8 (C) on agent readiness against Pushover's 53.1 (D), and leads in 4 of 7 scored categories. Pushover leads on transparency \u0026 trust.", "b": { "slug": "pushover", "name": "Pushover", "vendor": "Pushover", "vendorUrl": "https://pushover.net", "kind": "http-api", "category": "notifications", "summary": "Push notification service for your own phone, tablet or desktop.", "url": "https://www.anchorterminal.com/tools/pushover", "markdownUrl": "https://www.anchorterminal.com/tools/pushover.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/pushover.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/pushover.json", "transports": [ "http" ], "remoteUrl": "https://api.pushover.net/1/messages.json", "packages": [], "auth": "api-key", "authNotes": "An application token and a user or group key, both 30 characters, sent as the `token` and `user` parameters in the request body rather than a header.", "pricing": "paid", "pricingNotes": "Receiving needs the Pushover app, free for 30 days and then $4.99 once per platform (iOS, Android, desktop). Pushover for Teams is $5 per user a month. Sending is free up to 10,000 messages a month per account (25,000 for a team), shared across all of an account's applications since 2026-05-01. Capacity upgrades exist but their price isn't on the pricing page (https://pushover.net/pricing, https://support.pushover.net/i12-message-size-and-frequency-limitations, https://blog.pushover.net/posts/2026/4/app-limits).", "priceSummary": "$5 / seat-mo", "where": "hosted", "x402": { "level": "no", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-09-30" }, "docsUrl": "https://pushover.net/api", "capabilities": [ "notify.push" ], "tags": [ "hosted", "webhooks" ], "lastRelease": "2026-06-23", "graded": true, "anchor": { "graded": true, "score": 53.1, "grade": "D", "agentReady": false, "rank": 716, "ranked": true, "rankOf": 950, "categoryRank": 12, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 64, "maintenance": 20, "payments": 30, "reliability": 62, "schema": 50, "security": 52, "transparency": 87 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-01" }, "negative": 0, "verdict": "One POST with three required fields, form or JSON. Recipients need the app, $4.99 per platform after a 30-day trial.", "bestFor": "An agent that must reach its owner or an on-call team and get an acknowledgement.", "strengths": [ "One POST with three required fields, form or JSON", "Emergency priority repeats until acknowledged, up to 3 hours, with pollable receipts", "Every response reports the remaining monthly quota in `X-Limit-App-*` headers", "Messages deleted from the servers once delivery is verified, and nine processors named", "10,000 free messages a month, 25,000 on Teams" ], "weaknesses": [ "Recipients need the app, $4.99 per platform after a 30-day trial", "No idempotency key, so a retry after a timeout can send twice", "No OpenAPI spec, llms.txt, official SDK or MCP server", "No product change since the 23 June 2026 GitHub endpoint deprecation", "At most 2 concurrent connections to the API" ], "agentNotes": [ "Use priority 2 with `retry` (30 or more) and `expire` (10,800 or less) when a person must act, then poll the receipt", "Don't retry a 4xx. Fix the parameter named in `errors`. Wait at least 5 seconds before retrying a 5xx", "Read `X-Limit-App-Remaining` before a batch. Over the monthly quota every send returns 429", "Keep messages to 1,024 characters and titles to 250", "Send to a group key to reach several people in one call. Each person still counts against the quota" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 2, "avgRating": 3.5, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "D", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 53.1 } ], "editorialScores": { "ergonomics": 64, "maintenance": 20, "payments": 30, "reliability": 62, "schema": 50, "security": 52, "transparency": 77 }, "provenanceScore": 96 }, "connect": { "http": "curl -s https://api.pushover.net/1/messages.json \\\n --form-string \"token=$PUSHOVER_APP_TOKEN\" --form-string \"user=$PUSHOVER_USER_KEY\" \\\n --form-string \"title=Build finished\" --form-string \"message=All tests passed\"" }, "letme": { "capability": "https://letme.dev/notify.push", "tool": "https://letme.dev/pushover" }, "area": "everyday", "unitPrices": [ { "item": "Pushover for Teams", "unit": "seat-month", "usd": 5 } ], "provenance": { "legalEntity": "Pushover, LLC", "domain": "pushover.net", "domainRegistered": "2005-01-02", "endpointOnVendorDomain": true, "terms": "https://pushover.net/terms", "privacy": "https://pushover.net/privacy", "statusPage": "https://status.pushover.net", "changelog": "https://blog.pushover.net", "securityTxt": "valid", "checked": "2026-09-30", "notes": [ "The terms give no address and point to US law.", "Product changes are announced on the blog. The 2026-06-23 post deprecates the GitHub notification endpoint in favour of webhooks." ], "score": 96 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/pushover.json", "live": { "slug": "pushover", "probe": { "target": "https://api.pushover.net/1/messages.json", "method": "get", "lastAt": "2026-10-10T02:55:07.048329437Z", "lastOk": true, "lastStatus": 400, "lastMs": 183, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 185, "p95ms24h": 272, "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.pushover.net", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-10-10T00:51:11.028241899Z" }, "securityTxt": { "url": "https://pushover.net/.well-known/security.txt", "state": "valid", "expires": "2038-01-19T03:14:08.000Z", "checkedAt": "2026-10-09T15:39:16.06990861Z" }, "domain": { "domain": "pushover.net", "registered": "2005-01-02", "source": "https://rdap.verisign.com/net/v1/domain/pushover.net", "checkedAt": "2026-10-04T13:08:13.137695898Z" }, "pages": [ { "url": "https://blog.pushover.net", "kind": "changelog", "status": 304, "checkedAt": "2026-10-09T18:33:10.997527219Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "1c780b34fb64" }, { "url": "https://pushover.net/pricing", "kind": "pricing", "status": 200, "checkedAt": "2026-10-09T18:44:06.044435451Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "6b0b637534bf" }, { "url": "https://pushover.net/privacy", "kind": "privacy", "status": 200, "checkedAt": "2026-10-09T18:44:08.1564993Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "0642611ad7b6" }, { "url": "https://pushover.net/terms", "kind": "terms", "status": 200, "checkedAt": "2026-10-09T18:44:10.165303913Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "87db56879b09" } ], "updatedAt": "2026-10-10T02:55:07.048329437Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Expo", "b": "Pushover", "name": "Vendor" }, { "a": "https://exp.host/--/api/v2/push/send", "b": "https://api.pushover.net/1/messages.json", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP", "name": "Transports" }, { "a": "OAuth or key", "b": "API key", "name": "Auth" }, { "a": "Free", "b": "Paid", "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": "none", "name": "Licence" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "no", "name": "llms.txt" }, { "a": "2026-08-24", "b": "2026-06-23", "name": "Last release" }, { "a": "2025-05-29", "b": "2026-05-01", "name": "Terms last updated" }, { "a": "2025-10-21", "b": "2026-05-01", "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": "not found in the text", "name": "Arbitration or class-action waiver" }, { "a": "1k stars, 1.3M npm/wk", "b": "none", "name": "Popularity" }, { "a": "none", "b": "3.5/5 (2)", "name": "Agent reviews" } ], "faq": [ { "answer": "Expo Push Notifications scores 58.8 (C) on agent readiness against Pushover's 53.1 (D), and leads in 4 of 7 scored categories. Pushover leads on transparency \u0026 trust.", "question": "Which is better for AI agents, Expo Push Notifications or Pushover?" }, { "answer": "Expo Push Notifications takes an API key or an OAuth sign-in. Pushover needs an API key.", "question": "Do Expo Push Notifications and Pushover need an API key?" }, { "answer": "Yes. Expo Push Notifications has a hosted endpoint at https://exp.host/--/api/v2/push/send and Pushover at https://api.pushover.net/1/messages.json.", "question": "Can an agent call Expo Push Notifications and Pushover without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Schema \u0026 documentation, 60 against 50", "Payments \u0026 pricing, 40 against 30", "Maintenance \u0026 community, 74 against 20" ], "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": [ "Transparency \u0026 trust, 87 against 68" ], "also": null, "goodFor": "An agent that must reach its owner or an on-call team and get an acknowledgement.", "slug": "pushover", "watchFor": "Recipients need the app, $4.99 per platform after a 30-day trial" } ], "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-pushover.json", "title": "Amazon SNS vs Pushover", "url": "https://www.anchorterminal.com/compare/amazon-sns-vs-pushover" }, { "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-pushover.json", "title": "Courier vs Pushover", "url": "https://www.anchorterminal.com/compare/courier-vs-pushover" }, { "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-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-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-pushover.json", "title": "Firebase Cloud Messaging vs Pushover", "url": "https://www.anchorterminal.com/compare/firebase-cloud-messaging-vs-pushover" }, { "json": "https://www.anchorterminal.com/compare/knock-vs-pushover.json", "title": "Knock vs Pushover", "url": "https://www.anchorterminal.com/compare/knock-vs-pushover" }, { "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/novu-vs-pushover.json", "title": "Novu vs Pushover", "url": "https://www.anchorterminal.com/compare/novu-vs-pushover" }, { "json": "https://www.anchorterminal.com/compare/ntfy-vs-pushover.json", "title": "ntfy vs Pushover", "url": "https://www.anchorterminal.com/compare/ntfy-vs-pushover" }, { "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/pingram-vs-pushover.json", "title": "Pingram vs Pushover", "url": "https://www.anchorterminal.com/compare/pingram-vs-pushover" }, { "json": "https://www.anchorterminal.com/compare/pushover-vs-suprsend.json", "title": "Pushover vs SuprSend", "url": "https://www.anchorterminal.com/compare/pushover-vs-suprsend" } ], "scores": [ { "by": 3, "edge": "expo-push-notifications", "expo-push-notifications": 65, "key": "reliability", "name": "Reliability", "pushover": 62, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 10, "edge": "expo-push-notifications", "expo-push-notifications": 60, "key": "schema", "name": "Schema \u0026 documentation", "pushover": 50, "weight": 13 }, { "by": 1, "edge": "pushover", "expo-push-notifications": 63, "key": "ergonomics", "name": "Agent ergonomics", "pushover": 64, "weight": 13 }, { "by": 4, "edge": "pushover", "expo-push-notifications": 48, "key": "security", "name": "Security \u0026 auth", "pushover": 52, "weight": 14 }, { "by": 10, "edge": "expo-push-notifications", "expo-push-notifications": 40, "key": "payments", "name": "Payments \u0026 pricing", "pushover": 30, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 54, "edge": "expo-push-notifications", "expo-push-notifications": 74, "key": "maintenance", "name": "Maintenance \u0026 community", "pushover": 20, "weight": 7 }, { "by": 19, "edge": "pushover", "expo-push-notifications": 68, "key": "transparency", "name": "Transparency \u0026 trust", "pushover": 87, "weight": 7 } ], "summary": "Expo Push Notifications scores 58.8 (C) on agent readiness against Pushover's 53.1 (D), and leads in 4 of 7 scored categories. Pushover leads on transparency \u0026 trust. 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.", "pushover": "One POST with three required fields, form or JSON. Recipients need the app, $4.99 per platform after a 30-day trial." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/expo-push-notifications-vs-pushover", "json": "https://www.anchorterminal.com/compare/expo-push-notifications-vs-pushover.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/expo-push-notifications-vs-pushover.md", "slim": "https://www.anchorterminal.com/compare/expo-push-notifications-vs-pushover.min.md" }, "markdown": "Expo Push Notifications scores 58.8 (C) on agent readiness against Pushover's 53.1 (D), and leads in 4 of 7 scored categories. Pushover leads on transparency \u0026 trust. 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- Pushover: grade D, 53.1/100, rank #716 of 950. Markdown https://www.anchorterminal.com/tools/pushover.md · JSON https://www.anchorterminal.com/api/v1/tools/pushover.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- Schema \u0026 documentation, 60 against 50\n- Payments \u0026 pricing, 40 against 30\n- Maintenance \u0026 community, 74 against 20\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### Pushover (D)\n\nGood for: An agent that must reach its owner or an on-call team and get an acknowledgement.\n\nAhead on:\n- Transparency \u0026 trust, 87 against 68\n\nWatch for: Recipients need the app, $4.99 per platform after a 30-day trial\n\n\n## Score by category\n\n| Category | Weight | Expo Push Notifications | Pushover | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 65 | 62 | Expo Push Notifications +3 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 60 | 50 | Expo Push Notifications +10 |\n| Agent ergonomics | 13% (16.2 this run) | 63 | 64 | Pushover +1 |\n| Security \u0026 auth | 14% (17.5 this run) | 48 | 52 | Pushover +4 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 40 | 30 | Expo Push Notifications +10 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 74 | 20 | Expo Push Notifications +54 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 68 | 87 | Pushover +19 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **58.8 · C** | **53.1 · D** | |\n\n## Facts side by side\n\n| Fact | Expo Push Notifications | Pushover |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Expo | Pushover |\n| Hosted endpoint | `https://exp.host/--/api/v2/push/send` | `https://api.pushover.net/1/messages.json` |\n| Transports | HTTP | HTTP |\n| Auth | OAuth or key | API key |\n| Pricing | Free | Paid |\n| x402 | no | no |\n| Licence | Proprietary service under Expo's terms of service. The Node.js server SDK is MIT | none |\n| Read-only variant documented | no | no |\n| llms.txt | yes | no |\n| Last release | 2026-08-24 | 2026-06-23 |\n| Terms last updated | 2025-05-29 | 2026-05-01 |\n| Privacy policy last updated | 2025-10-21 | 2026-05-01 |\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 | not found in the text |\n| Popularity | 1k stars, 1.3M npm/wk | none |\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**Pushover.** One POST with three required fields, form or JSON. Recipients need the app, $4.99 per platform after a 30-day trial.\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### Pushover\n\n1. Use priority 2 with `retry` (30 or more) and `expire` (10,800 or less) when a person must act, then poll the receipt\n2. Don't retry a 4xx. Fix the parameter named in `errors`. Wait at least 5 seconds before retrying a 5xx\n3. Read `X-Limit-App-Remaining` before a batch. Over the monthly quota every send returns 429\n4. Keep messages to 1,024 characters and titles to 250\n5. Send to a group key to reach several people in one call. Each person still counts against the quota\n\n## Questions\n\n### Which is better for AI agents, Expo Push Notifications or Pushover?\n\nExpo Push Notifications scores 58.8 (C) on agent readiness against Pushover's 53.1 (D), and leads in 4 of 7 scored categories. Pushover leads on transparency \u0026 trust.\n\n### Do Expo Push Notifications and Pushover need an API key?\n\nExpo Push Notifications takes an API key or an OAuth sign-in. Pushover needs an API key.\n\n### Can an agent call Expo Push Notifications and Pushover without installing anything?\n\nYes. Expo Push Notifications has a hosted endpoint at https://exp.host/--/api/v2/push/send and Pushover at https://api.pushover.net/1/messages.json.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/expo-push-notifications-vs-pushover.json, and with the fewest tokens: https://www.anchorterminal.com/compare/expo-push-notifications-vs-pushover.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"expo-push-notifications\", \"b\": \"pushover\"}`. From a terminal: `anchor compare expo-push-notifications pushover`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/expo-push-notifications.json and https://www.anchorterminal.com/api/v1/tools/pushover.json\n\n## Other comparisons with Expo Push Notifications or Pushover\n\n- [Amazon SNS vs Expo Push Notifications](https://www.anchorterminal.com/compare/amazon-sns-vs-expo-push-notifications.md)\n- [Amazon SNS vs Pushover](https://www.anchorterminal.com/compare/amazon-sns-vs-pushover.md)\n- [Courier vs Expo Push Notifications](https://www.anchorterminal.com/compare/courier-vs-expo-push-notifications.md)\n- [Courier vs Pushover](https://www.anchorterminal.com/compare/courier-vs-pushover.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 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 SuprSend](https://www.anchorterminal.com/compare/expo-push-notifications-vs-suprsend.md)\n- [Firebase Cloud Messaging vs Pushover](https://www.anchorterminal.com/compare/firebase-cloud-messaging-vs-pushover.md)\n- [Knock vs Pushover](https://www.anchorterminal.com/compare/knock-vs-pushover.md)\n- [MagicBell vs Pushover](https://www.anchorterminal.com/compare/magicbell-vs-pushover.md)\n- [Novu vs Pushover](https://www.anchorterminal.com/compare/novu-vs-pushover.md)\n- [ntfy vs Pushover](https://www.anchorterminal.com/compare/ntfy-vs-pushover.md)\n- [OneSignal vs Pushover](https://www.anchorterminal.com/compare/onesignal-vs-pushover.md)\n- [Pingram vs Pushover](https://www.anchorterminal.com/compare/pingram-vs-pushover.md)\n- [Pushover vs SuprSend](https://www.anchorterminal.com/compare/pushover-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 Pushover", "url": "" } ], "description": "Expo Push Notifications scores 58.8 (C) to Pushover's 53.1 (D) for push notifications. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Expo Push Notifications C 58.8", "Pushover D 53.1", "scores" ], "h1": "Expo Push Notifications vs Pushover", "image": "https://www.anchorterminal.com/assets/og/compare-expo-push-notifications-vs-pushover.png", "path": "/compare/expo-push-notifications-vs-pushover", "published": "2026-10-01", "section": "tools", "title": "Expo Push Notifications vs Pushover for AI agents (2026)", "toc": null, "updated": "2026-10-09", "url": "https://www.anchorterminal.com/compare/expo-push-notifications-vs-pushover" }, "tokens": { "markdown": 2300, "slim": 630 }, "version": 1 }