# Postman — API Agent Score

> Score: 83/100 (Grade: A) | Domain: postman.com | Rubric: 1.0.0 | Checked: July 31, 2026

Postman scored 83/100 (A), classified "ai-ready".

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

## Summary

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

## Category Scores

- API Design: 79/100 (B)
- Developer Experience: 78/100 (B)
- Agent Discovery: 100/100 (A+)
- Agent Understanding: 73/100 (B)
- Agent Usability: 83/100 (A)

## Check Results

### API Design

- [warn] Machine-readable, versioned contract — info.version="1.0.0" set but no versioning scheme (URL / header / media type) detected. Investigated: spec 83%, cli 75%, docs 65%.
- [warn] Schema coverage & depth — 262 of 1190 public signatures use loose types (anyTypeRatio=0.220). Investigated: sdk 70%, spec 48%.
- [pass] Security & governance hygiene — No credential-shaped strings detected in spec. Investigated: spec 100%, wellknown 100%.
- [warn] Auth declared & discoverable — No securitySchemes declared. Investigated: docs 50%, cli 50%, spec 25%, wellknown 0%.
- [pass] Example coverage — 100% example coverage across params + responses. Investigated: spec 100%, docs 100%, sdk 100%, cli 100%.

### Developer Experience

- [pass] Self-service developer portal — Self-service signup at https://www.postman.com/signup; no free tier or sandbox language detected. Investigated: docs 100%.
- [pass] Code samples in docs — Code samples present on 4/20 pages across 2 language(s); broader multi-language coverage missing. Investigated: docs 100%.
- [warn] Description completeness — 406/424 operations carry a description. Investigated: sdk 96%, spec 10%.
- [warn] Quickstart present — Quickstart page reachable (2 variants scanned starting at https://learning.postman.com/docs/getting-started/overview/) but no runnable code sample detected in HTML or .md variant. Investigated: docs 50%.
- [fail] Changelog published — No changelog URL or mention found in spec metadata. Investigated: spec 0%, docs 0%.

### Agent Discovery

- [pass] llms.txt present, valid & comprehensive — llms-full.txt reachable at https://learning.postman.com/api-docs/api-reference/llms-full.txt. Investigated: docs 100%, sdk 0%.
- [pass] Registry & SDK presence — Indexed on Context7 (websites/learning_postman, 9228 snippets). Investigated: docs 100%, cli 100%, mcp 100%, sdk 83%, wellknown 0%.
- [pass] Crawlable / AEO — Docs paths crawlable by all monitored AI agents. Investigated: wellknown 100%.
- [skip] Docs reachable, not hard auth-gated — No surface produced evidence for this capability in this run.

### Agent Understanding

- [pass] Machine-readable errors (RFC 9457) — No 4xx/5xx response codes (or default error response) documented anywhere in the spec. Investigated: docs 100%, sdk 100%, spec 58%, cli 0%.
- [warn] Operation purpose clarity — 71% of operations are agent-inferable (target 90%+). Investigated: spec 95%.
- [warn] Description consistency across surfaces — Mean pairwise description similarity across 3 surfaces (spec, docs, sdk) is 5% (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 3 assessed pages (3 JS-rendered). Investigated: docs 0%.
- [skip] Agent-navigable, token-efficient docs — No surface produced evidence for this capability in this run.

### Agent Usability

- [pass] Idempotency documented — Built-in retry machinery is present (grep-derived). Investigated: sdk 100%, cli 25%, spec 0%, docs 0%.
- [warn] Pagination documented & consistent — 21/23 list method(s) return an auto-paginating iterable. Investigated: sdk 91%, spec 50%, docs 50%.
- [pass] Sandbox separation — Sandbox environments are exposed (sandbox). Investigated: sdk 100%, spec 0%, docs 0%.
- [warn] Rate-limit signaling — No rate-limit response headers documented. Investigated: spec 40%, docs 40%.
- [warn] Runnable collection with test scripts — No test scripts found in the workspace's collections. Investigated: platform 50%.

## Executive Summary

Postman's API program shows genuine strengths in agent usability and API design, but two areas demand immediate attention: partners and their AI agents cannot track what has changed between versions (no published changelog), and agents lack the structured context files they need to parse and act on the API surface without guesswork. Closing these gaps — a public changelog and machine-readable agent context files — will meaningfully accelerate partner integration, reduce support burden, and make the program viable for the AI-native toolchains partners increasingly rely on.