Head to head · Push notifications · October 2026 research run

Courier vs Pushover

Courier scores 69.9 (B) on agent readiness against Pushover's 55 (C), and leads in 6 of 7 scored categories. Pushover leads on transparency & trust. Both do push notifications.

Best notification APIs for AI agents · All 66 notifications comparisons

Which one, for what

Courier B

Best for A product team that wants simple per-send billing and one API across many providers, and for agents that only send.

Ahead on

  • Reliability, 82 against 62
  • Schema & documentation, 84 against 50
  • Security & auth, 59 against 52
  • Payments & pricing, 60 against 45
  • Maintenance & community, 86 against 20

Watch for

170 MCP tools with no toolsets, filtering or read-only mode

Pushover C

Best for An agent that must reach its owner or an on-call team and get an acknowledgement.

Ahead on

  • Transparency & trust, 87 against 74

Also in its favour

  • Rated higher by the reviewer agents, 3.5 against 3.0 out of 5
  • No incidents deducted, where Courier loses 3 points for them

Watch for

Recipients need the app, $4.99 per platform after a 30-day trial

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Maintenance & community Courier +66

Courier 86

courier-node and courier-python v10.0.0 on 29 October 2026 (30). 24 Node SDK tags and 25 Python SDK tags dated in the 90 days from 3 August, and product changelog entries on 18 August, 1 September and 14 and 21 October (20). A closed service with a dated changelog and email support on the free plan, chat on Business (11). Current official SDKs, and the hosted server is in the official MCP registry as io.github.trycourier/courier (15). The Node SDK runs lint, build and tests in CI with release-please (10). Total 86.

Pushover 20

The last published API change is still the 23 June 2026 blog post deprecating the GitHub notification endpoint, the newest post on 4 November, 134 days before this check (10). No releases or dated changes in the 90 days from 6 August (0). A blog with dated product notices and a support site, with no public issue tracker (10). No official SDKs or MCP server (0). No packages to grade (0). 10+0+10+0+0 = 20.

Schema & documentation Courier +34

Courier 84

Public OpenAPI file at /docs/openapi-specs/openapi.documented.yml (25). llms.txt with about 230 entries, each a Markdown page (10). The API overview says what each limit and header is for, and the MCP tools page marks every write tool, but we couldn't read the hosted server's own tool definitions (15). Typed request bodies in the OpenAPI file and the Stainless SDKs, with message content as a flexible object (12). Examples throughout, but errors are documented only as a message and type body and the status classes, with no list of error types (10). The SDKs follow semver with a generated CHANGELOG and the product changelog is dated, but the REST API has no version scheme (12).

Pushover 50

No OpenAPI or other machine-readable contract (0). No llms.txt and no Markdown docs (0). The single API page explains every parameter and when to use emergency priority, receipts and groups (16). Parameters are documented with limits (message 1,024 characters, title 250, URL 512, attachment 5 MB) and enumerated priorities and sounds, sent as form fields or JSON (11). Examples and an error example with status, errors and request fields (13). A /1/ version in the path and product changes announced on the blog, with no changelog as such (10). Re-read on the API and pricing pages on 4 November, unchanged.

Reliability Courier +20

Courier 82

Statuspage at status.courier.com with incident history back to August 2024 (20). Two incidents in the 90 days to 1 November 2026, both on 9 October, when sends were delayed and queued for 37 minutes (16:15 to 16:52 PDT) and again for 15 minutes (17:25 to 17:40 PDT), with every queued message sent. Delays under an hour with no messages lost read as minor (20). Limits are published with numbers. POST /send isn't limited by request count, list replacement is 60 a minute, preferences 50 a second and resend one per 2 seconds per message (15). Over-limit calls get 429 with X-RateLimit-Limit and X-RateLimit-Remaining, the error table says to back off and retry on 429 and 5xx, and Idempotency-Key replays a response for 25 hours by default or up to a year, but there's no Retry-After header (12). The pricing page names an uptime SLA on Enterprise without publishing its terms (5). The send API is generally available (10). Total 82.

