/vendor/emirates/AgentRouting.json or
/vendor/emirates/AgentContext.json directly.
emirates.com
Overview
Does emirates.com support MCP?
No confirmed MCP support was found for emirates.com as of 2026-06-28.
What agentic protocols does emirates.com support?
As of 2026-06-28, emirates.com has confirmed support for proprietary.
Is emirates.com's API publicly accessible or partner-gated?
Partner only.
Does emirates.com explicitly prohibit automated access?
Yes. emirates.com's terms of service explicitly prohibit automated or scraper access to the public website without prior written permission.
Is emirates.com agent-ready?
Partial. emirates.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 Emirates (emirates.com) participates in or has implemented the Agent2Agent protocol. The named A2A launch partners (Google Cloud Next, April 2025) include enterprise software and services firms such as Atlassian, Salesforce, SAP, PayPal, and Workday — no travel carriers or consumer travel brands appear among them. A second search targeting Emirates and A2A directly returned no relevant results. No vendor-specific statement, deprecation, or confirmed absence was found; this is a not_found rather than confirmed_absent because Emirates has made no declaration either way.
No evidence that Emirates (emirates.com) participates in the Agentic Commerce Protocol as a launch partner, early adopter, or announced integrator. Known ACP launch partners are retail/fashion brands (URBN, Coach, Kate Spade, Revolve, Ashley Furniture) and e-commerce platform players (commercetools, Checkout.com); no airline or travel vendor appears in any partner list found. Not confirmed_absent because Emirates has made no vendor-specific statement about ACP — the absence is simply unconfirmed.
No evidence found that Emirates (emirates.com) is among the 60+ launch partners for the Agent Payments Protocol, nor that the airline has made any public commitment to AP2 adoption. Search results for AP2 name financial-sector actors (Google, Mastercard, Visa) and FIDO Alliance members as key participants, but no travel carrier — and specifically no Emirates mention — appears in any launch-partner context. Confirmed not-found rather than confirmed-absent because no Emirates-specific denial or deprecation notice exists.
No MCP server or Model Context Protocol integration was found for emirates.com across its developer portal (developer.emirates.group), press releases, and industry MCP travel landscape coverage. Emirates Group's OpenAI partnership (announced November 2025) is an internal ChatGPT Enterprise deployment, not an externally callable MCP surface. Industry sources (AltexSoft, PhocusWire) name Kiwi.com, Sabre, lastminute.com, BCD Travel, and Apaleo as airlines/travel companies with MCP servers — Emirates is absent from all such lists.
No evidence found that Emirates (emirates.com) has adopted or is a launch partner for MPP, the multi-rail machine payment settlement protocol co-developed by Stripe and Tempo. Named early adopters and discussed use cases in MPP launch coverage (mpp.dev, Stripe blog, Tekedia) are API/compute vendors and generic e-commerce contexts — no airline or OTA partners, including Emirates, are mentioned. Not confirmed_absent because no Emirates-specific statement or deprecation notice exists; simply no vendor-specific evidence of any engagement with MPP.
No evidence that emirates.com has implemented NLWeb or appears in any NLWeb launch partner lists. Named early adopters confirmed in public announcements include O'Reilly, TripAdvisor, Eventbrite, Condé Nast, Redfin, and Priceline — Emirates is not among them. No /ask or /mcp endpoint at emirates.com was found.
No usable finding available for this protocol (no legitimate scan available within the candidate window).
WebMCP is an early-preview browser-native protocol (Chrome 146 Canary, April 2026), and no evidence was found of Emirates (emirates.com) implementing or being listed as a partner or adopter. Named early-context sources (Chrome for Developers, PhocusWire on travel readiness) reference travel as a future use case generically but name no specific airlines or travel vendors as confirmed participants. Emirates has not published any WebMCP documentation or window.AICommands integration.
No evidence found that emirates.com has adopted or piloted the x402 protocol. The x402 ecosystem page (x402.org/ecosystem) lists members such as Visa, Aleo, Fireblocks, Cloudflare, and various API/data vendors; Coinbase's own launch partner announcements reference Chainlink, Boosty Labs, Zyte.com, and AWS — none involve airlines or Emirates specifically. Emirates' partner pages concern codeshare and loyalty integrations with no crypto payment infrastructure signals.
Emirates' OpenAI relationship is an internal enterprise deployment of ChatGPT Enterprise (announced November 2025) focused on staff productivity and an AI Centre of Excellence — not a consumer-facing app or integration built on the OpenAI Apps SDK for the ChatGPT Apps store. No evidence was found of emirates.com publishing or listing an app via the OpenAI Apps SDK platform. The confirmed_absent status was not used because Emirates has not issued any statement specifically declining to build a ChatGPT Apps SDK integration; the absence is simply unannounced.
Loyalty/Skywards member management (search, profile retrieval, enrollment, tier/status queries) and partner OAuth/OIDC authentication and SSO credential management; flight booking or search scope not confirmed from publicly accessible documentation
Emirates operates a proprietary REST API developer portal at developer.emirates.group (built on Apigee Edge) exposing APIs for Skywards and Business Rewards loyalty programme management, partner SSO, and member profile operations. The API catalogue page requires SAML login to browse product details, so the full scope of available endpoints cannot be confirmed externally. A separate partner-facing portal exists at emirates.partners for travel-agency/trade integrations.
Direct network access to emirates.com was blocked in the sandbox (DNS resolution timed out), preventing direct HTTP checks of paths such as /llms.txt, /AGENTS.md, /.well-known/agent, /.well-known/ai-plugin.json, and /.well-known/llms.txt. Web searches returned no third-party evidence, crawl confirmations, or vendor announcements indicating Emirates has published any self-declaration file at a predictable domain path. The Emirates–OpenAI collaboration announced in November 2025 is an internal enterprise deployment, not an externally callable agent-discovery surface. Per pattern #11, the blocked direct fetch prevents a confident not_found determination, so unable_to_verify is appropriate.
Summary
Has agent interface: partial
Apply for partner access via developer.emirates.group and emirates.partners to determine the full scope of the proprietary API catalogue; specifically verify whether flight search or booking endpoints exist beyond the confirmed Skywards loyalty and SSO surfaces.
AgentContext
Five discrepancy categories were checked for emirates.com: (1) pricing — searches for hidden fees, deceptive checkout pricing, regulatory fines, or class-action settlements returned only isolated BBB complaints without a verified pattern; (2) availability — searches for ghost inventory or bait-and-switch seat/fare issues returned only official Emirates pages with no independent findings; (3) identity — searches for merchant-of-record ambiguity or liability deflection returned no evidence that Emirates departs from acting as direct counterparty on tickets booked via emirates.com; (4) policy — searches for enforcement gaps between stated and applied cancellation/refund policies returned no regulator findings, court settlements, or verified consumer-body reports specific to Emirates; (5) undisclosed constraints — searches for mid-transaction failures or implied-but-unavailable capabilities surfaced a May 2025 Skywards first-class award restriction, but this was publicly announced in advance and does not constitute an undisclosed platform-level constraint. No category produced findings that met the inclusion threshold for a human handoff trigger, so the handoff list is empty.