Get an audit

Head to head · Push notifications · October 2026 research run

Expo Push Notifications vs Pingram

Expo Push Notifications scores 58.8 (C) on agent readiness against Pingram's 57.4 (C), and leads in 2 of 7 scored categories. Pingram leads on schema & documentation and maintenance & community. Both do push notifications.

Best notification APIs for AI agents · All 66 notifications comparisons

Expo Push NotificationsExpo · HTTP API C58.8/100#571 of 950 PingramPingram · HTTP API C57.4/100#611 of 950

Which one, for what

Expo Push Notifications C

Good for An agent that must push to an app already built with Expo, at no cost and with one call for both platforms.

Ahead on

  • Reliability, 65 against 58
  • Transparency & trust, 68 against 54

Watch 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

Pingram C

Good for An agent that needs to send transactional email and SMS and read replies through one account without separate carrier or SMTP providers.

Ahead on

  • Schema & documentation, 69 against 60
  • Maintenance & community, 81 against 74

Watch for

The terms of service forbid using the service for benchmarking. This matters before any probe is run

Score by category

CategoryWeight this runExpo Push NotificationsPingramEdge
Reliability16%206558Expo Push Notifications +7
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.26069Pingram +9
Agent ergonomics13%16.26367Pingram +4
Security & auth14%17.54851Pingram +3
Payments & pricing10%12.54040even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.87481Pingram +7
Transparency & trust7%8.86854Expo Push Notifications +14
Negative events≤150-2
Total58.8 · C57.4 · C

Facts side by side

FactExpo Push NotificationsPingram
KindHTTP APIHTTP API
VendorExpoPingram
Hosted endpointhttps://exp.host/--/api/v2/push/sendhttps://mcp.pingram.io
TransportsHTTPHTTP
AuthOAuth or keyOAuth or key
PricingFreeFreemium
x402nono
LicenceProprietary service under Expo's terms of service. The Node.js server SDK is MITProprietary 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
Read-only variant documentednono
llms.txtyesyes
MCP registrynot listedio.pingram/mcp
Last release2026-08-242026-10-08
Terms last updated2025-05-292025-04-16
Privacy policy last updated2025-10-212025-04-16
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessyesnot found in the text
Terms restrict benchmarkingnot found in the textyes
Terms or service can change without noticeyesyes
Arbitration or class-action waiveryesnot found in the text
Popularity1k stars, 1.3M npm/wk1 stars, 13k npm/wk

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.

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.

Before you call either

Expo Push Notifications

  1. Send an array of up to 100 messages per request, all for one project, and stay under 600 notifications a second
  2. Keep each ticket id and POST them to /--/api/v2/push/getReceipts about 15 minutes later. Receipts are cleared after 24 hours
  3. Stop sending to a token when a ticket or receipt returns DeviceNotRegistered
  4. If the project has enhanced push security on, send Authorization: Bearer <access token> or the call fails with UNAUTHORIZED
  5. Retry 429 and 5xx with exponential backoff, and expect an occasional duplicate because there is no idempotency key

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

Questions

Which is better for AI agents, Expo Push Notifications or Pingram?

Expo Push Notifications scores 58.8 (C) on agent readiness against Pingram's 57.4 (C), and leads in 2 of 7 scored categories. Pingram leads on schema & documentation and maintenance & community.

Do Expo Push Notifications and Pingram need an API key?

Both take an API key or an OAuth sign-in.

Can an agent call Expo Push Notifications and Pingram without installing anything?

Yes. Expo Push Notifications has a hosted endpoint at https://exp.host/--/api/v2/push/send and Pingram at https://mcp.pingram.io.

Other comparisons with Expo Push Notifications or Pingram

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.

Get an auditSee a sample report