{ "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": "Knock scores 66.5 (B) on agent readiness against Expo Push Notifications's 58.8 (C), and leads in 4 of 7 scored categories. Expo Push Notifications leads on reliability and transparency \u0026 trust.", "b": { "slug": "knock", "name": "Knock", "vendor": "Knock", "vendorUrl": "https://knock.app", "kind": "http-api", "category": "notifications", "summary": "Notification workflow API.", "url": "https://www.anchorterminal.com/tools/knock", "markdownUrl": "https://www.anchorterminal.com/tools/knock.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/knock.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/knock.json", "repo": "https://github.com/knocklabs/knock-node", "license": "Apache-2.0 (Node SDK)", "transports": [ "http", "streamable-http" ], "remoteUrl": "https://api.knock.app/v1", "packages": [ { "registry": "npm", "name": "@knocklabs/node" }, { "registry": "pypi", "name": "knockapi" } ], "auth": "mixed", "authNotes": "Secret API key per environment as a Bearer token for server calls, and a public key plus signed user tokens for client feeds. The hosted MCP signs in with OAuth or takes a service token (`knock_st_...`) as a Bearer credential for headless use.", "pricing": "freemium", "pricingNotes": "Developer plan free with 10,000 messages a month, 500 guide active users and 500 AI agent credits. Starter $250 a month with 50,000 messages prepaid, then $0.005 a message, 2,500 guide active users ($0.05 each after) and 2,000 agent credits ($0.01 each after). Enterprise is priced by volume or by notified users. A message is one delivery to one user on one channel, and bounced or failed messages aren't billed. No setup fee, billed monthly in arrears (https://knock.app/pricing).", "priceSummary": "$250 / mo", "where": "hosted", "x402": { "level": "no", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": 50, "npmWeekly": 926382, "pypiWeekly": 233669, "asOf": "2026-09-30" }, "docsUrl": "https://docs.knock.app", "llmsTxt": "https://docs.knock.app/llms.txt", "openapi": "https://docs.knock.app/openapi.json", "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-29", "graded": true, "anchor": { "graded": true, "score": 66.5, "grade": "B", "agentReady": false, "rank": 286, "ranked": true, "rankOf": 950, "categoryRank": 6, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 64, "maintenance": 86, "payments": 40, "reliability": 58, "schema": 88, "security": 71, "transparency": 60 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-01" }, "negative": 0, "verdict": "Hosted MCP server with OAuth, six capability toggles and no delete tools. Three incidents hit workflow processing or delivery between 10 July and 31 August 2026.", "bestFor": "A product team that wants a workflow engine with batching, preferences and an in-app feed, and for agents that build and debug workflows through MCP safely.", "strengths": [ "Hosted MCP server with OAuth, six capability toggles and no delete tools", "Idempotency keys on trigger for 24 hours, plus cancellation keys for delayed runs", "Rate limits published in five tiers from 1 to 1,000 requests a second", "Audit logs attribute management API changes to the service token that made them", "Free plan with 10,000 messages a month and no card" ], "weaknesses": [ "Three incidents hit workflow processing or delivery between 10 July and 31 August 2026", "No SLA, Retry-After header or backoff guidance found", "Service tokens carry the creator's full privileges with no expiry, and skip MCP consent", "Starter jumps from free to $250 a month", "Email, SMS and push go through providers you configure and pay for separately" ], "agentNotes": [ "Create the workflow in the dashboard or through the MCP server before you trigger it. Triggers reference it by key", "Send an `Idempotency-Key` on every trigger. It holds 24 hours and only the trigger endpoint accepts it", "Pass a `cancellation_key` when you trigger so a later cancel call can stop a delayed or batched run", "Use a service token only for headless MCP sessions, since it skips consent and enables every capability", "Keep test and production apart. Rate limits and keys are scoped to an environment" ], "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": 66.5 } ], "editorialScores": { "ergonomics": 64, "maintenance": 86, "payments": 40, "reliability": 58, "schema": 88, "security": 71, "transparency": 39 }, "provenanceScore": 81 }, "connect": { "http": "curl -X POST https://api.knock.app/v1/workflows/new-comment/trigger \\\n -H \"Authorization: Bearer $KNOCK_SECRET_API_KEY\" -H \"Content-Type: application/json\" \\\n -d '{\"recipients\":[\"user_123\"],\"data\":{\"message\":\"Build finished\"}}'", "claudeCode": "claude mcp add --transport http knock https://mcp.knock.app/mcp", "config": { "mcpServers": { "knock": { "headers": { "Authorization": "Bearer ${KNOCK_SERVICE_TOKEN}" }, "type": "http", "url": "https://mcp.knock.app/mcp" } } } }, "letme": { "capability": "https://letme.dev/notify.push", "tool": "https://letme.dev/knock" }, "area": "everyday", "unitPrices": [ { "item": "Starter", "unit": "month", "usd": 250, "note": "50,000 messages included" }, { "item": "Starter overage", "unit": "message", "usd": 0.005 }, { "item": "AI agent credit overage", "unit": "credit", "usd": 0.01 } ], "provenance": { "legalEntity": "Knock Labs, Inc.", "domain": "knock.app", "domainRegistered": "2020-08-28", "endpointOnVendorDomain": true, "terms": "https://knock.app/terms", "privacy": "https://knock.app/legal/privacy-policy", "statusPage": "https://status.knock.app", "changelog": "https://knock.app/changelog", "securityTxt": "none", "checked": "2026-09-30", "notes": [ "Terms are governed by New York law. A separate data processing addendum is published at knock.app/legal/data-processing-addendum.", "The status page tracks the in-dashboard agent as its own component." ], "score": 81 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/knock.json", "live": { "slug": "knock", "probe": { "target": "https://api.knock.app/v1", "method": "get", "lastAt": "2026-10-10T02:54:59.529478975Z", "lastOk": true, "lastStatus": 404, "lastMs": 295, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 296, "p95ms24h": 358, "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.knock.app", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-10T02:50:26.036516158Z" }, "versions": [ { "registry": "github", "name": "knocklabs/knock-node", "version": "v1.36.0", "released": "2026-09-30", "seenAt": "2026-10-09T17:00:42.430172293Z" }, { "registry": "npm", "name": "@knocklabs/node", "version": "1.36.0", "seenAt": "2026-10-09T17:00:41.243705774Z" }, { "registry": "pypi", "name": "knockapi", "version": "1.31.0", "released": "2026-09-30", "seenAt": "2026-10-09T17:00:42.231541939Z" } ], "githubStars": 50, "npmWeekly": 816839, "pypiWeekly": 188542, "securityTxt": { "url": "https://knock.app/.well-known/security.txt", "state": "none", "checkedAt": "2026-10-09T15:40:04.908236027Z" }, "llmsTxt": { "url": "https://docs.knock.app/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-10-09T14:02:12.811305284Z" }, "domain": { "domain": "knock.app", "registered": "2020-08-28", "source": "https://pubapi.registry.google/rdap/domain/knock.app", "checkedAt": "2026-10-04T13:04:01.050922733Z" }, "pages": [ { "url": "https://knock.app/changelog", "kind": "changelog", "status": 200, "checkedAt": "2026-10-09T18:40:45.122757089Z", "changedAt": "2026-10-09T18:40:45.122757089Z", "fingerprint": "d178c7ea1881" }, { "url": "https://knock.app/pricing", "kind": "pricing", "status": 200, "checkedAt": "2026-10-09T18:40:49.365988229Z", "changedAt": "2026-10-07T18:06:47.972051612Z", "fingerprint": "88884ef8f29a" }, { "url": "https://knock.app/legal/privacy-policy", "kind": "privacy", "status": 200, "checkedAt": "2026-10-09T18:40:47.504246902Z", "changedAt": "2026-10-07T18:06:45.716206824Z", "fingerprint": "8b88939fcacf" }, { "url": "https://knock.app/terms", "kind": "terms", "status": 200, "checkedAt": "2026-10-09T18:40:51.214668721Z", "changedAt": "2026-10-07T18:06:49.489482879Z", "fingerprint": "2855cc420ae7" } ], "updatedAt": "2026-10-10T02:54:59.529478975Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Expo", "b": "Knock", "name": "Vendor" }, { "a": "https://exp.host/--/api/v2/push/send", "b": "https://api.knock.app/v1", "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": "Apache-2.0 (Node SDK)", "name": "Licence" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "2026-08-24", "b": "2026-09-29", "name": "Last release" }, { "a": "2025-05-29", "b": "2026-03-04", "name": "Terms last updated" }, { "a": "2025-10-21", "b": "2026-03-04", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "yes", "b": "yes", "name": "Terms restrict automated access" }, { "a": "not found in the text", "b": "not found in the text", "name": "Terms restrict benchmarking" }, { "a": "yes", "b": "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": "50 stars, 926k npm/wk, 234k PyPI/wk", "name": "Popularity" }, { "a": "none", "b": "3.5/5 (2)", "name": "Agent reviews" } ], "faq": [ { "answer": "Knock scores 66.5 (B) on agent readiness against Expo Push Notifications's 58.8 (C), and leads in 4 of 7 scored categories. Expo Push Notifications leads on reliability and transparency \u0026 trust.", "question": "Which is better for AI agents, Expo Push Notifications or Knock?" }, { "answer": "Both take an API key or an OAuth sign-in.", "question": "Do Expo Push Notifications and Knock need an API key?" }, { "answer": "Yes. Expo Push Notifications has a hosted endpoint at https://exp.host/--/api/v2/push/send and Knock at https://api.knock.app/v1.", "question": "Can an agent call Expo Push Notifications and Knock without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 65 against 58", "Transparency \u0026 trust, 68 against 60" ], "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, 88 against 60", "Security \u0026 auth, 71 against 48", "Maintenance \u0026 community, 86 against 74" ], "also": null, "goodFor": "A product team that wants a workflow engine with batching, preferences and an in-app feed, and for agents that build and debug workflows through MCP safely.", "slug": "knock", "watchFor": "Three incidents hit workflow processing or delivery between 10 July and 31 August 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-knock.json", "title": "Amazon SNS vs Knock", "url": "https://www.anchorterminal.com/compare/amazon-sns-vs-knock" }, { "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-knock.json", "title": "Courier vs Knock", "url": "https://www.anchorterminal.com/compare/courier-vs-knock" }, { "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-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/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-knock.json", "title": "Firebase Cloud Messaging vs Knock", "url": "https://www.anchorterminal.com/compare/firebase-cloud-messaging-vs-knock" }, { "json": "https://www.anchorterminal.com/compare/knock-vs-magicbell.json", "title": "Knock vs MagicBell", "url": "https://www.anchorterminal.com/compare/knock-vs-magicbell" }, { "json": "https://www.anchorterminal.com/compare/knock-vs-novu.json", "title": "Knock vs Novu", "url": "https://www.anchorterminal.com/compare/knock-vs-novu" }, { "json": "https://www.anchorterminal.com/compare/knock-vs-ntfy.json", "title": "Knock vs ntfy", "url": "https://www.anchorterminal.com/compare/knock-vs-ntfy" }, { "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/knock-vs-pingram.json", "title": "Knock vs Pingram", "url": "https://www.anchorterminal.com/compare/knock-vs-pingram" }, { "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/knock-vs-suprsend.json", "title": "Knock vs SuprSend", "url": "https://www.anchorterminal.com/compare/knock-vs-suprsend" } ], "scores": [ { "by": 7, "edge": "expo-push-notifications", "expo-push-notifications": 65, "key": "reliability", "knock": 58, "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 28, "edge": "knock", "expo-push-notifications": 60, "key": "schema", "knock": 88, "name": "Schema \u0026 documentation", "weight": 13 }, { "by": 1, "edge": "knock", "expo-push-notifications": 63, "key": "ergonomics", "knock": 64, "name": "Agent ergonomics", "weight": 13 }, { "by": 23, "edge": "knock", "expo-push-notifications": 48, "key": "security", "knock": 71, "name": "Security \u0026 auth", "weight": 14 }, { "by": 0, "edge": "", "expo-push-notifications": 40, "key": "payments", "knock": 40, "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 12, "edge": "knock", "expo-push-notifications": 74, "key": "maintenance", "knock": 86, "name": "Maintenance \u0026 community", "weight": 7 }, { "by": 8, "edge": "expo-push-notifications", "expo-push-notifications": 68, "key": "transparency", "knock": 60, "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "Knock scores 66.5 (B) on agent readiness against Expo Push Notifications's 58.8 (C), and leads in 4 of 7 scored categories. Expo Push Notifications leads on reliability and 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.", "knock": "Hosted MCP server with OAuth, six capability toggles and no delete tools. Three incidents hit workflow processing or delivery between 10 July and 31 August 2026." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/expo-push-notifications-vs-knock", "json": "https://www.anchorterminal.com/compare/expo-push-notifications-vs-knock.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/expo-push-notifications-vs-knock.md", "slim": "https://www.anchorterminal.com/compare/expo-push-notifications-vs-knock.min.md" }, "markdown": "Knock scores 66.5 (B) on agent readiness against Expo Push Notifications's 58.8 (C), and leads in 4 of 7 scored categories. Expo Push Notifications leads on reliability and 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- Knock: grade B, 66.5/100, rank #286 of 950. Markdown https://www.anchorterminal.com/tools/knock.md · JSON https://www.anchorterminal.com/api/v1/tools/knock.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- Reliability, 65 against 58\n- Transparency \u0026 trust, 68 against 60\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### Knock (B)\n\nGood for: A product team that wants a workflow engine with batching, preferences and an in-app feed, and for agents that build and debug workflows through MCP safely.\n\nAhead on:\n- Schema \u0026 documentation, 88 against 60\n- Security \u0026 auth, 71 against 48\n- Maintenance \u0026 community, 86 against 74\n\nWatch for: Three incidents hit workflow processing or delivery between 10 July and 31 August 2026\n\n\n## Score by category\n\n| Category | Weight | Expo Push Notifications | Knock | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 65 | 58 | Expo Push Notifications +7 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 60 | 88 | Knock +28 |\n| Agent ergonomics | 13% (16.2 this run) | 63 | 64 | Knock +1 |\n| Security \u0026 auth | 14% (17.5 this run) | 48 | 71 | Knock +23 |\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 | 86 | Knock +12 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 68 | 60 | Expo Push Notifications +8 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **58.8 · C** | **66.5 · B** | |\n\n## Facts side by side\n\n| Fact | Expo Push Notifications | Knock |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Expo | Knock |\n| Hosted endpoint | `https://exp.host/--/api/v2/push/send` | `https://api.knock.app/v1` |\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 | Apache-2.0 (Node SDK) |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| Last release | 2026-08-24 | 2026-09-29 |\n| Terms last updated | 2025-05-29 | 2026-03-04 |\n| Privacy policy last updated | 2025-10-21 | 2026-03-04 |\n| Customer content may train models | not found in the text | not found in the text |\n| Terms restrict automated access | yes | yes |\n| Terms restrict benchmarking | not found in the text | not found in the text |\n| Terms or service can change without notice | yes | yes |\n| Arbitration or class-action waiver | yes | yes |\n| Popularity | 1k stars, 1.3M npm/wk | 50 stars, 926k npm/wk, 234k 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**Knock.** Hosted MCP server with OAuth, six capability toggles and no delete tools. Three incidents hit workflow processing or delivery between 10 July and 31 August 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### Knock\n\n1. Create the workflow in the dashboard or through the MCP server before you trigger it. Triggers reference it by key\n2. Send an `Idempotency-Key` on every trigger. It holds 24 hours and only the trigger endpoint accepts it\n3. Pass a `cancellation_key` when you trigger so a later cancel call can stop a delayed or batched run\n4. Use a service token only for headless MCP sessions, since it skips consent and enables every capability\n5. Keep test and production apart. Rate limits and keys are scoped to an environment\n\n## Questions\n\n### Which is better for AI agents, Expo Push Notifications or Knock?\n\nKnock scores 66.5 (B) on agent readiness against Expo Push Notifications's 58.8 (C), and leads in 4 of 7 scored categories. Expo Push Notifications leads on reliability and transparency \u0026 trust.\n\n### Do Expo Push Notifications and Knock 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 Knock without installing anything?\n\nYes. Expo Push Notifications has a hosted endpoint at https://exp.host/--/api/v2/push/send and Knock at https://api.knock.app/v1.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/expo-push-notifications-vs-knock.json, and with the fewest tokens: https://www.anchorterminal.com/compare/expo-push-notifications-vs-knock.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"expo-push-notifications\", \"b\": \"knock\"}`. From a terminal: `anchor compare expo-push-notifications knock`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/expo-push-notifications.json and https://www.anchorterminal.com/api/v1/tools/knock.json\n\n## Other comparisons with Expo Push Notifications or Knock\n\n- [Amazon SNS vs Expo Push Notifications](https://www.anchorterminal.com/compare/amazon-sns-vs-expo-push-notifications.md)\n- [Amazon SNS vs Knock](https://www.anchorterminal.com/compare/amazon-sns-vs-knock.md)\n- [Courier vs Expo Push Notifications](https://www.anchorterminal.com/compare/courier-vs-expo-push-notifications.md)\n- [Courier vs Knock](https://www.anchorterminal.com/compare/courier-vs-knock.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 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- [Expo Push Notifications vs SuprSend](https://www.anchorterminal.com/compare/expo-push-notifications-vs-suprsend.md)\n- [Firebase Cloud Messaging vs Knock](https://www.anchorterminal.com/compare/firebase-cloud-messaging-vs-knock.md)\n- [Knock vs MagicBell](https://www.anchorterminal.com/compare/knock-vs-magicbell.md)\n- [Knock vs Novu](https://www.anchorterminal.com/compare/knock-vs-novu.md)\n- [Knock vs ntfy](https://www.anchorterminal.com/compare/knock-vs-ntfy.md)\n- [Knock vs OneSignal](https://www.anchorterminal.com/compare/knock-vs-onesignal.md)\n- [Knock vs Pingram](https://www.anchorterminal.com/compare/knock-vs-pingram.md)\n- [Knock vs Pushover](https://www.anchorterminal.com/compare/knock-vs-pushover.md)\n- [Knock vs SuprSend](https://www.anchorterminal.com/compare/knock-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 Knock", "url": "" } ], "description": "Knock scores 66.5 (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", "Knock B 66.5", "scores" ], "h1": "Expo Push Notifications vs Knock", "image": "https://www.anchorterminal.com/assets/og/compare-expo-push-notifications-vs-knock.png", "path": "/compare/expo-push-notifications-vs-knock", "published": "2026-10-01", "section": "tools", "title": "Expo Push Notifications vs Knock for AI agents (2026)", "toc": null, "updated": "2026-10-09", "url": "https://www.anchorterminal.com/compare/expo-push-notifications-vs-knock" }, "tokens": { "markdown": 2300, "slim": 630 }, "version": 1 }