On October 21 Walmart announced Agent Profiles, the Walmart Agent Gateway and terms for AI agents. The Gateway lets agents search and buy across Walmart and Sam's Club over MCP, starting with a beta for companies and developers. Agent Profiles, due next month, let shoppers authorize each agent separately, see its orders apart from their own, set a spending limit or approve every purchase, and revoke access at any time. Agents never receive payment-card data and are blocked if they break the terms. TechCrunch reports Amazon is moving the other way and blocking third-party shopping agents.
Key Takeaways
- ✓Access: the Walmart Agent Gateway uses MCP (Model Context Protocol), opening first as a beta for companies and developers, instead of agents clicking through the website in a browser
- ✓Agent Profiles arrive next month: one profile per agent, orders listed separately, spending limits such as $50, $100 or $200 (Walmart's examples) or approval for every purchase
- ✓Terms: purchases need customer approval by default, agents never get payment-card data or change payment methods, see only the data the task needs, and are blocked if they break the rules
- ✓Pricing (vendor statement): agents see the same prices a person sees on Walmart.com; per Reuters no Walmart+ membership is required
- ✓Walmart already integrates with Muse, ChatGPT, Gemini and others for conversational shopping; TechCrunch reports Amazon is blocking third-party shopping agents
Key Decision Metrics at a Glance
Turn your technical choice into a development budget
Compare 40 dev plans & simulate token costs vs $20/mo subscriptions
In-Depth Technical Analysis
Background and pain points
Most shopping agents today sign in with the customer's own account and click through a website built for people. Walmart says in its announcement that this is slow and error-prone and agents often get stuck, and that agent orders are mixed in with the customer's own. Meanwhile TechCrunch reports Amazon is blocking third-party shopping agents, so the two biggest US retailers are taking opposite paths.
How it works
Walmart is shipping three pieces. The Walmart Agent Gateway gives agents a structured search-and-checkout channel over MCP, starting as a beta for companies and developers; it can also help an agent find a shopper's usual items without handing over their full purchase history. Agent Profiles, due next month, are created automatically the first time an agent shops through the Gateway; the shopper links it by signing in to Walmart, then sets a spending limit or per-purchase approval and can delete it any time. Walmart compares it to adding an authorized user on a credit card. The terms require approval by default, keep payment-card data away from agents, limit them to the data a task needs, and block agents that break the rules.
Benchmarks
This is a commerce platform launch. Walmart has published no performance, success-rate or latency figures and no public Gateway API docs. The only concrete numbers are its example spending limits of $50, $100 and $200 and the next-month timeline for Agent Profiles (vendor statements).
Getting started
Teams building shopping or personal-assistant agents should watch for the Gateway developer beta and make purchase confirmation and budget caps first-class features, since Walmart's terms require approval by default and may ask for extra approval even within a limit. Agents that still scrape Walmart pages through a browser should plan to move to the MCP channel or risk being blocked under the new terms. Tell users the agent never touches their card and that Walmart's normal returns process still applies.
Benchmark side-by-side against alternatives, or calculate monthly token cost vs subscription break-even.
Discussion & Comments
0Sign in to join the discussion
Connect with AI developers to exchange benchmark insights.