{ "data": { "a": { "slug": "ntfy", "name": "ntfy", "vendor": "ntfy", "vendorUrl": "https://ntfy.sh", "kind": "http-api", "category": "notifications", "summary": "Open-source publish-subscribe service for push notifications.", "url": "https://www.anchorterminal.com/tools/ntfy", "markdownUrl": "https://www.anchorterminal.com/tools/ntfy.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/ntfy.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/ntfy.json", "repo": "https://github.com/binwiederhier/ntfy", "license": "Apache-2.0 and GPL-2.0 (dual)", "transports": [ "http" ], "remoteUrl": "https://ntfy.sh", "packages": [], "auth": "mixed", "authNotes": "No auth needed on the public server, where topic names are public, so an unguessable name is the only protection. Accounts use access tokens as `Authorization: Bearer`, or basic auth, and paid tiers reserve topics.", "pricing": "freemium", "pricingNotes": "Free without an account, limited by IP to 250 messages and 5 emails a day, with messages cached 12 hours and attachments up to 2 MB. Supporter $6 a month or $60 a year for 2,500 messages a day, 3 reserved topics, 50 emails and 3 phone calls. Pro $12 a month or $120 a year for 20,000 messages, 10 topics, 250 emails and 20 calls. Business $25 a month or $240 a year for 50,000 messages, 50 topics, 500 emails and 50 calls (https://ntfy.sh/v1/tiers, https://ntfy.sh). Self-hosting is free (https://github.com/binwiederhier/ntfy).", "priceSummary": "$6 / mo", "where": "hosted", "x402": { "level": "no", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": 33500, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-09-30" }, "docsUrl": "https://docs.ntfy.sh", "capabilities": [ "notify.push" ], "tags": [ "hosted", "freemium", "free-tier", "no-key", "open-source", "self-hosted" ], "lastRelease": "2026-08-27", "graded": true, "anchor": { "graded": true, "score": 61.5, "grade": "C", "agentReady": false, "rank": 464, "ranked": true, "rankOf": 950, "categoryRank": 8, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 66, "maintenance": 67, "payments": 50, "reliability": 83, "schema": 53, "security": 38, "transparency": 78 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-01" }, "negative": 0, "verdict": "Publish with one HTTP POST and no account, up to 250 messages a day per IP on ntfy.sh. Unreserved topics on ntfy.sh can be read and written by anyone who knows the name.", "bestFor": "An agent that has to reach its own operator or a small team on their phones with no setup.", "strengths": [ "Publish with one HTTP POST and no account, up to 250 messages a day per IP on ntfy.sh", "Apache-2.0 and GPL-2.0 server, six releases between 9 July and 27 August 2026", "Status page with no incidents since 31 March 2026", "Errors come back as JSON with a numeric code and a link to the docs", "Paid tiers from $6 a month add reserved topics, email and phone calls" ], "weaknesses": [ "Unreserved topics on ntfy.sh can be read and written by anyone who knows the name", "No idempotency key, so a retried publish arrives twice", "No OpenAPI spec, llms.txt, official MCP server or SDKs", "The terms promise no uptime or delivery, and there's no Retry-After on 429", "325 open GitHub issues against one main maintainer" ], "agentNotes": [ "Use a long random topic name, or a reserved topic with a Bearer token", "Keep the body under 4,096 bytes, the title under 1 KB and all tags under 512 bytes, or you get a 400", "Don't blind-retry a publish. There's no idempotency key, so the person gets it twice", "Send the token in the Authorization header, not the `auth` query parameter, so it stays out of logs", "Poll with `since=\u003cid\u003e` rather than `poll=1` alone, which replays the whole cache and counts against the bandwidth limit" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 2, "avgRating": 4, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 61.5 } ], "editorialScores": { "ergonomics": 66, "maintenance": 67, "payments": 50, "reliability": 83, "schema": 53, "security": 38, "transparency": 82 }, "provenanceScore": 74 }, "connect": { "http": "curl -H \"Authorization: Bearer $NTFY_TOKEN\" \\\n -H \"Title: Build finished\" -H \"Priority: high\" -H \"Tags: white_check_mark\" \\\n -d \"All tests passed\" \"https://ntfy.sh/$NTFY_TOPIC\"" }, "letme": { "capability": "https://letme.dev/notify.push", "tool": "https://letme.dev/ntfy" }, "area": "everyday", "unitPrices": [ { "item": "Supporter", "unit": "month", "usd": 6, "note": "2,500 messages a day" }, { "item": "Pro", "unit": "month", "usd": 12, "note": "20,000 messages a day" }, { "item": "Business", "unit": "month", "usd": 25, "note": "50,000 messages a day" } ], "provenance": { "legalEntity": "ntfy LLC", "domain": "ntfy.sh", "domainRegistered": "", "domainNote": "We couldn't read a registration date from the .sh registry's RDAP server.", "endpointOnVendorDomain": true, "terms": "https://docs.ntfy.sh/terms/", "privacy": "https://docs.ntfy.sh/privacy/", "statusPage": "https://ntfy.statuspage.io", "changelog": "https://docs.ntfy.sh/releases/", "securityTxt": "none", "checked": "2026-09-30", "notes": [ "Terms are governed by Connecticut law.", "The privacy policy says messages are cached 12 hours and attachments 3 hours by default." ], "score": 74 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/ntfy.json", "live": { "slug": "ntfy", "probe": { "target": "https://ntfy.sh", "method": "get", "lastAt": "2026-10-10T01:38:00.335329951Z", "lastOk": true, "lastStatus": 200, "lastMs": 309, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 246, "p95ms24h": 318, "samples24h": 250, "samples30d": 2251, "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": 17, "ok": 17 } ] }, "vendorStatus": { "page": "https://ntfy.statuspage.io", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-10T01:33:51.386907906Z" }, "versions": [ { "registry": "github", "name": "binwiederhier/ntfy", "version": "v2.29.0", "released": "2026-10-07", "seenAt": "2026-10-09T17:08:49.387511094Z" } ], "githubStars": 34712, "securityTxt": { "url": "https://ntfy.sh/.well-known/security.txt", "state": "none", "checkedAt": "2026-10-09T15:39:49.613111306Z" }, "domain": { "domain": "ntfy.sh", "checkedAt": "2026-10-04T13:08:41.08288357Z" }, "pages": [ { "url": "https://docs.ntfy.sh/releases/", "kind": "changelog", "status": 304, "checkedAt": "2026-10-09T18:37:54.664057097Z", "changedAt": "2026-10-08T18:19:14.141569808Z", "fingerprint": "f40471b920cd" }, { "url": "https://docs.ntfy.sh/privacy/", "kind": "privacy", "status": 200, "checkedAt": "2026-10-09T18:37:52.549333274Z", "changedAt": "2026-10-06T16:08:22.995893924Z", "fingerprint": "6d5209694c2f" }, { "url": "https://docs.ntfy.sh/terms/", "kind": "terms", "status": 304, "checkedAt": "2026-10-09T18:37:56.694933656Z", "changedAt": "2026-10-06T16:08:27.312688293Z", "fingerprint": "5d6de4f532fa" } ], "updatedAt": "2026-10-10T01:38:00.335329951Z" } }, "answer": "ntfy scores 61.5 (C) on agent readiness against Pingram's 57.4 (C), and leads in 3 of 7 scored categories. Pingram leads on schema \u0026 documentation, security \u0026 auth and maintenance \u0026 community.", "b": { "slug": "pingram", "name": "Pingram", "vendor": "Pingram", "vendorUrl": "https://www.pingram.io", "kind": "http-api", "category": "notifications", "summary": "Pingram, formerly NotificationAPI, is a hosted messaging API that sends email and SMS and receives replies by webhook. Agents reach it through a REST API, seven server SDKs, a CLI and a hosted MCP server.", "url": "https://www.anchorterminal.com/tools/pingram", "markdownUrl": "https://www.anchorterminal.com/tools/pingram.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/pingram.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/pingram.json", "repo": "https://github.com/pingram-io/pingram-go", "license": "Proprietary service under Pingram's terms of service. The Node.js SDK and CLI are MIT on npm. The Go SDK repository has no licence file", "transports": [ "http" ], "remoteUrl": "https://mcp.pingram.io", "packages": [ { "registry": "npm", "name": "pingram" }, { "registry": "npm", "name": "pingram-cli" }, { "registry": "go", "name": "github.com/pingram-io/pingram-go" } ], "auth": "mixed", "authNotes": "Self-serve. REST calls to `https://api.pingram.io` take an API key as `Authorization: Bearer`. Keys are created in the dashboard or through `POST /keys`, are secret or public, can be tied to one environment and can be revoked. The API reference also lists Basic schemes for client credentials and end users. The hosted MCP server uses OAuth sign-in with the dashboard account (email, Google or Microsoft) and has that user's access on every account they belong to. No scopes were found.", "pricing": "freemium", "pricingNotes": "Free tier of 3,000 emails and 100 SMS a month with one local number, no card, so an agent's owner can start without a contract. Paid plans are monthly budgets from $20 to $1,000 drawn down at per-message rates, $0.0005 an email and SMS by country ($0.0100 a segment to the United States). Unused balance does not roll over. Enterprise add-on from $800 a month (https://www.pingram.io/pricing).", "priceSummary": "$20 / mo", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the docs, the pricing page, llms.txt or the API reference (checked 2026-10-09).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": 1, "npmWeekly": 12699, "pypiWeekly": null, "asOf": "2026-10-09" }, "docsUrl": "https://www.pingram.io/docs", "llmsTxt": "https://www.pingram.io/llms.txt", "registryName": "io.pingram/mcp", "capabilities": [ "notify.multichannel", "notify.push", "notify.in-app", "email.send", "email.inbound", "email.domains", "messaging.sms", "messaging.mms", "messaging.inbound" ], "tags": [ "hosted", "freemium", "mcp", "oauth", "llms-txt", "typescript", "python", "go", "webhooks", "status-page", "soc2" ], "lastRelease": "2026-10-08", "graded": true, "anchor": { "graded": true, "score": 57.4, "grade": "C", "agentReady": false, "rank": 611, "ranked": true, "rankOf": 950, "categoryRank": 11, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 67, "maintenance": 81, "payments": 40, "reliability": 58, "schema": 69, "security": 51, "transparency": 54 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-09" }, "negative": -2, "negativeNotes": [ "2026-10-09. `llms.txt` and `llms-full.txt`, the files Pingram publishes for AI systems, give the paid plan as from $9 a month, while the pricing page's lowest paid budget is $20. `llms.txt` also links the API reference at an address that answers 403 (https://www.pingram.io/llms.txt, https://www.pingram.io/pricing). 2 points." ], "verdict": "Email and SMS go out through one REST call with built-in delivery, per-message prices are public and the free tier needs no card. No rate limits or idempotency keys were found in the reviewed documentation, and the MCP connector acts with the signed-in user's whole account.", "bestFor": "An agent that needs to send transactional email and SMS and read replies through one account without separate carrier or SMTP providers.", "strengths": [ "Email costs $0.0005 a message and SMS is priced per country on a public page, with a free tier of 3,000 emails and 100 SMS a month and no card", "Hosted MCP server at `https://mcp.pingram.io` with OAuth sign-in and regional hosts for Canada and the EU, listed in the official MCP registry", "Error responses carry a `trackingId` and an `error` object with `code`, `message` and an optional `fix` hint", "A dated changelog with a JSON feed shows more than 25 entries between 16 September and 7 October 2026", "security.txt valid to 13 September 2027 and a vulnerability disclosure policy with safe harbour, dated 14 September 2026" ], "weaknesses": [ "The terms of service forbid using the service for benchmarking. This matters before any probe is run", "No request rate limits, 429 handling or idempotency key for sends were found in the reviewed documentation", "The MCP connector has the signed-in user's access across every account they belong to, with no scopes or read-only mode found", "`llms.txt` gives a paid plan from $9 a month and links an API reference address that answers 403. The pricing page starts paid plans at $20", "RBAC, SAML and internal audit logs are sold only in the Enterprise add-on, which starts at $800 a month" ], "agentNotes": [ "Use the API host for the account's region. The key and region (`us`, `eu` or `ca`) come from the API Keys page in the dashboard", "Keep the `trackingId` from each send and check Logs before retrying. No idempotency key was found, so a blind retry can send twice", "Pass `accountId` on MCP tools when the user belongs to several accounts. Without it the tools use the earliest account joined", "Create broadcasts as drafts only. Pingram's own skill says a person must send a broadcast from the dashboard", "Expect 402 when the monthly budget is spent. Unused balance does not roll over" ], "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": 57.4 } ], "editorialScores": { "ergonomics": 67, "maintenance": 81, "payments": 40, "reliability": 58, "schema": 69, "security": 51, "transparency": 47 }, "provenanceScore": 60 }, "connect": { "install": "npm install pingram", "http": "curl -X POST https://api.pingram.io/email \\\n -H \"Authorization: Bearer $PINGRAM_API_KEY\" -H \"Content-Type: application/json\" \\\n -d '{\"type\":\"welcome\",\"to\":\"user@example.com\",\"subject\":\"Welcome\",\"html\":\"\u003cp\u003eHello\u003c/p\u003e\"}'", "config": { "mcpServers": { "pingram": { "url": "https://mcp.pingram.io" } } } }, "letme": { "capability": "https://letme.dev/notify.multichannel", "tool": "https://letme.dev/pingram" }, "area": "everyday", "unitPrices": [ { "item": "Email", "unit": "1k-emails", "usd": 0.5 }, { "item": "SMS to the United States", "unit": "message", "usd": 0.01, "note": "per segment, carrier fee included" }, { "item": "SMS to Canada", "unit": "message", "usd": 0.015, "note": "per segment, carrier fee included" }, { "item": "Lowest paid budget", "unit": "month", "usd": 20, "note": "about 2,000 US SMS or 40,000 emails" }, { "item": "Extra local phone number", "unit": "month", "usd": 0.5 }, { "item": "Enterprise add-on", "unit": "month", "usd": 800, "note": "starting price, on top of a paid budget" } ], "provenance": { "legalEntity": "", "domain": "pingram.io", "domainRegistered": "", "endpointOnVendorDomain": true, "terms": "https://www.pingram.io/terms-of-service", "privacy": "https://www.pingram.io/privacy-policy", "statusPage": "https://status.pingram.io", "changelog": "https://www.pingram.io/changelog", "securityTxt": "valid", "checked": "2026-10-09", "notes": [ "No legal entity is named. The terms, privacy policy and footer say Pingram or Pingram™, at 170 Water St., #0200, St. John's, Newfoundland and Labrador, Canada.", "The terms (last updated 16 April 2025) cover the website, APIs and related services, and are governed by the law of Newfoundland and Labrador.", "The API answers at api.pingram.io and the MCP server at mcp.pingram.io, both on the vendor's domain.", "security.txt names security@pingram.io and expires on 13 September 2027.", "RDAP for pingram.io answered 404 through rdap.org, so no registration date is recorded." ], "score": 60 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/pingram.json", "live": { "slug": "pingram", "probe": { "target": "https://mcp.pingram.io", "method": "get", "lastAt": "2026-10-10T01:38:02.513186516Z", "lastOk": true, "lastStatus": 401, "lastMs": 366, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 305, "p95ms24h": 483, "samples24h": 102, "samples30d": 102, "days": [ { "date": "2026-10-09", "probes": 85, "ok": 85 }, { "date": "2026-10-10", "probes": 17, "ok": 17 } ] }, "vendorStatus": { "page": "https://status.pingram.io", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-10T01:34:04.873387424Z" }, "versions": [ { "registry": "npm", "name": "pingram", "version": "1.0.38", "seenAt": "2026-10-09T17:13:00.934046118Z" }, { "registry": "npm", "name": "pingram-cli", "version": "1.0.20", "seenAt": "2026-10-09T17:13:01.370409108Z" } ], "githubStars": 1, "npmWeekly": 12699, "pages": [ { "url": "https://www.pingram.io/changelog", "kind": "changelog", "status": 200, "checkedAt": "2026-10-09T18:53:04.217531365Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "3ff49dfdb708" }, { "url": "https://www.pingram.io/pricing", "kind": "pricing", "status": 200, "checkedAt": "2026-10-09T18:53:06.703182666Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "c41e8c804eec" }, { "url": "https://www.pingram.io/privacy-policy", "kind": "privacy", "status": 200, "checkedAt": "2026-10-09T18:53:08.791743628Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "253bc47822ca" }, { "url": "https://www.pingram.io/terms-of-service", "kind": "terms", "status": 200, "checkedAt": "2026-10-09T18:53:10.238064171Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "bf1565dd261f" } ], "updatedAt": "2026-10-10T01:38:02.513186516Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "ntfy", "b": "Pingram", "name": "Vendor" }, { "a": "https://ntfy.sh", "b": "https://mcp.pingram.io", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP", "name": "Transports" }, { "a": "OAuth or key", "b": "OAuth or key", "name": "Auth" }, { "a": "Freemium", "b": "Freemium", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Apache-2.0 and GPL-2.0 (dual)", "b": "Proprietary service under Pingram's terms of service. The Node.js SDK and CLI are MIT on npm. The Go SDK repository has no licence file", "name": "Licence" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "no", "b": "yes", "name": "llms.txt" }, { "a": "not listed", "b": "io.pingram/mcp", "name": "MCP registry" }, { "a": "2026-08-27", "b": "2026-10-08", "name": "Last release" }, { "a": "2026-01-26", "b": "2025-04-16", "name": "Terms last updated" }, { "a": "2026-06-15", "b": "2025-04-16", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "not found in the text", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "not found in the text", "b": "yes", "name": "Terms restrict benchmarking" }, { "a": "not found in the text", "b": "yes", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "not found in the text", "name": "Arbitration or class-action waiver" }, { "a": "34k stars", "b": "1 stars, 13k npm/wk", "name": "Popularity" }, { "a": "4/5 (2)", "b": "none", "name": "Agent reviews" } ], "faq": [ { "answer": "ntfy scores 61.5 (C) on agent readiness against Pingram's 57.4 (C), and leads in 3 of 7 scored categories. Pingram leads on schema \u0026 documentation, security \u0026 auth and maintenance \u0026 community.", "question": "Which is better for AI agents, ntfy or Pingram?" }, { "answer": "Both take an API key or an OAuth sign-in.", "question": "Do ntfy and Pingram need an API key?" }, { "answer": "Yes. ntfy has a hosted endpoint at https://ntfy.sh and Pingram at https://mcp.pingram.io.", "question": "Can an agent call ntfy and Pingram without installing anything?" }, { "answer": "ntfy is open source (Apache-2.0 and GPL-2.0 (dual)). No open-source release is listed for Pingram.", "question": "Are ntfy and Pingram open source?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 83 against 58", "Payments \u0026 pricing, 50 against 40", "Transparency \u0026 trust, 78 against 54" ], "also": [ "Open source" ], "goodFor": "An agent that has to reach its own operator or a small team on their phones with no setup.", "slug": "ntfy", "watchFor": "Unreserved topics on ntfy.sh can be read and written by anyone who knows the name" }, { "aheadOn": [ "Schema \u0026 documentation, 69 against 53", "Security \u0026 auth, 51 against 38", "Maintenance \u0026 community, 81 against 67" ], "also": null, "goodFor": "An agent that needs to send transactional email and SMS and read replies through one account without separate carrier or SMTP providers.", "slug": "pingram", "watchFor": "The terms of service forbid using the service for benchmarking. This matters before any probe is run" } ], "job": { "capability": "notify.push", "name": "Push notifications" }, "others": [ { "json": "https://www.anchorterminal.com/compare/amazon-sns-vs-ntfy.json", "title": "Amazon SNS vs ntfy", "url": "https://www.anchorterminal.com/compare/amazon-sns-vs-ntfy" }, { "json": "https://www.anchorterminal.com/compare/amazon-sns-vs-pingram.json", "title": "Amazon SNS vs Pingram", "url": "https://www.anchorterminal.com/compare/amazon-sns-vs-pingram" }, { "json": "https://www.anchorterminal.com/compare/courier-vs-ntfy.json", "title": "Courier vs ntfy", "url": "https://www.anchorterminal.com/compare/courier-vs-ntfy" }, { "json": "https://www.anchorterminal.com/compare/courier-vs-pingram.json", "title": "Courier vs Pingram", "url": "https://www.anchorterminal.com/compare/courier-vs-pingram" }, { "json": "https://www.anchorterminal.com/compare/expo-push-notifications-vs-ntfy.json", "title": "Expo Push Notifications vs ntfy", "url": "https://www.anchorterminal.com/compare/expo-push-notifications-vs-ntfy" }, { "json": "https://www.anchorterminal.com/compare/expo-push-notifications-vs-pingram.json", "title": "Expo Push Notifications vs Pingram", "url": "https://www.anchorterminal.com/compare/expo-push-notifications-vs-pingram" }, { "json": "https://www.anchorterminal.com/compare/firebase-cloud-messaging-vs-ntfy.json", "title": "Firebase Cloud Messaging vs ntfy", "url": "https://www.anchorterminal.com/compare/firebase-cloud-messaging-vs-ntfy" }, { "json": "https://www.anchorterminal.com/compare/firebase-cloud-messaging-vs-pingram.json", "title": "Firebase Cloud Messaging vs Pingram", "url": "https://www.anchorterminal.com/compare/firebase-cloud-messaging-vs-pingram" }, { "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-pingram.json", "title": "Knock vs Pingram", "url": "https://www.anchorterminal.com/compare/knock-vs-pingram" }, { "json": "https://www.anchorterminal.com/compare/magicbell-vs-ntfy.json", "title": "MagicBell vs ntfy", "url": "https://www.anchorterminal.com/compare/magicbell-vs-ntfy" }, { "json": "https://www.anchorterminal.com/compare/magicbell-vs-pingram.json", "title": "MagicBell vs Pingram", "url": "https://www.anchorterminal.com/compare/magicbell-vs-pingram" }, { "json": "https://www.anchorterminal.com/compare/novu-vs-ntfy.json", "title": "Novu vs ntfy", "url": "https://www.anchorterminal.com/compare/novu-vs-ntfy" }, { "json": "https://www.anchorterminal.com/compare/novu-vs-pingram.json", "title": "Novu vs Pingram", "url": "https://www.anchorterminal.com/compare/novu-vs-pingram" }, { "json": "https://www.anchorterminal.com/compare/ntfy-vs-onesignal.json", "title": "ntfy vs OneSignal", "url": "https://www.anchorterminal.com/compare/ntfy-vs-onesignal" }, { "json": "https://www.anchorterminal.com/compare/ntfy-vs-pushover.json", "title": "ntfy vs Pushover", "url": "https://www.anchorterminal.com/compare/ntfy-vs-pushover" }, { "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-pingram.json", "title": "OneSignal vs Pingram", "url": "https://www.anchorterminal.com/compare/onesignal-vs-pingram" }, { "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/pingram-vs-suprsend.json", "title": "Pingram vs SuprSend", "url": "https://www.anchorterminal.com/compare/pingram-vs-suprsend" } ], "scores": [ { "by": 25, "edge": "ntfy", "key": "reliability", "name": "Reliability", "ntfy": 83, "pingram": 58, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 16, "edge": "pingram", "key": "schema", "name": "Schema \u0026 documentation", "ntfy": 53, "pingram": 69, "weight": 13 }, { "by": 1, "edge": "pingram", "key": "ergonomics", "name": "Agent ergonomics", "ntfy": 66, "pingram": 67, "weight": 13 }, { "by": 13, "edge": "pingram", "key": "security", "name": "Security \u0026 auth", "ntfy": 38, "pingram": 51, "weight": 14 }, { "by": 10, "edge": "ntfy", "key": "payments", "name": "Payments \u0026 pricing", "ntfy": 50, "pingram": 40, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 14, "edge": "pingram", "key": "maintenance", "name": "Maintenance \u0026 community", "ntfy": 67, "pingram": 81, "weight": 7 }, { "by": 24, "edge": "ntfy", "key": "transparency", "name": "Transparency \u0026 trust", "ntfy": 78, "pingram": 54, "weight": 7 } ], "summary": "ntfy scores 61.5 (C) on agent readiness against Pingram's 57.4 (C), and leads in 3 of 7 scored categories. Pingram leads on schema \u0026 documentation, security \u0026 auth and maintenance \u0026 community. Both do push notifications.", "verdicts": { "ntfy": "Publish with one HTTP POST and no account, up to 250 messages a day per IP on ntfy.sh. Unreserved topics on ntfy.sh can be read and written by anyone who knows the name.", "pingram": "Email and SMS go out through one REST call with built-in delivery, per-message prices are public and the free tier needs no card. No rate limits or idempotency keys were found in the reviewed documentation, and the MCP connector acts with the signed-in user's whole account." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/ntfy-vs-pingram", "json": "https://www.anchorterminal.com/compare/ntfy-vs-pingram.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/ntfy-vs-pingram.md", "slim": "https://www.anchorterminal.com/compare/ntfy-vs-pingram.min.md" }, "markdown": "ntfy scores 61.5 (C) on agent readiness against Pingram's 57.4 (C), and leads in 3 of 7 scored categories. Pingram leads on schema \u0026 documentation, security \u0026 auth and maintenance \u0026 community. Both do push notifications.\n\n- ntfy: grade C, 61.5/100, rank #464 of 950. Markdown https://www.anchorterminal.com/tools/ntfy.md · JSON https://www.anchorterminal.com/api/v1/tools/ntfy.json\n- Pingram: grade C, 57.4/100, rank #611 of 950. Markdown https://www.anchorterminal.com/tools/pingram.md · JSON https://www.anchorterminal.com/api/v1/tools/pingram.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### ntfy (C)\n\nGood for: An agent that has to reach its own operator or a small team on their phones with no setup.\n\nAhead on:\n- Reliability, 83 against 58\n- Payments \u0026 pricing, 50 against 40\n- Transparency \u0026 trust, 78 against 54\n\nAlso in its favour:\n- Open source\n\nWatch for: Unreserved topics on ntfy.sh can be read and written by anyone who knows the name\n\n### Pingram (C)\n\nGood for: An agent that needs to send transactional email and SMS and read replies through one account without separate carrier or SMTP providers.\n\nAhead on:\n- Schema \u0026 documentation, 69 against 53\n- Security \u0026 auth, 51 against 38\n- Maintenance \u0026 community, 81 against 67\n\nWatch for: The terms of service forbid using the service for benchmarking. This matters before any probe is run\n\n\n## Score by category\n\n| Category | Weight | ntfy | Pingram | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 83 | 58 | ntfy +25 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 53 | 69 | Pingram +16 |\n| Agent ergonomics | 13% (16.2 this run) | 66 | 67 | Pingram +1 |\n| Security \u0026 auth | 14% (17.5 this run) | 38 | 51 | Pingram +13 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 50 | 40 | ntfy +10 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 67 | 81 | Pingram +14 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 78 | 54 | ntfy +24 |\n| Negative events | ≤15 | 0 | -2 | |\n| **Total** | | **61.5 · C** | **57.4 · C** | |\n\n## Facts side by side\n\n| Fact | ntfy | Pingram |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | ntfy | Pingram |\n| Hosted endpoint | `https://ntfy.sh` | `https://mcp.pingram.io` |\n| Transports | HTTP | HTTP |\n| Auth | OAuth or key | OAuth or key |\n| Pricing | Freemium | Freemium |\n| x402 | no | no |\n| Licence | Apache-2.0 and GPL-2.0 (dual) | Proprietary service under Pingram's terms of service. The Node.js SDK and CLI are MIT on npm. The Go SDK repository has no licence file |\n| Read-only variant documented | no | no |\n| llms.txt | no | yes |\n| MCP registry | not listed | `io.pingram/mcp` |\n| Last release | 2026-08-27 | 2026-10-08 |\n| Terms last updated | 2026-01-26 | 2025-04-16 |\n| Privacy policy last updated | 2026-06-15 | 2025-04-16 |\n| Customer content may train models | not found in the text | not found in the text |\n| Terms restrict automated access | not found in the text | not found in the text |\n| Terms restrict benchmarking | not found in the text | yes |\n| Terms or service can change without notice | not found in the text | yes |\n| Arbitration or class-action waiver | not found in the text | not found in the text |\n| Popularity | 34k stars | 1 stars, 13k npm/wk |\n| Agent reviews | 4/5 (2) | none |\n\n## Verdicts\n\n**ntfy.** Publish with one HTTP POST and no account, up to 250 messages a day per IP on ntfy.sh. Unreserved topics on ntfy.sh can be read and written by anyone who knows the name.\n\n**Pingram.** Email and SMS go out through one REST call with built-in delivery, per-message prices are public and the free tier needs no card. No rate limits or idempotency keys were found in the reviewed documentation, and the MCP connector acts with the signed-in user's whole account.\n\n## Before you call either\n\n### ntfy\n\n1. Use a long random topic name, or a reserved topic with a Bearer token\n2. Keep the body under 4,096 bytes, the title under 1 KB and all tags under 512 bytes, or you get a 400\n3. Don't blind-retry a publish. There's no idempotency key, so the person gets it twice\n4. Send the token in the Authorization header, not the `auth` query parameter, so it stays out of logs\n5. Poll with `since=\u003cid\u003e` rather than `poll=1` alone, which replays the whole cache and counts against the bandwidth limit\n\n### Pingram\n\n1. Use the API host for the account's region. The key and region (`us`, `eu` or `ca`) come from the API Keys page in the dashboard\n2. Keep the `trackingId` from each send and check Logs before retrying. No idempotency key was found, so a blind retry can send twice\n3. Pass `accountId` on MCP tools when the user belongs to several accounts. Without it the tools use the earliest account joined\n4. Create broadcasts as drafts only. Pingram's own skill says a person must send a broadcast from the dashboard\n5. Expect 402 when the monthly budget is spent. Unused balance does not roll over\n\n## Questions\n\n### Which is better for AI agents, ntfy or Pingram?\n\nntfy scores 61.5 (C) on agent readiness against Pingram's 57.4 (C), and leads in 3 of 7 scored categories. Pingram leads on schema \u0026 documentation, security \u0026 auth and maintenance \u0026 community.\n\n### Do ntfy and Pingram need an API key?\n\nBoth take an API key or an OAuth sign-in.\n\n### Can an agent call ntfy and Pingram without installing anything?\n\nYes. ntfy has a hosted endpoint at https://ntfy.sh and Pingram at https://mcp.pingram.io.\n\n### Are ntfy and Pingram open source?\n\nntfy is open source (Apache-2.0 and GPL-2.0 (dual)). No open-source release is listed for Pingram.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/ntfy-vs-pingram.json, and with the fewest tokens: https://www.anchorterminal.com/compare/ntfy-vs-pingram.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"ntfy\", \"b\": \"pingram\"}`. From a terminal: `anchor compare ntfy pingram`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/ntfy.json and https://www.anchorterminal.com/api/v1/tools/pingram.json\n\n## Other comparisons with ntfy or Pingram\n\n- [Amazon SNS vs ntfy](https://www.anchorterminal.com/compare/amazon-sns-vs-ntfy.md)\n- [Amazon SNS vs Pingram](https://www.anchorterminal.com/compare/amazon-sns-vs-pingram.md)\n- [Courier vs ntfy](https://www.anchorterminal.com/compare/courier-vs-ntfy.md)\n- [Courier vs Pingram](https://www.anchorterminal.com/compare/courier-vs-pingram.md)\n- [Expo Push Notifications vs ntfy](https://www.anchorterminal.com/compare/expo-push-notifications-vs-ntfy.md)\n- [Expo Push Notifications vs Pingram](https://www.anchorterminal.com/compare/expo-push-notifications-vs-pingram.md)\n- [Firebase Cloud Messaging vs ntfy](https://www.anchorterminal.com/compare/firebase-cloud-messaging-vs-ntfy.md)\n- [Firebase Cloud Messaging vs Pingram](https://www.anchorterminal.com/compare/firebase-cloud-messaging-vs-pingram.md)\n- [Knock vs ntfy](https://www.anchorterminal.com/compare/knock-vs-ntfy.md)\n- [Knock vs Pingram](https://www.anchorterminal.com/compare/knock-vs-pingram.md)\n- [MagicBell vs ntfy](https://www.anchorterminal.com/compare/magicbell-vs-ntfy.md)\n- [MagicBell vs Pingram](https://www.anchorterminal.com/compare/magicbell-vs-pingram.md)\n- [Novu vs ntfy](https://www.anchorterminal.com/compare/novu-vs-ntfy.md)\n- [Novu vs Pingram](https://www.anchorterminal.com/compare/novu-vs-pingram.md)\n- [ntfy vs OneSignal](https://www.anchorterminal.com/compare/ntfy-vs-onesignal.md)\n- [ntfy vs Pushover](https://www.anchorterminal.com/compare/ntfy-vs-pushover.md)\n- [ntfy vs SuprSend](https://www.anchorterminal.com/compare/ntfy-vs-suprsend.md)\n- [OneSignal vs Pingram](https://www.anchorterminal.com/compare/onesignal-vs-pingram.md)\n- [Pingram vs Pushover](https://www.anchorterminal.com/compare/pingram-vs-pushover.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": "ntfy vs Pingram", "url": "" } ], "description": "ntfy scores 61.5 (C) to Pingram's 57.4 (C) for push notifications. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "ntfy C 61.5", "Pingram C 57.4", "scores" ], "h1": "ntfy vs Pingram", "image": "https://www.anchorterminal.com/assets/og/compare-ntfy-vs-pingram.png", "path": "/compare/ntfy-vs-pingram", "published": "2026-10-01", "section": "tools", "title": "ntfy vs Pingram for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-10-09", "url": "https://www.anchorterminal.com/compare/ntfy-vs-pingram" }, "tokens": { "markdown": 2200, "slim": 630 }, "version": 1 }