hotels.com

No evidence found that Hotels.com (an Expedia Group brand) implements or supports the A2A protocol. Expedia Group's publicly announced agentic strategy centers on MCP servers (a B2B MCP server described as arriving within months as of May 2026). The Google AI Mode agentic booking partnership naming Expedia as a partner operates via Google's own UCP layer, not A2A specifically. The A2A launch partner list (50+ organizations including Atlassian, Box, Cohere, PayPal, Salesforce, SAP, ServiceNow, Workday) includes no travel OTAs or Expedia Group brands. Hotels.com has no independent developer portal; all API/developer surface is under Expedia Group, and no Expedia Group A2A evidence was found either.

No evidence found that Hotels.com (an Expedia Group brand) has implemented or been approved for ACP. Named ACP merchant participants in publicly available sources include Etsy, Shopify-platform merchants, and retail brands such as Walmart, Target, Sephora, Nordstrom, Best Buy, Lowe's, and Wayfair — Hotels.com is not among them. Expedia Group does have a ChatGPT App integration (launched October 2025) for travel search and discovery, but this is a separate app-based channel distinct from ACP merchant implementation; these are not the same protocol surface. Expedia is also referenced as a flagship merchant for the Amex ACE framework, which is a different program. ACP access requires an approved partner application via OpenAI (developers.openai.com/commerce); no evidence that Hotels.com has applied or been approved. Recorded as not_found rather than confirmed_absent because no Hotels.com-specific statement or deprecation notice was located — absence from published merchant lists is the basis for this judgment.

No evidence found that hotels.com or its parent Expedia Group has adopted, announced support for, or been named as a partner in the AP2 (Agent Payments Protocol) ecosystem. Named AP2 launch partners (60+ organizations including Mastercard, American Express, PayPal, Adyen, Coinbase, Etsy, Salesforce, Worldpay, and others) do not include hotels.com or Expedia Group. Third-party travel-industry analysis mentions OTAs like Expedia and Booking.com as potential future adopters, but this is commentary, not a vendor-specific AP2 commitment. Recorded as not_found rather than confirmed_absent because no hotels.com-specific statement or deprecation notice was located — only the absence of the vendor from all published partner lists.

No official MCP server published by hotels.com or its parent Expedia Group under the Hotels.com brand was found. Expedia Group publishes an official MCP server (github.com/ExpediaGroup/expedia-travel-recommendations-mcp) branded as Expedia Travel Recommendations — covering hotel, flight, activity, and car rental search — but it is explicitly tied to the Expedia brand and EXPEDIA_API_KEY, with no Hotels.com-specific branding, endpoint, or documentation. Two third-party, community-built MCP wrappers were found: corneyc/hotels-mcp (a Cloudflare Worker proxying Hotels.com via RapidAPI, unsanctioned) and an Apify actor scraped from Hotels.com data — both excluded as non-official routes. No vendor-specific announcement, deprecation notice, or developer documentation from hotels.com itself regarding MCP was located.

No evidence found of hotels.com implementing or adopting MPP (the Stripe+Tempo Machine Payments Protocol, launched March 18, 2026). Named MPP launch partners and integrated services include Anthropic, DoorDash, Mastercard, Nubank, OpenAI, Ramp, Revolut, Shopify, Standard Chartered, Visa, Lightspark, and Browserbase; hotels.com is not among them. A separate, easily confused finding: Expedia Group (parent of hotels.com) is listed as a flagship merchant for American Express ACE (Agentic Commerce Experiences, April 2026) — a distinct protocol from MPP with different sponsors and mechanics. No hotels.com developer documentation, mpp.dev services directory listing, or vendor announcement referencing MPP was located. Recorded as not_found rather than confirmed_absent because no hotels.com-specific statement about MPP was found, only the absence of any presence in MPP partner lists and documentation.

No evidence found that hotels.com has implemented NLWeb /ask or /mcp endpoints. Named NLWeb early adopters at Build 2025 include Chicago Public Media, Common Sense Media, DDM, Eventbrite, Hearst (Delish/Allrecipes), Inception Labs, Milvus, O'Reilly Media, Qdrant, Shopify, Snowflake, and Tripadvisor; hotels.com (Expedia Group property) is not among them. No vendor-specific statement, deprecation notice, or third-party confirmation of hotels.com NLWeb deployment was located, so this is recorded as not_found rather than confirmed_absent.

