This is a human-readable page. If you're an agent, fetch /vendor/kayak/AgentRouting.json or /vendor/kayak/AgentContext.json directly.

kayak.com

last checked 2026-06-23

Overview

Does kayak.com support MCP?

No confirmed MCP support was found for kayak.com as of 2026-06-23.

What agentic protocols does kayak.com support?

As of 2026-06-23, kayak.com has confirmed support for proprietary.

Is kayak.com's API publicly accessible or partner-gated?

Partner only.

Does kayak.com explicitly prohibit automated access?

Yes. kayak.com's terms of service explicitly prohibit automated or scraper access to the public website without prior written permission.

Is kayak.com agent-ready?

Partial. kayak.com supports some agentic workflows but requires a human handoff for certain operations — see the protocols and summary sections for details.

Protocols

A2A not found

No vendor-specific evidence located that KAYAK exposes or consumes an Agent2Agent (A2A) interface, nor any reference to the historical 'Agent Communication Protocol' name. KAYAK's recent agent-related announcements describe its own KAYAK.ai assistant and a ChatGPT integration (apps-on-ChatGPT surface), with no mention of A2A agent cards, A2A endpoints, or Linux Foundation A2A participation; third-party A2A travel demos using KAYAK are community-built and not sanctioned. Recorded as not_found rather than confirmed_absent because no KAYAK statement explicitly declines or deprecates A2A.

ACP not found

ACP (OpenAI/Stripe Agentic Commerce Protocol) launch and expansion partners surfaced in research include URBN brands (Anthropologie, Free People, Urban Outfitters), Coach, Kate Spade, Revolve, Ashley Furniture, Scheels, Sézane, SharkNinja, ESW, Glossier, Vuori, Spanx, SKIMS, and Target; Kayak.com is not among them. Kayak has a ChatGPT integration (an older plug-in and an AI Mode powered by ChatGPT) but no evidence locates Kayak as an ACP merchant or a Stripe ACP travel partner, and travel/OTA verticals are not the current ACP focus. Recorded as not_found rather than confirmed_absent because no Kayak-specific statement disclaiming ACP participation was located.

AP2 not found

AP2 was announced by Google and Coinbase in September 2025 with 60+ launch/supporting partners; named participants include Mastercard, American Express, PayPal, Klarna, Adyen, Coinbase, Intuit, JCB, Revolut, Salesforce, ServiceNow, Worldpay, Lowe's Innovation Labs, PwC, 1Password, Shopee, and Etsy. Kayak.com is not among the named partners and no Kayak-specific statement of AP2 adoption was located, so this is recorded as not_found rather than confirmed_absent (no vendor self-statement of non-adoption was found).

MCP not found

No vendor-operated MCP server located on kayak.com or in KAYAK's developer surface. All MCP servers referencing KAYAK in the public registry and search results are third-party scraping wrappers (Apify listings by jupri, parseforge, axlymxp, scrapestorm, scraper-mind; Bright Data's kayak data-extraction MCP) — none are sanctioned by KAYAK. API Tracker explicitly reports no MCP servers for KAYAK. Recorded as not_found rather than confirmed_absent because no KAYAK statement explicitly denying MCP support was located.

MPP not found

MPP is a March 2026 multi-rail machine-payment standard from Stripe and Tempo with a public services directory of 100+ integrated services covering model providers, dev infra, and some commerce; no listing for Kayak was located in that directory or in Stripe/Tempo launch announcements. Kayak's only publicly documented agentic-commerce moves remain its OpenAI/ChatGPT partnership and internal AI itinerary features, with payments still handled via its standard checkout rather than any machine-payment rail. Recorded as not_found rather than confirmed_absent because no Kayak-specific statement disclaiming MPP was located.

NLWeb unable to verify

No usable finding available for this protocol (no legitimate scan available within the candidate window).

UCP not found

Google's May 20, 2026 UCP travel expansion announcement named specific lodging/OTA launch partners — Booking.com, Expedia Group, Hilton, Marriott, IHG, Accor, Amadeus, Choice Hotels, Trip.com, Wyndham — and Kayak (a Booking Holdings metasearch brand) is not among them. No Kayak-specific UCP implementation, endpoint, or vendor statement was located, so this is recorded as not_found rather than confirmed_absent. Passive checks (HTTPS, docs quality, domain alignment) were not performed against a Kayak UCP surface because none was found to check.

WebMCP not found

...

x402 not found

