# EasyPost — API Agent Score

> Score: 77/100 (Grade: B) | Domain: easypost.com | Rubric: 1.0.0 | Checked: July 24, 2026

EasyPost scored 77/100 (B), classified "partially-ready".

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

## Summary

- Overall: 77/100 (B)
- Classification: partially-ready

## Category Scores

- API Design: 68/100 (C)
- Developer Experience: 79/100 (B)
- Agent Discovery: 79/100 (B)
- Agent Understanding: 72/100 (B)
- Agent Usability: 90/100 (A+)

## Check Results

### API Design

- [warn] Schema coverage & depth — 2 of 14 public signatures use loose types (anyTypeRatio=0.143). Investigated: sdk 82%.
- [pass] Example coverage — Code samples present on 19/20 pages across 1 language(s); broader multi-language coverage missing. Investigated: docs 100%, sdk 100%.
- [fail] Security & governance hygiene — No security.txt at /.well-known/security.txt or /security.txt. Investigated: wellknown 0%.
- [skip] Machine-readable, versioned contract — No surface produced evidence for this capability in this run.
- [skip] Auth declared & discoverable — No surface produced evidence for this capability in this run.

### Developer Experience

- [pass] Self-service developer portal — Self-service signup at https://app.easypost.com/signup; no free tier or sandbox language detected. Investigated: docs 100%.
- [pass] Code samples in docs — Code samples present on 19/20 pages across 1 language(s); broader multi-language coverage missing. Investigated: docs 100%.
- [pass] Description completeness — 7/7 operations carry a description. Investigated: sdk 100%.
- [pass] Changelog published — Newest official SDK activity 3 day(s) ago. Investigated: sdk 100%.
- [fail] Quickstart present — No quickstart/getting-started page found at the conventional paths. Investigated: docs 0%.

### Agent Discovery

- [pass] Registry & SDK presence — Indexed on Context7 (websites/easypost, 3001 snippets). Investigated: docs 100%, sdk 92%, cli 0%, mcp 0%, wellknown 0%.
- [warn] Docs reachable, not hard auth-gated — Server ignores Accept: text/markdown header (0/50 sampled pages return markdown). Investigated: docs 75%.
- [warn] llms.txt present, valid & comprehensive — llms.txt exists but contains no parseable links. Investigated: docs 40%, sdk 0%.
- [pass] Crawlable / AEO — Docs paths crawlable by all monitored AI agents. Investigated: wellknown 100%.

### Agent Understanding

- [pass] Machine-readable errors (RFC 9457) — Single base error "EasyPostError" with 26 subclasses. Investigated: sdk 100%.
- [warn] Agent-navigable, token-efficient docs — 1 of 50 sampled pages appear to be client-side rendered SPA shells (__next detected); agents using HTTP fetches will see no content. Investigated: docs 56%.
- [warn] Docs structured data — OpenGraph/meta tags only across 20 assessed pages — no JSON-LD for answer engines to cite. Investigated: docs 50%.
- [fail] Agent instructions file (AGENTS.md) — No AGENTS.md at the site root or /.well-known/. Investigated: wellknown 0%.
- [skip] Operation purpose clarity — No surface produced evidence for this capability in this run.
- [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%.
- [pass] Pagination documented & consistent — An SDK-wide auto-paginator is present. (grep-derived). Investigated: sdk 100%.
- [pass] Sandbox separation — Sandbox environments are exposed (sandbox). Investigated: sdk 100%.
- [fail] Runnable collection with test scripts — No public Postman workspace discovered for the org. Investigated: platform 0%.
- [skip] Rate-limit signaling — No surface produced evidence for this capability in this run.

## Executive Summary

EasyPost's API program shows strong fundamentals in discoverability and documentation structure, but two areas put partner momentum at risk: security governance gaps in the API contract undermine partner confidence and enterprise procurement, while missing agent-facing context (an AGENTS.md file and runnable test collections) means AI coding agents cannot reliably integrate without guessing. Closing the security hygiene gap and adding machine-readable agent context should be the immediate priorities, followed by tightening the quickstart experience so partners reach a first successful call in minutes.