--- title: "Engie: the 360 check | Agent Ready Checklist" description: "Engie on Ora's agent-readiness scan, read 2026-11-09: 49 of 100, grade C. 7 of 22 checklist rows met, 12 not met. One company a day." canonical: https://agentreadychecklist.com/blog/engie-agent-readiness site: "Agent Ready Checklist" last_updated: 2026-11-09 date: 2026-11-09 section: "360 checks" --- # Engie: the 360 check | Agent Ready Checklist > Engie on Ora's agent-readiness scan, read 2026-11-09: 49 of 100, grade C. 7 of 22 checklist rows met, 12 not met. One company a day. Source: https://agentreadychecklist.com/blog/engie-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). # Engie against the checklist: the 360 agent-readiness check 360 check, 9 November 2026. Engie is the French energy group in gas, power and services. Engie scores 49 of 100 on Ora's agent-readiness scan, a C, read 9 November 2026. At the door, site accessible to 4 agent user-agents (ChatGPT-User, OAI-SearchBot, Claude-User, PerplexityBot). 7 of the 22 checklist rows with an Ora check are met. A readable corporate site whose only developer tool builds its design system. On 9 November 2026 the public site at engie.com scored **49 of 100** on [Ora's](https://ora.ai/?utm_source=agentreadychecklist.com&utm_medium=referral&utm_campaign=check) agent-readiness scan, a C. 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: ENGIE has a discoverable web presence and crawler-friendly robots.txt and sitemap, but lacks an OpenAPI spec and any publicly reachable API surface for agents. ## The score | Layer | Points | Share | What the layer asks | | --- | --- | --- | --- | | Discovery | 9 of 15 | 60% | Can agents find and recommend it | | Access | 29 of 54 | 54% | Can agents read it | | Usability | 22 of 54 | 41% | Can agents use it | | Payments | 0 of 0 | none apply | Can agents pay | | Total | 49 of 100 | 49% | Grade C | ## 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 | Met | robots.txt AI crawler policy (pass), robots.txt agent-user policy (pass), Agent crawler reachability (pass), Not blocked by bot detection (pass).; 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. | | 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 | Met | Sitemap exists (pass).; Valid sitemap found at https://www.engie.com/sitemap_index.xml with multiple sitemaps entries | | 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: 3253 chars of readable text, but no H1 tag. 5 of 5 sampled inner pages have text without JavaScript. | | 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 | Not met | Public API/docs linked from homepage (fail).; No public API or documentation page linked from homepage | | 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).; JSON-LD Organization found - missing description on this entity | | 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 | Met | OAuth 2.0 support (not applicable), Scoped permissions (pass).; Scoped permissions: pass, 5 of 5. | | 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 | Not met | MCP Apps support (fail).; 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. | | 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: @engie-group/fluid-cli | | AR-ACT-07; WebMCP tools | SHOULD | Not met | WebMCP support (fail).; No WebMCP support detected - no document.modelContext / navigator.modelContext usage found (scanned 6 of 6 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://engie.com does not meet the Markdown negotiation requirements: Accept: text/markdown returned text/html; charset=utf-8; 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 | Met | OAuth Protected Resource metadata (RFC 9728) (pass).; OAuth Protected Resource metadata (RFC 9728): pass, 2 of 2. | | 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://engie.com does not meet the Markdown negotiation requirements: Accept: text/markdown returned text/html; charset=utf-8; Vary header missing Accept (got "none") | | VERCEL-ROBOTS-EXCLUSIONS; Robots exclusions | vercel | Met | robots.txt AI crawler policy (pass), robots.txt agent-user policy (pass).; 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. | ## 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 Engie, each tied to the checklist row whose recipes cover it. Public API with reachable endpoints Fail, 0 of 7, about 5.8 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 4.9 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. Developer resource discoverability Fail, 0 of 3, about 4.4 points to gain. Ora saw: In a search for your API docs, none of the 10 results is your official docs. No checklist row names this check. OpenAPI spec published Fail, 0 of 7, about 4.3 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.1 points to gain. Ora saw: No WebMCP support detected - no document.modelContext / navigator.modelContext usage found (scanned 6 of 6 same-origin script bundle(s) for modelContext registrations). Row [AR-ACT-07](https://agentreadychecklist.com/checklist/ar-act-07/), WebMCP tools. ## Our read Engie is open and nearly complete on the reading side. All four test agents reached the home page, robots.txt allows the AI search and training crawlers, five of five sampled pages read with real text, the sitemap index is valid, and the JSON-LD Organization is missing only its description. The home page gives 3,253 characters and no H1, which with the missing llms.txt accounts for most of what the Access layer leaves on the table. On the act layer Ora found a CLI package on npm, @engie-group/fluid-cli, which is the tooling for the group's design system rather than an interface to its services, and a developer portal at /dashboard that is a login page; there is neither a public API nor an OpenAPI specification, and neither an MCP server nor OAuth. For a utility that sells energy contracts to millions of households, the gap that matters is on the act side, and nothing on the corporate domain points an agent to it. ## 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/engie.com, Ora's scan (vendor)](https://ora.ai/api/score/engie.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 - [engie.com, the company's site](https://www.engie.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.