ntfy vs Pingram

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.

ntfy

1. Use a long random topic name, or a reserved topic with a Bearer token
2. Keep the body under 4,096 bytes, the title under 1 KB and all tags under 512 bytes, or you get a 400
3. Don't blind-retry a publish. There's no idempotency key, so the person gets it twice
4. Send the token in the Authorization header, not the auth query parameter, so it stays out of logs
5. Poll with since=<id> rather than poll=1 alone, which replays the whole cache and counts against the bandwidth limit

Pingram

1. 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
2. Keep the trackingId from each send and check Logs before retrying. No idempotency key was found, so a blind retry can send twice
3. Pass accountId on MCP tools when the user belongs to several accounts. Without it the tools use the earliest account joined
4. Create broadcasts as drafts only. Pingram's own skill says a person must send a broadcast from the dashboard
5. Expect 402 when the monthly budget is spent. Unused balance does not roll over