360 check, 10 Nov 2026
IKEA on the pay layer: the 360 agent-readiness check
IKEA scores 47 of 100 on Ora's agent-readiness scan, a D, read 14 Nov 2026. The six payment checks did not apply to ikea.com on this read, which is how Ora treats a site it does not read as a shop. UCP at .well-known/ucp scores the pay layer 3 of 3; the act layer is empty.
On 14 Nov 2026 the public site at ikea.com scored 47 of 100 on Ora's agent-readiness scan, a D, in Ora's E-commerce category. IKEA is the Swedish furniture retailer, selling online in more than 60 markets, 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. Ora's one-line summary: Turns agents away at the door: no WebMCP or MCP Apps support, no llms.txt.
The score
| Layer | Points | Share | What the layer asks |
|---|---|---|---|
| Discovery | 5 of 6 | 83% | Can agents find and recommend it |
| Access | 15.83 of 26 | 61% | Can agents read it |
| Usability | 1 of 14 | 7% | Can agents use it |
| Payments | 3 of 3 | 100% | Can agents pay |
| Total | 47 of 100 | 47% | Grade D |
The pay layer
Ora did not run the six payment checks against ikea.com 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 retailer 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 | Not required: An agent wallet checkout already gives agents a way to pay, and one is enough (UCP checkout declares wallet handlers an agent can pay with (com.google.pay)) |
| MPP | Does not apply | 0 of 2 | MPP in the matrix | Not required: An agent wallet checkout already gives agents a way to pay, and one is enough (UCP checkout declares wallet handlers an agent can pay with (com.google.pay)) |
| UCP | Does not apply | 0 of 3 | UCP in the matrix | Not required: An agent wallet checkout already gives agents a way to pay, and one is enough (UCP checkout declares wallet handlers an agent can pay with (com.google.pay)). |
| ACP | Does not apply | 0 of 3 | ACP in the matrix | Not required: An agent wallet checkout already gives agents a way to pay, and one is enough (UCP checkout declares wallet handlers an agent can pay with (com.google.pay)) |
The other layers, check by check
Every check Ora ran on ikea.com, grouped by layer, with the result, the points and what Ora recorded where its wording passes this site's gate.
Discovery: 5 of 6
| 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 |
| Brand name discoverability | Pass | 3 of 3 | ikea.com ranks #5 for "IKEA" (searched your brand name alone: no main product term from your homepage qualified) |
| robots.txt AI crawler policy | Pass | 1 of 1 | 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. |
| 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: 15.83 of 26
| Check | Result | Points | What Ora saw |
|---|---|---|---|
| Sitemap exists | Pass | 1 of 1 | Valid sitemap found at https://www.ikea.com/sitemaps/sitemap.xml with multiple sitemaps entries |
| Content without JavaScript | Partial | 3.33 of 5 | Homepage: 4292 chars with H1, but 4.0% content ratio is below the 5% target. 1 of 1 sampled inner page has text without JavaScript (4 skipped). |
| 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 | Fail | 0 of 1 | No official skills self-published on skills.sh (27 community skills with potential relation to this domain found, but only self-published official skills count) |
| 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 |
| 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://ikea.com/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. This is a bonus check: it can add a point and never costs one. |
| robots.txt agent-user policy | Pass | 1 of 1 | No applicable crawl or usage restriction found for 3 user-triggered agents (chatgpt-user, claude-user, perplexity-user) on 1 public page: https://ikea.com/. Declared policy only |
| llms.txt exists | Fail | 0 of 1 | No llms.txt found at https://ikea.com/llms.txt. Publish it at the site root, where agents that follow the llms.txt spec look for it. |
| llms.txt formatting | Fail | 0 of 2 | No llms.txt found to evaluate quality |
| JSON-LD structured data | Pass | 2 of 2 | Rich JSON-LD identity: Organization with name, description, url, and sameAs/logo/address (1 block(s)) |
| Pricing info accessible | Fail | 0 of 3 | No pricing page or pricing data found |
| Agent instruction / when-to-use | Fail | 0 of 1 | No agent instruction file with when-to-use guidance found |
| Skills.sh skill quality | Fail | 0 of 2 | No official skills on skills.sh to evaluate |
| JSON-LD entity linking (sameAs) | Partial | 0.5 of 1 | Entity linking to linkedin.com - add more authority profiles (Wikipedia, Wikidata, LinkedIn, GitHub) |
| Metadata completeness | Pass | 1 of 1 | All metadata signals present: canonical URL, lang="en", og:image, og:type |
| Organization schema completeness | Partial | 0.5 of 1 | Organization schema found but missing: contactPoint |
| Trust anchor pages | Partial | 0.5 of 1 | Contact, Privacy pages verified - missing: About |
| 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 6 measured pages fit an agent context budget (largest ~1K tokens) |
| Content starts near the top | Pass | 1 of 1 | Pass, no detail recorded. |
| Content behind auth | Pass | 1 of 1 | All 5 sampled pages are publicly readable (5 with substantive content) |
| 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://ikea.com does not meet the Markdown negotiation requirements: Accept: text/markdown returned text/html; charset=utf-8; Vary header missing Accept (got "origin, 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 | 1 of 1 | Reachable to every agent we tested - ChatGPT-User: reachable, OAI-SearchBot: reachable, Claude-User: reachable, PerplexityBot: reachable |
Usability: 1 of 14
| Check | Result | Points | What Ora saw |
|---|---|---|---|
| Web Bot Auth directory | Fail | 0 of 2 | No /.well-known/http-message-signatures-directory found |
| 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: ikea.com, api.ikea.com. |
| Agent auth WWW-Authenticate hint | Fail | 0 of 1 | No 401 with WWW-Authenticate: Bearer resource_metadata=... found. Probed [https://ikea.com/api, https://ikea.com/api/v1, https://ikea.com/v1, https://ikea.com/v2, https://ikea.com/agent/identity, https://ikea.com/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 |
| WebMCP support | Fail | 0 of 8 | No WebMCP support detected - no document.modelContext / navigator.modelContext usage found (scanned 10 of 10 same-origin script bundle(s) for modelContext registrations) |
| 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. |
| Agent-friendly 404s | Partial | 1 of 2 | The nonexistent path https://ikea.com/__ora-404-probe-isgag181 correctly returns HTTP 404. Partial credit: no Markdown error body was detected. |
| Accessible document structure | Pass | 3 of 3 | Pass, no detail recorded. |
| 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 |
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 IKEA.
- WebMCP support
- Fail, 0 of 8, about 16 points to gain. Ora saw:
No WebMCP support detected - no document.modelContext / navigator.modelContext usage found (scanned 10 of 10 same-origin script bundle(s) for modelContext registrations)
. - MCP Apps support
- Fail, 0 of 4, about 8 points to gain. Ora saw:
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
. - Product + docs MCP coverage
- Fail, 0 of 2, about 4 points to gain. Ora saw:
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
. - Pricing info accessible
- Fail, 0 of 3, about 3.5 points to gain. Ora saw:
No pricing page or pricing data found
. - ARD discovery
- Fail, 0 of 1, about 3.3 points to gain. Ora saw:
No /.well-known/ard.json, no same-site rel="ard" link, and no legacy /.well-known/ai-catalog.json
.
Our read
IKEA's pay layer is the thing that turns this read. Ora found a UCP discovery profile at ikea.com/.well-known/ucp, version 2026-04-08, declaring the checkout and fulfillment capabilities, so UCP passes at 3 of 3 and the other five payment checks are marked not required, since one protocol is sufficient. The door matches: all four test agents reached the home page, robots.txt allows every AI crawler checked, and no restriction applies to the user-triggered agents. The reading layer is middling, a home page of 4,843 characters with an H1 at a 3.5 percent content ratio, a valid sitemap index, complete metadata and a full Organization block with description, url, logo and address, but no llms.txt. The act layer is the gap: neither an API nor an MCP server, OAuth is absent, and WebMCP is missing from all 10 script bundles, the single fix worth about 12 points. A B at 71 that an agent can pay through but cannot yet operate.
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/ikea.com, Ora's scan (vendor), read 14 Nov 2026
- Ora's scoring rules, version 3 (vendor), read 14 Nov 2026
- Ora check catalog (GET /api/checks), read 14 Nov 2026
- ikea.com, the company's site, read 14 Nov 2026
Last reviewed