--- title: "Inditex: the 360 check | Agent Ready Checklist" description: "Inditex on Ora's agent-readiness scan, read 2026-11-09: 46 of 100, grade D. 3 of 19 checklist rows met, 10 not met. One company a day." canonical: https://agentreadychecklist.com/blog/inditex-agent-readiness site: "Agent Ready Checklist" last_updated: 2026-11-09 date: 2026-11-09 section: "360 checks" --- # Inditex: the 360 check | Agent Ready Checklist > Inditex on Ora's agent-readiness scan, read 2026-11-09: 46 of 100, grade D. 3 of 19 checklist rows met, 10 not met. One company a day. Source: https://agentreadychecklist.com/blog/inditex-agent-readiness Site: Agent Ready Checklist Last reviewed: 2026-11-09 Agent endpoints: https://agentreadychecklist.com/llms.txt (index), https://agentreadychecklist.com/openapi.json (API), https://agentreadychecklist.com/mcp (MCP server), https://agentreadychecklist.com/ask (search) Access: https://agentreadychecklist.com/auth.md (no key). Pricing: https://agentreadychecklist.com/pricing.md (free). # Inditex against the checklist: the 360 agent-readiness check 360 check, 9 November 2026. Inditex is the owner of Zara and the world's largest fashion retailer. Inditex scores 46 of 100 on Ora's agent-readiness scan, a D, read 9 November 2026. At the door, site accessible to 4 agent user-agents (ChatGPT-User, OAI-SearchBot, Claude-User, PerplexityBot). 3 of the 19 checklist rows with an Ora check are met. A developer portal on another host; three files HTML or missing on this one. On 9 November 2026 the public site at inditex.com scored **46 of 100** on [Ora's](https://ora.ai/?utm_source=agentreadychecklist.com&utm_medium=referral&utm_campaign=check) agent-readiness scan, a D. Ora probes a site the way an agent would: it requests pages with the agents' own user agents, reads robots.txt, looks for the files agents read, and tries the API, MCP and payment surfaces. Below, each of the 31 checklist rows is read against the Ora checks the [crosswalk](https://agentreadychecklist.com/checklist/ora-checks/) names for it, so the result says which requirements this company meets, not only how many points it scored. Ora's one-line summary: Turns agents away at the door: no OpenAPI spec, no MCP server, and no JSON-LD or sitemap to read. ## The score | Layer | Points | Share | What the layer asks | | --- | --- | --- | --- | | Discovery | 11 of 15 | 73% | Can agents find and recommend it | | Access | 20 of 52 | 38% | Can agents read it | | Usability | 19.5 of 50 | 39% | Can agents use it | | Payments | 0 of 0 | none apply | Can agents pay | | Total | 46 of 100 | 46% | Grade D | ## Row by row A row is met when every Ora check the crosswalk names for it passes, not met when every one fails, and partly when the checks disagree or one is partial. A row with no Ora check in the catalogue, or whose checks did not apply to this site, is marked as such; the [Verify Kit](https://agentreadychecklist.com/kit/) tests those by hand. | Row | Level | Result | Ora checks, and what Ora saw | | --- | --- | --- | --- | | AR-FIND-01; Do not block agents | MUST | Partly | robots.txt AI crawler policy (partial), robots.txt agent-user policy (not applicable), Agent crawler reachability (pass), Not blocked by bot detection (pass).; robots.txt answered an HTML page instead of rules. Crawlers find no rules in it and read the whole site, so your AI crawler policy is not stated. Serve a plain-text robots.txt | | AR-FIND-02; Answers on one first-party page | SHOULD | No Ora check | No check in Ora's catalogue names this row. | | AR-FIND-03; Sitemap listed in robots.txt | SHOULD | Not met | Sitemap exists (fail).; No sitemap found | | AR-FIND-04; AI Catalog at .well-known | MAY | Partly | AI Catalog discovery (partial), ARD discovery (partial).; /.well-known/ai-catalog.json exists but is not valid JSON | | AR-READ-01; Answer in the initial HTML | MUST | Partly | Content without JavaScript (partial).; Homepage: 1585 chars with H1, but heading hierarchy skips H1 to H4; 2.1% content ratio is below the 5% target. Sampled pages with almost no text without JavaScript (1 of 5):. | | AR-READ-02; Real HTTP status codes | MUST | Met | Redirect hygiene (pass).; Redirect hygiene: pass, 1 of 1. | | AR-READ-03; Home page with real links | SHOULD | Met | Public API/docs linked from homepage (pass).; Documentation site found at https://developer.inditex.com | | AR-READ-04; Docs that answer agent tasks | SHOULD | No Ora check | No check in Ora's catalogue names this row. | | AR-READ-05; Fenced, language-tagged code | SHOULD | No Ora check | Code fence validity (not applicable). | | AR-READ-06; Link the discovery files | SHOULD | No Ora check | No check in Ora's catalogue names this row. | | AR-READ-07; Ship llms.txt | SHOULD | Partly | llms.txt exists (partial), llms.txt formatting (fail), llms.txt links resolve (not applicable).; A file is present at https://inditex.com/.well-known/llms.txt, but it returns an HTML page rather than a plain-text llms.txt. | | AR-READ-08; JSON-LD on key pages | SHOULD | Not met | JSON-LD structured data (fail).; No JSON-LD structured data found on homepage | | AR-READ-09; Advertise a markdown mirror | MAY | Not met | Markdown alternate link (fail).; No sampled page advertises a markdown alternate. Add (or the equivalent Link response header) pointing at a markdown twin of the page. | | AR-READ-11; Pricing as first-party HTML | SHOULD | No Ora check | Pricing info accessible (not applicable). | | AR-ACT-01; Auth an agent can finish | SHOULD | No Ora check | OAuth 2.0 support (not applicable), Scoped permissions (not applicable). | | AR-ACT-02; OpenAPI contract | SHOULD | Not met | OpenAPI spec published (fail).; No OpenAPI/Swagger specification found | | AR-ACT-03; MCP over Streamable HTTP | SHOULD | Not met | MCP server / manifest (fail), Listed in MCP registries (not applicable), MCP PKCE S256 support (not applicable), MCP OAuth metadata (not applicable).; No MCP server or manifest found | | AR-ACT-04; MCP server card | MAY | Not met | MCP server-card.json (fail).; 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-card) | | AR-ACT-05; MCP Apps view | MAY | No Ora check | MCP Apps support (not applicable). | | AR-ACT-06; SDKs and a CLI | SHOULD | Met | CLI tool available (pass), Multi-language SDK packages (not applicable), NPM/PyPI SDK package (pass).; CLI package found on npm: create-weave-backend-app | | AR-ACT-07; WebMCP tools | SHOULD | Not met | WebMCP support (fail).; No WebMCP support detected - no document.modelContext / navigator.modelContext usage found (scanned 14 of 14 same-origin script bundle(s) for modelContext registrations) | | AR-ACT-08; Agent payments | MAY | No Ora check | x402 payment protocol (not applicable), MPP payment protocol (not applicable), UCP - Universal Commerce Protocol (not applicable), ACP - Agentic Commerce Protocol (not applicable), ACP delegate payment (not applicable). | | AR-ACT-09; NLWeb /ask endpoint | MAY | Not met | NLWeb /ask endpoint (fail).; No NLWeb-conformant /ask endpoint found via GET or POST | | AR-ACT-10; An MCP server or a CLI | MUST | Partly | MCP server / manifest (fail), CLI tool available (pass).; No MCP server or manifest found | | CF-CONTENT-SIGNALS; Content-Signal line | cloudflare | No Ora check | No check in Ora's catalogue names this row. | | CF-MARKDOWN-NEGOTIATION; Markdown by Accept | cloudflare | Not met | Markdown content negotiation (acceptmarkdown.com) (fail), Markdown agent docs (fail).; Homepage https://inditex.com does not meet the Markdown negotiation requirements: Accept: text/markdown returned text/html; charset=utf-8; Vary header missing Accept (got "accept-encoding") | | CF-PAY-PER-CRAWL; Pay per crawl, HTTP 402 | cloudflare | No Ora check | No check in Ora's catalogue names this row. | | CF-OAUTH-DISCOVERY; OAuth discovery files | cloudflare | No Ora check | OAuth Protected Resource metadata (RFC 9728) (not applicable). | | CF-AGENT-SKILLS; Agent Skills index | cloudflare | No Ora check | Agent Skills index conformance (v0.2.0) (not applicable). | | VERCEL-NEGOTIATION-HEADERS; Markdown headers | vercel | Not met | Markdown content negotiation (acceptmarkdown.com) (fail).; Homepage https://inditex.com does not meet the Markdown negotiation requirements: Accept: text/markdown returned text/html; charset=utf-8; Vary header missing Accept (got "accept-encoding") | | VERCEL-ROBOTS-EXCLUSIONS; Robots exclusions | vercel | Partly | robots.txt AI crawler policy (partial), robots.txt agent-user policy (not applicable).; robots.txt answered an HTML page instead of rules. Crawlers find no rules in it and read the whole site, so your AI crawler policy is not stated. Serve a plain-text robots.txt | ## 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 Inditex, each tied to the checklist row whose recipes cover it. MCP server / manifest Fail, 0 of 6, about 5.3 points to gain. Ora saw: No MCP server or manifest found. Row [AR-ACT-03](https://agentreadychecklist.com/checklist/ar-act-03/), MCP over Streamable HTTP. OpenAPI spec published Fail, 0 of 7, about 4.5 points to gain. Ora saw: No OpenAPI/Swagger specification found. Row [AR-ACT-02](https://agentreadychecklist.com/checklist/ar-act-02/), OpenAPI contract. WebMCP support Fail, 0 of 5, about 4.4 points to gain. Ora saw: No WebMCP support detected - no document.modelContext / navigator.modelContext usage found (scanned 14 of 14 same-origin script bundle(s) for modelContext registrations). Row [AR-ACT-07](https://agentreadychecklist.com/checklist/ar-act-07/), WebMCP tools. Brand name discoverability Partial, 1 of 3, about 3 points to gain. Ora saw: inditex.com ranks #7 for "INDITEX" (searched your brand name alone: no main product term from your homepage qualified). No checklist row names this check. GraphQL typed error model Fail, 0 of 3, about 2.7 points to gain. Ora saw: GraphQL introspection auth-gated and no typed graphql error model documentation found on GraphQL-tagged pages. No checklist row names this check. ## Our read Inditex is the owner of Zara and runs a real developer portal at developer.inditex.com, and the corporate domain tells an agent almost none of that. The door is open to all four test agents, but robots.txt answers with an HTML page instead of rules, so crawlers read the whole site by default and the policy row cannot be met; the llms.txt at /.well-known/llms.txt is an HTML page too, there is no sitemap, and the home page carries no JSON-LD. The page itself gives 1,585 characters with an H1 at a 2.1 percent content ratio, with a heading order that skips from H1 to H4. The portal documents an API that Ora could not verify as a machine-readable surface, no OpenAPI specification is published, and the OpenID discovery probe at auth.inditex.com was answered 403 by a bot shield. The world's largest fashion retailer has the developer work done on another host; on this one, three files are the wrong format or missing. ## Verify your own site The scan above is free and needs no account: enter a domain at [ora.ai](https://ora.ai/?utm_source=agentreadychecklist.com&utm_medium=referral&utm_campaign=check) and read the same four layers for your own site, then take each failing row to its recipe on this site. 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. Payments did not apply to this company; a site that sells is read on that layer too. [Why Ora, and its limits](https://agentreadychecklist.com/verify-with-ora/). ```bash npx ax@0.10 audit https://example.com --min-score 70 ``` [All 360 checks](https://agentreadychecklist.com/blog/), one company a day. Corrections to [the corrections page](https://agentreadychecklist.com/corrections/). ## Sources - [ora.ai/api/score/inditex.com, Ora's scan (vendor)](https://ora.ai/api/score/inditex.com?utm_source=agentreadychecklist.com&utm_medium=referral&utm_campaign=check)read 2026-11-09 - [Ora's scoring rules, version 2 (vendor)](https://ora.ai/api/ranker/releases/2/rules?utm_source=agentreadychecklist.com&utm_medium=referral&utm_campaign=check)read 2026-11-09 - [ora.ai/api/checks, contract 1.38.0 (vendor)](https://ora.ai/api/checks?utm_source=agentreadychecklist.com&utm_medium=referral&utm_campaign=check)read 2026-11-05 - [inditex.com, the company's site](https://www.inditex.com/itxcomweb/es/en/home)read 2026-11-09 Edition Data 2026-11-04 Reviewed 2026-11-05 Spec AgentReady v2.0, 273d2d7 Crawl 13,071 rows, 2026-11-04 Ora 132 checks, contract 1.38.0, 2026-11-05 Verify with Ora The scanner this site recommends for the whole checklist. 132 checks, a score out of 100, no account. `npx ax@0.10 audit --min-score ` [Why Ora, and its limits](https://agentreadychecklist.com/verify-with-ora/) Method - [How rows, commands and rates are made](https://agentreadychecklist.com/method/) - [How an Ora check is matched to a row](https://agentreadychecklist.com/checklist/ora-checks/) - [Pass rates by rank band](https://agentreadychecklist.com/data/by-rank/) Sources and read dates sit at the foot of the page. Last reviewed 2026-11-09. AgentReady v2.0, read 2026-11-04.