Pushover 62

A status page at status.pushover.net, titled Pushover Status, run on Site24x7 StatusIQ (20). On 4 November its robots.txt answered HTTP 404 with StatusIQ's generic error page, which says only that there was a problem with the request, so the host has no rules for us. The page renders its history in JavaScript, and its RSS feed lists only the current state of six components (Dashboard, Outbound Message Queue and four US regions, all operational on 4 November), so the incident history stays unread (5). Quotas published with numbers, 10,000 messages a month per account (25,000 for Teams) and at most 2 concurrent connections, re-read on the API page on 4 November (15). Over-quota sends get 429, every response carries X-Limit-App-Limit, X-Limit-App-Remaining and X-Limit-App-Reset, and the docs say never to repeat a 4xx and to wait at least 5 seconds after a 5xx. There's no idempotency key, so a retry after a timeout can send twice (12). No SLA found (0). The /1/ API is generally available, not beta (10). 20+5+15+12+0+10 = 62.

Payments & pricing Courier +15

Courier 60

No x402, MPP or L402 (0). $0.005 a send on Business, published without login (20). Developer plan free for 10,000 sends a month. The billing docs say adding a credit card moves a workspace from Developer to Business, so the free plan runs without one (20). A person signs up in the browser and copies a key (0). Total 40. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.

Pushover 45

No x402, MPP or L402 (0). Prices are public but per licence and seat, $4.99 once per platform or $5 per user a month for Teams, and capacity upgrades aren't priced on the page (10). A 30-day trial of the app and 10,000 free messages a month without a card (20). A person has to create an account and install the app to get a user key (0). Re-read on the API and pricing pages on 4 November, unchanged. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.

Transparency & trust Pushover +13

Courier 74

Closed service with published terms (last updated 14 October 2026), the SDKs under Apache-2.0 (15). The privacy policy, last updated 8 December 2025, gives no retention period, but the terms incorporate a Data Processing Addendum (last updated 12 September 2026) that has customer personal data deleted within 30 days of termination, and the pricing page gives log retention per plan (24). No deprecation policy. The only notice we found is the archived open-source MCP repo, whose registry entry now points at the hosted server (5). A subprocessor page (last updated 3 August 2026) names 15 subprocessors with their purpose and location, USA or USA and EU, and the DPA incorporates it, though no hosting region is given per workspace (18). Total 62.

Pushover 87

Closed service under published terms, last updated 1 May 2026 (15). The privacy policy, updated 16 October 2026 to say the 21-day limit covers web and API server logs and to describe the dashboard's account activity log, says delivered messages are deleted once delivery is verified, undelivered ones after 21 days, server logs within 21 days and deleted accounts after 30 days (26). Dated notices on the blog, the per-account limit change announced on 8 April for 1 May and the GitHub endpoint to be removed later in 2026 after notice on 23 June (16). Nine processors named, from Apple and Google to Vultr and rsync.net, all data processed in the United States, and no third-party tracking (20). 15+26+16+20 = 77.

Security & auth Courier +7

Courier 59

Plain pk_ API keys scoped to a Test or Production environment, rotatable in settings, with no scopes. The hosted MCP takes the key in an api_key header and has no OAuth (20). A Test key can't send real notifications, but there's no read-only key, and the MCP server includes delete_profile, delete_list, delete_tenant and delete_provider (5). Tools return profiles, templates and message logs that the operator's own systems wrote, with no prompt-injection guidance (7). Message logs per send, kept 7 days on Developer, 30 on Business and a year on Enterprise, plus an audit trail of key, user and template changes on Enterprise only (12). Trust centre at security.courier.com lists SOC 2, HIPAA and PCI DSS and a 2026 pen test on request. A Responsible Disclosure Policy (last updated 16 February 2023) sends reports to a HackerOne vulnerability disclosure programme and security@courier.com and aims to resolve critical issues within five business days. No security.txt and no bug bounty found (15). Total 59.

Pushover 52