No Hotels.com-specific UCP evidence found. Google's named lodging UCP launch partners (announced at Google I/O, May 2026) are: Booking.com, Expedia Group, Hilton, Marriott International, IHG, Accor, Amadeus, Choice Hotels, Trip.com, and Wyndham. Hotels.com is a brand within Expedia Group, but the UCP partnership is attributed at the Expedia Group parent level with no vendor-specific confirmation that Hotels.com operates as a distinct UCP endpoint or participant. UCP for Lodging remains in waitlist/early-access phase (see https://developers.google.com/hotels/ucp); no Hotels.com-branded integration, announcement, or documentation was located.

No evidence that hotels.com (an Expedia Group brand) has implemented WebMCP. WebMCP is a W3C Community Group draft protocol currently in Chrome origin trial (Chrome 149 as of mid-2026); publicly named early adopters at Google I/O 2026 are retail brands — Nike, Sephora, Target, Ulta Beauty, Walmart, Wayfair, Fenty, and Steve Madden — with no travel OTA in that list. Hotels.com and Expedia Group appear in separate 2026 AI/agent contexts (Spark/MCP server integrations, Google UCP hotel expansion) but none of those are WebMCP. The Cloudflare Browser Run WebMCP hotel demo uses a Google-authored demo site (googlechromelabs.github.io/webmcp-tools/demos/hotel-chain/), not hotels.com. Recorded as not_found rather than confirmed_absent because no hotels.com-specific statement or deprecation was located — the absence is from the named-adopter record, not a vendor declaration.

No evidence found of hotels.com (an Expedia Group brand) adopting or announcing support for the x402 protocol. The x402 Foundation's named Premier and General members include Google, Mastercard, Fiserv, AWS, Cloudflare, Anthropic, Vercel, Circle, and Solana Foundation — hotels.com and Expedia Group are not among them. A historical 2014 Coinbase blog post exists noting Expedia.com accepted Bitcoin as a hotel payment method via Coinbase, but that is unrelated to x402. No vendor-specific statement, integration announcement, or developer documentation from hotels.com or Expedia Group referencing x402 was located.

No Hotels.com-specific ChatGPT App found on OpenAI's platform. Confirmed launch partners on the OpenAI ChatGPT Apps surface include Expedia, Booking.com, Tripadvisor, IHG, Wyndham, and Lighthouse — Hotels.com is not among them. Hotels.com is an Expedia Group brand, and the Expedia-branded ChatGPT app (https://www.expedia.com/product/expedia-in-chatgpt/) covers the Expedia brand specifically, not Hotels.com. No vendor-specific statement, deprecation notice, or confirmed absence from Hotels.com was located; this is recorded as not_found rather than confirmed_absent.

Distributor-side hotel search, real-time availability checking, rate retrieval, end-to-end booking creation, itinerary management, and cancellation. Hotels.com inventory is accessible as part of Expedia Group's shared lodging supply pool (750,000+ properties). No Hotels.com-specific API exists — inventory is accessed through Expedia Group's Rapid API, which covers all Expedia Group brands.

Hotels.com is an Expedia Group brand with no independent proprietary API. Distributor-facing programmatic access is via the Expedia Group Rapid API (docs: https://developers.expediagroup.com/docs/products/rapid), which replaced the deprecated EAN XML API (switched off 2019). Access requires a partner application reviewed case-by-case; sign-up page is https://partner.expediagroup.com/en-us/join-us/rapid-api. Unofficial scraper-based APIs exist on RapidAPI marketplace (e.g., tipsters, apidojo) but are not sanctioned by Hotels.com or Expedia Group.

Supply-side property connectivity: hotel properties, property management systems, and channel managers can push availability, rates, and restriction updates directly to Expedia Group brands including Hotels.com; also supports booking retrieval, property content management, and regulatory data updates.

The Expedia Group Connectivity Hub (docs: https://developers.expediagroup.com/supply/lodging) is the supply-side proprietary API, distinct from the demand-side Rapid API. It targets PMS vendors and channel managers enabling hotels to list across all Expedia Group storefronts including Hotels.com. Three core APIs are mandatory for all connectivity providers: Availability and Rates, Bookings, and Property Management. Certification by Expedia is required before production access is granted.

No evidence found of hotels.com publishing llms.txt, AGENTS.md, /.well-known/agent, or any comparable self-declaration file. Direct HTTP fetches were blocked in the research environment (all returned connection failures), but web searches — which did return hotels.com's actual robots.txt content, confirming the domain is reachable — produced no indexed or cached versions of any agent-discovery file at the hotels.com domain. Expedia Group (hotels.com's parent) has announced MCP capabilities via its developer hub but has not published any self-declaration convention file on the hotels.com domain itself. Status recorded as not_found rather than unable_to_verify because broad web search coverage (including direct robots.txt retrieval) gave sufficient indirect access to identify the absence.