Walmart's Agent Profiles Show How Retailers Can Admit AI Shoppers Without Giving Up Control

On October 21, Walmart announced three things for AI agents that shop on a customer's behalf: Agent Profiles, the Walmart Agent Gateway, and terms that agents must follow. Together, Walmart says, they will let customers shop with Walmart and Sam's Club "through the apps and agents they choose."

The interesting part is not that Walmart will allow outside agents. It is how. Walmart's announced model treats an outside agent as a separate user inside the customer's account, with its own identity and limits, rather than as the customer.

What Walmart announced

• Agent Profiles, launching in the next month. Each agent the customer authorizes gets a dedicated profile within the account, and its purchases appear separately from the customer's own. The customer chooses between approving every purchase or allowing purchases within a spending limit, with $50, $100 and $200 as Walmart's examples, and can delete a profile at any time.
• The Walmart Agent Gateway, an early beta. Walmart says it will give agents a faster, more reliable way to shop using MCP, the Model Context Protocol, an open standard for connecting AI applications to tools and data. The gateway page says it connects agents through Sparky, Walmart's own assistant, and replaces website scraping with product and fulfillment data "straight from the source." Access is limited and invitation-only for companies and developers.
• Terms for agents. Purchases require approval by default, and Walmart may require more approvals even within a spending limit. Agents do not receive payment-card information and cannot add or change payment methods. They may access only what the task needs and the customer allows. Walmart's returns process applies, including when an agent does not act as intended, and agents that break the terms will be blocked.

Walmart has not named any companies in the beta or disclosed any usage. This is an announced model, not a measured one.

The agent is becoming a separate account role

Walmart describes today's problem plainly. When a customer uses an AI agent now, the agent signs in with the customer's account, and every purchase, whether made by the person or the agent, appears together.

That arrangement collapses four things into one login: who the customer is, how they pay, what they have bought, and who is allowed to buy. Agent Profiles start to pull those apart. The customer still owns the account. The agent gets its own profile, limited authority and a visible purchase record. Payment stays attached to the account. The agent may initiate an authorized purchase, but it does not receive the card details or control the payment method. Walmart's own analogy is adding an authorized user to a credit card, with a spending limit and a statement you can check.

That is why this is more than giving a bot an API. A gateway provides the route. The delegated role determines which agent is using it, what it may do, what it may spend, how its actions are recorded and when its authority ends.

Customer authorization and retailer acceptance are different permissions

Two separate grants run through the model. The customer decides what the agent may do: require approval for every purchase, or spend up to a limit, and revoke whenever they like. Walmart decides what it will accept: the gateway page lists category restrictions, rate limits and compliance guardrails, and Walmart keeps the right to require extra approval and to block an agent outright.

That is the same split I described when Sierra and Meta announced Personal Agent Protocol, where customers decide what access to give and companies set what agents can do. Walmart is one of that protocol's named development partners, but its announcement does not say the gateway implements it, and I would not assume it does. The resemblance is in the permission model, not a confirmed standard.

Walmart's updated terms of use add the accountability side. Actions an authorized agent takes within the permissions a customer granted are treated as the customer's own, and Walmart says it is not responsible for a third-party agent's conduct, including misunderstanding instructions. Walmart separately says its normal returns process applies when an agent does not act as intended. That recourse does not change who authorized the purchase.

Why the gateway matters beyond access

Walmart's terms already require agents to identify themselves and respect rate limits. The gateway gives them a reason to comply: a faster, more reliable path than clicking through pages built for people. That matters because rules are easier to enforce on a route you built than on one an agent improvised. It is the commerce version of the permission stack that crawler controls became, where access stopped being one switch and became separate permissions.

Data is part of it too. Walmart says the gateway can help an agent find a customer's usual items, such as a preferred bread or brand of milk, without sharing the broader purchase history. Its terms also say authorizing an agent means consenting to share the account and order information reasonably necessary for the authorized task. Both can hold. Where "reasonably necessary" ends is a detail Walmart has not published.

Pricing carries over from Walmart's September customer letter: agents see the same prices as people, with offers and fees shown before purchase. It is the same negative permission I wrote about when Walmart said it would price the product, not the person.

What changed in Walmart's strategy

In March, I wrote that Walmart had moved Sparky into ChatGPT and Gemini and concluded that "Walmart won't let anyone else's AI sell Walmart products." The evidence then supported a retailer-owned-agent strategy. This announcement makes that sentence wrong.

Walmart has not abandoned Sparky. The gateway connects outside agents through it. What changed is where Walmart draws the line. It no longer has to own the agent. It has to own the permissions and transaction infrastructure beneath it. The updated conclusion is narrower and, I think, more durable: Walmart says it will let outside agents shop for customers, and its announced model routes identity, approvals, data access, payment and enforcement through Walmart.

The comparison with Amazon is sharper than open versus closed. According to Axios, when Amazon blocked Meta's Muse agent, it said it had not authorized Muse to access customer accounts, scrape data or process transactions. Those are the three things Walmart's model places under its own control. The disagreement is about who builds the sanctioned path, and whether one exists at all.

What remains unknown

Which companies are in the beta, and whether any are processing real orders. When Agent Profiles reach every account. Which categories are restricted, and what triggers an extra approval. What happens to agents that keep shopping through the website instead of the gateway. And whether customers want delegated purchasing at all; Walmart's announcement itself says it will not be for everyone.

What retailers and commerce operators should learn

Treat the agent as a user type, not a login. Separate what the customer authorizes from what you will accept. Give agents a better route than scraping so your rules apply. Keep payment credentials out of the agent's hands, keep its purchases visible, and make revocation immediate.

Openness, in this model, is permissioned, selective and revocable. If an outside agent arrived at your store tomorrow, would your systems know it was not the customer?