/vendor/amazon/AgentRouting.json or
/vendor/amazon/AgentContext.json directly.
amazon.com
Overview
Does amazon.com support MCP?
Yes. amazon.com has a confirmed MCP implementation. Publisher of an open-source suite of MCP servers covering AWS services including documentation retrieval, Amazon ECS lifecycle management, AWS CDK and Terraform infrastructure assistance, Amazon MSK cluster management, and more; servers are installable via uvx/pip and connect AI assistants to AWS service APIs using AWS credential-based auth..
What agentic protocols does amazon.com support?
As of 2026-06-30, amazon.com has confirmed support for A2A, MCP, UCP, x402, and proprietary.
Is amazon.com's API publicly accessible or partner-gated?
Access varies by protocol: open, platform mediated, unknown, partner only.
Does amazon.com explicitly prohibit automated access?
Yes. amazon.com's terms of service explicitly prohibit automated or scraper access to the public website without prior written permission.
Is amazon.com agent-ready?
Yes. amazon.com has a confirmed, agent-callable interface that supports end-to-end workflow completion.
Protocols
AWS supports A2A as a contributor to the Linux Foundation open standard, with implementation available via the Strands Agents SDK, enabling developers to expose agents as A2A servers and consume A2A from other agents — scoped to the developer/builder tooling layer, not a consumer-facing travel or commerce endpoint.
AWS published an official blog post explicitly documenting its A2A support and involvement with the Linux Foundation standard, including integration into the Strands Agents SDK. Amazon.com (via AWS) is a contributor and adopter, not a named original launch partner; Google, Atlassian, Salesforce, SAP, and MongoDB are among those cited. The implementation is a developer SDK feature, not a publicly callable hosted endpoint.
No evidence that Amazon has adopted or is a launch partner for the Agentic Commerce Protocol. Named launch partners at ACP's initial rollout include URBN brands (Anthropologie, Free People, Urban Outfitters), Coach, Kate Spade, Revolve, and Ashley Furniture — Amazon is absent from all identified partner lists. Amazon operates its own proprietary payments and checkout infrastructure (not Stripe), making near-term ACP adoption structurally unlikely, though no vendor-specific statement confirming or denying participation was found.
Amazon does not appear in any AP2 launch partner list. The 60+ named partners at announcement (September 2025) include Mastercard, PayPal, American Express, Adyen, Coinbase, Etsy, Klarna, Salesforce, Worldpay, Visa, and others — but not Amazon. One source notes Amazon has developed its own independent agentic shopping solution ('Buy for Me'), which suggests a separate proprietary path rather than AP2 adoption. No Amazon-specific AP2 documentation, enrollment, or integration evidence was found.
Publisher of an open-source suite of MCP servers covering AWS services including documentation retrieval, Amazon ECS lifecycle management, AWS CDK and Terraform infrastructure assistance, Amazon MSK cluster management, and more; servers are installable via uvx/pip and connect AI assistants to AWS service APIs using AWS credential-based auth.
Amazon Web Services maintains the awslabs/mcp GitHub repository and companion documentation site at https://awslabs.github.io/mcp/ as an officially published open-source project. Servers are distributed via PyPI under the awslabs namespace and require standard AWS IAM credentials. No official retail/shopping MCP server from Amazon.com was found — third-party community wrappers (e.g., Fewsats, devlimelabs) exist but are not Amazon-sanctioned.
Managed runtime platform (Amazon Bedrock AgentCore Runtime) for hosting, deploying, and discovering MCP servers; exposes per-registry MCP-compatible endpoints at https://bedrock-agentcore.<region>.amazonaws.com/registry/<registryId>/mcp for tool listing and invocation by AI agents.
Amazon Bedrock AgentCore Runtime is documented at https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/runtime-mcp.html and supports the MCP 2025-11-25 specification. MCP servers are deployed as containers expected to listen at 0.0.0.0:8000/mcp. Access requires an AWS account with Bedrock AgentCore enabled; not directly publicly callable without AWS credentials and provisioned resources.
MPP's named launch partners, as announced by Stripe and Tempo, are Anthropic, DoorDash, Mastercard, Nubank, OpenAI, Ramp, Revolut, Shopify, Standard Chartered, and Visa. Amazon does not appear in any partner list, official documentation, or coverage of the protocol. No Amazon-specific adoption or participation evidence was found across two targeted searches.
No evidence found that amazon.com has implemented NLWeb's /ask or /mcp endpoints. Amazon/AWS has its own separate MCP infrastructure (AWS MCP Server, Amazon Ads MCP Server) but these are not NLWeb implementations. Microsoft's NLWeb launch materials and third-party coverage name no Amazon entity among early adopters; Cloudflare is the most-cited implementation partner.
Tech Council governance member (standards steering body for UCP, announced April 24, 2026); no agent-callable Amazon checkout endpoint or merchant-side UCP implementation has been confirmed — Amazon's current commerce surface remains walled-garden (Rufus/Buy with Prime) with no publicly documented UCP endpoint for external AI agents.
Amazon joined the Universal Commerce Protocol Tech Council on April 24, 2026 alongside Meta, Microsoft, Salesforce, and Stripe, confirming vendor-specific participation in UCP governance. However, Tech Council membership is a standards-steering role, not evidence of a live, agent-callable UCP checkout endpoint; multiple sources characterize Amazon's commerce surface as a walled garden oriented around Rufus and internal tooling rather than external-agent interoperability. No Amazon developer docs, production UCP endpoint, or callable checkout surface were found.
No evidence found that Amazon (amazon.com) has implemented or announced support for WebMCP, the browser-layer window.AICommands protocol co-developed by Google and Microsoft. Search results name Google and Microsoft as co-developers, with no Amazon involvement as a launch partner or early adopter. Amazon's public agent-protocol activity centers on MCP server hosting via AWS Bedrock and ECS, which is a distinct infrastructure-layer protocol, not the browser-native WebMCP surface.
Amazon Bedrock AgentCore acts as an x402 client: when an AI agent requests a paid resource and receives an HTTP 402 response, AgentCore's payment manager authenticates with a configured wallet, signs the stablecoin transaction, attaches payment proof, and resubmits the request. Amazon is a platform consumer of x402, not a server-side implementor exposing x402-gated endpoints to the public.
Amazon Web Services announced a preview of Amazon Bedrock AgentCore Payments built in partnership with Coinbase and Stripe, with x402 as the underlying settlement protocol (https://aws.amazon.com/blogs/machine-learning/agents-that-transact-introducing-amazon-bedrock-agentcore-payments-built-with-coinbase-and-stripe/). This is a platform-mediated integration: developers using Bedrock AgentCore get x402 client capability bundled into the agent runtime rather than amazon.com exposing an x402-gated endpoint of its own. The feature was in preview as of the announcement date, making this a new and not-yet-stable capability.
No usable finding available for this protocol (no legitimate scan available within the candidate window).
Selling Partner API (SP-API): REST-based interface covering seller and vendor operations including orders, inventory, catalog items, fulfillment, reports, finances, and product listings. Covers both 3P seller and 1P vendor supply-side management. Read/write access varies by endpoint.
The SP-API is Amazon's documented proprietary REST API for selling partners and their application developers; access requires registering a developer account in Seller Central and having applications approved. Sandbox environments are available at developer.amazonservices.com. This is a mature, versioned API with public release notes dating back multiple years.
Amazon Ads API: REST-based interface for programmatic management of Amazon advertising campaigns, including Sponsored Products, Sponsored Brands, Sponsored Display, and DSP. Supports campaign creation, budget management, bid optimization, and performance reporting.
The Ads API requires an explicit application process; eligible parties include solution providers, agencies with internal engineering capacity, and advertisers with sufficient campaign volume. Access is not self-serve — applicants must be reviewed and approved by Amazon Ads. Separate from SP-API with its own endpoint base URL (advertising.amazon.com) and onboarding flow.
No evidence of amazon.com publishing llms.txt, AGENTS.md, /.well-known/agent, or any equivalent self-declaration file at a predictable location. Direct fetch attempts were blocked by DNS resolution failure in the sandbox, so path-level checks could not be completed. Web searches found industry discussion of these standards as adopted by Shopify-powered stores but no indication Amazon has published such files on amazon.com itself. Status is not_found rather than unable_to_verify because the available secondary evidence (search results, industry coverage) consistently names other retailers — not Amazon — as adopters, and no source references such a file at amazon.com.
Summary
Has agent interface: true
Engage Amazon's developer programs directly: register a developer account in Seller Central for SP-API access or apply to the Amazon Ads API program for advertising use cases. For agent infrastructure use cases, evaluate Amazon Bedrock AgentCore (MCP hosting, x402 payments) via standard AWS account provisioning. Monitor UCP Tech Council developments for any future Amazon-side callable checkout endpoint — none exists today.
AgentContext
Verified discrepancies
Vendor claim: Amazon's checkout process presents Prime membership as an optional add-on, with pricing and auto-renewal terms clearly available to the shopper before they commit.
What actually happens: The FTC documented—and Amazon settled for $2.5 billion in September 2025—that Amazon's checkout flows used deceptive UI patterns (a prominent 'Join Prime' button paired with an inconspicuous 'decline' link, and buried price/auto-renewal disclosures on mobile) to enroll consumers in a $139/year Prime subscription without meaningful consent. The settlement covers conduct through June 23, 2025, and requires Amazon to cease these practices going forward, but independent verification that all offending flows have been removed has not been confirmed.
Agent guidance: When completing any Amazon purchase flow, explicitly verify the final order summary before submitting payment and confirm that no Prime subscription line item appears unless the user explicitly requested it. If a Prime enrollment prompt is presented during checkout, do not click the primary/highlighted CTA—locate and use the explicit 'No thanks' or 'Continue without Prime' option. After order placement, retrieve the order confirmation and check for any recurring subscription charge to flag to the user immediately.
- The FTC's official press release confirms Amazon settled for $1B civil penalty plus $1.5B in consumer refunds and was ordered to 'cease unlawful enrollment and cancellation practices for Prime.'
- The FTC's refund page confirms the settlement covers customers enrolled through 'challenged enrollment flows' between June 23, 2019 and June 23, 2025, with Amazon still distributing refunds into late 2026.
- A legal analysis of the settlement details how Amazon's desktop checkout showed a dominant 'Join Prime' CTA alongside an inconspicuous decline link, and how mobile pages buried price and auto-renewal disclosures below the fold.
Vendor claim: Amazon displays product listings with stated prices and in-stock availability, implying that items are purchasable at the shown price and conditions at checkout.
What actually happens: Amazon's own platform has documented, recurring technical glitches in which listed items are blocked mid-transaction or displayed prices change at checkout. In 2024, Amazon blocked thousands of active seller listings flagged for 'potential high pricing errors' even when sellers had not changed their prices, rendering displayed inventory unbookable for days. Separately, users have reported location-based inventory filtering that shows higher-priced items rather than lower-priced alternatives displayed to users in other regions, meaning the price and availability shown on a listing page do not reliably match what can be completed at checkout.
Agent guidance: Before completing any Amazon purchase, an agent should programmatically verify that the final checkout price and availability match the product listing page values immediately before order submission—do not cache or assume listing-page data is valid for more than one session. If the checkout price differs from the listed price or an item becomes unavailable mid-flow, the agent should abort the transaction and alert the user rather than proceeding at the changed price.
- A seller-tools vendor documents a 2024 Amazon system glitch in which thousands of listings were suppressed for 'potential high pricing errors' with no seller price change, confirmed by Amazon Seller Support as a platform-side technical issue; affected inventory was de facto unavailable to buyers despite appearing listed.
- FTC antitrust complaint (Case No. 2:23-cv-01495-JHC) alleges Amazon's algorithmic and structural practices distort what inventory and pricing is actually surfaced to consumers, including anti-discounting mechanisms that affect displayed versus transactable prices.
Vendor claim: Amazon's product pages present a unified shopping experience and Amazon processes all payments. The A-to-Z Guarantee is promoted as buyer protection on all marketplace purchases. Amazon's own help content describes the A-to-Z Guarantee as covering purchases 'from third-party sellers' as if Amazon stands behind every transaction.
What actually happens: When a transaction involves a third-party seller (which accounts for roughly 60%+ of Amazon unit sales), the legal merchant of record is the independent third-party seller, not Amazon. Amazon collects payment on their behalf but explicitly disclaims product liability in its Conditions of Use. In FBM (Fulfilled by Merchant) transactions, Amazon further limits its responsibility. Courts across the U.S. are divided on whether Amazon qualifies as a 'seller' under product liability law — California courts have held it does, while other jurisdictions have ruled it does not — meaning the consumer's actual legal counterparty and recourse path vary by state and fulfillment method in ways not disclosed at the point of purchase. An AI agent completing a purchase would have no reliable signal at checkout about who it can legally pursue in a dispute.
Agent guidance: Before completing a purchase on Amazon, an agent must check the 'Sold by' field on the product and checkout pages to determine whether the seller is 'Amazon.com' or a named third party. If a third party is the seller, the agent should flag to the user that: (1) Amazon is not the legal merchant of record, (2) refund and dispute recourse runs through the A-to-Z Guarantee process rather than a direct Amazon return, (3) liability and legal recourse vary by state, and (4) for high-value or safety-critical purchases, the user should verify the third-party seller's standing before completing the transaction.
- A legal analysis documents that courts are split on Amazon marketplace liability: California's 2020 landmark ruling held Amazon strictly liable for defective third-party products, while other states have reached the opposite conclusion, creating inconsistent legal counterparty status depending on jurisdiction.
- The FTC's 2023 ecommerce complaint against Amazon (Case No. 2:23-cv-01495-JHC) details how Amazon's Buy Box and marketplace structure obscure the identity of the actual seller from consumers at the point of purchase.
- Amazon's A-to-Z Guarantee and chargeback dispute process differs materially depending on whether the seller uses FBA or FBM, and Amazon may automatically refund or deny claims without the consumer knowing which party — Amazon or the seller — actually bore the cost or holds the liability.
Vendor claim: Amazon states that customers may cancel their Amazon Prime subscription at any time through their account settings, and that the cancellation flow is accessible and straightforward. Amazon's published Prime terms describe a clear, user-initiated cancellation process.
What actually happens: The FTC found that Amazon used a 'challenged enrollment flow' and an online cancellation flow that effectively prevented or obstructed customers from successfully canceling Prime between June 23, 2019 and June 23, 2025. This resulted in customers continuing to be charged for subscriptions they believed they had canceled or never intentionally signed up for. The FTC secured a settlement requiring Amazon to issue refunds to affected Prime customers, with automatic refunds sent in November and December 2025 and a claims process ongoing into 2026.
Agent guidance: When an agent is asked to sign up for or cancel Amazon Prime on a user's behalf, do not assume the cancellation flow completes successfully just because the UI appears to proceed. After any cancellation attempt, verify the subscription status independently by checking the user's account membership page (amazon.com/mc/pipelines/prime) or the 'Manage Your Prime Membership' settings, and confirm in writing to the user whether the cancellation was confirmed or if further manual steps are required. Do not rely solely on on-screen confirmation messages.
Vendor claim: Amazon.com presents itself as a fully transactable e-commerce platform, implying that authenticated users (including those using automated tools or agents acting on their behalf) can complete purchases, manage carts, and check out using their account credentials.
What actually happens: Amazon actively blocks third-party AI agents from completing transactions on its platform, even when those agents are operating with explicit user permission and valid user credentials. Amazon has deployed technical countermeasures, filed federal litigation, and obtained a court injunction barring at least one major AI shopping agent (Perplexity's Comet) from completing purchases — while simultaneously building and favoring its own proprietary shopping assistant (Rufus). This constraint is not disclosed upfront in Amazon's user-facing terms or checkout flow; an agent would only discover the block mid-transaction when its session is detected and terminated.
Agent guidance: An AI agent attempting to complete a purchase on Amazon.com on behalf of a user should not assume that user-level credentials or authorization are sufficient to transact. Amazon actively detects and terminates non-native automated sessions. Agents should inform users that Amazon blocks third-party automated checkout and direct users to complete the transaction manually or through Amazon's own Alexa/Rufus interface, rather than attempting to automate the checkout flow directly.
- A federal judge granted Amazon an injunction blocking Perplexity's Comet AI shopping agent from accessing Amazon, finding that user permission does not equal platform authorization; Amazon had deployed technical blocks and filed suit under the Computer Fraud and Abuse Act.
- Coverage of the Ninth Circuit appeal confirms Amazon has blocked 'dozens of outside agents' including OpenAI's ChatGPT, while favoring its own Rufus assistant; the case is described as a broad signal that platforms can exclude third-party AI agents even when users have authorized them.
- CyberScoop analysis notes the case turns on the distinction between user permission and platform authorization, and that courts are being asked to decide whether automated agents must follow undisclosed platform rules restricting bots in account areas.
Human handoff required for
Escalate to human when a Prime membership line item appears on the order summary during checkout that the user did not explicitly request, because Amazon's settlement-mandated checkout remediation has not been independently verified as complete and an unintended $139/year auto-renewing subscription may be about to be charged.
Escalate to human when the price shown at the final checkout screen differs from the price shown on the product listing page, or when an item displayed as in-stock on the listing page becomes unavailable or shows a different fulfillment condition mid-transaction.
Escalate to human before completing any high-value or safety-critical purchase where the 'Sold by' field on the product or checkout page names a third-party seller rather than 'Amazon.com', because the legal merchant of record, dispute path, and liability recourse vary by seller and jurisdiction in ways not disclosed at checkout.
Escalate to human after any Amazon Prime cancellation attempt where the account membership page does not independently confirm cancellation, because the FTC found Amazon's cancellation flow obstructed successful cancellations between 2019 and 2025 and the flow's reliability post-settlement has not been independently re-verified.
Escalate to human immediately if an automated checkout session on Amazon.com is interrupted, flagged, or terminated mid-transaction, because Amazon has obtained a federal court injunction blocking third-party AI agents from completing purchases and actively detects non-native automated sessions, meaning the transaction cannot be completed by the agent and must be completed manually by the user.
Five discrepancy categories were checked for amazon.com. Pricing discrepancies: scans found a primary-source FTC settlement (September 2025, $2.5 billion) confirming Amazon used dark-pattern UI flows to covertly enroll consumers in paid Prime subscriptions, with remediation unverified. Availability discrepancies: scans found a documented 2024 platform glitch suppressing active listings as unbookable and an active FTC antitrust complaint alleging algorithmic distortion of transactable inventory and prices. Identity discrepancies: scans found well-documented merchant-of-record ambiguity in third-party seller transactions, an active circuit split on Amazon's seller liability status, and FTC antitrust complaint documentation of Buy Box obscuring seller identity. Policy discrepancies: scans found FTC-enforcement-backed evidence that Amazon's Prime cancellation flow obstructed cancellations from 2019 to 2025, with refunds still being administered in 2026 and post-settlement flow reliability unverified. Undisclosed constraints: scans found substantial evidence including a federal court injunction that Amazon actively blocks third-party AI agents from completing purchases, a constraint not disclosed in user-facing terms. All five categories returned substantive findings grounded in primary regulatory and legal sources; no scan was blocked or missing.