# Developer Docs — API Agent Score

> Score: 71/100 (Grade: B) | Domain: developer-docs.amazon | Rubric: 1.0.0 | Checked: July 29, 2026

Developer Docs scored 71/100 (B), classified "partially-ready".

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

## Summary

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

## Category Scores

- API Design: 76/100 (B)
- Developer Experience: 75/100 (B)
- Agent Discovery: 84/100 (A)
- Agent Understanding: 61/100 (C)
- Agent Usability: 64/100 (C)

## Check Results

### API Design

- [pass] Auth declared & discoverable — authentication documented in the docs site at https://developer-docs.amazon/sp-api/docs/automate-your-sp-api-calls-using-the-c-sdk. Investigated: docs 100%, spec 50%.
- [warn] Machine-readable, versioned contract — info.version="v0" set but no versioning scheme (URL / header / media type) detected. Investigated: spec 75%, docs 50%.
- [pass] Security & governance hygiene — No credential-shaped strings detected in spec. Investigated: spec 100%, wellknown 50%.
- [warn] Schema coverage & depth — Only 25% of operations have documented schemas. Investigated: spec 50%.
- [fail] Example coverage — 8% example coverage. Investigated: spec 0%, docs 0%.

### Developer Experience

- [pass] Self-service developer portal — Self-service signup at https://developer-docs.amazon/sp-api/page/404; free tier / sandbox documented. Investigated: docs 100%.
- [pass] Description completeness — 100% of operations + parameters have substantive descriptions. Investigated: spec 100%.
- [pass] Changelog published — changelog documented in the docs site at https://developer-docs.amazon/sp-api/changelog. Investigated: spec 100%, docs 100%, sdk 100%.
- [warn] Quickstart present — Quickstart page reachable (24 variants scanned starting at https://developer-docs.amazon/sp-api/page/404) but no runnable code sample detected in HTML or .md variant. Investigated: docs 50%.
- [fail] Code samples in docs — No detectable code samples across 20 sampled docs pages. Investigated: docs 0%.

### Agent Discovery

- [pass] Registry & SDK presence — Indexed on Context7 (worldcoin/developer-docs, 1059 snippets). Investigated: docs 100%, sdk 0%, cli 0%.
- [warn] llms.txt present, valid & comprehensive — llms.txt is 313,507 characters (exceeds 100,000 threshold; will be truncated by most agents). Investigated: docs 88%.
- [warn] Docs reachable, not hard auth-gated — 50 of 50 sampled pages return 200 for non-existent URLs (soft 404). Investigated: docs 50%.
- [pass] Crawlable / AEO — Docs paths crawlable by all monitored AI agents. Investigated: wellknown 100%.

### Agent Understanding

- [pass] Machine-readable errors (RFC 9457) — 9 distinct 4xx/5xx response codes documented. Investigated: docs 100%, spec 50%.
- [warn] Agent-navigable, token-efficient docs — 2 of 50 pages exceed 100K chars (max 147K). Investigated: docs 80%.
- [fail] Operation purpose clarity — 0% of operations are agent-inferable. Investigated: spec 0%.
- [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 20 sampled pages — likely a CSR-only docs site. Investigated: docs 0%.
- [skip] Description consistency across surfaces — Only 1 surface description(s) with ≥6 tokens available; need at least 2 to compare.

### Agent Usability

- [pass] Rate-limit signaling — rate-limit behavior documented in the docs site at https://developer-docs.amazon/sp-api/docs/performance-management. Investigated: spec 100%, docs 100%.
- [pass] Sandbox separation — sandbox documented in the docs site at https://developer-docs.amazon/sp-api/docs/onboarding-step-4-register-your-first-sandbox-application. Investigated: spec 100%, docs 100%.
- [fail] Idempotency documented — 0% of mutating operations document idempotency. Investigated: spec 0%, docs 0%.
- [fail] Runnable collection with test scripts — No public Postman workspace discovered for the org. Investigated: platform 0%.
- [skip] Pagination documented & consistent — No surface produced evidence for this capability in this run.

## Executive Summary

Agent discoverability is a clear strength, with documentation reachability and discovery already well-handled. However, the program has two significant gaps that put partner integration velocity and AI-agent compatibility at risk: the API design lacks the concrete examples agents and developers need to build confidently, and the understanding layer — operation semantics, structured data, and agent context files — is largely absent, meaning AI agents cannot reliably parse, interpret, or act on your APIs without manual intervention. Prioritize enriching your contract with examples and agent-ready context first, then move to making those APIs runnable and operationally trustworthy for partner workflows.