$HEADLESS SYSTEMS
03 / Scorecard / Communications

Courier

B
Headless Index
65/100
JAIRF
N/A
Verified
MAY 21, 2026
Methodology v1 · JAIRF v1.0.0

Powered by JAIRF v1.0.0 by Jentic · open methodology at /the-headless-index/methodology

Editorial verdict
Courier is solidly built for programmatic consumption. The Headless Index thesis-fit score of 65/100 lands it in the upper-middle of the index, and JAIRF is recorded as N/A for this vendor because no public OpenAPI specification was reachable for the open-source scorer. In practice, vendors at this tier ship most of the primitives agents need, with one or two surfaces still leaning on documentation rather than discovery, and the rest of this verdict explains where Courier lands inside that pattern. On the API surface, the question is whether the API is the product or a layer beneath the dashboard. Courier is multi-channel notification API with REST plus SDKs in Node, Python, Ruby, PHP, Java, Go, and .NET. The product abstracts SMS, email, push, chat, and in-app notification delivery through a unified API and a workflow designer.[1] Schema observability is the related test: can an agent introspect the contract from cold, or does it have to read prose documentation to do so? REST documented at courier.com/docs. SDKs are well-maintained. Schema discoverability is good.[2] An agent can drive this product across most practical workflows, with a handful of edges where documentation reading still beats schema discovery. On headless operability: Notifications, audiences, brand configuration, automations, and provider configuration are all programmable. The Courier Studio is the visual workflow authoring surface; the API does everything Studio does.[3] On the MCP and agent-integration axis, which is the fastest-moving criterion in the index: No first-party Courier MCP server. The product is multi-channel notifications; agent integration is community-led.[4] Event posture closes the loop: an agent that cannot react to state changes is reduced to polling. Courier webhooks deliver notification events with signing. Catalog covers the multi-channel notification use case. Net assessment: Courier can be operated by agents for the majority of practical workflows. The closest thing to a gap is webhooks and events[5], which integrators should sanity-check against their own use case before committing. Strong fit for agent-driven use cases.
Verdict by Headless Index pipeline (auto)
// AI-drafted from the evidence layer. Editorial review pending.
Scores

Scorecard detail

Headless Index · 5 sub-criteria
API-first design intent15/20
scored

Courier is multi-channel notification API with REST plus SDKs in Node, Python, Ruby, PHP, Java, Go, and .NET. The product abstracts SMS, email, push, chat, and in-app notification delivery through a unified API and a workflow designer.

signals (6)
  • +AI review appliedReviewer: Editorial review on 2026-05-20
  • OpenAPI specNot found across 17 probe paths
  • ·GraphQL endpointDiscovered at https://www.courier.com/graphql, introspection disabled or scoped
  • +SDKs maintained3 (java, javascript, kotlin); top by stars: trycourier/courier-java (8 stars)
  • +SDK recency1 of 3 SDK repos pushed within 30 days (most recent SDK commit: 2026-05-19)
  • +npm weekly downloads110.3k across published packages; top: @trycourier/courier-js @ 110.3k/week
cite (5)
  • openapi.probes_tried@2026-05-19
  • graphql.url@2026-05-19
  • github.sdks@2026-05-19
  • freshness.most_recent_sdk_commit@2026-05-19
  • github.sdks@2026-05-19
Headless operation12/20
scored

Notifications, audiences, brand configuration, automations, and provider configuration are all programmable. The Courier Studio is the visual workflow authoring surface; the API does everything Studio does.

signals (9)
  • +AI review appliedReviewer: Editorial review on 2026-05-20
  • API operations exposedNo OpenAPI spec; operations count unknown
  • ·Docs pages crawled0 pages (crawler: none)
  • ·Auth schemes documentedAuth documentation page not reached by crawler
  • ·Setup / quickstart docsNot reached by crawler
  • ·Billing docsNot reached by crawler
  • ·Teams / org docsNot reached by crawler
  • ·CLI docsNot reached by crawler
  • ·Schema / data model docsNot reached by crawler
cite (1)
  • ai_review_browser.topics_found@2026-05-20
MCP & agent posture20/20
scored

No first-party Courier MCP server. The product is multi-channel notifications; agent integration is community-led.

signals (4)
  • +AI review appliedReviewer: Editorial review on 2026-05-20
  • +Official MCP serverhttps://github.com/trycourier/courier-mcp (1 stars, last commit 12 days ago)
  • Community MCP serversNone found
  • +Agent-friendly SDKs1 TS/JS SDKs available; top: @trycourier/courier-js (110.3k/week downloads)
cite (1)
  • ai_review_browser.mcp@2026-05-20
Schema observability14/20
scored

REST documented at courier.com/docs. SDKs are well-maintained. Schema discoverability is good.

signals (3)
  • +AI review appliedReviewer: Editorial review on 2026-05-20
  • OpenAPINot discovered across 17 standard probe paths
  • ·GraphQL introspectionGraphQL endpoint at https://www.courier.com/graphql but introspection is disabled, scoped, or behind authentication
cite (1)
  • ai_review_browser.schema@2026-05-20
Webhooks & events4/20
scored

Courier webhooks deliver notification events with signing. Catalog covers the multi-channel notification use case.

signals (2)
  • +AI review appliedReviewer: Editorial review on 2026-05-20
  • ·Webhook docs pageNot reached by crawler within budget (0 pages crawled). Cannot confirm whether vendor offers webhooks.
cite (1)
  • ai_review_browser.pages_fetched@2026-05-20
JAIRF · 6 dimensions
JAIRF · N/A

This vendor does not publish a public OpenAPI specification. JAIRF cannot be computed. The Headless Index score and editorial verdict carry the readiness assessment.

No public OpenAPI specification discovered during collection

Powered by JAIRF v1.0.0 by Jentic

Band rationale:B band: JAIRF=N/A HeadlessIndex=65

04 / Embed

Show Courier's score on your site.

Drop a live badge into your README, footer, or marketing page. It updates automatically when we re-score, and every embed is a dofollow link back here.

Calibration

How THI compares to external scorers

SourceScoreMeasuresLast checked
Fern Agent Scorenot foundDocumentation completeness and SDK shape (~22 checks)
CLIRank Agent Friendliness0CLI readiness, docs quality, and overall agent affordances
Cloudflare Is It Agent Ready?blockedCloudflare's manual agent-readiness heuristic per vendor URL
Jentic Scorecardn aJAIRF-based scorecard requiring a public OpenAPI specification
THI 65 vs external median 0, delta +65Methodology delta noted — see verdict

THI display 65 vs external median 0 (delta +65). Deviation > 25 points: editor should review whether THI methodology is over-strict or external scorers are over-generous for this vendor.