← Leaderboard
7.4 L3

Courier

Ready Assessed · Docs reviewed ยท Mar 21, 2026 Confidence 0.54 Last evaluated Mar 21, 2026

Score breakdown

Dimension Score Bar
Execution Score

Measures reliability, idempotency, error ergonomics, latency distribution, and schema stability.

7.6
Access Readiness Score

Measures how easily an agent can onboard, authenticate, and start using this service autonomously.

7.0
Aggregate AN Score

Composite score: 70% execution + 30% access readiness.

7.4

Autonomy breakdown

P1 Payment Autonomy
โ€”
G1 Governance Readiness
โ€”
W1 Web Agent Accessibility
โ€”
Overall Autonomy
Pending

Active failure modes

No active failure modes reported.

Reviews

Published review summaries with trust provenance attached to each card.

How are reviews sourced?

Docs-backed Built from public docs and product materials.

Test-backed Backed by guided testing or evaluator-run checks.

Runtime-verified Verified from authenticated runtime evidence.

Courier: Comprehensive Agent-Usability Assessment

Docs-backed

Courier is a multi-channel notification infrastructure platform providing a single REST API for sending notifications across email, push, SMS, Slack, in-app, and other channels. Rather than integrating with each notification channel separately, agents call Courier's send API with the notification content and recipient, and Courier routes to the appropriate channel based on user preferences and channel availability. This routing abstraction is particularly valuable for agents that need to reach users across their preferred channel without managing per-channel integration logic.

Rhumb editorial team Mar 21, 2026

Courier: Auth & Access Control

Docs-backed

Authentication uses API keys for the REST API. Courier separates production and test environment keys. The key model is straightforward for server-side agent integration. Teams should monitor key usage and implement appropriate secrets management given that Courier keys authorize notification delivery to real users.

Rhumb editorial team Mar 21, 2026

Courier: API Design & Integration Surface

Docs-backed

The API covers notification sends, templates, routing rules, user preferences, and delivery tracking. The send API accepts a recipient ID, template reference, and data โ€” Courier handles channel selection, template rendering, and delivery. Agents can also subscribe users to channels, retrieve delivery status, and manage notification preferences through the API. The routing engine supports fallback logic (try email, fall back to SMS if undelivered).

Rhumb editorial team Mar 21, 2026

Courier: Error Handling & Operational Reliability

Docs-backed

Reliability is production-grade for a notification platform. Courier maintains the delivery infrastructure and handles provider fallback when individual notification providers experience issues. Delivery analytics enables agents to monitor notification delivery rates and detect systematic delivery failures.

Rhumb editorial team Mar 21, 2026

Courier: Documentation & Developer Experience

Docs-backed

Documentation is thorough and covers the send API, template system, and routing configuration clearly. The multi-channel routing documentation explains how to configure recipient channel preferences and fallback rules. Teams evaluating Courier versus Knock for multi-channel notification infrastructure should compare the routing rule expressiveness and template design capabilities.

Rhumb editorial team Mar 21, 2026

Use in your agent

mcp
get_score ("courier")
● Courier 7.4 L3 Ready
exec: 7.6 · access: 7.0

Trust & provenance

This score is documentation-derived. Treat it as a docs-based evaluation of API design, auth, error handling, and documentation quality.

Read how the score works, how disputes are handled, and how Rhumb scored itself before launch.

Overall tier

L3 Ready

7.4 / 10.0

Alternatives

No alternatives captured yet.