Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
KAYAK website screenshot

KAYAK

KAYAK is a global travel meta-search engine headquartered in Stamford, Connecticut, owned by Booking Holdings (NASDAQ: BKNG). Founded in 2004 by Steve Hafner and Paul English, KAYAK aggregates results from hundreds of online travel agencies, airlines, hotel chains, car-rental companies, and cruise providers to help travelers compare prices for flights, hotels, cars, vacation packages, and cruises across a single interface. The company operates the KAYAK consumer brand, the HotelsCombined and Momondo meta-search brands, and KAYAK for Business, a corporate travel platform. KAYAK also runs a global Affiliate Network that lets publishers, content sites, and travel partners embed KAYAK search via co-branded search forms, iframes, deep links, and white-label search pages, with revenue share on redirected click traffic. KAYAK does not publish a self-serve public REST or GraphQL API for third-party developers; the consumer experience is delivered through its websites, native apps, voice integrations (Alexa, Google Assistant), and chat surfaces (Slack, Messenger). Programmatic access is limited to vetted partners under the KAYAK Affiliate Network and KAYAK Partner Network agreements, which typically expose XML/JSON feeds, deep-link builders, white-label search results pages, and conversion tracking — all gated behind a partner application process. There is no public OpenAPI specification, no published SDK, and no developer portal for KAYAK's underlying meta-search infrastructure.

human only

Index entry only — little beyond a description and a link, and nothing machine-readable enough for an agent to act on without a human reading the site first.

Kin Score

API Evangelist profiles KAYAK the way a machine reads it — 4 machine-readable artifacts, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.

Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — KAYAK scores 12.4/100 (minimal), with a separate agent-readiness read of 0/100 (human only). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.

Kin Score

This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.

Kin Score Kin Score How this is scored →
scored 2026-07-27 · rubric v0.5
Composite quality — 12.4/100 · minimal
Contract Quality 0.0 / 25
Developer Ergonomics 1.3 / 20
Commercial Clarity 3.7 / 20
Operational Transparency 0.7 / 13
Governance 0.0 / 12
Discoverability 6.8 / 10
Agent readiness — 0/100 · human only
Machine-Readable Contract 0 / 18
Agentic Access Contract 0 / 15
MCP Server 0 / 12
Machine-Readable Auth 0 / 10
Idempotency 0 / 9
Stable Error Semantics 0 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling 0 / 7
Typed Event Surface 0 / 6
Agent Skills 0 / 5
Well-Known Catalog 0 / 4
Consent & Bot Identity 0 / 3

How we profile KAYAK

Each block below is one kind of artifact we hold for KAYAK. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.

GraphQL 1

Where a provider ships GraphQL, the schema is the contract. We profile it alongside the REST surface so the whole interface is legible in one place.

GraphQL schemas published by this provider.

Security Posture 3

Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Kayak Com Domain Security

TLSv1.3 · DMARC

SECURITY

Kayak Com Vulnerability Disclosure

Hackerone · security.txt · contact published

SECURITY

Kayak Com Trust Center

SOC 2, PCI DSS, GDPR

SECURITY

Resources

Every other property we hold for KAYAK — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.

Build 1

SDKs, sample code, and the tooling you integrate with

Access & Security 3

Authentication, authorization, and security posture

Learn 1

Tutorials, courses, talks, and written guidance

Operate 1

Status, limits, changes, and where to get help

Commercial 2

Pricing, plans, and the legal terms of use

← All providers · Data indexed from github.com/api-evangelist/kayak-com · machine-readable index on apis.io