360 check, 9 Nov 2026
Accor on the pay layer: the 360 agent-readiness check
In short
Accor scores 49 of 100 on Ora's agent-readiness scan, a C, read 14 Nov 2026. The six payment checks did not apply to accor.com on this read, which is how Ora treats a site it does not read as a shop. Six agents in, and a robots.txt and an llms.txt that both come back as HTML.
On 14 Nov 2026 the public site at accor.com scored 49 of 100 on Ora's agent-readiness scan, a C. Accor is Europe's largest hotel group, with more than 5,000 hotels, 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: Accor.com offers developer resources, but lacks an OpenAPI/Swagger specification.
The score
| Layer | Points | Share | What the layer asks |
|---|---|---|---|
| Discovery | 11 of 14 | 79% | Can agents find and recommend it |
| Access | 22 of 55 | 40% | Can agents read it |
| Usability | 28 of 67 | 42% | Can agents use it |
| Payments | 0 of 0 | none apply | Can agents pay |
| Total | 49 of 100 | 49% | Grade C |
The pay layer
Ora did not run the six payment checks against accor.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 travel seller 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 | No commerce signals detected - agent-payment protocols are optional for non-commerce sites |
| MPP | Does not apply | 0 of 2 | MPP in the matrix | No commerce signals detected - agent-payment protocols are optional for non-commerce sites |
| UCP | Does not apply | 0 of 3 | UCP in the matrix | No commerce signals detected - agent-payment protocols are optional for non-commerce sites |
| ACP | Does not apply | 0 of 3 | ACP in the matrix | No commerce signals detected - agent-payment protocols are optional for non-commerce sites |
| ACP delegate payment | Does not apply | 0 of 3 | ACP in the matrix | No commerce signals detected - agent-payment protocols are optional for non-commerce sites |
| AP2 | Does not apply | 0 of 3 | AP2 in the matrix | No commerce signals detected - agent-payment protocols are optional for non-commerce sites |
The other layers, check by check
Every check Ora ran on accor.com, grouped by layer, with the result, the points and what Ora recorded where its wording passes this site's gate.
Discovery: 11 of 14
| Check | Result | Points | What Ora saw |
|---|---|---|---|
| ARD discovery | Partial | 0 of 1 | /.well-known/ard.json exists but is not valid JSON |
| AI Catalog discovery | Partial | 0 of 1 | /.well-known/ai-catalog.json exists but is not valid JSON |
| Developer resource discoverability | Pass | 3 of 3 | Pass, no detail recorded. |
| Brand name discoverability | Partial | 2 of 3 | accor.com ranks #6 for "Accor Group Hospitality" and appears 2 times in the top 10 |
| Wikipedia / Wikidata entity presence | Pass | 4 of 4 | Wikipedia "Accor" and Wikidata Q212599 both verified - domain confirmed on both sources |
| NPM/PyPI SDK package | Fail | 0 of 1 | No NPM or PyPI SDK package found |
| 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 | Pass | 2 of 2 | Pass, no detail recorded. |
Access: 22 of 55
| Check | Result | Points | What Ora saw |
|---|---|---|---|
| Sitemap exists | Fail | 0 of 2 | No sitemap found |
| Content without JavaScript | Partial | 2 of 3 | 1933 chars with H1, but 0.9% content ratio is below the 5% target |
| Not blocked by bot detection | Pass | 2 of 2 | Site accessible to 6 AI agent user-agents |
| 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 (100 community skills with potential relation to this domain found, but only self-published official skills count) |
| pricing.md exists | Partial | 1 of 2 | pricing.md found at /pricing.md (1 line), but it has fewer than 5 lines and it does not open with a # heading - add plan tiers, prices, and feature breakdowns; start it with a # title so agents read it as markdown |
| 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 |
| Agent mode view | Fail | 0 of 2 | ?mode=agent returns same content as homepage (no dedicated agent view) |
| 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://accor.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 files found (optional) |
| llms.txt exists | Partial | 0 of 1 | A file is present at https://accor.com/.well-known/llms.txt, but it returns an HTML page rather than a plain-text llms.txt. |
| llms.txt formatting | Fail | 0 of 2 | No llms.txt found to evaluate quality |
| JSON-LD structured data | Fail | 0 of 4 | No JSON-LD structured data found on homepage |
| Pricing info accessible | Fail | 0 of 3 | No pricing page or pricing data found |
| Public API/docs linked from homepage | Pass | 3 of 3 | Documentation site found at https://developer.accor.com |
| Agent instruction / when-to-use | Fail | 0 of 3 | 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) | Fail | 0 of 2 | No JSON-LD found - no entity linking possible |
| Metadata completeness | Partial | 1 of 2 | 3/4 metadata signals present - missing: og:type |
| Organization schema completeness | Fail | 0 of 2 | No JSON-LD found - Organization schema missing |
| Schema type breadth | Fail | 0 of 2 | No extended schema types found - AI can only answer basic questions about this entity |
| Trust anchor pages | Partial | 1 of 2 | About, Contact pages verified - missing: Privacy |
| 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 2 measured pages fit an agent context budget (largest ~1K tokens) |
| Content behind auth | Pass | 2 of 2 | All 5 sampled pages are publicly readable (1 with substantive content) |
| OpenAPI spec published | Fail | 0 of 7 | No OpenAPI/Swagger specification found |
| Developer portal | Pass | 6 of 6 | Developer documentation portal found at https://developer.accor.com |
| API catalog (RFC 9727) | Partial | 1 of 2 | api-catalog responded but body is not valid JSON |
| 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://accor.com does not meet the Markdown negotiation requirements: Accept: text/markdown returned text/html; charset=utf-8; Vary header missing Accept (got "rsc,accept-encoding, origin") |
| Bot-UA markdown serving | Fail | 0 of 1 | No probed bot User-Agent (GPTBot, ClaudeBot, ChatGPT-User, PerplexityBot, Google-Extended, Applebot-Extended, ora-agent, DeepSeekBot) receives markdown when requesting HTML. |
| Agent crawler reachability | Pass | 2 of 2 | Reachable to all major AI crawlers - ChatGPT-User: reachable, ClaudeBot: reachable, Google-Extended: reachable, ora-agent: reachable, DeepSeekBot: reachable |
Usability: 28 of 67
| Check | Result | Points | What Ora saw |
|---|---|---|---|
| Public API with reachable endpoints | Partial | 3 of 7 | API described in documentation at https://developer.accor.com but no machine-verifiable API surface confirmed. Best-of-protocols score: 3/7. |
| OAuth 2.0 support | Pass | 5 of 5 | OpenID Connect discovery endpoint found at https://login.accor.com |
| Scoped permissions | Fail | 0 of 5 | No declared OAuth scopes, security schemes, or scoped-permission documentation found |
| Agent onboarding friction | Pass | 2 of 2 | Pass, no detail recorded. |
| Web Bot Auth directory | Partial | 1 of 2 | Web Bot Auth directory found but body is not valid JSON |
| OAuth Protected Resource metadata (RFC 9728) | Fail | 0 of 2 | No /.well-known/oauth-protected-resource found (RFC 9728) |
| auth.md exists | Fail | 0 of 2 | Path https://accor.com/auth.md returned HTML (SPA / 404 fallback), not an auth.md document |
| 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: accor.com, api.accor.com. |
| Agent auth WWW-Authenticate hint | Fail | 0 of 1 | No 401 with WWW-Authenticate: Bearer resource_metadata=... found. Probed [https://accor.com/api, https://accor.com/api/v1, https://accor.com/v1, https://accor.com/v2, https://accor.com/agent/identity, https://accor.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 |
| MCP server / manifest | Fail | 0 of 6 | No MCP server or manifest found |
| WebMCP support | Fail | 0 of 5 | No WebMCP support detected - no tool-attribute forms and no document.modelContext / navigator.modelContext usage found (scanned 8 of 23 same-origin script bundle(s) for modelContext registrations) |
| Rate limit response headers | Fail | 0 of 2 | No REST rate-limit headers found on probed endpoints |
| Idempotency-Key support | Fail | 0 of 3 | No REST Idempotency-Key support detected |
| JSON error responses | Pass | 4 of 4 | Pass, no detail recorded. |
| CLI tool available | Fail | 0 of 3 | No CLI tool found |
| Multi-language SDK packages | Fail | 0 of 3 | No SDK packages found across language ecosystems |
| 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. |
| Sandbox / test environment | Fail | 0 of 2 | No sandbox or test environment found |
| REST batch / bulk endpoint | Fail | 0 of 2 | No batch or bulk endpoint pattern found |
| Agent-friendly 404s | Fail | 0 of 2 | Nonexistent paths return HTTP 200 with the app shell (soft-404). Agents probing for resources conclude every path exists. Return a real HTTP 404 status for unknown paths. |
| 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. |
| Form control labeling | 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 |
| API schema complexity analysis | Partial | 1 of 2 | REST: OpenAPI spec found but failed to parse for complexity analysis |
| Function calling compatibility | Partial | 1 of 2 | API spec found but couldn't validate function calling compatibility |
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 Accor.
- OpenAPI spec published
- Fail, 0 of 7, about 4.2 points to gain. Ora saw:
No OpenAPI/Swagger specification found
. - MCP server / manifest
- Fail, 0 of 6, about 4 points to gain. Ora saw:
No MCP server or manifest found
. - Scoped permissions
- Fail, 0 of 5, about 3.3 points to gain. Ora saw:
No declared OAuth scopes, security schemes, or scoped-permission documentation found
. - WebMCP support
- Fail, 0 of 5, about 3.3 points to gain. Ora saw:
No WebMCP support detected - no tool-attribute forms and no document.modelContext / navigator.modelContext usage found (scanned 8 of 23 same-origin script bundle(s) for modelContext registrations)
. - MCP Apps support
- Fail, 0 of 4, about 2.7 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
.
Our read
Accor opens the door to all six agent user agents and hands them the wrong files. robots.txt answers with an HTML page instead of rules, so the policy rows cannot be met, and the llms.txt at accor.com/.well-known/llms.txt is an HTML page too. The home page gives 1,933 characters with an H1 at a 0.9 percent text ratio, and there is neither a sitemap nor JSON-LD. Ora read no commerce signals on the group behind more than 5,000 hotels, so the six payment checks did not apply on this read. The act layer is half built: OpenID Connect discovery at login.accor.com and a documentation portal at developer.accor.com, though the API it describes has no machine-verifiable surface, and Ora found neither an OpenAPI specification nor an MCP server, and no declared scopes. The brand search placed the domain sixth for a term read off the page, Accor Group Hospitality. Two files served as text would move this C.
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/accor.com, Ora's scan (vendor), read 14 Nov 2026
- Ora check catalog (GET /api/checks), read 14 Nov 2026
- accor.com, the company's site, read 14 Nov 2026
Last reviewed