Walmart Agent Gateway and Agent Profiles: What Businesses Should Know

On October 21, 2026, Walmart announced three things for AI agents that shop for its customers: Agent Profiles, the Walmart Agent Gateway and a set of terms agents must follow. Together they give each agent its own profile inside a customer's account, a spending limit the customer sets, and a structured way to shop that does not depend on clicking through a website built for people.

This post covers what Walmart announced, what is still missing, and what it means for three groups: businesses that might let an agent buy supplies, teams building shopping agents, and other stores deciding how to treat agents on their own sites.

We read Walmart's announcement, Walmart Makes It Possible for Agents to Shop on Behalf of Customers, on October 22, 2026. Every Walmart fact below comes from that page. We have not used the gateway, which starts as a beta for companies and developers.

Agent Profiles launch "in the next month," per Walmart. The gateway is an MCP server, starting with a developer beta. The terms apply now in the sense that Walmart has published them, and Walmart says agents that do not follow them will be blocked from its site. Walmart's announcement does not include gateway documentation, a public launch date or a list of approved agents.

Walmart says that today an agent signs in with the customer's own account, so the agent's orders and the customer's orders appear together with nothing to tell them apart. Agent Profiles change that:

• The first time you shop through an agent using the Walmart Agent Gateway, Walmart creates an Agent Profile for that agent.
• You link the profile by signing into your Walmart account. Walmart says only Walmart sees this step.
• You choose how purchases are approved: approve every purchase, or let the agent buy within a spending limit you set. Walmart's examples are $50, $100 and $200.
• You can see each agent's purchases separately and delete a profile at any time.

Walmart compares it to adding someone as a cardholder on your credit card. It also says the prices an agent sees are the same prices a person sees on Walmart.com, with offers and fees shown before purchase.

Walmart says agents shopping through a browser are slow, error-prone and can get stuck, because the site is built for people. The gateway gives agents a faster, more reliable way to shop through MCP. (Walmart's release calls it "model text protocol." MCP stands for Model Context Protocol. Our explainer on what MCP servers are covers the basics.)

One detail stands out. Walmart says the gateway can help an agent find a customer's usual items, its example is a certain sourdough bread or brand of milk, without sharing the customer's wider shopping history with the agent.

Walmart's published terms say:

1. 1Customers stay in control, and Walmart's returns process applies, including when an agent does not act as intended.
2. 2Customers must approve agent purchases by default, and Walmart may ask for extra approval even inside a spending limit.
3. 3Agents must not take actions beyond what the shopper intends.
4. 4Agents do not receive card details and cannot add or change payment methods.
5. 5Agents can access only the information the task needs and the customer allows.
6. 6The agent company's privacy policy covers what it receives. Walmart's Privacy Notice covers what the agent sends Walmart.
7. 7Agents that break the terms will be blocked from Walmart's site.

For a team planning work around this, the gaps matter as much as the features. The announcement does not give the gateway's tool list, how agents authenticate, rate limits, a sandbox, how failed orders are reported, or any fees. It says profiles arrive in the next month without a date. It does not say which agent apps are in the first beta. Plan nothing on a date until Walmart publishes one.

The terms cover both Walmart and Sam's Club. Many small offices, clinics and restaurants reorder the same supplies every few weeks. Agent Profiles fit that job well, because the profile keeps the agent's orders separate and the limit caps what it can spend. These are designs we would build. None of them describes a client result.

1. 1Restock with a cap. A weekly agent checks a simple stock sheet, builds a cart of the usual items and either asks for approval or buys inside a limit the owner chose. Start with approval on every order for the first month.
2. 2One agent, one job. Give each agent its own profile so you can see which one bought what. Do not let a general assistant and a restock agent share one.
3. 3A weekly spend report. Pull each agent's orders into the books every week, matched to the stock sheet, so an odd order shows up within days rather than at month end.

When it is not worth it: if you order a handful of items twice a year, a saved list and five minutes of your own time beats any agent. If your supplies come from a distributor with net terms, the Walmart gateway does not help with that at all.

Our post on typed action budgets for AI agents covers how to set limits by amount, count and expiry, which is the same idea Walmart is building into its profiles.

Walmart's gateway follows Shopify's Shop MCP, which launched on October 13, 2026. Both point the same way: use the store's tools instead of driving its website, which our post on agents using the browser instead of MCP explains.

What we would build into an agent now, before the gateway docs arrive:

• Treat approval as the normal path, not an edge case. Walmart says approval is the default and it may ask for more approvals even inside a limit, so the agent must be able to pause, ask the owner and resume.
• Never store card numbers. Walmart's terms say agents do not get them, and tools like Agent Vault show the same pattern elsewhere.
• Keep a log of every cart and order the agent placed, so a return under Walmart's returns process is easy to start.
• Do not keep using browser automation on Walmart.com once the gateway is open to you. Walmart says agents that break its terms will be blocked, and the terms say agents must not go beyond what the shopper intends.

Walmart's three pieces are a useful template for any store that expects agent shoppers: a separate identity for each agent, limits the customer sets, and written rules with a consequence for breaking them. The Personal Agent Protocol draft from Sierra and Meta is another take on letting a business decide what customer agents can do. A small store does not need a gateway of its own. It does need clean product data, a clear returns policy for agent orders and a way to tell agent orders apart.

OrchestriAI is not a Walmart partner and has no gateway access. We build systems integration and MCP development work that connects agents to the tools a business already uses, with limits and logs on every action. If you want to know which buying or ordering steps in your business are worth handing to an agent, start with the free automation audit.

OrchestriAI is an independent implementation provider. Product names are used for identification only. OrchestriAI is not affiliated with, endorsed by, or sponsored by Walmart, Sam's Club, Shopify or any other company named here. This article summarizes Walmart's public announcement as of October 22, 2026. Agent Profiles had not launched and the gateway was in beta on that date, so features, terms and timing can change. Check Walmart's pages before you plan around them.