No evidence located that kayak.com has adopted or integrated the x402 protocol. Public x402 ecosystem listings (x402.org/ecosystem, x402daily.xyz, Coinbase developer launches, Cloudflare's x402 Foundation announcement) name participants such as Coinbase, Stripe, Cloudflare, Visa, Chainlink, SKALE, Polygon, and Merit Systems; KAYAK is not among them. No vendor-specific statement from KAYAK was found either adopting or rejecting x402, so recorded as not_found rather than confirmed_absent.

openai_apps_sdk not found

OpenAI's Apps SDK launch (October 2025) named pilot partners Booking.com, Canva, Coursera, Figma, Expedia, Spotify, and Zillow; Kayak is not among them. Kayak's parent Booking Holdings is represented via Booking.com sibling, but Kayak itself has only the older 2023 ChatGPT plugin lineage and a 2025 'AI Mode'/'Ask AI' on kayak.com powered by ChatGPT, neither of which is a vendor-specific Apps SDK app. No vendor-issued statement explicitly denies an Apps SDK build, so recorded as not_found rather than confirmed_absent.

proprietary confirmed present

Search and comparison across flights, hotels, and cars (Flights Search, Flights Price Insights, Hotels Search, Cars Search, Autocomplete, Static Data Feeds), plus ad-unit APIs (CompareTo Ads, Inline Ads). Affiliate/comparison surface only — no booking, reservation creation, modification, or cancellation; bookings handoff to supplier/OTA sites.

Vendor publishes a documented affiliate/partner HTTP API surface at developers.kayak.com covering Flights, Hotels, Cars, Autocomplete, Static Data Feeds, Price Insights, and ad APIs (CompareTo, Inline). Access is gated: sandbox keys on request, production keys after affiliate use-case approval — capture as partner_only with non-self-serve enrollment in notes. HTTPS in use and domain alignment (developers.kayak.com / affiliates.kayak.com under kayak.com) verified passively; no booking/order-management endpoints documented, scope is search/comparison plus ad units.

self_declared_discovery unable to verify

Direct fetches from this environment to kayak.com returned no response (connectivity blocked), so the standard well-known locations (llms.txt, AGENTS.md, /.well-known/agent, /.well-known/agent.json, /.well-known/ai-plugin.json) could not be examined. No vendor announcement of such a file was located via search. Recorded as unable_to_verify rather than not_found because the passive check itself was blocked, per discipline rule distinguishing examined-and-empty from could-not-examine.

Summary

Has agent interface: partial

Apply to Kayak's affiliate/partner program at developers.kayak.com to obtain sandbox then production credentials for the documented HTTP API surface (Flights, Hotels, Cars, Autocomplete, Static Data Feeds, Price Insights, CompareTo/Inline ad units); use this for search and price-comparison only. For any actual booking, reservation modification, or cancellation, hand off the user to the supplier or OTA site Kayak links to — Kayak's own surface does not expose those actions. Do not scrape kayak.com; the Terms of Use explicitly prohibit automated data extraction.

AgentContext

Verified discrepancies

pricing discrepancy remediation claimed not reverified

Vendor claim: KAYAK displays hotel room prices in search results intended to represent the cost of a booking, with fees and taxes presented as a consolidated 'Taxes and Fees' line item at checkout.

What actually happens: The Texas Attorney General's lawsuit against Booking Holdings Inc. — the parent company that explicitly operates Kayak.com — found that consumers were shown artificially low initial room rates that were not actually available, and that mandatory fees were bundled with government taxes under a single 'Taxes and Fees' line item, obscuring the true mandatory cost from consumers prior to checkout. A $9.5 million settlement was reached.

Agent guidance: Do not treat the price shown on KAYAK's hotel search results page as the final bookable price. Before confirming any hotel booking, an agent must expand all fee line items at checkout and compare the full itemized total — including any amounts labeled 'Taxes and Fees' — against the originally displayed rate. If the checkout total exceeds the searched price by more than local tax rates would explain, surface the full breakdown to the user before completing the transaction.

last checked 2026-06-27

availability discrepancy active

Vendor claim: KAYAK presents itself as a fast, comprehensive travel search engine where users can compare prices and click through to book at the rates displayed. The KAYAK interface shows specific fares and rates as if they are currently available inventory.

What actually happens: KAYAK does not pull real-time inventory when generating search results. Displayed fares are cached or indexed prices that may no longer exist at the linked booking site. Users — and agents acting on their behalf — are regularly redirected to third-party booking pages where the advertised fare is unavailable or significantly higher. KAYAK's own help page explicitly states it cannot guarantee the prices it displays.

Agent guidance: Do not treat a fare or rate displayed on KAYAK as confirmed bookable inventory. Before completing any transaction on behalf of a user, an agent must click through to the actual booking site and verify that the displayed price is still available at that site before presenting the outcome to the user as successful. Never confirm a booking based solely on the KAYAK search results page.

last checked 2026-06-27

identity discrepancy active

Vendor claim: KAYAK presents itself as the booking interface and accepts payment through its 'Book with KAYAK' feature, creating a clear transactional relationship with the consumer at the point of purchase.

What actually happens: KAYAK's own Terms of Use explicitly state that it 'has no responsibility for the booking or the Travel Product' and directs consumers to 'address and resolve' all disputes 'with the Travel Provider and not with us.' Its Book with KAYAK Terms similarly disclaim all refund liability, stating KAYAK 'will not make any refund or accept responsibility.' BBB complaints document real cases where KAYAK and the underlying travel provider each blamed the other, leaving consumers without recourse from either party.

Agent guidance: Before completing any booking through KAYAK's interface, an agent must identify the actual merchant of record from the booking confirmation (which may be a separate OTA or airline, not KAYAK). If a refund or dispute is anticipated, the agent should record the name and contact information of the true fulfilling provider at time of booking, not rely on KAYAK as the dispute counterparty. Do not initiate chargebacks or refund requests through KAYAK — direct them to the merchant of record named in the confirmation email.

last checked 2026-06-27

undisclosed constraint discrepancy active

Vendor claim: KAYAK presents itself as a platform where users can search and complete travel bookings (flights, hotels, cars) directly. The search results interface implies that listed fares and rates are bookable, and the 'Book with KAYAK' feature suggests end-to-end booking capability on the platform itself.

What actually happens: KAYAK operates primarily as a metasearch engine that redirects users to third-party supplier or OTA sites to complete the actual transaction. Even on results that appear bookable on-site, the platform discloses in its Terms of Use that it acts as an intermediary and that final pricing, availability, and booking completion are controlled by the third-party provider — not KAYAK. An agent initiating a booking workflow on KAYAK may reach a point mid-transaction where it is redirected to a separate domain (airline, hotel, or OTA site) to enter payment details, and the displayed price or availability may no longer be valid at that point. This constraint — that KAYAK cannot itself complete most bookings and has no control over supplier-side failures — is not surfaced clearly on the search results page.

Agent guidance: An agent must not treat a KAYAK search result as a confirmed booking. Before initiating any transaction, the agent should identify whether the result will complete on KAYAK itself ('Book with KAYAK') or redirect to a third-party site. If a redirect occurs, the agent should treat the destination site as the actual merchant, re-verify price and availability on that site before entering payment details, and be prepared for the transaction to fail or reprice at the supplier's page. Do not rely on KAYAK-displayed prices as binding.

last checked 2026-06-27

Human handoff required for

Escalate to a human when the total price shown at the third-party checkout (after clicking through from KAYAK) exceeds the KAYAK-displayed rate by more than the applicable local tax rate would explain, because the bundled 'Taxes and Fees' line item may include mandatory resort or facility fees that were not visible in the original search result.

Escalate to a human when the fare or rate displayed on KAYAK's search results page is no longer available or is priced higher at the actual booking partner's site after redirect, before any payment details are entered.

Escalate to a human when a refund, cancellation, or dispute arises for a booking completed through KAYAK's 'Book with KAYAK' feature and it is unclear whether KAYAK or the underlying travel provider (airline, hotel, or OTA) is the merchant of record responsible for processing the refund, particularly when each party is directing the consumer to the other.

Escalate to a human when a mid-transaction redirect occurs from KAYAK to a third-party domain (a separate airline, hotel, or OTA site) to complete payment, because the agent is now operating on a different platform with potentially different pricing, availability, terms, and merchant identity than what was displayed on KAYAK.

Five categories were checked for kayak.com. Discrepancy_pricing: a finding was confirmed, grounded in the Texas Attorney General's $9.5 million settlement with Booking Holdings Inc. (KAYAK's parent) over deceptive hotel pricing and bundled fee disclosure on Kayak.com. Discrepancy_availability: a finding was confirmed, supported by KAYAK's own help documentation and multiple independent consumer sources documenting fares shown in search results that are unavailable or repriced at partner sites. Discrepancy_identity: a finding was confirmed, supported by KAYAK's own published Terms of Use and BBB complaint records documenting the merchant-of-record ambiguity and bilateral liability deflection between KAYAK and underlying travel providers. Discrepancy_policy: no actionable finding was surfaced; KAYAK's terms do explicitly disclose its no-refund stance and the BBB complaint page was located but yielded no independently verified systemic policy enforcement discrepancy rising above the inclusion threshold. Discrepancy_undisclosed_constraint: a finding was confirmed, documenting that KAYAK's metasearch redirect model and lack of control over supplier-side pricing and availability are not prominently disclosed on the search results interface, despite being acknowledged in KAYAK's own terms and help pages.