/vendor/lufthansa/AgentRouting.json or
/vendor/lufthansa/AgentContext.json directly.
lufthansa.com
Overview
Does lufthansa.com support MCP?
No confirmed MCP support was found for lufthansa.com as of 2026-06-28.
What agentic protocols does lufthansa.com support?
As of 2026-06-28, lufthansa.com has confirmed support for proprietary.
Is lufthansa.com's API publicly accessible or partner-gated?
Access varies by protocol: open, partner only.
Does lufthansa.com explicitly prohibit automated access?
Yes. lufthansa.com's terms of service explicitly prohibit automated or scraper access to the public website without prior written permission.
Is lufthansa.com agent-ready?
Partial. lufthansa.com supports some agentic workflows but requires a human handoff for certain operations — see the protocols and summary sections for details.
Protocols
No evidence found that Lufthansa has adopted, piloted, or been named as a launch partner for the Agent2Agent (A2A) protocol. Search results for A2A launch partners surface Google Cloud, IBM, and various AI platform vendors — no airline or travel operator presence, and no Lufthansa-specific mention. Lufthansa's own developer/partner-facing pages relate to traditional travel-agent booking portals, not agent-to-agent communication protocols.
No usable finding available for this protocol (no legitimate scan available within the candidate window).
No official Lufthansa MCP server or integration was found. The only MCP-related artifact found is an auto-generated community server (github.com/ag2-mcp-servers/lh-partner-api) produced by a third-party tool (AG2's MCP builder) wrapping a public Lufthansa OpenAPI spec from apis.guru — not a Lufthansa-published integration. Lufthansa's own developer portal (developer.lufthansa.com) shows no MCP references.
No evidence found that Lufthansa or the Lufthansa Group has adopted MPP. Known launch partners identified in MPP announcements include Anthropic, OpenAI, Shopify, Alchemy, Dune Analytics, Visa, Lightspark, and Cloudflare — Lufthansa does not appear among them. Search results for Lufthansa's payment-related pages return only consumer-facing card payment options, with no mention of Stripe/Tempo machine payment infrastructure.
No evidence that lufthansa.com has implemented NLWeb or appeared in any NLWeb launch partner list. NLWeb was announced at Microsoft Build 2025 and is an early-stage open-source project; named early adopters found in search results do not include Lufthansa or any Lufthansa Group entity. Lufthansa's developer-facing surface centers on its own REST-based Open API at developer.lufthansa.com, with no reference to /ask or /mcp NLWeb endpoints.
No evidence found that Lufthansa (lufthansa.com) has adopted or announced support for the Universal Commerce Protocol. Search results for UCP adoption reference Shopify, Google, Adyen, and generic e-commerce merchants — not airlines or Lufthansa specifically. Lufthansa's public developer portal (developer.lufthansa.com) focuses on flight data and cargo APIs with no checkout or agentic commerce layer discoverable.
WebMCP remains in early preview (Chrome 146 Canary, behind a flag) with effectively zero production adoption as of mid-2026 — one independent developer survey confirmed no Fortune 500 or major enterprise site has shipped it yet. No evidence found of lufthansa.com implementing window.AICommands or any WebMCP toolset; the only Lufthansa-adjacent MCP artifact found is a third-party auto-generated Model Context Protocol server for the Lufthansa Partner API on GitHub (ag2-mcp-servers/lh-partner-api), which is unrelated to the browser-layer WebMCP protocol. Chose not_found over unable_to_verify because the protocol's own known early-adopter set is documented and Lufthansa is absent from it.
No evidence found linking Lufthansa or lufthansa.com to the x402 protocol in any capacity. Known x402 launch partners and ecosystem participants include Coinbase, Cloudflare, Solana Foundation, and Stellar Foundation — all infrastructure/platform players, none in the airline or consumer travel segment. Lufthansa's own web presence shows no developer API surface related to stablecoin payments or HTTP 402 integration.
No evidence found of Lufthansa (lufthansa.com) having built or published an app via the OpenAI Apps SDK on the ChatGPT Apps platform. OpenAI's announced pilot partners at launch were Booking.com, Canva, Coursera, Figma, Expedia, Spotify, and Zillow — Lufthansa is not among them. The chatgpt.com GPT entries found (e.g., chatgpt.com/g/g-1hVGhdG5P-lufthansa) are third-party or unofficial custom GPTs, not Apps SDK integrations built by lufthansa.com. Lufthansa Group's documented OpenAI activity is internal (staff use of ChatGPT, a hackathon), not a customer-facing ChatGPT Apps SDK integration.
Public REST API covering reference data (airports, aircraft, airlines), flight schedules, flight status for LH Group carriers, and seat maps; offer/pricing endpoints (BestPrice, Fares) available on the self-serve Public Plan via self-registration at developer.lufthansa.com
Lufthansa operates its own proprietary REST API (the 'LH Open API') published at developer.lufthansa.com, self-serviced via a Public Plan requiring only free registration. A Partner Plan extends this with additional commercial endpoints (seat details, promotions, price offers, OND data) gated behind a commercial agreement. This is a Lufthansa-built, non-standard interface separate from the NDC standard.
Extended commercial REST API ('Partner Plan') adding seat details, promotional fares, price offers, OND data, and BestPrice fares beyond the public tier; requires a commercial partner relationship with Lufthansa
The Partner API is an extension of the same Lufthansa proprietary REST platform but with a distinct token endpoint URI and access gated via commercial agreement rather than self-registration. The Partner APIs page at developer.lufthansa.com/partner_apis also references the Lufthansa NDC Partner Program as a separate registration path for NDC-based distribution access.
FlightOps/Crew API providing crew check-in times, crew lists, duty events, flight leg details, landing reports, hotel information, and crew rotation data; restricted to Lufthansa crew staff and authorized FlightOps partners only
The FlightOps/Crew API is a structurally distinct proprietary interface with its own OAuth2 server, its own registration process, and operational-data scope entirely separate from the public and partner commercial APIs. Documentation is publicly visible but access is restricted to Lufthansa crew staff or registered FlightOps partners.
Direct HTTP checks against lufthansa.com for /llms.txt, /agents.md, /.well-known/agent, and /.well-known/ai-catalog.json all returned connection-level failures (HTTP 000), indicating network-level blocking of the sandbox's outbound requests rather than confirmed absence — the checks could not complete. Web searches for Lufthansa publishing any self-declaration file returned no vendor-specific evidence; results referenced Shopify, Anthropic, and other unrelated vendors. Because the direct checks were blocked and could not be completed, not_found rather than confirmed_absent is the appropriate status — the material could not actually be examined.
Summary
Has agent interface: partial
Register for the self-serve Public Plan at developer.lufthansa.com to obtain OAuth2 client credentials and test the publicly callable REST endpoints (flight status, schedules, reference data); separately, initiate a commercial partnership inquiry for the Partner Plan if pricing or seat-detail endpoints are required.
AgentContext
Verified discrepancies
Vendor claim: Lufthansa advertises ticket prices at the search and fare-selection stage of its booking flow. The Environmental Cost Surcharge, ranging from approximately €1 to €72 per segment depending on cabin class and route, is disclosed only at the final step of the booking process, not in the upfront advertised fare.
What actually happens: An agent completing a Lufthansa booking for eligible routes (departures from EU, UK, Norway, or Switzerland on or after 1 January 2025) will encounter a higher total at the final checkout screen than the price displayed during search and fare selection. The surcharge is per segment, so on a multi-leg itinerary or in a premium cabin the gap can reach €72 per segment. A 2023 European Court of Justice ruling requires airlines operating in the EU to display all-in pricing from the outset; industry observers noted at launch that disclosing the surcharge only at the last step may conflict with this requirement.
Agent guidance: When booking on lufthansa.com for any flight departing from an EU country, UK, Norway, or Switzerland on or after 1 January 2025, do not treat the fare shown at the search or fare-selection step as the final price. Proceed to the last step of the booking process and read the full price breakdown before confirming. Add the Environmental Cost Surcharge (€1–€72 per segment, varying by cabin and route) to the initial fare when comparing prices or reporting a total cost to the user. Do not finalize the booking until the all-in price at checkout has been confirmed and communicated to the user.
- One Mile at a Time reports that Lufthansa's Environmental Cost Surcharge 'will be displayed during the last step of the booking process, in the price details,' and notes a 2023 ECJ ruling requires airlines to display all-in pricing, creating a potential compliance conflict.
- Lufthansa Group's official newsroom announcement confirms the surcharge applies to tickets issued from 26 June 2024 for travel from 1 January 2025, and that amounts range from €1 to €72 per segment depending on route and fare class.
- Lufthansa's own Environmental Cost Surcharge page confirms the surcharge covers SAF mandate and EU ETS costs and is levied per segment on affected routes.
Vendor claim: Lufthansa's website displays available seats and fares—including Allegris First Class upgrade options and multi-city economy itineraries—as selectable and bookable at the shown price.
What actually happens: Multiple independently documented reports show that seats and fares displayed as available on lufthansa.com cannot be completed at checkout. Two distinct patterns have been reported: (1) Allegris First Class upgrade inventory shown as selectable that errors out or reprices upward before confirming; (2) multi-city economy itineraries that display available seats but throw booking errors, described by community experts as 'phantom inventory.' In both cases the booking cannot be completed via the website and users must call, use an OTA, or use Lufthansa's legacy booking interface.
Agent guidance: Before committing to any itinerary on lufthansa.com, an agent must attempt to reach the payment confirmation screen before treating the booking as complete. If a booking error or unexpected price change occurs mid-flow, the agent should not retry the same interface; instead it should surface the failure to the user and suggest calling Lufthansa directly (+1-800-645-3880 in the US) or using the legacy booking tool (book.lufthansa.com) or a reputable OTA, as the displayed inventory may be phantom.
- One Mile at a Time (July 2025) documents the Allegris First Class upgrade glitch where seats shown as available cannot be booked—prices can simultaneously increase and the booking still fails, a pattern user comments describe as 'bait and switch.'
- FlyerTalk forum thread (January 2024) documents multi-city economy routes on lufthansa.com displaying phantom inventory—seats appear available but booking errors occur; moderator notes 'phantom inventory' and recommends workarounds including the legacy booking URL or OTAs.
Vendor claim: Lufthansa's own refund and customer-relations pages state that if Lufthansa is the merchant of record, it will process refunds directly. The implication when booking on lufthansa.com is that Lufthansa holds payment and dispute responsibility.
What actually happens: Lufthansa's own published policies explicitly condition refund liability on whether Lufthansa is the merchant of record — a determination that is not disclosed to the customer at the point of checkout. When Lufthansa is not the merchant of record (e.g., tickets issued through certain agency or GDS channels, even those surfaced within or alongside lufthansa.com), Lufthansa deflects all refund and dispute responsibility to the travel agent or third-party portal, telling consumers to 'contact them directly' and that 'your travel agent is the responsible party.' A consumer or agent completing a booking on or via Lufthansa's platform may not know which merchant-of-record scenario applies until a refund is sought and Lufthansa declines responsibility.
Agent guidance: Before completing any ticket purchase on or via lufthansa.com, an agent must confirm whether Lufthansa will be the merchant of record for that specific ticket. If the booking is fulfilled through a GDS, OTA, or agency intermediary — even one surfaced via Lufthansa's own site — refund and dispute rights run against that intermediary, not Lufthansa. The agent should capture and record the issuing entity shown on the ticket (the 'issued by' field or IATA code on the e-ticket receipt) before confirming the transaction, and alert the user that their legal counterparty for disputes may differ from Lufthansa itself.
- Lufthansa's US refund page explicitly gates its refund obligation on the phrase 'If we are the merchant of record,' without disclosing this determination to the buyer at checkout time.
- Lufthansa's Customer Relations USA page instructs consumers who purchased via a travel agency to contact the agent directly, calling the agent 'the responsible party to review and process any refund due,' even for tickets that may have been discovered or initiated through Lufthansa channels.
Vendor claim: Lufthansa states on its website that passengers are entitled to refunds when flights are cancelled or significantly changed, and provides an online portal for submitting compensation and refund claims, implying prompt and compliant refund processing.
What actually happens: The U.S. Department of Transportation found that Lufthansa systematically failed to provide timely refunds for cancelled or significantly changed flights, in violation of federal law. During peak periods, thousands of refund requests took longer than 100 days to process. DOT received over 2,500 complaints about Lufthansa's refund handling, and Lufthansa itself received tens of thousands more directly. A separate class action settlement also arose from Lufthansa's failure to refund passengers for COVID-era cancelled flights between January 2020 and August 2021.
Agent guidance: When booking or cancelling a Lufthansa flight on behalf of a user, do not rely on the vendor's stated refund process alone. Explicitly document the cancellation confirmation, the refund request submission, and the expected refund amount. Advise the user that refunds may be significantly delayed in practice; if a refund is not received within 7 business days (DOT's required window for credit card purchases), the user should file a complaint directly with the U.S. DOT at https://airconsumer.dot.gov/ and consider initiating a chargeback with their card issuer.
- The U.S. DOT's Office of Aviation Consumer Protection issued a cease-and-desist order against Lufthansa (Order 2024-5-26), finding it violated 49 U.S.C. § 41712 by failing to provide timely refunds for cancelled or significantly changed flights, with some requests taking over 100 days.
- A class action settlement site documents that Lufthansa passengers whose flights were cancelled between January 1, 2020 and August 16, 2021 may be entitled to benefits, with an appeal still pending as of the site's last update.
- Top Class Actions reports Lufthansa agreed to pay up to $50 million in claims under a class action settlement for failing to refund consumers for COVID-19-cancelled flights.
Human handoff required for
Confirm the all-in price at the final checkout screen before completing any Lufthansa booking for flights departing from an EU country, UK, Norway, or Switzerland on or after 1 January 2025, because the Environmental Cost Surcharge (€1–€72 per segment, varying by cabin class and route) is not included in the fare shown at search or fare-selection stages — escalate to a human if the checkout total exceeds the user-approved budget after the surcharge is added.
Stop and escalate to a human when a booking error occurs or the price changes unexpectedly mid-session on lufthansa.com — specifically for Allegris First Class upgrade selections that error out or reprice upward, and for multi-city economy itineraries that display available seats but throw booking errors (phantom inventory) — because retrying the same interface is unlikely to succeed and the user must be advised to call Lufthansa directly or use an alternative channel.
Before completing a ticket purchase on or via lufthansa.com, verify whether Lufthansa will be the merchant of record for that specific ticket by checking the issuing entity on the e-ticket receipt — escalate to a human if the ticket is issued through a GDS, OTA, or agency intermediary, because Lufthansa's published policy explicitly deflects all refund and dispute responsibility to that intermediary rather than Lufthansa itself, which the user may not expect.
After submitting a refund or cancellation request on behalf of a user on lufthansa.com, escalate to a human if the refund is not received within 7 business days of the cancellation for a credit card purchase — because the U.S. DOT found Lufthansa systematically delayed thousands of refunds beyond 100 days, and the user may need to file a DOT complaint or initiate a chargeback rather than waiting on Lufthansa's stated process.
Five categories were checked for lufthansa.com. Discrepancy_pricing: a confirmed finding — Lufthansa's Environmental Cost Surcharge (€1–€72 per segment) is disclosed only at the final checkout step, not in upfront search fares, supported by Lufthansa's own materials and independent industry reporting. Discrepancy_availability: a confirmed finding — two distinct phantom-inventory patterns (Allegris First Class upgrades and multi-city economy itineraries) are corroborated by frequent-flyer community sources with specific workarounds. Discrepancy_identity: a confirmed finding — Lufthansa's own published US refund pages reveal an undisclosed merchant-of-record determination that can shift all refund liability to a third-party intermediary without the customer's knowledge at checkout. Discrepancy_policy: a confirmed finding — U.S. DOT Order 2024-5-26 documents systematic refund delays in violation of federal law, and a class action settlement covers COVID-era cancellations. Discrepancy_undisclosed_constraint: no qualifying finding — individual complaints about system glitches and fare restriction edge cases were found, but none cleared the bar of a verified, systemic, independently-documented mid-transaction capability failure.