# Postman docs: AI Agent Readiness Score 75.0% (C)

**75.0% · 60/80 · AI Agent Readiness Score · 20/30 reading points · 40/50 agent surface points**

Postman received 5 PASS votes and passed 4 of five agent surface checks. The clearest finding came from the find the exact limits task.

- Tested: 2026-09-22
- Published: 2026-09-22
- Battery: v1
- Scoring: reading 30 pts · surface 50 pts
- Docs: https://learning.postman.com/docs/getting-started/overview/

Three AI models, GPT 5.6 Sol, Claude Opus 5, and DeepSeek v4 Flash, each read Postman’s public documentation independently and attempted five first-hour developer jobs: make the first API call, find the exact limits, recover from a 429, trigger a collection by webhook, page through a list.

No accounts, API calls, or code execution were used. Every verdict came from public pages and every published quotation passed a live verification check. Preflight substitutions: T4: Postman's webhook triggers a collection run rather than delivering an event, so confirming the triggered run replaces receiving and verifying a signed payload. T5: List pagination on the Postman API replaces the SDK task because Postman publishes no official client library for the Postman API.

## Freshness

[How rechecks work](https://docsforagents.com/methodology/#freshness)

- Category: [Cloud & developer platforms](https://docsforagents.com/grades/?category=cloud-platforms)
- Tested: 2026-09-22
- Quotes verified: 2026-09-22
- Surface rechecked: Not yet rechecked

## Agent surface checks · 40/50

| Check | Verdict | Points |
| --- | --- | --- |
| llms.txt | PASS | 10 |
| llms-full.txt | FAIL | 0 |
| Markdown mirror | PASS | 10 |
| MCP server | PASS | 10 |
| Docs AI | PASS | 10 |

## The Reading Test · 20/30

| Task | GPT 5.6 Sol | Opus 5 | DeepSeek v4F | Consensus |
| --- | --- | --- | --- | --- |
| Make the first API call | PARTIAL | PARTIAL | PASS | PARTIAL |
| Find the exact limits | PARTIAL | PARTIAL | PARTIAL | PARTIAL |
| Recover from a 429 | PARTIAL | PARTIAL | PASS | PARTIAL |
| Trigger a collection by webhook | PARTIAL | PASS | PARTIAL | PARTIAL |
| Page through a list | PARTIAL | PASS | PASS | PASS |

Docs platform: Fern (unscored) · verified 2026-09-22

## What to fix first

These 5 fixes could add up to 19 points to the AI Agent Readiness Score. The list ranks each fix by the points it would add. [How the ranking works](https://docsforagents.com/methodology/#what-to-fix-first)

1. **+10 points · llms-full.txt · check failed**

   **Found:** HTTP 301 redirecting to llms.txt, so no separate full-text file exists.

   **Fix:** Publish llms-full.txt at the docs root with the full text of every docs page in one plain-text file.

   **Evidence:** [learning.postman.com/llms-full.txt](https://learning.postman.com/llms-full.txt)

2. **+3 points · Find the exact limits · PARTIAL**

   **Found:** The per-endpoint limits sit only in the API reference overview, the dedicated rate limits page omits them, and no page states a monthly call allowance per plan.

   **Fix:** List every per-endpoint limit on the rate limits page, state the monthly call allowance for each plan, and say whether the limit counts per user or per IP.

   **Evidence:** [learning.postman.com/docs/reference/postman-api/postman-api-rate-limits](https://learning.postman.com/docs/reference/postman-api/postman-api-rate-limits/)

3. **+2 points · Make the first API call · PARTIAL**

   **Found:** The first-call tutorial is GUI-only and tells the reader to store the key in Postman Vault, then to select the environment where the key is stored.

   **Fix:** Pick one place to store the key in the first-call tutorial, and add a plain HTTP request example that sends the X-API-Key header.

   **Evidence:** [learning.postman.com/docs/reference/postman-api/make-postman-api-call](https://learning.postman.com/docs/reference/postman-api/make-postman-api-call/)

4. **+2 points · Recover from a 429 · PARTIAL**

   **Found:** The API reference names the Retry-After header, the dedicated rate limits page calls it RetryAfter, and the 429 help article gives no retry procedure.

   **Fix:** Spell the header Retry-After on the rate limits page as well, and add the wait-and-retry steps to the 429 help article.

   **Evidence:** [learning.postman.com/api-docs/api-reference](https://learning.postman.com/api-docs/api-reference)

5. **+2 points · Trigger a collection by webhook · PARTIAL**

   **Found:** The create-webhook page treats the workspace parameter as both required and omittable, and the collection webhooks page leaves run confirmation to the monitors API.

   **Fix:** Say once whether the workspace parameter is required, and show the GET /monitors/{id} lastRun check on the collection webhooks page.

   **Evidence:** [learning.postman.com/docs/tests-and-scripts/running-collections/collection-webhooks](https://learning.postman.com/docs/tests-and-scripts/running-collections/collection-webhooks/)

## What the docs get right

- **Page through a list: 2 PASS votes.** limit and offset are both defined, the sample response carries a meta object of total, offset and limit that supplies the loop termination condition, and the incompatibility between name and limit/offset is stated explicitly.
- **Make the first API call: 1 PASS votes.** The tutorial reaches /me, but it tells the reader to store the key in Vault and later select an environment.
- **4 of 5 agent surface checks.** Present: llms.txt, markdown mirrors, an MCP server, docs AI. Missing: llms-full.txt.

## Make the first API call

**PARTIAL**

PARTIAL consensus from 1 PASS, 2 PARTIAL.

The tutorial reaches /me, but it tells the reader to store the key in Vault and later select an environment. Key generation and the X-API-Key header are unambiguous, but the official first-call tutorial is GUI-only (fork a collection, click Send) and contradicts itself by telling you to store the key in Postman Vault and then to select the environment where you stored your API key. The docs provide a clear step-by-step path: generate an API key in account settings, then authenticate with the X-API-Key header.

## Find the exact limits

**PARTIAL**

PARTIAL consensus from 3 PARTIAL.

The values require overview, pricing, and endpoint pages, and the per-user scope conflicts with support's public-IP explanation. The per-endpoint limits appear only in the API reference overview and are absent from the dedicated rate limits page, and no page states the numeric monthly call allowance for any plan, deferring instead to an external pricing page. The base rate (300/min) and some per-endpoint limits are documented, but the per-plan monthly usage limits are not given as specific values, they redirect to the external pricing page.

## Recover from a 429

**PARTIAL**

PARTIAL consensus from 1 PASS, 2 PARTIAL.

The overview gives the wait-and-retry action, but the limits page names RetryAfter while the overview names Retry-After. A complete correction is reachable only from the API reference, because the dedicated rate limits page names the same header RetryAfter rather than Retry-After and the help article for a 429 offers diagnosis with no retry procedure. The docs explain both the rateLimited and serviceLimitExhausted error bodies, and document the X-RateLimit-RetryAfter and Retry-After headers with their semantics.

## Trigger a collection by webhook

**PARTIAL**

PARTIAL consensus from 1 PASS, 2 PARTIAL.

The linked pages cover creation, payload access, and run confirmation, but workspace is both required and omittable. The full loop is documented end to end: POST /webhooks with a cURL example, the returned webhookUrl, the JSON-only payload rule, reading the payload through pm.globals.get('previousRequest') and JSON.parse(), and confirming the run through the monitor run details. Creating the webhook and sending a custom payload is fully documented, but confirming the triggered collection run programmatically requires cross-referencing the monitors API docs for GET /monitors/{id} and lastRun.

## Page through a list

**PASS**

PASS consensus from 2 PASS, 1 PARTIAL.

The endpoint defines limit, offset, and response metadata, but gives no default, maximum, or next-page procedure. limit and offset are both defined, the sample response carries a meta object of total, offset and limit that supplies the loop termination condition, and the incompatibility between name and limit/offset is stated explicitly. The pagination parameters (limit and offset) and the meta response object (total, offset, limit) are fully documented with a complete example showing paginated results.

## The receipt

> This endpoint has a rate limit of 300 calls every 3 hours. This does not accrue Postbot usage.

The values require overview, pricing, and endpoint pages, and the per-user scope conflicts with support's public-IP explanation.

- [learning.postman.com/api-docs/api-reference/postbot/generate-tool](https://learning.postman.com/api-docs/api-reference/postbot/generate-tool)

## Agent surface notes

Initialize returned JSON-RPC protocol 2025-06-18 and serverInfo name fern-docs-mcp-server.

Clicking the docs Ask AI control opened a chat panel with an "Ask AI a question..." input.

## Method note

This is a reading test of public documentation, not an execution test. No accounts were created and no API calls were run. The AI Agent Readiness Score counts fifteen reading votes at PASS 2, PARTIAL 1, and FAIL 0, for 30 possible points. Five agent surface checks add 10 points each. The total is 80. Consensus chips show each row majority and do not affect scoring. The panel split on 4 of five tasks. Quotes shown here were re-fetched and confirmed verbatim on 2026-09-22.

Methodology: https://docsforagents.com/methodology/

Canonical URL: https://docsforagents.com/reports/postman-docs-ai-agent-readiness/