Walmart: 59 of 100 on Ora's agent-readiness scan

The score

Walmart is a retailer and grocer based in Bentonville, Arkansas, with stores in the United States, Mexico, Canada, Chile, China and India.

• 59of 100, grade C
  Ora's agent-readiness scan of walmart.com, read 9 November 2026, listed under E-commerce.
• 12Discovery, of 16
  Whether assistants find the company: search presence, Wikipedia and Wikidata, catalogues.
• 30Access, of 58
  Whether they can read it: the door, text without JavaScript, llms.txt, structured data.
• 46Usability, of 81
  Whether they can act through it: an MCP server, an API with a specification, sign-in for agents.
• 0Payments, of 0
  No check in this layer applied to the site.

60 percent of the 132,085 domains Ora ranks score under 50, and the average score is 44.

Ora's one-line summary: Walmart offers solid public content and bot-accessible robots and sitemap setup, but lacks an OpenAPI specification for agents to call its services.

What an assistant meets at the door

Before an assistant can read, compare or buy, it has to get in. These rows are the door: whether the bot shield lets the main agents through, what robots.txt tells the search, training and user-triggered agents, and whether the home page has text without running JavaScript.

What it can read, and what it can do

The reading layer is what an assistant takes away from the pages: a text file written for it, markdown on request, structured data about the company, a sitemap. The act layer is whether it can do anything through a published interface rather than by clicking through the site.

Ora probed the six payment checks and found no x402, MPP, UCP, ACP or AP2 signal, so the pay layer reads 0 of 0.

Three fixes to hand to the web team

Ora estimates how many points each open check would return. These are the largest on this read, in Ora's words where it gave them, so a leader can hand the list over without translating it.

1. OpenAPI spec published, worth about 4 points by Ora's estimate: No OpenAPI/Swagger specification found.
2. WebMCP support, worth about 2.7 points by Ora's estimate: No WebMCP support detected - no document.modelContext / navigator.modelContext usage found (scanned 1 of 1 same-origin script bundle(s) for modelContext registrations).
3. JSON error responses, worth about 2.2 points by Ora's estimate: API does not return JSON error responses (or no API detected).

Our read

Walmart has built more for agents to act through than any retailer here, and still gives them 1,750 characters to read. All four agent user agents get in, robots.txt allows the crawlers, the sitemap lists 12,720 category pages, the metadata is complete and the Organization block lacks only its description, but the home page's text ratio is 2 percent, one sampled page had almost no text without JavaScript and there is no llms.txt, so the Access layer reads 30 of 58. The act layer is the strongest of the shops here: an MCP server at developer.walmart.com/mcp that requires authentication, OAuth authorization server metadata, REST documentation at /api, a GraphQL endpoint and an SDK on RubyGems, with scopes described in prose and no OpenAPI specification; the Usability layer reads 46 of 81. Ora probed the six payment checks and found no protocol, so the pay layer reads 0 of 0. An OpenAPI specification is the fix with the most points, about 4; the server it would describe is already live.

Test your own site

Run the same scan on your own domain at ora.ai. The score, the layers and the fixes on this page come from its public result for walmart.com; a scan of a public site takes a few minutes and needs no account.

• Scan your domain on OraThe same checks, the same scoring, on your own site.
• The self-check, 18 questionsWhat to ask for, in business terms, before the scan.
• All the 360 checksThe other companies in this series, newest first.