/vendor/skyscanner/AgentRouting.json or
/vendor/skyscanner/AgentContext.json directly.
skyscanner.net
Overview
Does skyscanner.net support MCP?
Yes. skyscanner.net has a confirmed MCP implementation. Selected flight search and travel content lookups for LLM-based partner products; scope described as limited to specific approved use cases rather than full booking/order management..
What agentic protocols does skyscanner.net support?
As of 2026-06-23, skyscanner.net has confirmed support for MCP, openai_apps_sdk, and proprietary.
Is skyscanner.net's API publicly accessible or partner-gated?
Access varies by protocol: partner only, open.
Does skyscanner.net explicitly prohibit automated access?
Yes. skyscanner.net's terms of service explicitly prohibit automated or scraper access to the public website without prior written permission.
Is skyscanner.net agent-ready?
Partial. skyscanner.net supports some agentic workflows but requires a human handoff for certain operations — see the protocols and summary sections for details.
Protocols
No vendor-specific evidence that Skyscanner exposes or consumes an Agent2Agent (A2A) interface, no agent card discoverable at a well-known path, and Skyscanner is not listed among the 50+ named A2A launch partners (Atlassian, Box, Cohere, Intuit, LangChain, MongoDB, PayPal, Salesforce, SAP, ServiceNow, UKG, Workday, etc.). Public Skyscanner AI-agent activity is via OpenAI/Operator and a community MCP wrapper, neither of which is A2A; recorded as not_found rather than confirmed_absent because no explicit Skyscanner statement ruling A2A out was located.
ACP (OpenAI/Stripe Agentic Commerce Protocol) launch partners publicly named by OpenAI/Stripe were retail merchants (e.g., Etsy, Shopify merchants); no Skyscanner-specific ACP merchant integration was located. Skyscanner has been mentioned among travel companies that launched a ChatGPT app, but a ChatGPT app is a separate surface from ACP merchant checkout, and no vendor statement from Skyscanner indicates ACP adoption. Recorded as not_found rather than confirmed_absent because no Skyscanner-issued deprecation or rejection statement was found; Skyscanner is also a metasearch/referral business, not a direct merchant of record, which makes ACP merchant checkout structurally a poor fit but not affirmatively ruled out by the vendor itself.
No vendor-specific evidence of Skyscanner adopting Google/FIDO Agent Payments Protocol (AP2) found. Public AP2 partner lists name payment networks and merchants such as Mastercard, American Express, PayPal, Adyen, Coinbase, Klarna, Salesforce, ServiceNow, Intuit, Etsy, Revolut, JCB, Worldpay, Ant International — Skyscanner is not among them, and no Skyscanner blog/dev-portal mention of AP2 was located. Recorded as not_found rather than confirmed_absent since no Skyscanner statement explicitly declines AP2.
Selected flight search and travel content lookups for LLM-based partner products; scope described as limited to specific approved use cases rather than full booking/order management.
Vendor's own developer docs at https://developers.skyscanner.net/docs/mcp-server announce a Skyscanner-operated MCP server for partners building AI travel experiences, gated case-by-case via Account Manager or partners@skyscanner.net. Auth mechanism inferred from the same developer portal's authentication page (x-api-key header against partners.api.skyscanner.net, HTTPS). Several unofficial community MCP wrappers (shadyvb/mcp-skyscanner, Apify, Bright Data) also exist as demand signal but are excluded from routing.
MPP is a newly announced machine-to-machine payment protocol co-authored by Stripe and Tempo. No vendor-specific evidence located linking Skyscanner to MPP — Skyscanner is not named in MPP's listed services/launch material on mpp.dev or in Stripe/Tempo announcements, and Skyscanner's developer docs make no reference to MPP. Recorded as not_found rather than confirmed_absent because no Skyscanner-specific statement (e.g. own deprecation notice or explicit non-adoption) was located.
No evidence of an NLWeb deployment on skyscanner.net (no /ask or /mcp endpoint surfaced; no listing in Microsoft's published NLWeb pioneer/customer roster, which names Tripadvisor, O'Reilly Media, Qdrant, Shopify and others but not Skyscanner). Skyscanner appears as a Copilot Actions launch partner, which is a distinct integration and not evidence of NLWeb adoption. Recorded as not_found rather than confirmed_absent because no Skyscanner-specific statement rejecting NLWeb was located.
No vendor-specific evidence of Skyscanner adopting Google/Shopify's Universal Commerce Protocol was located. Public UCP coverage names Google's surfaces, Shopify merchants, and travel-segment expansion to Lodging/Food, with no Skyscanner mention; Skyscanner's own publicly visible agentic activity centers on a ChatGPT app and OpenAI Operator collaboration rather than UCP. Recorded as not_found rather than confirmed_absent because no Skyscanner statement explicitly disclaiming UCP was located.
No vendor-specific evidence located that skyscanner.net exposes a WebMCP in-browser tool surface (e.g. a window.AICommands declaration or equivalent declarative/imperative agent-tool API on its pages). WebMCP is an early-preview Chrome/Microsoft browser-layer proposal; Skyscanner has publicly launched a (server-side) MCP server for partners but no statement, docs, or launch-partner listing ties Skyscanner to WebMCP specifically. Recorded as not_found rather than confirmed_absent because no Skyscanner-issued statement disclaims participation; passive checks on actual page tool declarations were not performed, so sketchiness is insufficient_data.
No evidence found of Skyscanner adopting or accepting x402 stablecoin micropayments. x402 (Coinbase/Cloudflare-originated, May 2025) launch and ecosystem materials name participants such as Anthropic, AWS, Cloudflare, Stripe, Zuplo, Alchemy, QuickNode, and Coinbase itself; Skyscanner is not among them, and Skyscanner's own developer/partner surface advertises no HTTP 402 / USDC paywall on its APIs. Recorded not_found rather than confirmed_absent because no Skyscanner-specific statement (positive or negative) on x402 was located.
Conversational flight search inside ChatGPT: natural-language queries return live flight results with prices, airlines, and layovers; follow-up turns refine dates/airports. No booking completion inside the app — selecting an option hands off to Skyscanner's website.
Skyscanner is listed in the ChatGPT Apps directory (asdk_app_694546cd042881919bb746a8dc300f38) and announced a ChatGPT app in Feb 2026 for UK/US covering flight search via @skyscanner invocation. Scope is flight discovery only; the app surfaces Skyscanner pricing/results, with deeper booking flows redirecting out to skyscanner.net.
Flight search (live and cached/indicative pricing, browse quotes/routes), hotels content and pricing, car hire live and indicative pricing, plus supporting reference data (culture/localization, places, currencies); read-only metasearch with deep-link handoff to travel providers for actual booking — no booking, ticketing, or post-booking management exposed via the API
Vendor operates a documented proprietary Travel API for approved partners covering flights, hotels, and car hire as read-only search/content with deep-link handoff (no booking via API). Developer docs at developers.skyscanner.net/docs/intro and partner application at partners.skyscanner.net/product/travel-api; HTTPS in use and domains align with the vendor. Rated new because this is a first-pass observation with no prior history; access is gated behind a partner approval process (not self-serve), so access_tier is partner_only.
Direct HTTP fetches of common self-declaration paths (llms.txt, AGENTS.md, /.well-known/agent, /.well-known/agent.json, /.well-known/ai-plugin.json, robots.txt) at www.skyscanner.net and partners.skyscanner.net could not be performed from this environment (all returned HTTP 000/timeout, consistent with bot-protection blocking — skyscanner.net is known to serve a captcha/PerimeterX challenge). Search for vendor self-declared agent discovery files on the domain surfaced no announcements or third-party references; absence is recorded as unable_to_verify rather than not_found because the primary check (loading each predictable path) was structurally blocked, not completed.
Summary
Has agent interface: partial
For conversational flight discovery, invoke the vendor's ChatGPT app (@skyscanner) — note that booking completion redirects to the vendor's website and is not completed in-app. For programmatic partner integrations (MCP server or the proprietary read-only Travel API covering flights/hotels/car hire with deep-link handoff), apply for partner access via partners@skyscanner.net or partners.skyscanner.net; both are gated by Account Manager approval and are search/content only, not booking. Do not scrape the public website — the vendor's Terms of Service explicitly prohibit unauthorised automated access and the site actively bot-blocks.
AgentContext
Verified discrepancies
Vendor claim: Skyscanner displays flight prices in search results and on calendar/graph pages, presenting them as the prices users can expect to pay when booking.
What actually happens: Prices routinely change — sometimes materially — when users are redirected from Skyscanner's search results to the airline or OTA booking page. Skyscanner itself acknowledges in its own help documentation that prices shown on calendar, graph, and country pages are not live and cannot be guaranteed until the actual booking step. Users also report advertised fares that are unavailable or cannot actually be issued at the displayed price, a pattern consistent with ghost inventory or stale rate caching.
Agent guidance: An agent must not treat the price displayed on Skyscanner search results, calendar views, or graph pages as the confirmed bookable fare. Before finalizing any transaction, the agent must follow through to the airline or OTA's own checkout page, confirm the fare shown there matches the Skyscanner-displayed price, and only then record the price as the actual cost. If the redirected price differs from the Skyscanner-displayed price, the agent should surface the discrepancy to the user before completing the booking.
- Skyscanner's own help article explicitly states that prices shown on calendar, graph, and country pages are not live prices and may change at booking time because 'it's not possible for us to show live prices until the actual booking time.'
- A second Skyscanner help article confirms that when a user is redirected to a travel provider, the price is 'updated again' at that point, meaning the fare displayed in search results is not the guaranteed final price.
- Aggregated user complaints on a consumer review platform describe a recurring pattern where Skyscanner-listed fares look attractive but 'when I attempt to book, the tickets cannot actually be issued,' characterizing it as bait-and-switch behavior.
Vendor claim: Skyscanner presents itself as a travel search and booking platform where users can find and book flights, hotels, and car hire. Its interface directs users through a booking flow that gives the appearance of a unified booking experience, and Skyscanner collects or facilitates payment at the point of purchase.
What actually happens: Skyscanner is a metasearch engine that redirects users to third-party Online Travel Agents (OTAs) such as Gotogate, eDreams, and others to complete the actual transaction. These third parties are the true merchant of record and hold the payment. When refunds or disputes arise, Skyscanner deflects responsibility entirely to these third-party OTAs, leaving consumers without recourse through Skyscanner. Consumers have reported being unable to obtain refunds and discovering—only after problems arose—that their legal counterparty was an OTA rather than Skyscanner, which had no obligation to resolve the issue.
Agent guidance: Before completing any booking initiated via Skyscanner, an agent must identify and display to the user the name of the actual third-party OTA that will process the payment and hold the ticket. The agent should confirm with the user that their legal counterparty for the transaction is that OTA—not Skyscanner—and that any refund, cancellation, or dispute must be directed to the OTA. The agent should not represent the transaction as a 'Skyscanner booking.'
- Multiple consumer complaints on PissedConsumer document users being redirected from Skyscanner to OTAs like Gotogate, then being unable to recover funds when those OTAs refuse refunds, with Skyscanner declining responsibility.
- BBB complaint filings against Skyscanner Inc. document unresolved refund disputes where Skyscanner responded but did not resolve issues, consistent with deflection of liability to third-party booking agents.
- A complaint on Sikayetvar/Xolvie describes a user redirected from Skyscanner to eDreams, where an unauthorized €99.99 membership charge was applied—a charge Skyscanner had no visibility into or responsibility for, illustrating the merchant-of-record gap.
Vendor claim: Skyscanner presents flight, hotel, and car-hire options with 'Book' calls-to-action and price displays that imply a transaction can be completed through the platform, positioning itself as a place to find and secure travel.
What actually happens: Skyscanner is a pure metasearch engine; no booking can be completed on skyscanner.net itself. Every 'Book' action redirects the user to a third-party airline, hotel, or OTA where the actual transaction occurs. Prices and seat availability displayed by Skyscanner are cached search results that frequently differ — usually higher or already sold out — from what is available on the destination site. Skyscanner's own help documentation confirms it is not the merchant of record and that users must contact the airline or OTA directly for any post-booking support. Documented user complaints show a recurring 'Flight is fully booked at this rate' error appearing only after a user has entered traveler details and attempted to proceed, meaning the constraint surfaces mid-transaction rather than upfront.
Agent guidance: An AI agent must not attempt to complete a booking on skyscanner.net. Skyscanner should be used only to identify candidate itineraries and prices; the agent must then navigate directly to the airline's own website or an OTA's own website to complete the actual transaction. Before committing traveler details, the agent should re-verify price and availability on the destination site, as Skyscanner's displayed price is not guaranteed and seats may already be sold out.
- Skyscanner's own help article on contacting customer service states users must identify 'who you bought from first' because Skyscanner itself is not the seller; support for any booking must go to the third-party provider.
- Skyscanner's changes, cancellation, and refunds help page explicitly states it is 'a travel search engine' and that bookings are made with third-party travel agencies, airlines, hotels, or car rental companies — not with Skyscanner directly.
- ComplaintsBoard aggregates 295 Skyscanner complaints (rated 1.8/5) including a documented case where a user received a 'Flight is fully booked at this rate. The selected flight has just sold out.' error after entering traveler details, demonstrating that unavailability is disclosed only mid-transaction.
Human handoff required for
Escalate to a human when the fare shown on the airline's or OTA's checkout page differs from the price Skyscanner displayed in search results, calendar, or graph views, because the agent cannot determine whether the discrepancy is an acceptable dynamic-pricing shift or a bait-and-switch error without user authorization to proceed at the new price.
- Skyscanner's own help documentation confirms that prices on calendar, graph, and country pages are not live and may change when the user reaches the provider's booking page.
- User complaint records corroborate a pattern of fares being advertised that cannot actually be issued at the displayed price, consistent with stale rate caching.
Escalate to a human before completing any booking where Skyscanner redirects to a third-party OTA (e.g., Gotogate, eDreams) that the user has not previously reviewed or authorized, so the user can confirm they accept that the OTA — not Skyscanner — is the merchant of record and the sole point of contact for refunds, cancellations, and disputes.
- Multiple consumer complaint sources confirm that Skyscanner redirects users to third-party OTAs for payment processing and declines responsibility when refunds or disputes arise, leaving consumers stranded.
- Skyscanner's own help documentation states it is a travel search engine that redirects to third-party providers and places responsibility for cancellations and refunds on those providers.
Escalate to a human when a 'flight fully booked at this rate' or equivalent sold-out error appears after traveler details have already been entered on the destination OTA or airline page, because the agent has reached a mid-transaction failure state and cannot independently determine whether an alternative itinerary is acceptable to the user.
- Documented user complaints show a recurring 'Flight is fully booked at this rate' error appearing only after a user has entered traveler details and attempted to proceed on the destination site.
- Skyscanner's own help documentation confirms it is not the merchant of record and that cached prices and availability frequently differ from what is available on the destination site.
Escalate to a human if a user requests a refund or cancellation for a booking that originated via Skyscanner and the third-party OTA or airline is denying the request or is unresponsive, because Skyscanner has documented no obligation to intervene and the user's legal recourse lies entirely with an OTA they may not have knowingly chosen.
- Consumer complaints on BBB and PissedConsumer confirm Skyscanner declines all responsibility for post-booking issues and directs users to the OTA, which itself may be difficult to contact.
- Skyscanner's structural role as a metasearch engine means it holds no payment and has no contractual obligation to resolve disputes on behalf of the user.
Five discrepancy categories were evaluated for Skyscanner (skyscanner.net). Pricing (discrepancy_pricing): Searched for hidden fees, deceptive pricing, and regulatory actions; no findings specific to Skyscanner were identified — any pricing issues are attributable to downstream airlines and OTAs, not Skyscanner itself. Availability (discrepancy_availability): A finding was confirmed; Skyscanner's own help documentation and user complaints document that displayed prices are cached and frequently change or become unavailable on redirect. Identity (discrepancy_identity): A finding was confirmed; Skyscanner is a metasearch engine, not a merchant of record, yet its interface can mislead users about who their legal counterparty is, with multiple consumer sources documenting refund abandonment. Policy (discrepancy_policy): Searched for divergences between Skyscanner's stated cancellation and refund policies and actual enforcement; no independently verified discrepancy was found beyond the already-documented identity deflection. Undisclosed constraints (discrepancy_undisclosed_constraint): A finding was confirmed; Skyscanner cannot complete any booking itself, yet presents 'Book' calls-to-action without prominent upfront disclosure, and mid-transaction sold-out errors are documented after traveler details are entered. No category scans were blocked, but primary regulatory filings or court records naming Skyscanner specifically were not located; findings rely on Skyscanner's own help documentation and consumer complaint aggregators.