/vendor/expedia/AgentRouting.json or
/vendor/expedia/AgentContext.json directly.
expedia.com
Overview
Does expedia.com support MCP?
Yes. expedia.com has a confirmed MCP implementation. Retrieves Expedia travel recommendations (hotels, flights, activities, car rentals) filtered by destination, dates and traveler preferences via the Expedia Travel Recommendation Service API.
What agentic protocols does expedia.com support?
As of 2026-06-23, expedia.com has confirmed support for MCP, UCP, openai_apps_sdk, and proprietary.
Is expedia.com's API publicly accessible or partner-gated?
Access varies by protocol: partner only, platform mediated.
Does expedia.com explicitly prohibit automated access?
Yes. expedia.com's terms of service explicitly prohibit automated or scraper access to the public website without prior written permission.
Is expedia.com agent-ready?
Yes. expedia.com has a confirmed, agent-callable interface that supports end-to-end workflow completion.
Protocols
No vendor-specific evidence of an Agent2Agent (A2A) implementation by Expedia Group was located. Google's April 2025 A2A launch partner list (e.g., Salesforce, SAP, ServiceNow, Atlassian, MongoDB, Cohere, LangChain, Box, Workday, etc.) does not include Expedia; Expedia's own 2026 Explore announcements and B2B agentic AI rollout emphasize an MCP server and a partnership with Google on agent payments (AP2), with no mention of A2A by name or of publishing an Agent Card. Recorded as not_found rather than confirmed_absent because no Expedia-issued statement explicitly disavowing A2A was located.
Expedia is a confirmed ChatGPT pilot partner via the Apps SDK (apps in ChatGPT), and OpenAI/Stripe narrowed ACP's checkout scope to a small set of large integrated retailers (Instacart, Target, Etsy, Shopify-backed merchants commonly cited). No vendor-specific evidence located that Expedia exposes or consumes the OpenAI/Stripe Agentic Commerce Protocol checkout endpoints; coverage indicates Expedia's ChatGPT integration completes transactions inside Expedia's own app surface rather than via ACP's Stripe-mediated Instant Checkout. Recorded as not_found rather than confirmed_absent because no Expedia statement explicitly disclaiming ACP adoption was located.
No evidence Expedia Group is participating in AP2. AP2 (announced by Google on 2025-09-16, since contributed to FIDO Alliance) listed launch partners across card networks, processors, wallets, crypto rails, enterprise platforms, and merchants — named partners include Mastercard, American Express, PayPal, Adyen, Coinbase, Salesforce, ServiceNow, Worldpay, JCB, UnionPay International, Etsy, Lowe's, Ant International, Revolut, Intuit, Forter, Mysten Labs, Ethereum Foundation, MetaMask; Expedia is not among them. Travel-side AP2 deployment cited publicly is Ant International's Alipay+ Voyager travel agent, not Expedia. No vendor-specific Expedia statement on AP2 located, so recorded as not_found rather than confirmed_absent.
Retrieves Expedia travel recommendations (hotels, flights, activities, car rentals) filtered by destination, dates and traveler preferences via the Expedia Travel Recommendation Service API. Scope is recommendation/search only — no booking creation, modification, cancellation, payment or order management is exposed through this MCP surface.
Expedia Group publishes an official open-source MCP server (ExpediaGroup/expedia-travel-recommendations-mcp on GitHub) wrapping its Travel Recommendation Service API, and the Expedia Group developer hub AI-solutions page corroborates that MCP capabilities are being built across its APIs for B2B partners. The server is self-hosted by partners using their own Expedia partner API key rather than a vendor-hosted remote endpoint, so publicly_callable is false; access requires an existing Expedia partner/API relationship, hence partner_only.
MPP is a new agent-to-service payment standard co-authored by Stripe and Tempo Labs, launched alongside Tempo mainnet. Named launch/integration partners publicly listed include Anthropic, DoorDash, Mastercard, Nubank, OpenAI, Ramp, Revolut, Shopify, Standard Chartered, Visa, and Parallel — Expedia is not among them, and no vendor-specific statement from Expedia regarding MPP support was located. Recorded as not_found rather than confirmed_absent because no explicit Expedia disclaimer or deprecation notice exists; passive checks against an Expedia MPP surface could not be attempted because no such surface was found.
Searched Microsoft's NLWeb announcements, Build 2025 coverage, and the NLWeb Pioneers list; named participants include Tripadvisor, Chicago Public Media, Common Sense Media, DDM (Allrecipes/Serious Eats), Milvus, Shopify, and Snowflake, and early OpenAI-era partners reportedly included Condé Nast, Redfin, Eventbrite, and Priceline — Expedia.com is not among any named NLWeb adopter. No /ask or /mcp endpoint advertised on expedia.com surfaced; Expedia's own agentic announcements (Skift May 2026) describe an MCP server for B2B partners, not NLWeb. Recorded as not_found rather than confirmed_absent because no Expedia statement explicitly disclaims NLWeb.
Announced as a travel partner in Google's UCP expansion to hotels/lodging; intended scope is agent-driven hotel discovery, availability lookup, and direct booking through AI surfaces (Google Search AI Mode, Gemini) with the merchant retaining Merchant-of-Record status. Booking management/post-purchase scope not explicitly documented for this vendor.
Expedia Group is explicitly named among travel partners in Google's announced UCP expansion to lodging/hotels alongside Booking.com, Hilton, Marriott, IHG, Accor, Amadeus, Choice, Trip.com, and Wyndham. No vendor-specific Expedia developer documentation, endpoint, or auth details for UCP were locatable; integration appears to be platform-mediated via Google rather than a self-serve Expedia surface. Sketchiness rated insufficient_data because no Expedia-hosted UCP docs could be examined for the usual passive checks.
WebMCP is an early-preview W3C proposal flag-gated in Chrome 146 (March 2026) co-developed by Google and Microsoft; no vendor-specific evidence located that expedia.com has implemented a window.AICommands surface or registered as an early-preview participant. Travel-vertical mentions in WebMCP coverage are illustrative examples, not named integrations; Expedia's own publicly discussed agent strategy centers on a server-side MCP for B2B partners (Skift, May 2026), with no statement about browser-layer tool exposure. Recorded as not_found rather than confirmed_absent because no Expedia statement explicitly disclaims WebMCP adoption.
No evidence of Expedia or Expedia Group adopting x402 for stablecoin micropayment settlement. The x402 ecosystem directory and related listings highlight participants such as Coinbase, Fiserv, Chainlink, Stellar, SKALE, and Daydreams Systems; Expedia is not among the named adopters, facilitators, or integrators. No vendor-specific statement from Expedia confirming absence was located, so recorded as not_found rather than confirmed_absent.
In-ChatGPT app enabling natural-language search for flights and accommodations with live inventory/pricing and interactive map/card visuals; users add the Expedia connector in ChatGPT and query for stays/flights. Booking completion flow occurs via Expedia rather than directly inside the chat surface based on launch coverage.
Expedia was named as a launch partner for OpenAI's Apps in ChatGPT (Oct 2025 DevDay) and ships a user-installable connector at expedia.com/product/expedia-in-chatgpt. The underlying Apps SDK is built on MCP, but this entry covers the OpenAI-platform-specific app surface, which is only invokable from inside ChatGPT, not as a general callable endpoint.
Lodging shopping, availability search, pricing, booking creation/retrieval/cancellation, post-booking change notifications, and content retrieval across hotels and vacation rentals (Vrbo) inventory; partner-side supply/property management capabilities are part of the same developer hub but distinct workflow
Vendor operates a documented proprietary REST API product line marketed as 'Rapid' (formerly EAN), hosted on the Open World Developer Hub at developers.expediagroup.com with explicit endpoint references, SDKs (e.g. ExpediaGroup/expediagroup-python-sdk on GitHub), and partner onboarding via partner.expediagroup.com/en-us/join-us/rapid-api. Access requires a signed partner agreement (not self-serve), so access_tier is partner_only; HTTPS docs domain aligns with vendor brand and documentation is structured and versioned. Rating is 'new' per first-pass policy despite long vendor history of the product.
Direct fetches against expedia.com for the conventional self-declaration locations (/llms.txt, /AGENTS.md, /agents.md, /.well-known/agent, /.well-known/agent.json, /.well-known/ai-plugin.json) returned HTTP 000 / no response from this sandbox (no internet egress to expedia.com), so passive on-domain verification could not be completed. Web search surfaced no third-party report or vendor announcement that Expedia publishes any such self-declaration file; named adopters in current coverage are unrelated platforms (e.g., Shopify auto-shipping /llms.txt and /agents.md), with Expedia not mentioned. Recorded as not_found rather than confirmed_absent (no Expedia statement disclaiming these files was located) and rather than unable_to_verify (a web-evidence check was performed even though the direct fetch was blocked); sketchiness left as insufficient_data because the passive on-domain checks could not actually be executed.
Summary
Has agent interface: true
For B2B/partner agent integrations, apply for an Expedia partner account and use the documented Rapid REST API (developers.expediagroup.com) for booking-grade lodging workflows, or self-host the official ExpediaGroup travel-recommendations MCP server with a partner API key for search/recommendation use cases. For end-user agent surfaces, invoke Expedia inside ChatGPT via the official Expedia connector (Apps SDK) or via Google's AI Mode/Gemini lodging surfaces (UCP). Do not scrape expedia.com — the consumer, partner, and Developer Hub ToS each explicitly prohibit automated access without written permission.
AgentContext
Verified discrepancies
Vendor claim: Expedia publicly states it has embraced transparent pricing and displays mandatory fees such as resort fees in hotel search results so travelers can see the true cost of a stay.
What actually happens: Independent reporting and consumer advocacy sources document that, prior to and even following the FTC's Junk Fees Rule (effective May 12, 2025), mandatory fees including resort fees and destination fees on Expedia were frequently surfaced only late in the checkout flow rather than in the initial search result price — meaning the price an agent or consumer sees at search differs from the final checkout total. The FTC rule itself was prompted by over 72,000 consumer comments about exactly this category of pricing discrepancy on hotel booking platforms, including OTAs like Expedia.
Agent guidance: When using Expedia to book lodging, do not treat the price shown in search results as the final price. Before confirming any booking, explicitly navigate to the final checkout screen and verify the itemized total — including all mandatory resort fees, destination fees, and taxes — matches the user's budget. If the checkout total exceeds the searched price, surface the discrepancy to the user before completing the transaction. Do not confirm a booking based solely on the search-result price.
- The FTC finalized its Rule on Unfair or Deceptive Fees (16 C.F.R. Part 464) in December 2024, effective May 12, 2025, directly targeting the practice of displaying base lodging prices without mandatory fees upfront — a practice documented on platforms including Expedia.
- The FTC's FAQ page for the Junk Fees Rule confirms that as of May 12, 2025, businesses selling short-term lodging must clearly disclose all mandatory fees at the point prices are first displayed, indicating this was not being done consistently before.
- Consumer-facing reporting notes that Expedia and other OTAs display resort fees in results but that verification of full upfront compliance with the new FTC rule is still ongoing, and consumers are directed to file FTC complaints if fees are not shown upfront.
Vendor claim: Expedia displays available hotel rooms and rates that users can book through its platform, with listings shown as available representing genuine, bookable inventory. Expedia has also publicly stated it works throughout the booking process to verify pricing and availability to show customers the latest information.
What actually happens: A class action lawsuit (Buckeye Tree Lodge et al. v. Expedia) established and was settled in court that Expedia listed hotels as 'sold out' or 'unavailable' when those properties were in fact available to book directly — steering consumers toward partner hotels that paid Expedia referral fees. Separately, Expedia has internally acknowledged that its shopping system and booking system can return 'disparate fares,' meaning a displayed price at the search stage is not always the price that holds at checkout. Consumer complaints of prices jumping materially at the final booking step remain documented across multiple forums.
Agent guidance: An agent booking on Expedia should not treat the search-results price or availability status as confirmed until the final checkout screen explicitly reconfirms both the price and room/flight availability. If the price at checkout differs from the search-result price, the agent should abort the transaction and report the discrepancy to the user rather than completing the booking at the higher price. For hotels specifically, if a property shows as unavailable on Expedia, the agent should verify availability directly with the property before concluding the stay cannot be booked.
- Top Class Actions reports that a class action settlement was approved in which Expedia agreed travelers would 'no longer be misled as to the availability of class member hotels that are not bookable on Expedia's websites,' confirming the court-verified existence of false 'sold out' listings used to redirect consumers to fee-paying partner hotels.
- Top Class Actions' original lawsuit coverage explains that Expedia's site 'falsely shows there is no availability at the hotel' and redirects consumers to partner hotels that pay Expedia a fee, with the complaint characterizing the practice as deliberate deception.
- A Frommer's investigation quotes an Expedia spokesperson acknowledging that the platform runs two separate systems for shopping and booking fares, and that these systems 'will rarely return disparate fares' — confirming that the displayed price is not always the price confirmed at booking.
Human handoff required for
Escalate to a human when the total price shown at the final Expedia checkout screen (including all mandatory resort fees, destination fees, and taxes) exceeds the price displayed in the initial search results, before confirming or paying for the booking.
- The FTC finalized a Junk Fees Rule (effective May 12, 2025) directly prompted by over 72,000 consumer complaints about mandatory fees being disclosed late in the checkout flow on hotel booking platforms including OTAs like Expedia, confirming a documented gap between search-result prices and final checkout totals.
- Expedia's own spokesperson acknowledged in published reporting that the platform's separate shopping and booking systems can return differing fares, meaning the price displayed at search is not guaranteed to hold at checkout.
Escalate to a human when a hotel property shows as 'sold out' or 'unavailable' on Expedia but the booking is time-sensitive or high-priority, so a human can verify actual availability directly with the property before concluding the stay cannot be booked.
- A court-settled class action (Buckeye Tree Lodge et al. v. Expedia) established that Expedia listed hotels as 'sold out' or 'unavailable' on its platform when those properties were in fact available to book directly, in order to redirect consumers to fee-paying partner hotels.
- The settled lawsuit confirmed a verified pattern of false availability display on Expedia's platform, meaning an 'unavailable' status in search results cannot be treated as a reliable signal that a property is genuinely unbookable.
Escalate to a human when the price shown at the Expedia checkout step for a flight differs materially from the price displayed during the initial search, rather than proceeding to confirm the booking at the higher fare.
- Expedia's own internal acknowledgment, reported publicly, that its shopping system and booking system are separate and can return 'disparate fares,' meaning a displayed flight price at search is not always the price that holds at checkout.
- Consumer complaints of prices jumping materially at the final booking step on Expedia remain documented across multiple forums through at least 2025, corroborating the platform's own admission of fare discrepancy between systems.
Five discrepancy categories were checked for Expedia.com. Pricing (discrepancy_pricing): Confirmed finding — documented gap between search-result prices and final checkout totals for hotel mandatory fees, grounded in the FTC Junk Fees Rule finalization and widespread consumer complaints specific to OTAs including Expedia. Availability (discrepancy_availability): Confirmed finding — a court-settled class action verified that Expedia displayed false 'unavailable' or 'sold out' statuses for hotels to redirect consumers, and Expedia's own spokesperson confirmed fare discrepancies between its shopping and booking systems. Identity/merchant-of-record (discrepancy_identity): No confirmed finding — Expedia's dual merchant/agency model is disclosed in SEC filings, but no regulatory enforcement action or court record documenting deceptive identity deflection was found at the required evidentiary threshold. Policy enforcement (discrepancy_policy): No confirmed finding — searches returned only anecdotal complaints and general regulatory guidance not specific to Expedia; no verified systemic gap between stated and enforced cancellation/refund policies was found. Undisclosed constraints (discrepancy_undisclosed_constraint): No confirmed finding — a UK CMA finding on undisclosed paid placement and general service fee commentary were surfaced, but neither constitutes a mid-transaction capability gap or hidden booking blocker meeting the inclusion bar.