Courier

PASS consensus from 2 PASS, 1 PARTIAL.

The quickstart links the Test key, gives a complete POST /send request, and directs users to Test Logs. The quickstart gives a clean three-step path from Test key to a verified delivery timeline, but the docs state two different success status codes for POST /send, so an agent cannot write a correct success check. The quickstart walks from zero to a delivered message in three steps with a working code example for every major SDK.

PARTIAL consensus from 1 PASS, 2 PARTIAL.

The rate table is specific, but the old send-limits Markdown URL failed and current pages disagree on 1 MB versus 6 MB payload caps. Request-count limits and the 6 MB payload cap are stated exactly and consistently, but the per-user, topic, and tenant send limits are only described as a concept with no documented values, defaults, or configuration location. The rate-limit table and payload limits are identical on both the statuses and API overview pages.

PARTIAL consensus from 1 PASS, 2 PARTIAL.

The docs identify the cause and generic action but give no Retry-After or reset header for a complete retry decision. The docs name the cause, the affected endpoints with exact limits, the X-RateLimit-Limit and X-RateLimit-Remaining headers, and Idempotency-Key for safe retries, but no Retry-After or reset header and no backoff parameters, so an agent cannot compute how long to wait. The docs name the cause, the retry signal (429 + rate_limit_error), and the recovery path. The SDK retries 429s up to 2 times with exponential backoff.

PASS consensus from 3 PASS.

The outbound guide covers dashboard setup and secret storage, while the security page provides matching raw-body HMAC verification code. The outbound guide covers creation and the whsec_ secret and hands off to the security page, which gives the header format, the <t>.<raw_body> signed payload, runnable Node verification code, and explicit warnings to hash the raw body and compare in constant time. The outbound webhooks guide links to the security page, which documents the full HMAC-SHA256 verification including splitting the courier-signature header, constant-time comparison, and requiring the raw body.

PASS consensus from 3 PASS.

The SDK quick start uses client.send.message({ message: ... }), matching the API reference's JavaScript request shape. The Node SDK page and the Send a message reference use the same constructor option apiKey, the same message wrapper around to and template, and the same response.requestId field, so the SDK example matches the API form. The SDK's client.send.message() parameter shape is the same message object that POST /send accepts in the API reference.