360 check, 9 Nov 2026
Otto on the pay layer: the 360 agent-readiness check
In short
Otto scores 41 of 100 on Ora's agent-readiness scan, a D, read 14 Nov 2026. The six payment checks did not apply to otto.de on this read, which is how Ora treats a site it does not read as a shop. An llms.txt, an Organization block and a sitemap, and no API behind them.
On 14 Nov 2026 the public site at otto.de scored 41 of 100 on Ora's agent-readiness scan, a D. Otto is Germany's second-largest online retailer and the group's marketplace, so this check reads the Payments layer first: the six checks that look for x402, MPP, UCP, ACP and AP2 on the domain, the same protocols this site's matrix tracks row by row. The other layers follow, with every check Ora ran and what it saw.
The score
| Layer | Points | Share | What the layer asks |
|---|---|---|---|
| Discovery | 9 of 13 | 69% | Can agents find and recommend it |
| Access | 22 of 52 | 42% | Can agents read it |
| Usability | 13 of 51 | 25% | Can agents use it |
| Payments | 0 of 0 | none apply | Can agents pay |
| Total | 41 of 100 | 41% | Grade D |
The pay layer
Ora did not run the six payment checks against otto.de on this read: it marks them not applicable on a site it does not read as a shop, so the layer has no maximum and costs nothing. A marketplace that sells online can still publish any of the five protocols; the matrix says which processors and platforms carry each one. Each protocol links to its matrix row, where the processors and platforms that carry it are dated and sourced.
| Payment check | Result | Points | Matrix row | What Ora saw |
|---|---|---|---|---|
| x402 | Does not apply | 0 of 2 | x402 in the matrix | No commerce signals detected - agent-payment protocols are optional for non-commerce sites |
| MPP | Does not apply | 0 of 2 | MPP in the matrix | No commerce signals detected - agent-payment protocols are optional for non-commerce sites |
| UCP | Does not apply | 0 of 3 | UCP in the matrix | No commerce signals detected - agent-payment protocols are optional for non-commerce sites |
| ACP | Does not apply | 0 of 3 | ACP in the matrix | No commerce signals detected - agent-payment protocols are optional for non-commerce sites |
| ACP delegate payment | Does not apply | 0 of 3 | ACP in the matrix | No commerce signals detected - agent-payment protocols are optional for non-commerce sites |
| AP2 | Does not apply | 0 of 3 | AP2 in the matrix | No commerce signals detected - agent-payment protocols are optional for non-commerce sites |
The other layers, check by check
Every check Ora ran on otto.de, grouped by layer, with the result, the points and what Ora recorded where its wording passes this site's gate.
Discovery: 9 of 13
| Check | Result | Points | What Ora saw |
|---|---|---|---|
| ARD discovery | Fail | 0 of 1 | No /.well-known/ard.json, no same-site rel="ard" link, and no legacy /.well-known/ai-catalog.json |
| Developer resource discoverability | Fail | 0 of 3 | In a search for your API docs, none of the 10 results is your official docs |
| Brand name discoverability | Pass | 3 of 3 | otto.de ranks #4 for "OTTO Online Shop" and #6 for "OTTO Shopping" |
| Wikipedia / Wikidata entity presence | Partial | 2 of 4 | Wikidata Q466688 (Otto Group) verified - draft a Wikipedia page with cited references to complete knowledge graph coverage |
| robots.txt AI crawler policy | Pass | 2 of 2 | AI search crawlers: allowed in 3 of 3 checks (3 crawlers on 1 page). AI training crawlers: allowed in 2 of 2 checks (2 crawlers on 1 page), not scored. |
| NPM/PyPI SDK package | Pass | 1 of 1 | Pass, no detail recorded. |
| Agent platform configs | Fail | 0 of 1 | Could not locate a public repo containing agent configs or rules. If our probes missed it, AI coding agents likely will too - link the repo from your homepage or docs so it's discoverable. |
| Agent Plugins manifest | Fail | 0 of 1 | No Agent Plugins manifest (plugin.json) found in discovered repos |
| ChatGPT app listed | Fail | 0 of 2 | Not found in ChatGPT app directory |
| Homepage not hidden from search | Pass | 1 of 1 | No noindex on the homepage: no robots, googlebot or bingbot meta tag and no X-Robots-Tag header hides it from search. |
Access: 22 of 52
| Check | Result | Points | What Ora saw |
|---|---|---|---|
| Sitemap exists | Pass | 2 of 2 | Valid sitemap found at https://www.otto.de/category-sitemap/sitemap_index.xml.gz with multiple sitemaps entries |
| Content without JavaScript | Partial | 2 of 3 | Homepage: 4242 chars with H1, but 2.7% content ratio is below the 5% target. 4 of 4 sampled inner pages have text without JavaScript. |
| Not blocked by bot detection | Pass | 2 of 2 | Site accessible to 4 agent user-agents (ChatGPT-User, OAI-SearchBot, Claude-User, PerplexityBot). |
| Agent discovery file | Fail | 0 of 2 | No agent discovery file found |
| A2A / agent-card | Fail | 0 of 2 | No A2A agent card found at /.well-known/agent-card.json |
| Listed on skills.sh | Pass | 1 of 1 | Pass, no detail recorded. |
| pricing.md exists | Fail | 0 of 2 | No pricing.md found - agents need machine-readable pricing to compare products and make purchase recommendations |
| NLWeb Schema Feeds | Fail | 0 of 1 | No schemamap: directive in robots.txt |
| MCP well-known discovery | Fail | 0 of 2 | No MCP server URL discovered |
| Agent mode view | Fail | 0 of 2 | No agent mode view detected at ?mode=agent (optional) |
| HTTP Link headers (RFC 8288) | Fail | 0 of 1 | No HTTP Link response headers (RFC 8288) found |
| Markdown URL fallback | Fail | 0 of 2 | Homepage does not support the .md suffix. Probed https://otto.de/index.md and it did not return markdown (expected text/markdown content-type or a heading-led non-HTML body). |
| Modular llms.txt per product area | Fail | 0 of 1 | No section-level llms.txt found. Tried /docs/llms.txt, /api/llms.txt, /developers/llms.txt, /guides/llms.txt, /reference/llms.txt, /wishlist-view/llms.txt, /babys/llms.txt, /buerobedarf/llms.txt, /camping/llms.txt, /dekoration/llms.txt. |
| Sitemap freshness (lastmod) | Fail | 0 of 1 | None of the 500 sampled sitemap entries carries a lastmod date. Add <lastmod> (W3C datetime) so agents can prioritize fresh content. |
| robots.txt agent-user policy | Pass | 2 of 2 | No applicable crawl or usage restriction found for 3 user-triggered agents (chatgpt-user, claude-user, perplexity-user) on 1 public page: https://otto.de/. Declared policy only |
| llms.txt exists | Pass | 1 of 1 | Found the llms.txt at https://otto.de/llms.txt. |
| llms.txt formatting | Pass | 2 of 2 | The llms.txt is well-formatted: 150 lines with markdown links, 14,947 characters in total. |
| JSON-LD structured data | Partial | 2 of 4 | JSON-LD Organization found - missing description on this entity |
| Pricing info accessible | Fail | 0 of 3 | No pricing page or pricing data found |
| Public API/docs linked from homepage | Fail | 0 of 3 | No public API or documentation page linked from homepage |
| Agent instruction / when-to-use | Fail | 0 of 3 | No agent instruction file with when-to-use guidance found |
| Skills.sh skill quality | Partial | 0 of 2 | Minimal skills.sh presence - 1 skill, 1 installs. Too thin for agents to understand capabilities |
| JSON-LD entity linking (sameAs) | Partial | 1 of 2 | Entity linking to linkedin.com - add more authority profiles (Wikipedia, Wikidata, LinkedIn, GitHub) |
| Metadata completeness | Partial | 1 of 2 | 2/4 metadata signals present - missing: og:image, og:type |
| Organization schema completeness | Partial | 1 of 2 | Organization schema found but missing: contactPoint, address |
| Schema type breadth | Fail | 0 of 2 | No extended schema types found - AI can only answer basic questions about this entity |
| Trust anchor pages | Fail | 0 of 2 | No trust anchor pages found with sufficient content (About, Contact, Privacy) |
| llms.txt links resolve | Fail | 0 of 2 | 5 of 5 probed llms.txt links do not resolve: https://www.otto.de/damen/, https://www.otto.de/damen/mode/, https://www.otto.de/damen/schuhe/, https://www.otto.de/damen/taschen/, and https://www.otto.de/damen/accessoires/. |
| Markdown alternate link | Fail | 0 of 1 | No sampled page advertises a markdown alternate. Add <link rel="alternate" type="text/markdown" href="..."> (or the equivalent Link response header) pointing at a markdown twin of the page. |
| Redirect hygiene | Pass | 1 of 1 | Pass, no detail recorded. |
| Page token budget | Pass | 1 of 1 | All 5 measured pages fit an agent context budget (largest ~6K tokens) |
| Code fence validity | Pass | 1 of 1 | Pass, no detail recorded. |
| Content behind auth | Pass | 2 of 2 | All 4 sampled pages are publicly readable (4 with substantive content) |
| OpenAPI spec published | Fail | 0 of 7 | No OpenAPI/Swagger specification found |
| API catalog (RFC 9727) | Fail | 0 of 2 | No /.well-known/api-catalog found (RFC 9727) |
| Markdown agent docs | Fail | 0 of 1 | Missing markdown content negotiation. Homepage returned text/html when probed with Accept: text/markdown (expected text/markdown), and none of the well-known root paths (/llms.md, /auth.md, /agents.md, /developers.md |
| Markdown content negotiation (acceptmarkdown.com) | Fail | 0 of 1 | Homepage https://otto.de does not meet the Markdown negotiation requirements: Accept: text/markdown returned text/html; Vary header missing Accept (got "accept-encoding") |
| 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. |
| Agent crawler reachability | Pass | 2 of 2 | Reachable to every agent we tested - ChatGPT-User: reachable, OAI-SearchBot: reachable, Claude-User: reachable, PerplexityBot: reachable |
Usability: 13 of 51
| Check | Result | Points | What Ora saw |
|---|---|---|---|
| Public API with reachable endpoints | Fail | 0 of 7 | No publicly reachable API surface detected (REST and GraphQL both absent or auth-gated) |
| OAuth 2.0 support | Fail | 0 of 5 | No OAuth 2.0 or OpenID Connect support detected |
| Scoped permissions | Fail | 0 of 5 | No declared OAuth scopes, security schemes, or scoped-permission documentation found |
| Agent onboarding friction | Partial | 1 of 2 | Onboarding signals described but not verified live: self-serve key generation, sandbox/test environment |
| Web Bot Auth directory | Fail | 0 of 2 | No /.well-known/http-message-signatures-directory found |
| OAuth Protected Resource metadata (RFC 9728) | Fail | 0 of 2 | No /.well-known/oauth-protected-resource found (RFC 9728) |
| auth.md exists | Fail | 0 of 2 | No /auth.md found at site root |
| auth.md structure | Fail | 0 of 2 | No /auth.md found at site root |
| Agent auth discovery metadata | Fail | 0 of 3 | Neither /.well-known/oauth-protected-resource nor /.well-known/oauth-authorization-server found. Probed: otto.de, api.otto.de. |
| Agent auth WWW-Authenticate hint | Fail | 0 of 1 | No 401 with WWW-Authenticate: Bearer resource_metadata=... found. Probed [https://otto.de/api, https://otto.de/api/v1, https://otto.de/v1, https://otto.de/v2, https://otto.de/agent/identity, https://otto.de/agent/auth |
| agent_auth endpoints reachable | Fail | 0 of 2 | No agent_auth endpoint URIs found in AS metadata or /auth.md prose; nothing to probe |
| MCP server / manifest | Fail | 0 of 6 | No MCP server or manifest found |
| WebMCP support | Fail | 0 of 5 | No WebMCP support detected - no document.modelContext / navigator.modelContext usage found (scanned 25 of 25 same-origin script bundle(s) for modelContext registrations) |
| JSON error responses | Pass | 4 of 4 | Pass, no detail recorded. |
| NLWeb /ask endpoint | Fail | 0 of 1 | No NLWeb-conformant /ask endpoint found via GET or POST |
| NLWeb streaming support | Fail | 0 of 1 | NLWeb /ask does not support SSE streaming via GET or POST |
| MCP server-card.json | Fail | 0 of 2 | No MCP server card found (checked /.well-known/mcp/server-card.json, the site's ai-catalog.json, servers[].card in mcp.json, and <server>/server-card) |
| Product + docs MCP coverage | Fail | 0 of 2 | This bonus needs two MCP servers: one for your product so agents can take actions, and a separate one for your documentation so agents can answer questions from your docs. |
| Sandbox / test environment | Fail | 0 of 2 | No sandbox or test environment found |
| Agent-friendly 404s | Partial | 1 of 2 | The nonexistent path https://otto.de/__ora-404-probe-c98wvynn correctly returns HTTP 404. Partial credit: no Markdown error body was detected. |
| Native interactive controls | Pass | 3 of 3 | Pass, no detail recorded. |
| Accessible names on controls | Pass | 2 of 2 | Pass, no detail recorded. |
| Accessibility-tree injection safety (bonus) | Pass | 2 of 2 | Pass, no detail recorded. |
| MCP Apps support | Fail | 0 of 4 | No MCP Apps support detected - this product has an in-agent UI surface but exposes no ui:// resources or tool UI metadata for agents to render. |
| A2UI / generative UI support | Fail | 0 of 2 | No A2UI or generative UI support detected |
| API schema complexity analysis | Fail | 0 of 2 | No API schema detected |
| Function calling compatibility | Fail | 0 of 2 | No API spec found - function calling requires discoverable endpoints |
The fixes worth most points
Ora attaches an estimate to each failing or partial check: how many points the site would gain by passing it. These are the 5 with the largest estimates for Otto.
- Public API with reachable endpoints
- Fail, 0 of 7, about 6.1 points to gain. Ora saw:
No publicly reachable API surface detected (REST and GraphQL both absent or auth-gated)
. - MCP server / manifest
- Fail, 0 of 6, about 5.2 points to gain. Ora saw:
No MCP server or manifest found
. - Developer resource discoverability
- Fail, 0 of 3, about 5.1 points to gain. Ora saw:
In a search for your API docs, none of the 10 results is your official docs
. - OpenAPI spec published
- Fail, 0 of 7, about 4.5 points to gain. Ora saw:
No OpenAPI/Swagger specification found
. - OAuth 2.0 support
- Fail, 0 of 5, about 4.4 points to gain. Ora saw:
No OAuth 2.0 or OpenID Connect support detected
.
Our read
Otto is the one retailer in this batch whose reading layer is close to complete: an llms.txt at otto.de/llms.txt, a JSON-LD Organization block that lacks only its description, a valid sitemap index, a door open to all four agent user agents, robots.txt permitting the search and training crawlers. The home page gives 3,765 characters with an H1 at a 2.9 percent text ratio, the one reading row that falls short. Ora read no commerce signals on the largest online retailer in Germany after Amazon, so the six payment checks did not apply on this read. The act layer is the D, and it is empty: no publicly reachable API, and neither a developer portal nor an OpenAPI specification, neither an MCP server nor OAuth discovery. The brand search placed otto.de third for OTTO Online Shop, and Ora matched the Wikidata item for the Otto Group without a Wikipedia article. A shop that has written for agents, and given them no way to buy.
Test your own checkout
The scan above is free and needs no account: enter a domain at ora.ai and read the same layers for your own site, with the six payment checks mapped to this matrix on the Ora Payments page. The command below runs the same audit from a terminal and exits with 1 under the score you set, so it can gate a deploy. Why Ora, and its limits.
npx ax@0.10 audit https://example.com --min-score 70All 360 checks, one company a day. Corrections to the corrections page.
Sources
- ora.ai/api/score/otto.de, Ora's scan (vendor), read 14 Nov 2026
- Ora's scoring rules, version 2 (vendor), read 14 Nov 2026
- Ora check catalog (GET /api/checks), read 14 Nov 2026
- otto.de, the company's site, read 14 Nov 2026
Last reviewed