# Amazon Seller Central — API Agent Score

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

Amazon Seller Central scored 70/100 (B), classified "partially-ready".

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

## Summary

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

## Category Scores

- API Design: 76/100 (B)
- Developer Experience: 75/100 (B)
- Agent Discovery: 77/100 (B)
- 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 0%.
- [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://sellercentral.amazon.com/ap/signin?openid.pape.preferred_auth_policies=Policy15&openid.pape.max_auth_age=300&openid.return_to=https%3A%2F%2Fsellercentral.amazon.com%2Fget-started&openid.identity=http%3A%2F%2Fspecs.openid.net%2Fauth%2F2.0%2Fidentifier_select&openid.assoc_handle=sc_na_amazon_v2&openid.mode=checkid_setup&intercept=false&language=zh_CN&openid.claimed_id=http%3A%2F%2Fspecs.openid.net%2Fauth%2F2.0%2Fidentifier_select&pageId=sc_amazon_v3_unified&openid.ns=http%3A%2F%2Fspecs.openid.net%2Fauth%2F2.0&ssoResponse=eyJ6aXAiOiJERUYiLCJlbmMiOiJBMjU2R0NNIiwiYWxnIjoiQTI1NktXIn0.SGPeNK8Og14a-p5OVAYN-d-v8tjvT17abBw7uWfzdny626Xk9XVcGQ.v1FP82JD_E-ycqRM.eL97kHDIlxaV71cFZhAgRJQ2qC_FPBFfnNLJAZdbBnALSN1AFDhfZ01aOkGw-1BXJAKG3plSrqwh0fqTF6QZojFVbSYyC9fls95-eMsaqg9BX2odx1ZumS674DFdAawzBMT8FQoBpoGlo1x0GdQE53PkQCjgdh3umXvEjWm-MRqb4FTuf5hkOyN8cpI8WmVGaV_sRbKe.Gxc_UjtA_TaYCelXpqqt0g; 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 1 sampled docs pages. Investigated: docs 0%.

### Agent Discovery

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

### 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 49 pages exceed 100K chars (max 337K). Investigated: docs 75%.
- [warn] Docs structured data — OpenGraph/meta tags only across 1 assessed pages — no JSON-LD for answer engines to cite. Investigated: docs 50%.
- [warn] Description consistency across surfaces — Mean pairwise description similarity across 2 surfaces (spec, docs) is 7% (threshold 35% for full credit).
- [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%.

### 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

Sellercentral's API program shows relative strength in documentation discoverability and schema design, but partners and their AI agents face two critical gaps: the API surface lacks the concrete examples and operation-level context agents need to integrate without guessing, and there is no runnable, executable layer to get partners to a first successful call quickly. Closing these gaps — by enriching the contract with realistic examples and clear operation semantics, publishing an agent instructions file, and providing a runnable collection with test scripts — will materially shorten partner onboarding and make the API reliably usable by both humans and AI agents.