/vendor/british-airways/AgentRouting.json or
/vendor/british-airways/AgentContext.json directly.
britishairways.com
Overview
Does britishairways.com support MCP?
No confirmed MCP support was found for britishairways.com as of 2026-06-28.
What agentic protocols does britishairways.com support?
As of 2026-06-28, britishairways.com has confirmed support for proprietary.
Is britishairways.com's API publicly accessible or partner-gated?
Open.
Does britishairways.com explicitly prohibit automated access?
Yes. britishairways.com's terms of service explicitly prohibit automated or scraper access to the public website without prior written permission.
Is britishairways.com agent-ready?
Partial. britishairways.com supports some agentic workflows but requires a human handoff for certain operations — see the protocols and summary sections for details.
Protocols
No evidence that British Airways has adopted, implemented, or been named as a partner for the Agent2Agent (A2A) protocol. The confirmed launch partner list for A2A (Atlassian, Box, Cohere, Intuit, LangChain, MongoDB, PayPal, Salesforce, SAP, ServiceNow, UKG, Workday) contains no airline or travel-operator entrants, and British Airways appears in none of the A2A ecosystem announcements found. This is not_found rather than confirmed_absent because no British Airways-specific statement or deprecation notice was located — the vendor simply has not surfaced in this context.
No evidence that British Airways (britishairways.com) appears in any ACP launch partner list, merchant announcement, or integration documentation. Confirmed ACP early adopters are retail-focused (Etsy, Shopify merchants, Walmart, Target, Sephora, Nordstrom, Best Buy, Lowe's, Wayfair); travel-sector merchants such as Delta, Expedia, and Hilton appear as flagship merchants in Amex's separate ACE program, not in ACP specifically. Chosen not_found rather than confirmed_absent because there is no British Airways-specific statement or deprecation notice — simply no presence detected.
No evidence that British Airways is among the 60+ launch partners or contributing organizations when Google donated AP2 to the FIDO Alliance. Known AP2 contributors include payment processors and fintechs such as Adyen, Nexi, Worldpay, Revolut, Mastercard, and Visa — no travel-sector airlines appear in the partner lists surfaced. British Airways' own developer and partner documentation contains no mention of AP2 or cryptographic payment mandate protocols.
No evidence of a British Airways (britishairways.com or its developer portal at developer.iairgroup.com) MCP server or Model Context Protocol integration was found across multiple searches. The IAG developer portal does offer REST/NDC APIs but no MCP surface. No third-party registries or community wrappers specific to British Airways under the MCP protocol were identified either.
No evidence found that British Airways has adopted or is a launch partner for MPP (the Stripe + Tempo Multi-rail Machine Payment Protocol). Known launch-related discussions name AI agent infrastructure providers and Web3/crypto-focused platforms (e.g., MultiversX) rather than traditional airlines. British Airways' own payment and partner pages reference conventional payment methods and airline alliances (oneworld) only, with no mention of MPP.
No evidence that British Airways has implemented or piloted NLWeb. Microsoft's named launch collaborators include Chicago Public Media, Common Sense Media, Eventbrite, Hearst (Delish), Shopify, Snowflake, Tripadvisor, DDM (Allrecipes/Serious Eats), and Milvus — no airline appears in any announced cohort. No /ask or /mcp endpoint was found under britishairways.com.
No evidence found that British Airways (britishairways.com) has implemented or announced UCP integration. Searches returned general UCP coverage, industry commentary on UCP's impact on airlines and travel booking broadly (via PhocusWire, gettransfer.com), and Google's own documentation for UCP for Lodging — none of which name British Airways as a participating merchant. A site-restricted search on britishairways.com for UCP or agentic commerce terms returned zero results. The not_found status reflects actual examination of available material that simply did not surface any vendor-specific evidence; this is not a blocked or gated check.
No evidence that British Airways has implemented or announced support for WebMCP on britishairways.com. WebMCP is an early-preview browser-native protocol (co-developed by Google and Microsoft, currently targeting broad availability in late 2026) with no publicly named airline or travel-brand early adopters. Search results for WebMCP launch partners returned no mention of British Airways; britishairways.com partner/alliance pages are entirely about commercial airline partnerships unrelated to this protocol.
No evidence that British Airways (britishairways.com) has adopted or announced support for the x402 stablecoin micropayment protocol. Known x402 launch and foundation partners include Coinbase, Cloudflare, Amazon Bedrock, Stellar, and Solana — no airline or major consumer travel vendor appears in that set. British Airways' payment infrastructure centers on Avios loyalty currency and conventional card/fiat rails, with no public signals toward stablecoin or HTTP 402-based settlement.
No evidence of a British Airways app built on OpenAI's Apps SDK or listed in the ChatGPT Apps directory was found across searches targeting britishairways.com, the OpenAI ChatGPT app store, and general travel-AI integration announcements. Results surfaced British Airways' own native iOS/Android app and the IAG developer portal (developer.iairgroup.com), neither of which is an OpenAI Apps SDK integration. The not_found status reflects a genuine absence of discoverable evidence rather than a blocked or gated check.
Read-only flight status, lowest-fare offers (Flight Offer Basic and Flight Offer Market Affiliates), and in-flight entertainment data via British Airways' own REST API v1 at api.ba.com; does NOT support booking or ticketing — those functions are handled through the separate NDC interface
British Airways operates a publicly documented proprietary REST API (api.ba.com/rest-v1/) for flight status queries and fare offers, distinct from its IATA NDC implementation. The IAG Developer Portal at developer.iairgroup.com/british_airways lists plans including Flight Offer Basic, Flight Offer Market Affiliates, and In-Flight Entertainment — all read-only, capped at 500 calls/day on some plans. No booking or order-creation capability exists in this proprietary surface; that scope belongs to the NDC layer.
Direct HTTP checks to britishairways.com for /llms.txt, /AGENTS.md, /agents.md, /.well-known/agent, and /.well-known/ai-catalog.json all returned HTTP 000 (connection-level failure/block), meaning the sandbox environment could not reach the domain at all. A targeted web search for these files on britishairways.com produced no results specific to British Airways. Neither check was able to confirm presence or absence — network access to the domain was blocked from within this research environment.
Summary
Has agent interface: partial
Monitor IAG Developer Portal (developer.iairgroup.com) for expansion of the proprietary REST API beyond its current read-only, no-booking scope, and watch for British Airways adoption of any agentic protocols (MCP, A2A, UCP) given the airline sector's emerging engagement with agentic commerce infrastructure.
AgentContext
Verified discrepancies
Vendor claim: British Airways states on its own legal pages that it complies with UK and EU regulations (UK261/EC261) entitling passengers to compensation and refunds when flights are cancelled or significantly delayed for reasons within the airline's control. BA's published cancellation compensation page affirms these passenger rights.
What actually happens: In practice, British Airways routinely invokes an overly broad interpretation of the 'extraordinary circumstances' exemption to deny legally owed compensation. Aviation legal practitioners and compensation specialists document that BA's definition of 'unavoidable' frequently does not align with how UK courts interpret the same term, leading to denials that are overturned when pursued legally. Direct claims to BA can take six months or more with no response, and many cases require third-party legal escalation before payment is made.
Agent guidance: When processing a disruption-related claim on behalf of a user against British Airways, do not accept BA's first-response denial of compensation at face value. Verify whether the cited 'extraordinary circumstances' reason would survive UK261 scrutiny (e.g., technical faults and many operational issues do not qualify). If BA denies the claim, advise the user to escalate via the UK Civil Aviation Authority (CAA) or a no-win-no-fee claims service rather than treating BA's denial as the final word. Do not mark a compensation task as complete based solely on a BA refusal letter.
- UK aviation lawyer Michael Higgins, quoted on AirAdvisor, states that when BA claims a delay was 'unavoidable,' they apply a definition broader than what UK courts accept, shifting financial burden away from BA improperly.
- Flightright, a claims enforcement firm, documents that direct BA claims routinely take six months or longer (if BA responds at all) and that legal leverage is typically needed to secure payment within a reasonable timeframe.
Vendor claim: British Airways presents its website as a full self-service booking and management platform, with a dedicated reward flight search (Avios/redemption bookings) available online alongside cash bookings, and Manage My Booking promoted as a tool that lets customers view and change their bookings without needing to call. No prominent upfront disclosure is made that certain booking types cannot be completed online.
What actually happens: Two documented constraints cause mid-transaction failures: (1) Avios reward flight searches on ba.com persistently return a 'There was a problem with your request, please try again later' error that blocks online completion, while cash bookings on the same routes succeed — BA acknowledged the issue is known but directs affected users to phone instead. (2) BA's own Manage My Booking FAQ discloses (only in that FAQ section) that bookings made through travel agents cannot have changes passed back to the agent system, and group bookings of 10 or more passengers cannot be accessed at all via Manage My Booking — constraints not surfaced at the point of transaction.
Agent guidance: When attempting to book reward/Avios flights on ba.com, build in an explicit fallback: if the reward flight search returns any error after two attempts, route the task to a phone call to BA (+44 344 493 0787 or regional equivalent) rather than retrying online — the failure is a known platform-side issue, not a transient error. For managing any booking originally made through a travel agent, do not use ba.com's Manage My Booking to make changes; contact the original travel agent directly, as changes made through ba.com will not propagate back to the agent's system.
- Multiple users across an extended period reported that Avios reward flight searches on ba.com return a persistent error while cash bookings complete normally; BA confirmed it was aware of the issue and told affected customers to call instead. The forum thread headline explicitly advises users to avoid booking on BA.com for this reason.
- British Airways' own Manage My Booking FAQ states that for travel agent bookings, 'changes made through Manage My Booking to British Airways flights will normally not be passed back to your travel agent booking,' and that group bookings of 10 or more passengers cannot be accessed through the self-service tool at all.
Human handoff required for
When BA issues a written denial of UK261/EC261 disruption compensation citing 'extraordinary circumstances', do not mark the claim as resolved — escalate to a human to evaluate whether the cited reason (e.g., technical fault, operational issue) would survive UK court or CAA scrutiny before accepting the denial as final.
- British Airways routinely invokes an overly broad 'extraordinary circumstances' exemption to deny compensation legally owed under UK261/EC261; aviation legal practitioners document that BA's interpretation frequently does not align with how UK courts define the same term, and denials are regularly overturned on legal escalation.
- BA's published cancellation compensation page affirms UK261/EC261 passenger rights, but in practice direct claims can take six months or more with no response and often require third-party legal escalation before payment is made.
When a disruption compensation claim has received no substantive response from British Airways after more than 30 days, escalate to a human to initiate formal escalation via the UK Civil Aviation Authority (CAA) or a no-win-no-fee claims service rather than continuing to wait for BA's direct response.
When an Avios reward flight search on ba.com returns an error ('There was a problem with your request, please try again later') after two sequential attempts on the same route where cash bookings succeed, escalate to a human to complete the booking via BA's telephone reservations line rather than retrying online — the failure is a known persistent platform issue, not a transient error.
- Multiple user reports on frequent-flyer forums document persistent mid-transaction failures specifically affecting Avios reward flight searches while cash bookings on the same routes succeed; BA acknowledged the issue is known and directs affected users to phone instead of resolving it online.
- BA's own customer service pages direct users experiencing online booking errors to call +44 344 493 0787 as the fallback channel for completing reward bookings that cannot be processed on the website.
When asked to modify or cancel a booking originally made through a travel agent using ba.com's Manage My Booking tool, stop and escalate to a human — changes made via Manage My Booking will not propagate back to the agent's system, and the correct channel is the original travel agent directly.
When a group booking of 10 or more passengers needs to be accessed or modified via ba.com's Manage My Booking, escalate to a human — group bookings of 10+ are entirely inaccessible through that tool and require direct contact with BA's group bookings team.
Five categories were checked for britishairways.com. Discrepancy_pricing: searched for hidden fees, deceptive checkout pricing, and regulatory enforcement; no qualifying finding was identified — YQ surcharges on Avios redemptions are disclosed at checkout and criticism of their size does not constitute a pricing discrepancy. Discrepancy_availability: searched for ghost inventory, bait-and-switch fares, and systematic unavailability of advertised seats; no regulatory action or verified pattern was found beyond a standard legal disclaimer in BA's terms. Discrepancy_identity: searched for merchant-of-record ambiguity, liability deflection, and refund responsibility confusion; BA's codeshare carrier disclosures follow regulated Montreal Convention requirements and no systemic deceptive deflection pattern was found. Discrepancy_policy: a verified finding was identified — BA demonstrably overapplies the 'extraordinary circumstances' exemption under UK261/EC261 to deny legally owed compensation, a gap between stated policy and actual enforcement that UK courts and the CAA regularly correct on escalation. Discrepancy_undisclosed_constraint: two verified findings were identified — persistent Avios reward search failures on ba.com that BA acknowledges and routes to phone, and undisclosed limitations in Manage My Booking affecting agent-booked itineraries and group bookings of 10+, neither disclosed prominently at the point of transaction.