/vendor/walmart/AgentRouting.json or
/vendor/walmart/AgentContext.json directly.
walmart.com
Overview
Does walmart.com support MCP?
No confirmed MCP support was found for walmart.com as of 2026-06-30.
What agentic protocols does walmart.com support?
As of 2026-06-30, walmart.com has confirmed support for A2A, ACP, UCP, openai_apps_sdk, proprietary, and self_declared_discovery.
Is walmart.com's API publicly accessible or partner-gated?
Access varies by protocol: unknown, platform mediated, open, partner only.
Does walmart.com explicitly prohibit automated access?
Yes. walmart.com's terms of service explicitly prohibit automated or scraper access to the public website without prior written permission.
Is walmart.com agent-ready?
Yes. walmart.com has a confirmed, agent-callable interface that supports end-to-end workflow completion.
Protocols
Internal orchestration backbone: A2A is explicitly cited as the delegation and chaining layer within Walmart's WIBEY (internal agentic AI platform), enabling multi-agent coordination across internal domains — not as an externally callable consumer or partner API surface.
Walmart's own engineering blog (tech.walmart.com) explicitly names A2A alongside MCP as 'connective tissue' for WIBEY, their internal agentic orchestration system announced at Converge 2025. A separate Walmart Global Tech Medium post discusses A2A and MCP as part of their enterprise AI architecture strategy. No externally callable A2A endpoint or developer-facing A2A surface for walmart.com has been found; usage appears entirely internal. Walmart is also a co-developer of UCP (Universal Commerce Protocol), the separate agentic commerce protocol, which is distinct from A2A.
Merchant participant in ChatGPT ACP-powered product discovery and Instant Checkout; Walmart joined as a retail partner approximately one month after the initial September 2025 launch, enabling product catalog discovery and direct checkout for Walmart inventory through ChatGPT.
Multiple independent sources (Retail Dive, Lengow, Mars United, Digital Commerce 360) confirm Walmart integrated ACP for ChatGPT Instant Checkout in October 2025, approximately one month after the protocol's September 29, 2025 launch. Walmart is listed alongside other ACP-integrated retailers (Target, Sephora, Nordstrom, Best Buy, Lowe's, The Home Depot, Wayfair). Integration is platform-mediated via OpenAI's ChatGPT surface; no directly callable public endpoint is documented for Walmart's ACP implementation.
Walmart's own January 11, 2026 announcement of its Google partnership explicitly names UCP (Universal Commerce Protocol) as the integration layer — not AP2. The 60-organization FIDO Alliance contributor list published at the time of Google's AP2 donation does not include Walmart. One third-party analysis (offbounds.tv) lists Walmart among "20+ AP2 partners," but this appears to conflate Walmart's UCP integration with AP2 adoption; no walmart.com source corroborates AP2 specifically. Named AP2 contributors confirmed present include Mastercard, American Express, PayPal, Adyen, Etsy, and Coinbase.
Walmart has publicly acknowledged using MCP internally — their WIBEY developer platform (announced at Converge 2025) explicitly cites MCP as connective tissue for agent orchestration alongside A2A, and their externally-facing AI agents (Sparky, Marty) are described as MCP-adopting. However, no official, externally-callable MCP server has been published on developer.walmart.com or announced for third-party consumption. All discoverable 'Walmart MCP servers' (Apify, GitHub repos by DomingosNgongo and taazkareem, PulseMCP listing by Strider Labs) are third-party community projects wrapping the Walmart Affiliate REST API or using browser automation — not sanctioned Walmart-published endpoints. Internal adoption does not constitute a publicly routable MCP surface.
No evidence that Walmart (walmart.com) has adopted or been named as a launch partner for MPP. Known early participants in MPP include Stripe-native merchants and MultiversX. The walmart.com search result for 'Mpp' refers only to an unrelated product brand sold on the retail site, not the payment protocol.
No evidence that Walmart has implemented or announced NLWeb support. Named NLWeb launch partners identified in Microsoft's May 2025 rollout include O'Reilly, Tripadvisor, Eventbrite, Snowflake, and Cloudflare — Walmart does not appear in any of these lists. No walmart.com /ask or /mcp endpoint was found.
Co-developer and endorsing merchant; Walmart participated in designing the UCP specification alongside Google, Shopify, Etsy, Wayfair, and Target, and is positioned as a merchant participant enabling AI-agent-driven product discovery and checkout flows against Walmart's own catalog — not as an agent orchestrator or protocol infrastructure provider.
Walmart is named as a co-developer of UCP in Google's official announcement blog and confirmed across multiple independent sources including the Shopify engineering post and ucp.dev. Its role is as a participating merchant/retailer in the protocol coalition, not as a platform operator or primary spec author (that role belongs to Google and Shopify). No publicly callable Walmart-specific UCP endpoint or implementation documentation was found; the public-facing spec and tooling are hosted at ucp.dev and GitHub under the UCP project rather than by Walmart directly.
Walmart (walmart.com) is a named co-developer and launch partner for Google's Universal Commerce Protocol (UCP), which is a separate, server-side agentic commerce standard. No evidence found that Walmart has implemented WebMCP — the browser-layer window.AICommands JavaScript surface co-developed by Google and Microsoft for in-browser agent-callable tools. Named WebMCP launch partners and coverage (Chrome for Developers, particula.tech, summit.co.uk) mention no retailer-specific WebMCP deployments at all; Walmart's association is exclusively with UCP.
No evidence found of Walmart (walmart.com) adopting or evaluating x402. The confirmed x402 Foundation Premier members and ecosystem partners include Fiserv, Google, Mastercard, Shopify, Stripe, Visa, Cloudflare, Solana, and Chainlink — Walmart appears in none of these lists. This is a not_found rather than confirmed_absent because no Walmart-specific statement or deprecation notice was found; Walmart simply has no documented presence in the x402 ecosystem.
Full shopping journey support within ChatGPT via Walmart's Sparky commerce agent: product discovery, account linking, loyalty program integration, and handoff to Walmart-controlled checkout environment. Walmart initially participated in OpenAI's Instant Checkout (direct in-ChatGPT purchase) but replaced that with this Sparky-powered in-platform app experience after Instant Checkout conversion rates underperformed (approximately one-third the rate of clickouts to Walmart's own site).
Walmart debuted a ChatGPT in-platform app experience backed by its Sparky AI commerce agent, confirmed by both Walmart and OpenAI per Retail Dive reporting (March 2026). The integration replaced the earlier Instant Checkout arrangement and covers the full shopping journey from discovery in ChatGPT through handoff to Walmart's own environment for final payment. No public-facing developer documentation URL was found; this appears to be a direct commercial partnership integration rather than a self-serve app-store submission.
Third-party seller and solution-provider operations on Walmart.com Marketplace: item catalog management, inventory, order fulfillment, pricing, promotions, and reporting via REST endpoints under marketplace.walmartapis.com
Documented at developer.walmart.com; credentials require an approved Marketplace seller or certified solution-provider account. Covers items, inventory, orders, pricing, promotions, and on-request/scheduled reports. TLS 1.0/1.1 deprecated August 2025; TLS 1.2+ required.
First-party (1P) supplier operations for vendors selling directly to Walmart: item setup, order management, and inventory management via REST endpoints on the Supplier API
Separate from the Marketplace API; intended for direct (1P) suppliers, not third-party sellers. Access requires an existing Retail-Link supplier relationship with Walmart. Documented at developer.walmart.com alongside other Walmart developer APIs.
Affiliate and consumer-app product data access: product search, product lookup (price and availability), catalog browsing, post-browse retargeting, and product reviews on Walmart.com
Hosted on the separate walmart.io developer portal (distinct from developer.walmart.com). Read-only product-data access; no order or transaction capabilities. Accessible to affiliate program participants who obtain a publisher ID via Impact Radius.
Delivery carrier and logistics integration via Walmart GoLocal delivery-as-a-service REST API, and advertising campaign management via Walmart Connect Ads API
Both the GoLocal (delivery carrier) API and Connect Ads API require an existing direct Walmart partnership with no public application form available. Sandbox/simulator environment documented for GoLocal testing prior to production. Access is effectively invitation- or contract-only.
AI agent access governance for walmart.com: signals how external LLMs and shopping agents may interact with and retrieve content from the site, restricting certain agent behaviors while permitting others via a published llms.txt file at the domain root
Multiple credible secondary sources — including a briefing by The Information and a LinkedIn post by a retail-tech analyst — confirm Walmart published an llms.txt file at walmart.com governing how AI agents and LLMs may access its site. Direct fetch of walmart.com/llms.txt was not possible from this research environment due to network restrictions, so exact file contents could not be verified, but vendor-level publication is well-attested. No evidence was found for AGENTS.md, /.well-known/agent, or similar conventions at this domain; only the llms.txt convention is reported.
Summary
Has agent interface: true
Prioritize verification of Walmart's llms.txt contents (direct fetch was blocked during research) to confirm which agent behaviors are permitted versus restricted at the domain level; then pursue Walmart Developer Portal credentials via the Marketplace or Affiliate program routes to access the confirmed proprietary REST APIs. For ACP and OpenAI Apps SDK access, engage OpenAI partnership channels directly, as both integrations are platform-mediated commercial arrangements rather than self-serve developer surfaces. Separately, monitor ucp.dev for Walmart-specific UCP implementation documentation as the protocol matures.
AgentContext
Verified discrepancies
Vendor claim: Walmart advertises product prices on shelf labels and on walmart.com product pages, implying that the displayed price is what the customer will be charged at checkout.
What actually happens: A 2024 class-action lawsuit allowed to proceed by the 7th U.S. Circuit Court of Appeals alleged a systematic gap between shelf/displayed prices and final checkout prices — a 'bait-and-switch' pricing scheme. Walmart also settled with New Jersey for $1.64 million in June 2024 over unlawful unit pricing practices. The court ruled that an accurate receipt does not retroactively cure the deception caused by inaccurate pre-checkout prices, meaning an AI agent relying on the displayed price would record an incorrect expected total.
Agent guidance: When completing a purchase on walmart.com, do not treat the displayed product page price as the confirmed transaction total. Always capture and verify the final itemized checkout total (including any price changes between cart and payment confirmation) before recording the transaction amount or reporting back to the user. Flag any difference between the product-page price and the order-confirmation price to the user before finalizing.
- The 7th U.S. Circuit Court of Appeals allowed a class-action to proceed in July 2024, finding that inaccurate shelf/displayed prices constituted deception even when the final receipt was accurate; the court called it a 'bait-and-switch' pricing scheme.
- Walmart settled with New Jersey customers for $1.64 million in June 2024 over repeated unlawful unit pricing practices, with plaintiffs arguing it was unreasonable for consumers to track discrepancies between displayed and checkout prices.
Vendor claim: Walmart advertises specific prices on shelf labels and product listings, and customers are led to believe they will pay those displayed prices at checkout.
What actually happens: Multiple independently verified sources — including a 2024 7th U.S. Circuit Court of Appeals ruling, a 2024 New Jersey settlement, and prior state regulatory actions — document that Walmart customers are systematically charged prices higher than the advertised/displayed price at checkout, with overcharges ranging from 5–15% on affected items. This pricing gap persists across in-store transactions and has not been fully resolved for online transactions where displayed prices may similarly diverge from the final charged price.
Agent guidance: When completing a purchase transaction on walmart.com or in-store via Walmart systems, always capture the displayed/advertised price before checkout and then verify the final order total or receipt against that pre-checkout price before confirming the transaction as complete. If the charged price exceeds the advertised price on any line item, flag the discrepancy to the user before finalizing payment rather than assuming the checkout price is correct.
- The 7th U.S. Circuit Court of Appeals (July 2024) allowed a class-action lawsuit to proceed, affirming that Walmart customers may have been systematically charged more than advertised shelf prices, constituting a 'bait-and-switch' scheme.
- Walmart settled for $1.64 million with New Jersey customers in June 2024 over repeated unlawful unit pricing practices, confirming documented discrepancies between advertised and charged prices.
- Law firm Bernstein Liebhard's investigation summarizes the class-action complaint: Walmart shelf pricing 'frequently misrepresents the prices consumers are charged at the point of sale,' with overcharges of 5–10% or more on affected goods.
Vendor claim: Walmart.com presents a unified shopping experience where buyers transact on walmart.com; Walmart states it will step in to resolve disputes and find a 'right final solution' if a seller is unresponsive or unabiding, implying Walmart backstops all transactions on its platform.
What actually happens: For Walmart Marketplace orders, the actual merchant of record is the individual third-party seller, not Walmart. Return windows, refund policies, and dispute responsibility differ by seller and are not standardized. Walmart only intervenes as a fallback — the primary legal counterparty for the transaction is the third-party seller. An agent completing a purchase may not be able to determine at checkout whether it is buying from Walmart directly or a third party, and the applicable refund/return terms can vary materially depending on which seller is involved.
Agent guidance: Before completing a purchase on walmart.com, an agent must programmatically verify whether the item is 'Sold and Shipped by Walmart' or 'Sold by [third-party seller].' If it is a third-party seller, the agent should surface that seller's specific return/refund policy to the user before confirming payment, and make clear that dispute resolution is primarily the seller's responsibility — with Walmart only as a fallback — so the user can make an informed decision about the transaction counterparty.
- Walmart's own consumer-facing help page clarifies that marketplace items are sold by third-party sellers, and that Walmart only steps in after the seller is given 2 business days to resolve; the seller — not Walmart — is the primary counterparty.
- Third-party analysis notes that Walmart Marketplace sellers set their own return windows (14–30 days, varying by seller), meaning the return policy a buyer sees may differ from Walmart's standard 30-day policy, and Walmart only intervenes when sellers are unresponsive or uncooperative.
- Chargeback Gurus notes that for Walmart Marketplace chargebacks, the merchant (seller) is required to respond within 48 hours; many chargeback decisions are made by the card network, not Walmart, with no recourse to appeal — illustrating that dispute liability sits with the third-party seller, not Walmart.
Vendor claim: Walmart.com presents products for browsing and adding to cart without any upfront indication that completing a purchase requires a registered account. The platform's product and cart pages imply a standard e-commerce checkout flow accessible to any shopper.
What actually happens: Walmart.com has eliminated guest checkout entirely. An account must be created or signed into before an order can be placed. This requirement is not disclosed on product listing pages or cart pages — it is only enforced at the checkout step, meaning any agent or user who has browsed, selected items, and proceeded to checkout without pre-existing credentials will be blocked from completing the transaction mid-flow.
Agent guidance: Before initiating any Walmart.com purchase flow on behalf of a user, verify that valid Walmart.com account credentials (email and password) are available and functional. Do not assume guest checkout is an option — attempting to complete a transaction without a pre-authenticated session will result in a hard block at checkout. If credentials are unavailable, the transaction cannot be completed programmatically and the user must be notified prior to any checkout attempt.
- A dedicated 2024 consumer-facing article confirms Walmart has removed its guest checkout option entirely, requiring all online shoppers to create an account before completing any purchase — a change not disclosed on product pages.
- Ongoing user complaint thread on sitedown.co documents repeated instances of shoppers discovering the mandatory account requirement only at the checkout step, with users unable to proceed without registration.
Human handoff required for
Escalate to a human when the final order-confirmation price on walmart.com differs from the product-page or cart-displayed price on any line item, as systematic overcharging above displayed prices has been documented in active litigation and regulatory settlements — the agent cannot assume the checkout price is correct.
- The 7th U.S. Circuit Court of Appeals allowed a class-action lawsuit to proceed in 2024 alleging Walmart systematically charged prices higher than those displayed on shelf labels and product pages, ruling that an accurate receipt does not cure pre-checkout deception.
- Walmart settled with New Jersey for $1.64 million in June 2024 over unlawful unit pricing practices, confirming a documented pattern of displayed-price-vs-charged-price discrepancies.
Escalate to a human when a walmart.com purchase involves a third-party Marketplace seller (i.e., the item is not listed as 'Sold and Shipped by Walmart') and the user needs to initiate a return, refund, or dispute — because the legal counterparty is the individual seller, not Walmart, and applicable return windows and refund terms vary materially by seller with Walmart only intervening as a secondary fallback.
- Walmart's own Marketplace seller policies confirm that return windows and refund terms differ by seller, and Walmart only steps in to resolve disputes after the seller has failed to respond, meaning the primary liability rests with the third-party merchant.
- Walmart.com commingles first-party and third-party Marketplace inventory in the same checkout flow without clearly distinguishing the merchant of record at the point of purchase, creating ambiguity about the legal counterparty and applicable dispute terms.
Escalate to a human before initiating any walmart.com purchase flow if valid, pre-authenticated Walmart.com account credentials are not available — because guest checkout has been eliminated entirely and the absence of credentials will result in a hard block at the checkout step with no programmatic workaround.
Escalate to a human when a refund or return dispute arises on a walmart.com Marketplace order where the third-party seller is unresponsive or disputes responsibility, requiring Walmart's backstop intervention — because the timeline and outcome of Walmart's secondary dispute process are not guaranteed and exceed the scope of autonomous agent action.
Five categories were checked for walmart.com: (1) discrepancy_pricing — findings present; active 2024 litigation (7th Circuit) and a New Jersey regulatory settlement confirm systematic gaps between displayed and charged prices at checkout. (2) discrepancy_availability — findings present; the same pricing-gap evidence was surfaced, confirming that advertised prices are not reliably honored at checkout across in-store and online channels. (3) discrepancy_identity — findings present; walmart.com commingles first-party and third-party Marketplace sellers in a single checkout flow, with the actual merchant of record and applicable return/refund terms varying materially and not clearly disclosed at point of purchase. (4) discrepancy_policy — no finding; the FTC's June 2025 $10 million Walmart settlement relates to money-transfer fraud and is unrelated to product return or refund enforcement; no verified evidence of material policy-vs-practice gaps in return/cancellation terms was found. (5) discrepancy_undisclosed_constraint — findings present; Walmart.com has eliminated guest checkout, a constraint not disclosed on product or cart pages that only surfaces mid-checkout, blocking any agent without pre-authenticated credentials. All five categories received active scans with substantive results or confirmed absence of findings.