360 check, 9 Nov 2026
Lufthansa on the pay layer: the 360 agent-readiness check
Lufthansa scores 36 of 100 on Ora's agent-readiness scan, a D, read 14 Nov 2026. The six payment checks did not apply to lufthansa.com on this read, which is how Ora treats a site it does not read as a shop. Four agents blocked and five crawlers welcomed, by a shield and a policy that disagree.
On 14 Nov 2026 the public site at lufthansa.com scored 36 of 100 on Ora's agent-readiness scan, a D, in Ora's Travel & Hospitality category. Lufthansa is the largest airline group in Europe by revenue, 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: Turns agents away at the door: bot detection blocks ChatGPT, Claude and Perplexity, and no MCP server or OpenAPI spec exists.
The score
| Layer | Points | Share | What the layer asks |
|---|---|---|---|
| Discovery | 6 of 10 | 60% | Can agents find and recommend it |
| Access | 15.5 of 39 | 40% | Can agents read it |
| Usability | 15 of 72 | 21% | Can agents use it |
| Payments | 0 of 0 | none apply | Can agents pay |
| Total | 36 of 100 | 36% | Grade D |
The pay layer
Ora did not run the six payment checks against lufthansa.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 x402 payment protocol support detected. 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 MPP (Machine Payments Protocol) support detected. 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 UCP (Universal Commerce Protocol) signals detected. 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 ACP (Agentic Commerce Protocol) signals detected. No commerce signals detected - agent-payment protocols are optional for non-commerce sites |
The other layers, check by check
Every check Ora ran on lufthansa.com, grouped by layer, with the result, the points and what Ora recorded where its wording passes this site's gate.
Discovery: 6 of 10
| Check | Result | Points | What Ora saw |
|---|---|---|---|
| ARD discovery | Fail | 0 of 1 | No /.well-known/ard.json, no same-site rel="ard" link, and no legacy /.well-known/ai-catalog.json |
| Developer resource discoverability | Pass | 4 of 4 | Pass, no detail recorded. |
| Brand name discoverability | Partial | 1 of 3 | lufthansa.com ranks #8 for "lufthansa" (searched your brand name alone: we could not read a product term from your site) |
| robots.txt AI crawler policy | Pass | 1 of 1 | 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. |
| 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 | Fail | 0 of 2 | Not found in ChatGPT app directory |
Access: 15.5 of 39
| Check | Result | Points | What Ora saw |
|---|---|---|---|
| Sitemap exists | Fail | 0 of 1 | No sitemap found |
| Not blocked by bot detection | Fail | 0 of 2 | Agents blocked: ChatGPT-User, OAI-SearchBot, Claude-User, PerplexityBot |
| 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 (3 community skills with potential relation to this domain found, but only self-published official skills count) |
| pricing.md exists | Fail | 0 of 2 | No pricing.md found - agents need machine-readable pricing to compare products and make purchase recommendations |
| 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 |
| 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://lufthansa.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 | Partial | 0 of 1 | Only 1 section-level llms.txt found (de). Add one for another section and link it from your root llms.txt to earn this bonus point. |
| robots.txt agent-user policy | Pass | 1 of 1 | No applicable crawl or usage restriction found for 3 user-triggered agents (chatgpt-user, claude-user, perplexity-user) on 1 public page: https://lufthansa.com/. Declared policy only |
| llms.txt exists | Pass | 1 of 1 | Found the llms.txt at https://developer.lufthansa.com/llms.txt. |
| llms.txt formatting | Pass | 2 of 2 | The llms.txt is well-formatted: 11 lines with markdown links, 1,089 characters in total. |
| JSON-LD structured data | Fail | 0 of 2 | 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 | 4 of 4 | Documentation site found at https://developer.lufthansa.com |
| Agent instruction / when-to-use | Fail | 0 of 1 | 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 1 | No JSON-LD found - no entity linking possible |
| Metadata completeness | Partial | 0.5 of 1 | Only 1/4 metadata signals present - missing: canonical URL, og:image, og:type |
| Organization schema completeness | Fail | 0 of 1 | No JSON-LD found - Organization schema missing |
| Trust anchor pages | Fail | 0 of 1 | No trust anchor pages found with sufficient content (About, Contact, Privacy) |
| llms.txt links resolve | Fail | 0 of 2 | 4 of 5 probed llms.txt links could not be verified: https://www.lufthansa.com/legal.md (HTTP 403), https://www.lufthansa.com/resources.md (HTTP 403), https://www.lufthansa.com/glossary.md (HTTP 403) |
| Redirect hygiene | Pass | 1 of 1 | Pass, no detail recorded. |
| Page token budget | Pass | 1 of 1 | All 5 measured pages fit an agent context budget (largest ~3K tokens) |
| Code fence validity | Pass | 1 of 1 | Pass, no detail recorded. |
| OpenAPI spec published | Fail | 0 of 8 | No OpenAPI/Swagger specification found |
| Developer portal | Pass | 5 of 5 | Developer portal found at https://developer.lufthansa.com |
| API catalog (RFC 9727) | Fail | 0 of 2 | No /.well-known/api-catalog found (RFC 9727) |
| 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://lufthansa.com does not meet the Markdown negotiation requirements: Accept: text/markdown returned text/html; charset=utf-8; Vary header missing Accept (got "none") |
| Bot-UA markdown serving | Fail | 0 of 1 | No probed bot User-Agent (ChatGPT-User, Claude-User, Perplexity-User) receives markdown when requesting HTML. Optional: detect AI-bot UAs server-side and serve them a markdown representation directly. |
| Agent crawler reachability | Fail | 0 of 1 | No agent we tested can reach the homepage - ChatGPT-User: blocked, OAI-SearchBot: blocked, Claude-User: blocked, PerplexityBot: blocked |
Usability: 15 of 72
| Check | Result | Points | What Ora saw |
|---|---|---|---|
| Public API with reachable endpoints | Pass | 8 of 8 | API described in documentation at https://developer.lufthansa.com but no machine-verifiable API surface confirmed. GraphQL endpoint at https://lufthansa.com/graphql is reachable |
| OAuth 2.0 support | Partial | 3 of 5 | OAuth mentioned in documentation at https://developer.lufthansa.com but no OAuth or OpenID Connect endpoint responded |
| Scoped permissions | Fail | 0 of 5 | No declared OAuth scopes, security schemes, or scoped-permission documentation found |
| Agent onboarding friction | Partial | 1 of 2 | Onboarding signals described but not verified live: sandbox/test environment, zero-auth access |
| Web Bot Auth directory | Fail | 0 of 2 | No /.well-known/http-message-signatures-directory found |
| 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 | No /auth.md found at site root |
| 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: lufthansa.com, api.lufthansa.com. |
| Agent auth WWW-Authenticate hint | Fail | 0 of 1 | No 401 with WWW-Authenticate: Bearer resource_metadata=... found. Probed [https://lufthansa.com/api, https://lufthansa.com/api/v1, https://lufthansa.com/v1, https://lufthansa.com/v2, https://lufthansa.com/agent/identity |
| 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 10 | No MCP server or manifest found |
| WebMCP support | Fail | 0 of 8 | No WebMCP support detected - no document.modelContext / navigator.modelContext usage found |
| Rate limit response headers | Fail | 0 of 2 | GraphQL introspection auth-gated and no header convention documented on GraphQL-tagged pages |
| Idempotency-Key support | Fail | 0 of 3 | GraphQL introspection auth-gated and no idempotency documentation found on GraphQL-tagged pages |
| JSON error responses | Fail | 0 of 3 | API does not return JSON error responses (or no API detected) |
| CLI tool available | Fail | 0 of 3 | No CLI tool found |
| NLWeb /ask endpoint | Pass | 1 of 1 | NLWeb /ask endpoint exists but requires authentication (HTTP 403, via GET) |
| NLWeb streaming support | Fail | 0 of 1 | NLWeb /ask requires authentication - cannot verify streaming |
| 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 |
| GraphQL typed error model | Fail | 0 of 3 | GraphQL introspection auth-gated and no typed graphql error model documentation found on GraphQL-tagged pages |
| GraphQL versioning / deprecation policy | Fail | 0 of 2 | GraphQL introspection auth-gated and no graphql versioning / deprecation policy documentation found on GraphQL-tagged pages |
| GraphQL pagination pattern | Fail | 0 of 2 | GraphQL introspection auth-gated and no graphql pagination pattern documentation found on GraphQL-tagged pages |
| GraphQL async-job pattern | Fail | 0 of 2 | GraphQL introspection auth-gated and no graphql async-job pattern documentation found on GraphQL-tagged pages |
| Agent-friendly 404s | Partial | 1 of 2 | Nonexistent paths return HTTP 403 instead of 404/410 - agents get a non-200 signal but not the standard not-found semantics. The docs host developer.lufthansa.com answers the same way or better. |
| 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 | Pass | 2 of 2 | Pass, no detail recorded. |
| Function calling compatibility | Fail | 0 of 2 | No API spec found - function calling requires discoverable endpoints |
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 Lufthansa.
- OpenAPI spec published
- Fail, 0 of 8, about 6.8 points to gain. Ora saw:
No OpenAPI/Swagger specification found
. - MCP server / manifest
- Fail, 0 of 10, about 6.2 points to gain. Ora saw:
No MCP server or manifest found
. - WebMCP support
- Fail, 0 of 8, about 4.9 points to gain. Ora saw:
No WebMCP support detected - no document.modelContext / navigator.modelContext usage found
. - Brand name discoverability
- Partial, 1 of 3, about 4.4 points to gain. Ora saw:
lufthansa.com ranks #8 for "lufthansa" (searched your brand name alone: we could not read a product term from your site)
. - Scoped permissions
- Fail, 0 of 5, about 3.1 points to gain. Ora saw:
No declared OAuth scopes, security schemes, or scoped-permission documentation found
.
Our read
Lufthansa blocks the agents and welcomes the crawlers: ChatGPT-User, OAI-SearchBot, Claude-User and PerplexityBot were refused while robots.txt permits the three search and two training crawlers Ora checked and states no restriction on user-triggered agents, a policy and a shield pointing in different directions. The home page returned no page to read, so the content and structured-data rows are unverified, and there is no sitemap. Ora found no commerce signals, so the six payment checks did not apply on this read, on the largest airline group in Europe. The act layer is the developer portal: developer.lufthansa.com is real and carries an llms.txt, and the airline's open API is described there, but Ora could confirm no machine-verifiable surface, the OAuth it mentions answered at no standard endpoint, and there is neither an OpenAPI specification nor an MCP server, and no declared scopes. The domain ranks eighth for its own name. The portal has done work the home page undoes; the two should agree.
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/lufthansa.com, Ora's scan (vendor), read 14 Nov 2026
- Ora's scoring rules, version 3 (vendor), read 14 Nov 2026
- Ora check catalog (GET /api/checks), read 14 Nov 2026
- lufthansa.com, the company's site, read 14 Nov 2026
Last reviewed