daysTime to key
NoNo-human path
6Human gates
4/10Onboarding score
CAPTCHAEmail verificationKYC / business checkMandatory 2FAManual reviewPhone OTP
Fastest path to a key
- Phone OTPHave an Amazon.com account (email + phone OTP; 2FA mandatory for Seller Central).
- Card before first callGather business registration number, government ID/passport, recent bank or credit-card statement.
- Sign in to Solution Provider Portal -> Register -> enroll -> 'Build applications that use SP APIs'.
- KYC / business checkVerify identity: business info, PIN via SMS/call + CAPTCHA, upload documents, live VIDEO call with an Amazon associate.
- Manual reviewCreate developer profile (use case, roles; restricted roles need security/data-protection docs) -> review.
- Manual reviewRegister a Sandbox app client (allowed while profile is under review) -> get LWA client id/secret -> first sandbox call.
- Manual reviewProduction: self-authorize a private app (refresh token) after profile approval; public apps need full security review + Appstore listing.
- Talk to salesSeller shortcut (no dev registration): add Claude connector https://sellingpartner-ai.amazon.com/mcp -> OAuth via sellercentral.amazon.com/apps/agents/authorize (requires an existing seller account).
- Working API key
Biggest gap
Video-call identity verification for developers; consumer side closed to third-party agents (robots + litigation) while Amazon pushes its own agents.
Worth copying
Doc pages advertise their llms.txt indexes in front-matter (agentTools), and the remote seller MCP lets an existing seller skip developer registration entirely.
Sources (12) · checked 2026-10-11
- https://developer-docs.amazon.com/sp-api/llms.txt
- https://developer-docs.amazon.com/sp-api/docs/onboarding-step-1-prepare-for-registration.md
- https://developer-docs.amazon.com/sp-api/docs/onboarding-step-2-create-an-spp-account.md
- https://developer-docs.amazon.com/sp-api/docs/onboarding-step-4-register-your-first-sandbox-application.md
- https://registry.npmjs.org/@amazon-sp-api-release%2Fsp-api-dev-mcp
- https://github.com/amzn/selling-partner-api-samples
- https://sellingpartner-ai.amazon.com/.well-known/oauth-protected-resource/mcp
- https://sellingpartner-ai.amazon.com/.well-known/oauth-authorization-server/mcp
- https://claude.com/marketplace/connectors/amazon-selling-partner
- https://www.amazon.com/robots.txt
- https://novadata.io/resources/news/amazon-cancels-sp-api-fees-may-2026
- https://ppc.land/amazon-drops-sp-api-fees-after-developer-pushback
16Readiness score / 100
L0 Agent-invisibleBeats 7% of 1,846 companies
Access10/20
Context0/20
Interfaces4/32
Onboarding0/19
Trust2/9
Biggest gains
- +12 Remote MCP server for the product. Host a remote MCP server (e.g. mcp.<domain>/mcp, Streamable HTTP) for your core actions.
- +8 llms.txt exists. Publish /llms.txt: a markdown index of your docs at the root or docs host.
- +8 Machine-readable API spec. Publish an OpenAPI spec at a stable URL like /openapi.json and link it from llms.txt.
All 20 checks
- PASSAgents get the real page, not a bot wall10
- FAILrobots.txt lets user-triggered agents in6
- FAILContent is server-rendered4
- FAILllms.txt exists8
- FAILllms-full.txt exists3
- FAILDocs available as markdown6
- FAILSitemap2
- FAILStructured metadata1
- PASSPublic developer docs4
- FAILMachine-readable API spec8
- FAILRemote MCP server for the product12
- FAILDocs MCP or searchable docs4
- FAILSDKs and a CLI4
- FAILOAuth discovery metadata5
- FAILAgents can self-register OAuth clients6
- FAILSelf-serve API keys5
- FAILFree tier or test mode3
- FAILAgent manifests4
- PASSsecurity.txt2
- FAILPublic status page3
Your fix pack: 18 changes, up to +84 points
Each change is ready to paste, filled in for amazon.com, with a command to check it worked. Or hand the whole list to your coding agent.
Add the badge to your README
[](https://agentsready.dev/c/amazon.com)