# USPS — API Agent Score

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

USPS scored 72/100 (B), classified "partially-ready".

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

## Summary

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

## Category Scores

- API Design: 91/100 (A+)
- Developer Experience: 75/100 (B)
- Agent Discovery: 57/100 (D)
- Agent Understanding: 76/100 (B)
- Agent Usability: 65/100 (C)

## Check Results

### API Design

- [warn] Machine-readable, versioned contract — info.version="3.2.9" set but no versioning scheme (URL / header / media type) detected. Investigated: spec 97%, docs 94%.
- [warn] Auth declared & discoverable — Authentication applied on 2/3 operations (partial coverage). Investigated: spec 91%, docs 81%, wellknown 0%.
- [warn] Schema coverage & depth — Only 67% of operations have documented schemas. Investigated: spec 73%, sdk 25%.
- [pass] Security & governance hygiene — No credential-shaped strings detected in spec. Investigated: spec 100%, wellknown 0%.
- [pass] Example coverage — README is present and includes a runnable quickstart. Investigated: sdk 100%, spec 13%, docs 0%.

### Developer Experience

- [pass] Self-service developer portal — Signup page at https://www.usps.com/signup/ (CSR-rendered — body classifier inconclusive); free tier / sandbox documented in pricing/docs. Investigated: docs 100%.
- [pass] Description completeness — 83% description completeness (target 90%+). Investigated: spec 100%, sdk 0%.
- [pass] Changelog published — Newest official SDK activity 8 day(s) ago. Investigated: sdk 100%, spec 0%, docs 0%.
- [warn] Quickstart present — Quickstart page reachable (1 variants scanned starting at https://developers.usps.com/getting-started) but no runnable code sample detected in HTML or .md variant. Investigated: docs 50%.
- [fail] Code samples in docs — No detectable code samples across 1 sampled docs pages. Investigated: docs 0%.

### Agent Discovery

- [warn] Docs reachable, not hard auth-gated — Server ignores Accept: text/markdown header (0/1 pages return markdown). Investigated: docs 75%.
- [warn] Registry & SDK presence — No MCP server, tool manifest, or list-tools capability is discoverable (server entrypoint: absent, tool manifest: unknown, list-tools: unknown). Investigated: sdk 50%, docs 0%, cli 0%.
- [warn] Crawlable / AEO — No sitemap discoverable via robots.txt or /sitemap.xml on the docs host. Investigated: wellknown 50%.
- [fail] llms.txt present, valid & comprehensive — No llms.txt found at any candidate location (https://developers.usps.com/llms.txt, https://developers.usps.com/docs/llms.txt). Investigated: docs 0%, sdk 0%.

### Agent Understanding

- [pass] Machine-readable errors (RFC 9457) — 5 distinct 4xx/5xx response codes documented. Investigated: docs 100%, spec 50%, sdk 0%.
- [pass] Operation purpose clarity — 100% of operations have a clear summary + operationId an agent can select on. Investigated: spec 100%.
- [warn] Agent-navigable, token-efficient docs — No pages support .md URLs (0/1 tested). Investigated: docs 79%.
- [warn] Description consistency across surfaces — Mean pairwise description similarity across 2 surfaces (spec, docs) is 3% (threshold 35% for full credit).
- [fail] Agent instructions file (AGENTS.md) — No AGENTS.md at the site root or /.well-known/. Investigated: wellknown 0%.
- [fail] Docs structured data — Neither JSON-LD nor OpenGraph/meta tags detected across 1 assessed pages (1 JS-rendered). Investigated: docs 0%.

### Agent Usability

- [pass] Pagination documented & consistent — Pagination params detected on 2 list endpoint(s). Investigated: spec 100%, docs 100%.
- [pass] Sandbox separation — Sandbox server declared but no distinguishable test credentials in scheme descriptions. Investigated: spec 100%, docs 100%, sdk 50%.
- [warn] Rate-limit signaling — Only 1 rate-limit header(s) documented. Investigated: spec 50%, docs 50%.
- [warn] Idempotency documented — 0% of mutating operations document idempotency. Investigated: spec 8%, docs 8%, sdk 0%.
- [fail] Runnable collection with test scripts — No public Postman workspace discovered for the org. Investigated: platform 0%.

## Executive Summary

USPS's API design is a clear strength — the contract is well-structured and machine-readable, giving partners a solid foundation to build against. However, Agent Discovery is the most critical gap: without an llms.txt file, structured docs metadata, or an agent-readable front door, partners and their AI agents cannot find or navigate the API without a manual conversation. Compounding this, partners lack runnable collections with test scripts and inline code samples, slowing hands-on validation and increasing integration risk. Prioritize making the API discoverable and executable for agents first, then close the remaining context and onboarding gaps.