--- title: "Schneider Electric: the 360 check | Agent Ready Checklist" description: "Schneider Electric on Ora's agent-readiness scan, read 2026-11-09: 27 of 100, grade F. 1 of 12 checklist rows met, 8 not met." canonical: https://agentreadychecklist.com/blog/schneider-electric-agent-readiness site: "Agent Ready Checklist" last_updated: 2026-11-09 date: 2026-11-09 section: "360 checks" --- # Schneider Electric: the 360 check | Agent Ready Checklist > Schneider Electric on Ora's agent-readiness scan, read 2026-11-09: 27 of 100, grade F. 1 of 12 checklist rows met, 8 not met. Source: https://agentreadychecklist.com/blog/schneider-electric-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). # Schneider Electric against the checklist: the 360 agent-readiness check 360 check, 9 November 2026. Schneider Electric is the French energy management and automation group. Schneider Electric scores 27 of 100 on Ora's agent-readiness scan, an F, read 9 November 2026. At the door, bot management challenged ChatGPT-User, OAI-SearchBot, Claude-User, PerplexityBot. 1 of the 12 checklist rows with an Ora check is met. 0 of 2 MUST rows are met. A two-letter domain behind a challenge page, so the scan saw almost nothing. On 9 November 2026 the public site at se.com scored **27 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: Se.com offers JSON error responses and NLWeb /ask endpoint support, but lacks WebMCP support. ## The score | Layer | Points | Share | What the layer asks | | --- | --- | --- | --- | | Discovery | 2 of 6 | 33% | Can agents find and recommend it | | Access | 0 of 31 | 0% | Can agents read it | | Usability | 4 of 9 | 44% | Can agents use it | | Payments | 0 of 0 | none apply | Can agents pay | | Total | 27 of 100 | 27% | 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 (not applicable), robots.txt agent-user policy (not applicable), Agent crawler reachability (partial), Not blocked by bot detection (partial).; Bot management challenged ChatGPT-User, OAI-SearchBot, Claude-User, PerplexityBot - a challenge is an identity check verified crawlers pass, so reachability is undetermined rather than blocked (ChatGPT-User: challenged, | | 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, no same-site rel="ard" link, 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 | No Ora check | Public API/docs linked from homepage (not applicable). | | 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 | No Ora check | OpenAPI spec published (not applicable). | | AR-ACT-03; MCP over Streamable HTTP | SHOULD | No Ora check | MCP server / manifest (not applicable), Listed in MCP registries (not applicable), MCP PKCE S256 support (not applicable), MCP OAuth metadata (not applicable). | | 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 | 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 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 | No Ora check | MCP server / manifest (not applicable), CLI tool available (not applicable). | | 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://se.com does not meet the Markdown negotiation requirements: Accept: text/markdown returned text/html; Vary header missing Accept (got "none") | | 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).; Homepage https://se.com does not meet the Markdown negotiation requirements: Accept: text/markdown returned text/html; Vary header missing Accept (got "none") | | VERCEL-ROBOTS-EXCLUSIONS; Robots exclusions | vercel | No Ora check | robots.txt AI crawler policy (not applicable), robots.txt agent-user policy (not applicable). | ## 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 Schneider Electric, each tied to the checklist row whose recipes cover it. WebMCP support Fail, 0 of 5, about 24.7 points to gain. Ora saw: No WebMCP support detected - no document.modelContext / navigator.modelContext usage found. Row [AR-ACT-07](https://agentreadychecklist.com/checklist/ar-act-07/), WebMCP tools. Brand name discoverability Fail, 0 of 3, about 11.1 points to gain. Ora saw: se.com was not in the top 10 for "se" (searched your brand name alone: we could not read a product term from your site). No checklist row names this check. Agent auth discovery metadata Fail, 0 of 3, about 6.2 points to gain. Ora saw: Neither /.well-known/oauth-protected-resource nor /.well-known/oauth-authorization-server found. Probed: se.com, api.se.com. No checklist row names this check. agent\_auth endpoints reachable Fail, 0 of 2, about 4.5 points to gain. Ora saw: No agent\_auth endpoint URIs found in AS metadata or /auth.md prose; nothing to probe. No checklist row names this check. auth.md exists Fail, 0 of 2, about 4.5 points to gain. Ora saw: No /auth.md found at site root. No checklist row names this check. ## Our read Schneider Electric lives at se.com, and the two-letter domain costs it twice. Ora's brand search for se found nothing, which is 11.1 points on a short scale, and the WAF in front of the site challenged ChatGPT-User, OAI-SearchBot, Claude-User and PerplexityBot and answered the robots.txt request with 403, so the policy, the home page and the structured data could not be read at all. With so few checks applicable the maximums are small and every absence weighs heavily: the WebMCP estimate alone is 24.7 points. Behind the wall Ora found JSON error responses and an NLWeb /ask endpoint, which is where the 4 usability points come from, and neither a sitemap nor an llms.txt. The energy management group has a well-known developer exchange on another host; from se.com an agent cannot reach it, read the policy, or confirm what the site is. The door is the whole story, and robots.txt is the first fix. ## 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/se.com, Ora's scan (vendor)](https://ora.ai/api/score/se.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 - [se.com, the company's site](https://www.se.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.