--- title: "ArcelorMittal: the 360 check | Agent Ready Checklist" description: "ArcelorMittal on Ora's agent-readiness scan, read 2026-11-09: 10 of 100, grade F. 1 of 17 checklist rows met, 11 not met." canonical: https://agentreadychecklist.com/blog/arcelormittal-agent-readiness site: "Agent Ready Checklist" last_updated: 2026-11-09 date: 2026-11-09 section: "360 checks" --- # ArcelorMittal: the 360 check | Agent Ready Checklist > ArcelorMittal on Ora's agent-readiness scan, read 2026-11-09: 10 of 100, grade F. 1 of 17 checklist rows met, 11 not met. Source: https://agentreadychecklist.com/blog/arcelormittal-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). # ArcelorMittal against the checklist: the 360 agent-readiness check 360 check, 9 November 2026. ArcelorMittal is the Luxembourg-based steelmaker, the largest outside China. ArcelorMittal scores 10 of 100 on Ora's agent-readiness scan, an F, read 9 November 2026. At the door, agents blocked: GPTBot, ClaudeBot, ChatGPT-User, PerplexityBot, Google-Extended, Applebot-Extended. 1 of the 17 checklist rows with an Ora check is met. 0 of 3 MUST rows are met. Ten points for being on Wikipedia; the site itself refused every agent. On 9 November 2026 the public site at arcelormittal.com scored **10 of 100** on [Ora's](https://ora.ai/?utm_source=agentreadychecklist.com&utm_medium=referral&utm_campaign=check) agent-readiness scan, an F. 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: Wikipedia and Wikidata entity presence, but no OpenAPI specification published. ## The score | Layer | Points | Share | What the layer asks | | --- | --- | --- | --- | | Discovery | 6 of 13 | 46% | Can agents find and recommend it | | Access | 0 of 43 | 0% | Can agents read it | | Usability | 0 of 28 | 0% | Can agents use it | | Payments | 0 of 0 | none apply | Can agents pay | | Total | 10 of 100 | 10% | Grade F | ## 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 (partial), Agent crawler reachability (fail), Not blocked by bot detection (fail).; robots.txt blocked by WAF/bot protection - cannot verify AI crawler policy | | 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 | Not met | AI Catalog discovery (not applicable), ARD discovery (fail).; No /.well-known/ard.json (and no legacy /.well-known/ai-catalog.json) | | AR-READ-01; Answer in the initial HTML | MUST | Partly | Content without JavaScript (partial).; Homepage blocked by WAF/security challenge - content not accessible to agents | | AR-READ-02; Real HTTP status codes | MUST | No Ora check | Redirect hygiene (not applicable). | | AR-READ-03; Home page with real links | SHOULD | Partly | Public API/docs linked from homepage (partial).; Homepage blocked by WAF - cannot check for docs links | | 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 | Not met | llms.txt exists (fail), llms.txt formatting (fail), llms.txt links resolve (not applicable).; No llms.txt found at /llms.txt or /.well-known/llms.txt. | | AR-READ-08; JSON-LD on key pages | SHOULD | Partly | JSON-LD structured data (partial).; Homepage blocked by WAF - cannot check structured data | | AR-READ-09; Advertise a markdown mirror | MAY | No Ora check | Markdown alternate link (not applicable). | | 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 at /.well-known/mcp/server-card.json | | AR-ACT-05; MCP Apps view | MAY | No Ora check | MCP Apps support (not applicable). | | AR-ACT-06; SDKs and a CLI | SHOULD | No Ora check | CLI tool available (not applicable), Multi-language SDK packages (not applicable), NPM/PyPI SDK package (not applicable). | | AR-ACT-07; WebMCP tools | SHOULD | Not met | WebMCP support (fail).; No WebMCP support detected - no tool-attribute forms and no document.modelContext / navigator.modelContext usage found | | 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 | Met | NLWeb /ask endpoint (pass).; NLWeb /ask endpoint exists but requires authentication (HTTP 403, via GET) | | AR-ACT-10; An MCP server or a CLI | MUST | Not met | MCP server / manifest (fail), CLI tool available (not applicable).; 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).; Not acceptmarkdown.com compliant: 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 | Not met | OAuth Protected Resource metadata (RFC 9728) (fail).; No /.well-known/oauth-protected-resource found (RFC 9728) | | 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).; Not acceptmarkdown.com compliant: 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 (partial).; robots.txt blocked by WAF/bot protection - cannot verify AI crawler policy | ## 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 ArcelorMittal, each tied to the checklist row whose recipes cover it. Public API with reachable endpoints Fail, 0 of 7, about 11.1 points to gain. Ora saw: No publicly reachable API surface detected (REST and GraphQL both absent or auth-gated). No checklist row names this check. MCP server / manifest Fail, 0 of 6, about 9.5 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. WebMCP support Fail, 0 of 5, about 7.9 points to gain. Ora saw: No WebMCP support detected - no tool-attribute forms and no document.modelContext / navigator.modelContext usage found. Row [AR-ACT-07](https://agentreadychecklist.com/checklist/ar-act-07/), WebMCP tools. JSON error responses Fail, 0 of 4, about 6.3 points to gain. Ora saw: API does not return JSON error responses (or no API detected). No checklist row names this check. OpenAPI spec published Fail, 0 of 7, about 5.4 points to gain. Ora saw: No OpenAPI/Swagger specification found. Row [AR-ACT-02](https://agentreadychecklist.com/checklist/ar-act-02/), OpenAPI contract. ## Our read ArcelorMittal scores 10, and the whole of it comes from being known: Wikipedia and Wikidata confirm the domain, and the site appears twice in a search for its own name. Nothing else was readable. Ora's probes found GPTBot, ClaudeBot, ChatGPT-User, PerplexityBot, Google-Extended and Applebot-Extended all blocked, and the WAF in front of the site refused even robots.txt, so there is no policy to read and no sitemap to follow. With the home page unreadable, the structured data, the llms.txt and the markdown rows cannot be met whatever the pages contain. The act layer has nothing to show, as a steelmaker's corporate site rarely does. The order of work is unusually clear here: let the agents through, then publish robots.txt and a sitemap, and only then look at anything the checklist asks beyond the door. ## 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/arcelormittal.com, Ora's scan (vendor)](https://ora.ai/api/score/arcelormittal.com?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 - [arcelormittal.com, the company's site](https://corporate.arcelormittal.com/)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.