# Courier — API Agent Score

> Score: 86/100 (Grade: A) | Domain: courier.com | Rubric: 1.0.0 | Checked: July 24, 2026

Courier scored 86/100 (A), classified "ai-ready".

[View full report](https://www.postman.com/ai/ai-ready-apis/company/courier)
[All organizations](https://www.postman.com/ai/ai-ready-apis/llms.txt)

## Summary

- Overall: 86/100 (A)
- Classification: ai-ready

## Category Scores

- API Design: 89/100 (A)
- Developer Experience: 85/100 (A)
- Agent Discovery: 91/100 (A+)
- Agent Understanding: 91/100 (A+)
- Agent Usability: 74/100 (B)

## Check Results

### API Design

- [pass] Auth declared & discoverable — Authentication required (global or on every operation). Investigated: spec 100%, docs 100%.
- [warn] Schema coverage & depth — 379/380 (100%) public params are fully typed (no any/**kwargs). Analyzer reports not all methods have a derivable input schema. Investigated: sdk 100%, spec 67%.
- [pass] Security & governance hygiene — No credential-shaped strings detected in spec. Investigated: spec 100%, wellknown 0%.
- [warn] Machine-readable, versioned contract — No info.version and no versioning scheme detected. Investigated: spec 50%, docs 0%.
- [pass] Example coverage — 56% example coverage (target 80%+). Investigated: spec 100%, sdk 100%, docs 0%.

### Developer Experience

- [pass] Self-service developer portal — Signup page at https://app.courier.com/signup; no free-tier language detected in docs/pricing. Investigated: docs 100%.
- [pass] Quickstart present — Quickstart at https://www.courier.com/docs/getting-started/quickstart with a runnable first-call sample. Investigated: docs 100%.
- [pass] Description completeness — 88% description completeness (target 90%+). Investigated: spec 100%, sdk 100%.
- [pass] Changelog published — changelog documented in the docs site at https://www.courier.com/changelog. Investigated: spec 100%, docs 100%, sdk 100%.
- [fail] Code samples in docs — No detectable code samples across 19 sampled docs pages. Investigated: docs 0%.

### Agent Discovery

- [pass] Docs reachable, not hard auth-gated — All 1 pages are publicly accessible. Investigated: docs 100%.
- [pass] Registry & SDK presence — Indexed on Context7 (gojek/courier-android, 157 snippets). Investigated: docs 100%, sdk 100%, cli 100%.
- [warn] llms.txt present, valid & comprehensive — No /llms-full.txt found at the candidate origins. Investigated: docs 75%, sdk 0%.
- [warn] Crawlable / AEO — Sitemap lastmod coverage 30% or newest entry older than 90 days. Investigated: wellknown 75%.

### Agent Understanding

- [pass] Machine-readable errors (RFC 9457) — 8 distinct 4xx/5xx response codes documented. Investigated: docs 100%, sdk 100%, spec 50%.
- [pass] Operation purpose clarity — 100% of operations have a clear summary + operationId an agent can select on. Investigated: spec 100%.
- [pass] Agent-navigable, token-efficient docs — All 1 pages contain server-rendered content. Investigated: docs 100%.
- [pass] Docs structured data — JSON-LD Article markup on 16/16 assessed pages (100%) with dateModified present. Investigated: docs 100%.
- [fail] Agent instructions file (AGENTS.md) — No AGENTS.md at the site root or /.well-known/. Investigated: wellknown 0%.
- [skip] Description consistency across surfaces — Only 1 surface description(s) with ≥6 tokens available; need at least 2 to compare.

### Agent Usability

- [pass] Idempotency documented — Built-in retry machinery is present (grep-derived). Investigated: sdk 100%, spec 0%, docs 0%.
- [pass] Pagination documented & consistent — Pagination params detected on 25 list endpoint(s). Investigated: spec 100%, docs 100%.
- [pass] Sandbox separation — Sandbox environments are exposed (sandbox). Investigated: sdk 100%, spec 0%, docs 0%.
- [fail] Rate-limit signaling — No rate-limit response headers documented. Investigated: spec 0%, docs 0%.
- [fail] Runnable collection with test scripts — No public Postman workspace discovered for the org. Investigated: platform 0%.

## Executive Summary

Courier's API program is strong across design, discovery, and developer experience — partners can find and evaluate your APIs with relatively little friction. The two areas that need immediate attention are agent readiness and runnable trust: there is no machine-readable instruction file to tell AI agents how to work with your API, and there are no executable, test-backed collections to give partners and their coding agents a verified, runnable starting point. Closing these two gaps will meaningfully accelerate partner integrations and ensure AI-assisted workflows produce correct results without manual intervention.