Kroger: 20 of 100 on Ora's agent-readiness scan
In short
Kroger scores 20 of 100 on Ora's agent-readiness scan, grade F, read on 9 November 2026. 9 percent of the 132,085 domains Ora ranks score under 20, and the average score is 44. A home page that would not open, scored on denominators of 29 and 7.
The score
Kroger is a supermarket chain based in Cincinnati.
- 20of 100, grade FOra's agent-readiness scan of kroger.com, read 9 November 2026.
- 10Discovery, of 11Whether assistants find the company: search presence, Wikipedia and Wikidata, catalogues.
- 0Access, of 29Whether they can read it: the door, text without JavaScript, llms.txt, structured data.
- 0Usability, of 7Whether they can act through it: an MCP server, an API with a specification, sign-in for agents.
- 0Payments, of 0No check in this layer applied to the site.
9 percent of the 132,085 domains Ora ranks score under 20, and the average score is 44.
Ora's one-line summary: Kroger offers strong developer resource discoverability, but lacks WebMCP support implementation.
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.
| Check | Result | What Ora saw |
|---|---|---|
| Not blocked by bot detection | error, 0 of 2 | Could not test bot user agents |
| Agent crawler reachability | Did not apply, 0 of 2 | Can't verify crawler reachability. A bot shield, rate limit, or timeout stopped our test request. Real crawlers come from their own networks and may get through. |
| robots.txt AI crawler policy | Did not apply, 0 of 2 | Cannot verify robots.txt permission for search crawlers: fetch unavailable |
| robots.txt agent-user policy | Did not apply, 0 of 2 | Cannot verify robots.txt permission for user-triggered agents: fetch unavailable |
| Content without JavaScript | error, 0 of 3 | Could not fetch homepage |
| Homepage not hidden from search | Did not apply, 0 of 1 | Homepage not read - cannot tell whether it is hidden from search |
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.
| Check | Result | What Ora saw |
|---|---|---|
| llms.txt exists | Fail, 0 of 1 | No llms.txt found at /llms.txt or /.well-known/llms.txt. |
| llms.txt formatting | Fail, 0 of 2 | No llms.txt found to evaluate quality |
| Markdown agent docs | error, 0 of 1 | Could not fetch with Accept: text/markdown |
| Bot-UA markdown serving | Fail, 0 of 1 | No probed bot User-Agent (ChatGPT-User, Claude-User, Perplexity-User) receives markdown when requesting HTML. Optional: detect AI-bot UAs server-side and serve them a markdown representation directly. |
| JSON-LD structured data | error, 0 of 4 | Could not fetch homepage |
| Organization schema completeness | error, 0 of 2 | Could not fetch homepage |
| Sitemap exists | Fail, 0 of 2 | No sitemap found |
| Metadata completeness | error, 0 of 2 | Could not fetch homepage |
| Page token budget | Did not apply, 0 of 1 | Nothing sampled to measure |
| Check | Result | What Ora saw |
|---|---|---|
| MCP server / manifest | Did not apply, 0 of 6 | No MCP server or manifest found |
| MCP well-known discovery | Fail, 0 of 2 | No MCP server URL discovered |
| Public API with reachable endpoints | Did not apply, 0 of 7 | No publicly reachable API surface detected (REST and GraphQL both absent or auth-gated) |
| Public API/docs linked from homepage | Did not apply, 0 of 3 | No public API or documentation page linked from homepage |
| OpenAPI spec published | Did not apply, 0 of 7 | No OpenAPI/Swagger specification found |
| Developer portal | Did not apply, 0 of 6 | No developer portal found |
| OAuth 2.0 support | Did not apply, 0 of 5 | No OAuth 2.0 or OpenID Connect support detected |
| Scoped permissions | Did not apply, 0 of 5 | No declared OAuth scopes, security schemes, or scoped-permission documentation found |
| Multi-language SDK packages | Did not apply, 0 of 3 | No SDK packages found across language ecosystems |
| CLI tool available | Did not apply, 0 of 3 | No CLI tool found |
| WebMCP support | Fail, 0 of 5 | No WebMCP support detected - no document.modelContext / navigator.modelContext usage found |
| Check | Result | What Ora saw |
|---|---|---|
| Wikipedia / Wikidata entity presence | Pass, 4 of 4 | Wikipedia "Kroger" and Wikidata Q153417 both verified - domain confirmed on both sources |
| Brand name discoverability | Pass, 3 of 3 | kroger.com ranks #3 for "kroger" |
| Category share of voice | Did not apply, 0 of 6 | Category share of voice is in beta. It measures whether agents surface you for capability and use-case searches (not just your name). |
| Developer resource discoverability | Pass, 3 of 3 | Agent discovered 2 developer-resource types by name (API docs, developer portal) across 3 pages |
The six payment checks did not apply on this read: Ora did not read the site as a shop.
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.
- WebMCP support, worth about 31.7 points by Ora's estimate: No WebMCP support detected - no document.modelContext / navigator.modelContext usage found.
- Agent auth discovery metadata, worth about 13.3 points by Ora's estimate: Neither /.well-known/oauth-protected-resource nor /.well-known/oauth-authorization-server found. Probed: kroger.com, api.kroger.com.
- agent_auth endpoints reachable, worth about 9.9 points by Ora's estimate: No agent_auth endpoint URIs found in AS metadata or /auth.md prose; nothing to probe.
Our read
Kroger's 20 is the arithmetic of a read that did not happen. A bot shield, rate limit or timeout stopped Ora's request for the home page, so the bot test could not run and the door, content, policy, structured-data and metadata rows are unverified rather than failed; with no sitemap and no llms.txt either, the Access layer reads 0 of 29. The act layer is empty, with no public API, no developer portal, and neither an MCP server nor OAuth discovery, so the Usability layer reads 0 of 7, and the WebMCP estimate of 31.7 points is large only because the denominators are so small. The Discovery layer is nearly full at 10 of 11: kroger.com ranks third for kroger, and a search found its API documentation and developer portal by name, pages the scan never reached. A grocer whose shoppers send assistants with a list has a site the scan could not open; a home page that answers is the first row, and everything else waits on it.
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 kroger.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.
Sources
- Ora report for kroger.com (ora.ai/score/kroger.com), read 9 Nov 2026. Vendor claim.
Last reviewed