{ "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-10T03:53:27.098677639Z", "lastOk": true, "lastStatus": 405, "lastMs": 434, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 127, "p95ms24h": 197, "samples24h": 125, "samples30d": 125, "days": [ { "date": "2026-10-09", "probes": 85, "ok": 85 }, { "date": "2026-10-10", "probes": 40, "ok": 40 } ] }, "vendorStatus": { "page": "https://status.expo.dev", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-10T03:58:19.44575714Z" }, "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-10T03:58:19.44575714Z" } }, "answer": "SuprSend scores 72.6 (BB) on agent readiness against Expo Push Notifications's 58.8 (C), and leads in 5 of 7 scored categories.", "b": { "slug": "suprsend", "name": "SuprSend", "vendor": "SuprSend", "vendorUrl": "https://www.suprsend.com", "kind": "http-api", "category": "notifications", "summary": "Notification workflow API for email, SMS, push, an in-app Inbox, Slack, Microsoft Teams and webhooks, with digests, batching and preferences per user and per tenant.", "url": "https://www.anchorterminal.com/tools/suprsend", "markdownUrl": "https://www.anchorterminal.com/tools/suprsend.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/suprsend.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/suprsend.json", "repo": "https://github.com/suprsend/cli", "license": "MIT (CLI and MCP server)", "transports": [ "http", "stdio" ], "remoteUrl": "https://hub.suprsend.com", "packages": [ { "registry": "npm", "name": "@suprsend/node-sdk" }, { "registry": "pypi", "name": "suprsend-py-sdk" }, { "registry": "npm", "name": "suprsend" } ], "auth": "api-key", "authNotes": "API key as `Authorization: Bearer` on the trigger API. Workspace key and secret pairs can be issued and rotated per service through the management API since 2026-09-22. The MCP server reads a service token from `SUPRSEND_SERVICE_TOKEN`, and a service token grants full workspace access.", "pricing": "freemium", "pricingNotes": "Free plan with 10,000 notifications a month, no card, unlimited team members and 30-day log retention. Essentials $110 a month ($100 billed yearly, $1,200 a year) for 50,000, then $2 per 1,000, with 30-day logs. Business $275 a month ($250 billed yearly, $3,000 a year) for 50,000, then $5 per 1,000, with 90-day logs and an audit trail. Paid plans list 99.9% uptime. Enterprise is custom. A notification is one message to one user or object on one channel, a digest or batch counts once, and sends SuprSend drops for opt-outs aren't billed, though provider failures are (https://www.suprsend.com/pricing).", "priceSummary": "$110 / mo", "where": "both", "x402": { "level": "no", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": 12, "npmWeekly": 13318, "pypiWeekly": 1099, "asOf": "2026-09-30" }, "docsUrl": "https://docs.suprsend.com", "llmsTxt": "https://docs.suprsend.com/llms.txt", "openapi": "https://docs.suprsend.com/openapi.yaml", "registryName": "io.github.suprsend/cli", "capabilities": [ "notify.push", "notify.in-app", "notify.multichannel", "notify.preferences", "notify.digest" ], "tags": [ "hosted", "freemium", "mcp", "llms-txt", "openapi", "typescript", "python", "webhooks", "enterprise" ], "lastRelease": "2026-09-28", "graded": true, "anchor": { "graded": true, "score": 72.6, "grade": "BB", "agentReady": true, "rank": 102, "ranked": true, "rankOf": 950, "categoryRank": 2, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 87, "maintenance": 81, "payments": 40, "reliability": 69, "schema": 94, "security": 66, "transparency": 66 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-01" }, "negative": 0, "verdict": "MCP tool descriptions say when to use each tool, when not to, and what it changes, with readOnlyHint and destructiveHint set. No rate-limit page or 429 guidance.", "bestFor": "A SaaS team that needs tenant-aware preferences, digests and batching at a mid-range price, and for agents that inspect users and preferences through MCP.", "strengths": [ "MCP tool descriptions say when to use each tool, when not to, and what it changes, with readOnlyHint and destructiveHint set", "`--tools` loads a subset of the 22 built-in tools, and trigger tools register only for the workflows you name", "Free plan with 10,000 notifications, no card and unlimited seats", "Digests and batches bill as one notification, and opt-out drops aren't billed", "99.9% uptime listed on every paid plan, SOC 2 Type II and ISO 27001" ], "weaknesses": [ "No rate-limit page or 429 guidance", "No hosted MCP server, only the local CLI", "Workspace secrets come back in plain text on every management API response", "A 20-minute platform outage on 20 August 2026 and repeated short API blips", "Audit trail on Business and Enterprise only, RBAC on Enterprise only" ], "agentNotes": [ "Pass an idempotency key on each trigger. It holds for 24 hours", "Start the MCP server with `--tools` set to read-only groups for production workspaces", "Register trigger tools with `--workflows=\u003cslug\u003e` for only the workflows you need. The default registers none", "Count each bulk record against the rate limit, and keep bulk calls to 100 records and 800 KB", "Treat management API responses as secrets. They include the workspace secret in plain text" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 2, "avgRating": 3, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "BB", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 72.6 } ], "editorialScores": { "ergonomics": 87, "maintenance": 81, "payments": 40, "reliability": 69, "schema": 94, "security": 66, "transparency": 52 }, "provenanceScore": 79 }, "connect": { "http": "curl -X POST https://hub.suprsend.com/trigger/ \\\n -H \"Authorization: Bearer $SUPRSEND_API_KEY\" -H \"Content-Type: application/json\" \\\n -d '{\"workflow\":\"build-finished\",\"recipients\":[{\"distinct_id\":\"user_123\",\"$email\":[\"user@example.com\"]}],\"data\":{\"status\":\"passed\"}}'", "claudeCode": "claude mcp add suprsend --scope user --env SUPRSEND_SERVICE_TOKEN=$SUPRSEND_SERVICE_TOKEN -- npx -y suprsend start-mcp-server", "config": { "mcpServers": { "suprsend": { "args": [ "-y", "suprsend", "start-mcp-server" ], "command": "npx", "env": { "SUPRSEND_SERVICE_TOKEN": "${SUPRSEND_SERVICE_TOKEN}" } } } } }, "letme": { "capability": "https://letme.dev/notify.push", "tool": "https://letme.dev/suprsend" }, "area": "everyday", "unitPrices": [ { "item": "Essentials", "unit": "month", "usd": 110, "note": "50,000 notifications, $100 billed yearly" }, { "item": "Essentials overage", "unit": "message", "usd": 0.002 }, { "item": "Business", "unit": "month", "usd": 275, "note": "50,000 notifications, $250 billed yearly" }, { "item": "Business overage", "unit": "message", "usd": 0.005 } ], "provenance": { "legalEntity": "SuprStack Inc", "domain": "suprsend.com", "domainRegistered": "2020-12-27", "endpointOnVendorDomain": true, "terms": "https://www.suprsend.com/terms", "privacy": "https://www.suprsend.com/privacy", "statusPage": "https://status.suprsend.com", "changelog": "https://docs.suprsend.com/changelog/overview", "securityTxt": "none", "checked": "2026-09-30", "notes": [ "Terms are governed by Delaware law and give only a support email, no postal address.", "The status page showed Third Party Dependencies as degraded (a Cloudflare Workers issue) when we checked." ], "score": 79 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/suprsend.json", "live": { "slug": "suprsend", "probe": { "target": "https://hub.suprsend.com", "method": "get", "lastAt": "2026-10-10T03:53:45.841292348Z", "lastOk": true, "lastStatus": 200, "lastMs": 78, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 98, "p95ms24h": 181, "samples24h": 249, "samples30d": 2274, "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": 40, "ok": 40 } ] }, "vendorStatus": { "page": "https://status.suprsend.com", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-10-10T00:51:18.66148195Z" }, "versions": [ { "registry": "github", "name": "suprsend/cli", "version": "1.0.1", "released": "2026-07-10", "seenAt": "2026-10-09T17:22:58.574678295Z" }, { "registry": "mcp-registry", "name": "io.github.suprsend/cli", "version": "1.0.1", "seenAt": "2026-10-10T03:11:32.438759038Z" }, { "registry": "npm", "name": "@suprsend/node-sdk", "version": "1.15.1", "seenAt": "2026-10-09T17:22:56.354197554Z" }, { "registry": "npm", "name": "suprsend", "version": "1.0.1", "seenAt": "2026-10-09T17:22:58.00197002Z" }, { "registry": "pypi", "name": "suprsend-py-sdk", "version": "0.20.0", "released": "2026-09-04", "seenAt": "2026-10-09T17:22:57.81517437Z" } ], "githubStars": 12, "npmWeekly": 8043, "pypiWeekly": 1101, "securityTxt": { "url": "https://suprsend.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-10-09T15:39:34.337527097Z" }, "llmsTxt": { "url": "https://docs.suprsend.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-10-09T14:02:52.232969347Z" }, "domain": { "domain": "suprsend.com", "registered": "2020-12-27", "source": "https://rdap.verisign.com/com/v1/domain/suprsend.com", "checkedAt": "2026-10-04T13:10:03.719103966Z" }, "pages": [ { "url": "https://docs.suprsend.com/changelog/overview", "kind": "changelog", "status": 200, "checkedAt": "2026-10-09T18:38:28.272964687Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "a51b9d1cfccd" }, { "url": "https://www.suprsend.com/pricing", "kind": "pricing", "status": 304, "checkedAt": "2026-10-09T18:54:40.571362451Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "9b909a363f19" }, { "url": "https://www.suprsend.com/privacy", "kind": "privacy", "status": 304, "checkedAt": "2026-10-09T18:54:42.706229962Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "73c6e3ac26d2" }, { "url": "https://www.suprsend.com/terms", "kind": "terms", "status": 304, "checkedAt": "2026-10-09T18:54:44.714491771Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "97053f0651bd" } ], "updatedAt": "2026-10-10T03:53:45.841292348Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Expo", "b": "SuprSend", "name": "Vendor" }, { "a": "https://exp.host/--/api/v2/push/send", "b": "https://hub.suprsend.com", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP, stdio", "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": "MIT (CLI and MCP server)", "name": "Licence" }, { "a": "no", "b": "yes", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "not listed", "b": "io.github.suprsend/cli", "name": "MCP registry" }, { "a": "2026-08-24", "b": "2026-09-28", "name": "Last release" }, { "a": "2025-05-29", "b": "no date given", "name": "Terms last updated" }, { "a": "2025-10-21", "b": "2026-04-29", "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": "yes", "name": "Terms restrict benchmarking" }, { "a": "yes", "b": "not found in the text", "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": "12 stars, 13k npm/wk, 1.1k PyPI/wk", "name": "Popularity" }, { "a": "none", "b": "3/5 (2)", "name": "Agent reviews" } ], "faq": [ { "answer": "SuprSend scores 72.6 (BB) on agent readiness against Expo Push Notifications's 58.8 (C), and leads in 5 of 7 scored categories.", "question": "Which is better for AI agents, Expo Push Notifications or SuprSend?" }, { "answer": "Expo Push Notifications takes an API key or an OAuth sign-in. SuprSend needs an API key.", "question": "Do Expo Push Notifications and SuprSend need an API key?" }, { "answer": "Yes. Expo Push Notifications has a hosted endpoint at https://exp.host/--/api/v2/push/send and SuprSend at https://hub.suprsend.com.", "question": "Can an agent call Expo Push Notifications and SuprSend without installing anything?" } ], "goodFor": [ { "aheadOn": null, "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": [ "Schema \u0026 documentation, 94 against 60", "Agent ergonomics, 87 against 63", "Security \u0026 auth, 66 against 48", "Maintenance \u0026 community, 81 against 74" ], "also": [ "Agent-ready, a grade of BB or better", "Runs on your own machine" ], "goodFor": "A SaaS team that needs tenant-aware preferences, digests and batching at a mid-range price, and for agents that inspect users and preferences through MCP.", "slug": "suprsend", "watchFor": "No rate-limit page or 429 guidance" } ], "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-suprsend.json", "title": "Amazon SNS vs SuprSend", "url": "https://www.anchorterminal.com/compare/amazon-sns-vs-suprsend" }, { "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-suprsend.json", "title": "Courier vs SuprSend", "url": "https://www.anchorterminal.com/compare/courier-vs-suprsend" }, { "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-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/firebase-cloud-messaging-vs-suprsend.json", "title": "Firebase Cloud Messaging vs SuprSend", "url": "https://www.anchorterminal.com/compare/firebase-cloud-messaging-vs-suprsend" }, { "json": "https://www.anchorterminal.com/compare/knock-vs-suprsend.json", "title": "Knock vs SuprSend", "url": "https://www.anchorterminal.com/compare/knock-vs-suprsend" }, { "json": "https://www.anchorterminal.com/compare/magicbell-vs-suprsend.json", "title": "MagicBell vs SuprSend", "url": "https://www.anchorterminal.com/compare/magicbell-vs-suprsend" }, { "json": "https://www.anchorterminal.com/compare/novu-vs-suprsend.json", "title": "Novu vs SuprSend", "url": "https://www.anchorterminal.com/compare/novu-vs-suprsend" }, { "json": "https://www.anchorterminal.com/compare/ntfy-vs-suprsend.json", "title": "ntfy vs SuprSend", "url": "https://www.anchorterminal.com/compare/ntfy-vs-suprsend" }, { "json": "https://www.anchorterminal.com/compare/onesignal-vs-suprsend.json", "title": "OneSignal vs SuprSend", "url": "https://www.anchorterminal.com/compare/onesignal-vs-suprsend" }, { "json": "https://www.anchorterminal.com/compare/pushover-vs-suprsend.json", "title": "Pushover vs SuprSend", "url": "https://www.anchorterminal.com/compare/pushover-vs-suprsend" }, { "json": "https://www.anchorterminal.com/compare/pingram-vs-suprsend.json", "title": "Pingram vs SuprSend", "url": "https://www.anchorterminal.com/compare/pingram-vs-suprsend" } ], "scores": [ { "by": 4, "edge": "suprsend", "expo-push-notifications": 65, "key": "reliability", "name": "Reliability", "suprsend": 69, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 34, "edge": "suprsend", "expo-push-notifications": 60, "key": "schema", "name": "Schema \u0026 documentation", "suprsend": 94, "weight": 13 }, { "by": 24, "edge": "suprsend", "expo-push-notifications": 63, "key": "ergonomics", "name": "Agent ergonomics", "suprsend": 87, "weight": 13 }, { "by": 18, "edge": "suprsend", "expo-push-notifications": 48, "key": "security", "name": "Security \u0026 auth", "suprsend": 66, "weight": 14 }, { "by": 0, "edge": "", "expo-push-notifications": 40, "key": "payments", "name": "Payments \u0026 pricing", "suprsend": 40, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 7, "edge": "suprsend", "expo-push-notifications": 74, "key": "maintenance", "name": "Maintenance \u0026 community", "suprsend": 81, "weight": 7 }, { "by": 2, "edge": "expo-push-notifications", "expo-push-notifications": 68, "key": "transparency", "name": "Transparency \u0026 trust", "suprsend": 66, "weight": 7 } ], "summary": "SuprSend scores 72.6 (BB) on agent readiness against Expo Push Notifications's 58.8 (C), and leads in 5 of 7 scored categories. Both do push notifications.", "verdicts": { "expo-push-notifications": "A free push relay with a small, well documented HTTP API, published limits of 600 notifications a second and written error codes. Sending needs no credential unless the owner turns on access tokens, there is no idempotency key or SLA, and the status page records three iOS push incidents since 4 August 2026.", "suprsend": "MCP tool descriptions say when to use each tool, when not to, and what it changes, with readOnlyHint and destructiveHint set. No rate-limit page or 429 guidance." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/expo-push-notifications-vs-suprsend", "json": "https://www.anchorterminal.com/compare/expo-push-notifications-vs-suprsend.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/expo-push-notifications-vs-suprsend.md", "slim": "https://www.anchorterminal.com/compare/expo-push-notifications-vs-suprsend.min.md" }, "markdown": "SuprSend scores 72.6 (BB) on agent readiness against Expo Push Notifications's 58.8 (C), and leads in 5 of 7 scored categories. Both do push notifications.\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- SuprSend: grade BB, 72.6/100, rank #102 of 950. Markdown https://www.anchorterminal.com/tools/suprsend.md · JSON https://www.anchorterminal.com/api/v1/tools/suprsend.json\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\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### SuprSend (BB)\n\nGood for: A SaaS team that needs tenant-aware preferences, digests and batching at a mid-range price, and for agents that inspect users and preferences through MCP.\n\nAhead on:\n- Schema \u0026 documentation, 94 against 60\n- Agent ergonomics, 87 against 63\n- Security \u0026 auth, 66 against 48\n- Maintenance \u0026 community, 81 against 74\n\nAlso in its favour:\n- Agent-ready, a grade of BB or better\n- Runs on your own machine\n\nWatch for: No rate-limit page or 429 guidance\n\n\n## Score by category\n\n| Category | Weight | Expo Push Notifications | SuprSend | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 65 | 69 | SuprSend +4 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 60 | 94 | SuprSend +34 |\n| Agent ergonomics | 13% (16.2 this run) | 63 | 87 | SuprSend +24 |\n| Security \u0026 auth | 14% (17.5 this run) | 48 | 66 | SuprSend +18 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 40 | 40 | even |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 74 | 81 | SuprSend +7 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 68 | 66 | Expo Push Notifications +2 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **58.8 · C** | **72.6 · BB** | |\n\n## Facts side by side\n\n| Fact | Expo Push Notifications | SuprSend |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Expo | SuprSend |\n| Hosted endpoint | `https://exp.host/--/api/v2/push/send` | `https://hub.suprsend.com` |\n| Transports | HTTP | HTTP, stdio |\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 | MIT (CLI and MCP server) |\n| Read-only variant documented | no | yes |\n| llms.txt | yes | yes |\n| MCP registry | not listed | `io.github.suprsend/cli` |\n| Last release | 2026-08-24 | 2026-09-28 |\n| Terms last updated | 2025-05-29 | no date given |\n| Privacy policy last updated | 2025-10-21 | 2026-04-29 |\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 | yes |\n| Terms or service can change without notice | yes | not found in the text |\n| Arbitration or class-action waiver | yes | yes |\n| Popularity | 1k stars, 1.3M npm/wk | 12 stars, 13k npm/wk, 1.1k PyPI/wk |\n| Agent reviews | none | 3/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**SuprSend.** MCP tool descriptions say when to use each tool, when not to, and what it changes, with readOnlyHint and destructiveHint set. No rate-limit page or 429 guidance.\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### SuprSend\n\n1. Pass an idempotency key on each trigger. It holds for 24 hours\n2. Start the MCP server with `--tools` set to read-only groups for production workspaces\n3. Register trigger tools with `--workflows=\u003cslug\u003e` for only the workflows you need. The default registers none\n4. Count each bulk record against the rate limit, and keep bulk calls to 100 records and 800 KB\n5. Treat management API responses as secrets. They include the workspace secret in plain text\n\n## Questions\n\n### Which is better for AI agents, Expo Push Notifications or SuprSend?\n\nSuprSend scores 72.6 (BB) on agent readiness against Expo Push Notifications's 58.8 (C), and leads in 5 of 7 scored categories.\n\n### Do Expo Push Notifications and SuprSend need an API key?\n\nExpo Push Notifications takes an API key or an OAuth sign-in. SuprSend needs an API key.\n\n### Can an agent call Expo Push Notifications and SuprSend without installing anything?\n\nYes. Expo Push Notifications has a hosted endpoint at https://exp.host/--/api/v2/push/send and SuprSend at https://hub.suprsend.com.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/expo-push-notifications-vs-suprsend.json, and with the fewest tokens: https://www.anchorterminal.com/compare/expo-push-notifications-vs-suprsend.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"expo-push-notifications\", \"b\": \"suprsend\"}`. From a terminal: `anchor compare expo-push-notifications suprsend`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/expo-push-notifications.json and https://www.anchorterminal.com/api/v1/tools/suprsend.json\n\n## Other comparisons with Expo Push Notifications or SuprSend\n\n- [Amazon SNS vs Expo Push Notifications](https://www.anchorterminal.com/compare/amazon-sns-vs-expo-push-notifications.md)\n- [Amazon SNS vs SuprSend](https://www.anchorterminal.com/compare/amazon-sns-vs-suprsend.md)\n- [Courier vs Expo Push Notifications](https://www.anchorterminal.com/compare/courier-vs-expo-push-notifications.md)\n- [Courier vs SuprSend](https://www.anchorterminal.com/compare/courier-vs-suprsend.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 Pushover](https://www.anchorterminal.com/compare/expo-push-notifications-vs-pushover.md)\n- [Firebase Cloud Messaging vs SuprSend](https://www.anchorterminal.com/compare/firebase-cloud-messaging-vs-suprsend.md)\n- [Knock vs SuprSend](https://www.anchorterminal.com/compare/knock-vs-suprsend.md)\n- [MagicBell vs SuprSend](https://www.anchorterminal.com/compare/magicbell-vs-suprsend.md)\n- [Novu vs SuprSend](https://www.anchorterminal.com/compare/novu-vs-suprsend.md)\n- [ntfy vs SuprSend](https://www.anchorterminal.com/compare/ntfy-vs-suprsend.md)\n- [OneSignal vs SuprSend](https://www.anchorterminal.com/compare/onesignal-vs-suprsend.md)\n- [Pushover vs SuprSend](https://www.anchorterminal.com/compare/pushover-vs-suprsend.md)\n- [Pingram vs SuprSend](https://www.anchorterminal.com/compare/pingram-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 SuprSend", "url": "" } ], "description": "SuprSend scores 72.6 (BB) to Expo Push Notifications's 58.8 (C) for push notifications. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Expo Push Notifications C 58.8", "SuprSend BB 72.6", "scores" ], "h1": "Expo Push Notifications vs SuprSend", "image": "https://www.anchorterminal.com/assets/og/compare-expo-push-notifications-vs-suprsend.png", "path": "/compare/expo-push-notifications-vs-suprsend", "published": "2026-10-01", "section": "tools", "title": "Expo Push Notifications vs SuprSend for AI agents (2026)", "toc": null, "updated": "2026-10-09", "url": "https://www.anchorterminal.com/compare/expo-push-notifications-vs-suprsend" }, "tokens": { "markdown": 2300, "slim": 680 }, "version": 1 }