/vendor/fliggy/AgentRouting.json or
/vendor/fliggy/AgentContext.json directly.
fliggy.com
Overview
Does fliggy.com support MCP?
Yes. fliggy.com has a confirmed MCP implementation. Real-time travel search and booking-link retrieval across flights, trains, hotels, attractions/POI, and vacation packages; an agent can execute structured queries (search-flight, search-train, search-hotel, search-poi, search-marriott-hotel, search-marriott-package, keyword-search, ai-search) and receive structured JSON results with direct Fliggy booking links — covering the full trip from planning through booking initiation..
What agentic protocols does fliggy.com support?
As of 2026-06-25, fliggy.com has confirmed support for MCP, proprietary, and self_declared_discovery.
Is fliggy.com's API publicly accessible or partner-gated?
Access varies by protocol: open, partner only.
Does fliggy.com explicitly prohibit automated access?
Yes. fliggy.com's terms of service explicitly prohibit automated or scraper access to the public website without prior written permission.
Is fliggy.com agent-ready?
Yes. fliggy.com has a confirmed, agent-callable interface that supports end-to-end workflow completion.
Protocols
No evidence of Fliggy (fliggy.com) implementing or supporting the A2A (Agent2Agent) protocol. Fliggy's external agent-callable surface is its FlyAI skill (github.com/alibaba-flyai/flyai-skill), which is explicitly built on MCP, not A2A. Alibaba's spring-ai-alibaba developer framework includes A2A support for building agents, but this is a general-purpose Java developer framework, not a Fliggy travel endpoint. Named A2A launch partners (Atlassian, Box, Cohere, Intuit, Langchain, MongoDB, PayPal, Salesforce, SAP, ServiceNow, Workday, Accenture, AWS, Cisco, Google, IBM, Microsoft) and the 150-org Linux Foundation milestone announcement do not include Alibaba or Fliggy. Recorded as not_found rather than confirmed_absent because no vendor-specific statement ruling out A2A was located; absence of evidence only.
No evidence that Fliggy (fliggy.com) participates in the OpenAI/Stripe Agentic Commerce Protocol. Named ACP launch partners include Etsy, Shopify merchants (Glossier, Vuori, Spanx), Instacart, URBN, Coach, Kate Spade, Revolve, and Ashley Furniture — Fliggy is not among them. Fliggy's agentic commerce activity runs entirely within Alibaba's own closed-loop ecosystem (Qwen AI chatbot + Taobao/Fliggy inventory + Alipay payments), which does not use or require the OpenAI/Stripe ACP stack. ACP is currently US-market-oriented and Stripe-dependent; Fliggy is a China-market OTA operating on domestic infrastructure with no documented Stripe or OpenAI commerce integration. Recorded as not_found rather than confirmed_absent because no Fliggy-specific statement explicitly rejecting ACP was located — the absence is structural/contextual, not vendor-declared.
No evidence found linking fliggy.com to AP2 (Agent Payments Protocol). The named AP2 launch partners (60+ organizations announced September 2025, donated to FIDO Alliance April 2026) include Mastercard, PayPal, American Express, Adyen, Coinbase, Revolut, Etsy, UnionPay International, Ant International, Salesforce, ServiceNow, Worldpay, Shopee, 1Password, and Lowe's — Fliggy is not among them. Ant International (an Alibaba Group fintech subsidiary) does appear on the partner list, but this is a separate entity from Fliggy, which operates its own AI booking stack (Qwen/flyai/AskMe) with no documented AP2 integration. Recorded as not_found rather than confirmed_absent because no Fliggy-specific deprecation or opt-out statement was located.
Real-time travel search and booking-link retrieval across flights, trains, hotels, attractions/POI, and vacation packages; an agent can execute structured queries (search-flight, search-train, search-hotel, search-poi, search-marriott-hotel, search-marriott-package, keyword-search, ai-search) and receive structured JSON results with direct Fliggy booking links — covering the full trip from planning through booking initiation.
Fliggy (Alibaba Group's travel division) launched 'FlyAI' in March–April 2026 as an open-source MCP-based travel skill, published at https://github.com/alibaba-flyai/flyai-skill and documented at https://open.fly.ai/docs/quickstart. The flyai-cli tool invokes Fliggy's MCP API backend and is installable via ClawHub or npm/npx with zero mandatory configuration; an official API key (self-serve from the open.fly.ai console) unlocks higher request quotas. This is a first-pass observation with no prior RoloCache history, so stability_rating is 'new' per policy.
No evidence found that fliggy.com has adopted or is implementing MPP (the Stripe/Tempo Machine Payments Protocol). MPP launched March 18, 2026 with over 100 early adopter services; named launch partners include Anthropic, OpenAI, Shopify, Alchemy, Dune Analytics, DoorDash, Nubank, Ramp, Revolut, and Visa — Fliggy is not among them, and no Fliggy-specific MPP reference appeared in the mpp.dev services directory, Stripe's documentation, or any third-party coverage. Fliggy's own agentic infrastructure work centers on its MCP-based FlyAI travel skill and Alipay-based payment flows, with no documented connection to Stripe or Tempo rails.
No evidence that fliggy.com has deployed NLWeb's /ask or /mcp endpoints under the NLWeb (Microsoft) framework. Microsoft's published NLWeb pioneer/early-adopter list names Tripadvisor, Delish, Eventbrite, O'Reilly Media, Qdrant, Inception Labs, Shopify, and Allrecipes — Fliggy is not among them. Fliggy does have an agent-callable travel interface ('flyai', github.com/alibaba-flyai/flyai-skill) built natively on MCP, but this is a standalone MCP skill, not an NLWeb deployment; the two are architecturally distinct. No vendor-specific statement or documentation from Fliggy references NLWeb.
No evidence found that Fliggy (fliggy.com) has adopted or is a named partner of the Universal Commerce Protocol. Named launch partners for UCP include Shopify, Etsy, Wayfair, Target, and Walmart (retail); Booking.com, Expedia Group, Hilton, Marriott International, IHG, Accor, Amadeus, Choice Hotels, Trip.com, and Wyndham (lodging/travel); and endorsers including Adyen, Mastercard, Stripe, and Visa. Fliggy does not appear in any of these lists. Fliggy's AI commerce activity in 2026 is focused on its own Alibaba/Qwen ecosystem (Qwen App + Fliggy AI collaborations with 40+ travel brands announced February 2026), not on Google's UCP standard. Recorded as not_found rather than confirmed_absent because no vendor-specific statement from Fliggy explicitly rejecting UCP was located.
No evidence found that fliggy.com has implemented WebMCP. Fliggy's browser-layer AI integration work is focused on its MCP-based 'flyai' skill (published on ClawHub and GitHub) and its 'AskMe' AI assistant — both standard MCP, not the browser-layer WebMCP protocol. The PhocusWire article on WebMCP and travel names no specific OTA adopters, and no Fliggy-specific WebMCP documentation, announcement, or window.AICommands surface was located. Recorded as not_found rather than confirmed_absent because no vendor-specific statement explicitly ruling out WebMCP was found.
No usable finding available for this protocol (no legitimate scan available within the candidate window).
No evidence of a Fliggy ChatGPT Apps SDK integration was found across OpenAI's launch announcement, the ChatGPT App Directory (chatgpt.com/apps), or any third-party coverage. Named pilot/launch partners for the OpenAI Apps SDK are Booking.com, Canva, Coursera, Expedia, Figma, Spotify, and Zillow — Fliggy is not among them. Fliggy's AI integration strategy is built on Alibaba's own Qwen platform, not OpenAI's stack, which further reduces the likelihood of an OpenAI Apps SDK presence. Recorded as not_found rather than confirmed_absent because no vendor-specific statement from Fliggy explicitly ruling out this platform was located.
Supply-side and distribution partner API covering hotel inventory upload and pricing query, domestic and international flight policy/order sync, vacation package transactions, car rental, ferry/bus, scenic spot ticketing, and affiliate (CPS) order tracking and coupon issuance. Partners can search and retrieve travel product data, push inventory and pricing updates, manage bookings, and query order status across all product categories.
Fliggy's proprietary platform runs on Alibaba's TOP (Taobao Open Platform) gateway at http://gw.api.taobao.com/router/rest. All API methods use Alibaba-proprietary naming (e.g., taobao.xhotel.distribution.info, alibaba.fliggy.promote.orders.newlist, alitrip.*). Docs are published at https://open.fliggy.com/ and https://open.alitrip.com/, with individual API references such as https://open.fliggy.com/docs/api.htm?apiId=23475. Access requires partner enrollment to obtain an app_key; the platform is not open to anonymous callers.
Search flights, trains, hotels, and attractions on Fliggy's inventory; execute bookings; run AI-powered trip planning queries. Full travel stack from inspiration through booking.
Fliggy's official GitHub org (alibaba-flyai) publishes a SKILL.md file at the root of github.com/alibaba-flyai/flyai-skill, conforming to the agentskills.io open standard (published December 2025). This is a vendor self-declaration at a predictable, convention-defined location — skill registries (ClawHub) and agent runtimes (Claude Code, OpenClaw) discover and load it from that path. The skill is also listed on ClawHub and documented at https://flyai.open.fliggy.com/docs/quickstart. Vendor-specific evidence is direct: Fliggy/Alibaba operates the alibaba-flyai GitHub org and launched flyai publicly in March 2026.
Direct HTTP checks of fliggy.com for domain-level self-declaration files (llms.txt, AGENTS.md, /.well-known/agent, agents.txt) returned connection failures (status 000) in this environment — the domain is not reachable from the sandbox. No external web evidence was found of these files existing at fliggy.com. This is recorded as unable_to_verify rather than not_found because the check was structurally blocked, not completed-and-empty.
Summary
Has agent interface: true
Use the FlyAI MCP skill (installable via npx or ClawHub from github.com/alibaba-flyai/flyai-skill) to search flights, trains, hotels, and attractions and retrieve Fliggy booking links; obtain an API key from the open.fly.ai console for production-level quota. For supply-side or distribution partner access (inventory push, order sync, affiliate tracking), enroll via the partner program at open.fliggy.com to obtain an app_key for the TOP gateway at gw.api.taobao.com.
AgentContext
Verified discrepancies
Vendor claim: Fliggy displays flight and travel prices in search results that represent the fare the user will pay, with any add-ons (such as insurance) presented as optional selections during checkout.
What actually happens: Independent reporting and consumer complaints document two distinct pricing discrepancies: (1) prices shown in search results are lower than the price actually charged at checkout, with users forced to restart searches when prices change mid-booking; and (2) insurance fees are pre-selected or hidden behind hard-to-find UI elements during checkout, adding undisclosed costs to the final total that many users discover only after payment or via customer service.
Agent guidance: Do not treat the price shown on Fliggy's search results page as the confirmed checkout price. Before submitting any booking, programmatically verify the final itemized total on the payment confirmation screen, explicitly check for pre-selected insurance or ancillary fee line items, and compare the sum against the originally quoted fare. If the total differs, abort the transaction and surface the discrepancy to the user before proceeding.
- A published investigation details how Fliggy's interface uses 'deceptive design' to embed insurance fees that are difficult to locate and remove, with user reports of prices rising between search and checkout.
- Consumer reviews on PissedConsumer document a systematic pattern where prices change after a user enters passenger information, and customer support only instructs users to 'start a new search,' offering no remedy.
Vendor claim: Fliggy's stated cancellation policy allows customers to cancel within 24 hours for a full refund; the platform also ran a 'summer full refund for ticket fees' campaign implying straightforward refund eligibility for certain bookings.
What actually happens: Multiple independently-sourced consumer reports document that Fliggy does not honor its own stated refund/cancellation policies in practice: customers who cancel within the advertised 24-hour window report receiving zero refund. Separately, China Railway 12306 publicly called out a Fliggy campaign as 'misleading consumers' regarding refund terms, and Fliggy deleted the relevant promotional post. Consumer review aggregators consistently note opaque enforcement of exchange, refund, and cancellation policies with no meaningful recourse.
Agent guidance: Do not rely on Fliggy's displayed cancellation or refund policy terms when completing a booking transaction. Before finalizing any booking, independently verify the actual refund conditions directly with the airline or hotel supplier rather than trusting Fliggy's platform-stated policy. If a transaction requires a guaranteed cancellation or refund right, do not use Fliggy as the booking channel without manual confirmation of the refund terms from the underlying supplier.
- A verified buyer on Trustpilot describes canceling within the stated 24-hour full-refund window and receiving no refund at all, with customer service refusing to honor the policy and eventually hanging up.
- PissedConsumer's aggregated Fliggy reviews specifically call out unexpected charges, altered dates, and opaque refund and cancellation policy enforcement, with limited customer support for resolution.
- A detailed article notes that in July 2024, China Railway 12306 officially called Fliggy's 'summer full refund for ticket fees' campaign 'misleading consumers,' and Fliggy later deleted the related promotional post.
Vendor claim: Fliggy presents itself as an online travel agency where users can search and book flights directly, implying the platform is the single counterparty handling the booking and that all relevant booking details (such as visa requirements and the identity of the fulfilling party) are disclosed before payment.
What actually happens: Fliggy routinely routes flight bookings through undisclosed third-party sub-agents without revealing their identity before the user pays. Users only discover the actual fulfilling party after completing payment. Additionally, Fliggy's passenger name entry form inserts a gender honorific (e.g., 'MR') into the ticket name field in a way that is not visible to the user during checkout, resulting in tickets issued with incorrect names that cannot be corrected post-issuance. A separate documented case shows the platform's booking confirmation stated no transit visa was required, a representation that proved incorrect and led to denied boarding.
Agent guidance: Before submitting payment on Fliggy for any flight: (1) Do not assume the displayed booking screen reflects the actual fulfilling party — request confirmation of the sub-agent identity before paying, or use an alternative OTA that discloses the merchant of record upfront. (2) Verify that the passenger name as it will appear on the ticket matches the passport exactly, including middle names/initials, by checking any preview or confirmation screen; if no preview is available, contact Fliggy support before paying. (3) Independently verify visa and transit requirements through official government sources rather than relying on any in-platform eligibility indicator.
- A TripAdvisor thread documents that Fliggy does not disclose the identity of the third-party sub-agent fulfilling a flight booking until after payment is completed, leaving users unable to vet the counterparty before committing funds.
- A TripAdvisor Air Travel forum post and a mirrored Trustpilot review describe how Fliggy's booking form silently inserts a gender title ('MR') into the ticket name field, producing an incorrectly named ticket that neither Fliggy nor the airline would correct, forcing the user to abandon the ticket.
- A PissedConsumer review describes a passenger denied boarding in Beijing because Fliggy's booking confirmation stated no transit visa was required for Pakistani passport holders, which proved to be incorrect.
Human handoff required for
Escalate to a human when the itemized total on the payment confirmation screen differs from the price shown at the search results stage, including any pre-selected insurance or ancillary fee line items that were not explicitly chosen by the user during the session.
Escalate to a human before finalizing any booking where a cancellation or refund right is a material requirement, because Fliggy's platform-stated 24-hour cancellation and refund policies have documented patterns of non-enforcement, and the underlying supplier's actual refund terms cannot be verified through Fliggy alone.
- Multiple independently-sourced consumer reports on Trustpilot and PissedConsumer document customers being denied refunds despite canceling within Fliggy's own advertised windows, with opaque enforcement and no meaningful recourse.
- China Railway 12306 publicly rebuked a Fliggy refund campaign in July 2024 as 'misleading consumers,' and Fliggy acknowledged the issue by deleting the relevant promotional post.
Escalate to a human when the identity of the party actually fulfilling a flight booking cannot be confirmed before payment, as Fliggy has documented patterns of routing bookings through undisclosed third-party sub-agents whose identity is revealed only after the user has paid.
Escalate to a human before submitting payment for any flight booking where the passenger name as it will appear on the issued ticket cannot be visually confirmed on a preview or confirmation screen, because Fliggy's name entry form has a documented defect that silently inserts a gender honorific into the ticket name field in a way invisible to the user during checkout, producing incorrectly issued tickets with no post-issuance correction available.
Escalate to a human before completing any booking involving international transit or entry where visa requirements are a factor, because Fliggy's in-platform visa requirement indicators have been documented to be incorrect, with at least one confirmed case of a booking confirmation stating no transit visa was required when one was in fact needed, resulting in denied boarding.
Five categories were checked for fliggy.com. Discrepancy_pricing returned a confirmed finding: search-to-checkout price inflation and pre-selected hidden insurance fees are documented in independent reporting and consumer complaint aggregators. Discrepancy_policy returned a confirmed finding: Fliggy's stated 24-hour cancellation and refund policies are documented as systematically unenforced, corroborated by a July 2024 public rebuke from China Railway 12306 and multiple Trustpilot and PissedConsumer reports. Discrepancy_undisclosed_constraint returned a confirmed finding covering three distinct issues: undisclosed third-party sub-agent identity, a silent honorific insertion defect in the passenger name field, and inaccurate in-platform visa requirement indicators. Discrepancy_availability returned no confirmed finding: consumer complaints were found but did not rise to a documented, repeatable pattern of ghost inventory or structurally unbookable advertised listings. Discrepancy_identity returned no confirmed finding: complaints about refund difficulty and opaque policies were found but no regulatory action or verified report confirmed a systematic merchant-of-record misdirection policy distinct from common OTA marketplace frictions.