◎ Discry Score
postman.com
devtools · API
C
0 / 100
DISCOVERY0
COMPREHENSION0
Category leader: 96 (A)
Discry your API →
DEVTOOLS · RANK #27 OF 39

Postman is Needs Work to agents.

Discry independently scored how well an AI agent can discover and understand the Postman API from what’s public — not whether it’s usable. Below: every signal we checked, what’s costing the score, and what to change.

Discry your API — freeView the docs ↗

SCORED UNDER RUBRIC 1.2 · A full re-launch under Discry Score 2.5 — a new behavioral instrument, not comparable to these scores — is in progress.

Discovery

45% of score · 40/100
OpenAPI specA machine-readable OpenAPI/Swagger spec agents can parse.Partial
llms.txtAn llms.txt index that points agents to the docs that matter.Fail
llms.txt qualityThe llms.txt is focused, current, and well under the size budget.Fail
llms-full.txtA full-text bundle agents can load in one request.Fail
AGENTS.mdAn AGENTS.md that tells coding agents how to build on the API.Fail
.well-known/mcp.jsonA discoverable MCP manifest at a well-known path.Fail
MCP registryThe API is listed in a public MCP registry.Pass
robots.txt AI directivesrobots.txt allows (or explicitly guides) AI crawlers.Pass
SitemapA sitemap so agents can enumerate the docs surface.Pass

Comprehension

55% of score · 85/100
Task-oriented descriptionsEndpoints described by what they accomplish, not just their shape.Pass
Realistic examplesRunnable, real-world request/response examples.Pass
Multi-step workflowsDocs that chain calls into complete jobs an agent can follow.Pass
Error-recovery guidanceDocumented failure modes and how to recover from them.Partial
Answer-first formatThe answer leads; preamble does not bury it.Pass
Capability boundariesClear limits — what the API can and cannot do.Pass
Naming consistencyConsistent, predictable naming across endpoints.Pass
Heading hierarchyClean heading structure agents can navigate.Pass
Markdown docsDocs available as clean markdown, not JS-rendered HTML only.Partial
Token efficiencyDocs are concise enough to fit an agent context window.Partial

What we found

  • Postman has an official MCP server on PulseMCP supporting the latest Streamable HTTP protocol — fitting for a developer tools leader
  • Despite being the leading API platform, Postman lacks its own llms.txt for developer documentation discovery
  • The Postman API itself has OpenAPI support but the spec is only accessible through the Postman platform, not via a standalone public URL
  • Documentation is comprehensive with task-oriented descriptions, realistic examples, and strong workflow guides
  • robots.txt is clean with no AI bot restrictions and explicit sitemap reference

What to change

Prioritized by impact on discoverability. You (or your docs platform) deploy these — Discry never touches your API.

  1. 01Add llms.txt to learning.postman.com covering API documentation and platform capabilities
  2. 02Host the Postman API OpenAPI spec at a public URL outside the Postman platform
  3. 03Add llms-full.txt with comprehensive documentation in markdown format
  4. 04Add AGENTS.md to postmanlabs GitHub org with context for coding agents
  5. 05Add .well-known/mcp.json pointing to the official Postman MCP server

Execution coverage · INFORMATIONAL, UNSCORED

Whether an agent can actually complete a call and recover from errors is the deeper Audit layer — documented here, but not part of the Discry Score.

API key✓ Error format documented✓ Rate limits documented✓ Pagination documented✕ Idempotency documented

Postman API uses API keys for auth. JSON error responses documented. Rate limits documented with specific quotas. Cursor-based pagination.

See your own Discry Score.

Drop your API docs URL. See what an agent sees — in 60 seconds, free.

Discry your API — free