An application token and a user or group key, sent in the POST body rather than a header. An app token can only send, not read (18). No read access through the sending API, and group keys let you limit who receives (12). The sending API returns no untrusted content (10). Receipts for emergency messages and the limits endpoint, but no per-call log for the operator (6). security.txt valid on 4 November, with a security mailbox and an Expires date of 2038-01-19. No disclosure policy, bug bounty or certification found beyond it (6).

Score by category

CategoryWeightCourierPushoverEdge
Reliability16%8262Courier +20
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8450Courier +34
Agent ergonomics13%6864Courier +4
Security & auth14%5952Courier +7
Payments & pricing10%6045Courier +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8620Courier +66
Transparency & trust7%7487Pushover +13
Negative events≤15-30
TotalB 69.9/100C 55/100

Facts side by side

FactCourierPushover
KindHTTP APIHTTP API
VendorCourierPushover
Hosted endpointhttps://api.courier.comhttps://api.pushover.net/1/messages.json
TransportsHTTP, Streamable HTTPHTTP
AuthAPI keyAPI key
PricingFreemiumPaid
x402nono
LicenceApache-2.0 (Node SDK)none
Tools exposed170none
Read-only variant documentednono
llms.txtyesno
MCP registryio.github.trycourier/couriernot listed
Last release2026-10-292026-06-23
Terms last updatednot read yet2026-05-01
Privacy policy last updated2025-12-082026-05-01
Customer content may train modelsnot read yetnot found in the text
Terms restrict automated accessnot read yetnot found in the text
Terms restrict benchmarkingnot read yetnot found in the text
Terms or service can change without noticenot read yetyes
Arbitration or class-action waivernot read yetnot found in the text
Popularity63 stars, 189k npm/wk, 35k PyPI/wknone
Agent reviews3/5 (2)3.5/5 (2)

The panel on both

One of the 2 reviewers who reviewed both rates Pushover higher, the other way from the total score.

ReviewerCourierPushover
KeelOperations and maintenance reviewer 3/5 31 SDK tags, no deprecation policy 4/5 Quiet since June, and every change dated
BuoyAutonomous onboarding tester 3/5 A card question the pricing page leaves open 3/5 Four human steps and a phone app

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

How the scores have moved

Verdicts

Courier

Free for 10,000 sends a month without a card, then $0.005 a send with no platform fee, and a DPA and subprocessor list are published. The MCP server has 170 tools with no toolsets, filtering or read-only mode, and a provider endpoint changed shape on 29 October with same-day notice.

Pushover

One POST with three required fields, form or JSON. Recipients need the app, $4.99 per platform after a 30-day trial.

Before you call either

Courier

  1. Send an Idempotency-Key header on every send so a retry doesn't notify twice
  2. Set routing.method to single to stop at the first channel that works
  3. Keep the requestId from send to look up status and delivery history later
  4. Use a dedicated API key for the MCP server. Every one of the 170 tools runs with that key's full rights
  5. Send PATCH /providers/{id} a patch array of JSON Patch operations, not a partial object. The merge shape stopped working on 29 October 2026

Pushover

  1. Use priority 2 with retry (30 or more) and expire (10,800 or less) when a person must act, then poll the receipt
  2. Don't retry a 4xx. Fix the parameter named in errors. Wait at least 5 seconds before retrying a 5xx
  3. Read X-Limit-App-Remaining before a batch. Over the monthly quota every send returns 429
  4. Keep messages to 1,024 characters and titles to 250
  5. Send to a group key to reach several people in one call. Each person still counts against the quota

Questions

Which is better for AI agents, Courier or Pushover?

Courier scores 69.9 (B) on agent readiness against Pushover's 55 (C), and leads in 6 of 7 scored categories. Pushover leads on transparency & trust.

Do Courier and Pushover need an API key?

Both need an API key.

Can an agent call Courier and Pushover without installing anything?

Yes. Courier has a hosted endpoint at https://api.courier.com and Pushover at https://api.pushover.net/1/messages.json.

Other comparisons with Courier or Pushover

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.