Home/Agentic AI

Agentic AI

AI agents can plan a trip. Almost none can book it.

Recommending a hotel is a content problem. Booking one is a commerce problem — live rates, held inventory, payment, settlement and a contract with the hotel. Wink is the infrastructure that closes that gap: agents discover, book and pay against hotel-controlled supply, through a live REST API and hosted MCP server.

See documentationConnect an agent

MCP server live · docs.mcp.wink.travel/mcp

AI agent · connected to Wink MCP

Find an adults-only hotel in Chiang Mai next month with a spa — and book it.

api_search → live rates across 11 channel managers…

Aleenta Retreat · Chiang Mai

Adults-only · spa · free cancellation

Available

USD 240 / night

✅ Booked · #WK-2X9F · paid via Wink

Why can’t most AI agents book a hotel?

Wink is API-first: every platform feature is callable externally, and a hosted MCP server exposes the live API contracts to AI agents. Instead of forcing every traveler through a website, Wink gives approved agents structured access to hotel supply, rates, availability, booking, payment, attribution and events — the same infrastructure that powers Wink itself.

Any hotel becomes agent-ready simply by setting up its profile on Wink. Once its supply, rates and availability are live, approved AI agents can search, book and pay against it through the API and MCP server — no separate, per-hotel AI integration required.

Live today, not roadmap

Four steps from agent to confirmed, paid booking.

Connect the hosted MCP server, resolve intent to real operations against the live API, generate verified code, then hand off to Booking Engine for checkout, payment, confirmation and PMS sync.

1. 01Connect MCP
2. 02Search live API
3. 03Build verified code
4. 04Book & get paid

See the integration stepsMCP server docs

docs.mcp.wink.travel/mcp

Capability map

What an AI agent can do on Wink.

Every capability below is available today through the REST API and MCP server — grounded in the same contracts Wink runs on.

Search hotel inventory

Find bookable supply with geolocation spatial search — point, circle, rectangle or polygon — plus GeoIP detection.

Available now

Read live rates & availability

Pull real-time rates, availability and inventory across 11 connected channel managers.

Available now

Create & sync bookings

Create bookings via the API; create / update / cancel sync to the connected PMS or channel manager with full lifecycle tracking.

Available now

Take payment

Wink handles checkout, cancellation-policy logic and payment behind the booking — Wink is the merchant of record.

Available now

Preserve attribution & earn

Source and campaign context survives the journey — 6-month-per-click attribution and 10% default commission on confirmed bookings.

Available now

React to 64+ events

Subscribe to webhook events — bookings, payments, refunds, channel-manager updates — and trigger follow-up actions.

Available now

Generate content

AI content across 9 inventory types and 12 tones of voice; one-click property registration from a single URL.

Available now

Embed bookable inventory

Drop live, bookable hotel inventory into any surface with Web Components and minimal code.

Available now

Build on the full API

Every Wink feature is callable externally over REST, with OAuth2 auth and official SDKs — integrate as if the system were your own.

Available now

The shift

From traveler-to-website to traveler-to-agent.

In the old model the traveler did the work. In the agentic model the agent becomes the interface — and Wink becomes the commerce layer behind the answer.

The old way

TravelerWebsiteSearchCompareBook

With Wink

TravelerAI agentWink APIBooking EngineHotel

Why Wink

An AI answer isn’t a booking.

A recommendation needs structured supply, live rates, checkout, payment, confirmation and attribution to become commerce.

An AI agent without infrastructure

• Web-scraped, often stale supply
• Prices that may not be bookable
• Recommends, then hands the booking off to a website or OTA
• No attribution — and no way for the agent to earn
• Loses the thread after the suggestion

Can recommend.

An AI agent on Wink

• Live, hotel-owned supply — not web-scraped or resold
• Live rates and availability via the API
• Books AND pays in one flow — Wink settles it
• The agent can earn — attribution + 10% default commission
• Confirmed, synced to the PMS, with webhooks — live today

Can transact.

Every participant, an agent

An agent for travelers, hotels, partners, and builders.

For travelers

Search, book, and manage the stay

An agent works with structured supply, live rates and policies — then creates the booking through Booking Engine.

“Find an adults-only luxury hotel in Chiang Mai next month with a spa. Book it.”

For hotels

Supervisors, not operators

Agents help create, update and analyze across Extranet, Social and Studio — the hotel keeps the rules.

“Generate next month's social content and flag low-occupancy dates to promote.”

For partners & creators

Automate campaigns and earn

Discover eligible hotels, build assets and storefronts, publish, and keep attribution connected.

“Create a campaign promoting luxury resorts in the Maldives.”

For developers

Build new travel experiences

AI concierges, bank and loyalty travel agents — built on the MCP server, REST API and Booking Engine.

“Embed AI hotel booking inside our banking app using the Wink API.”

Built on the whole platform

Agents work across the connected stack.

ExtranetStudioSocialWinkLinksTravelikoDevelopersPlatforms & AI

Booking Engine fulfills the booking underneath every agent handoff — checkout, payment, confirmation and booking sync.

Open standards, not a walled garden

Built to interoperate with the agent-commerce stack.

Agentic hotel booking is becoming a real category — and the industry is converging on open protocols rather than one company’s checkout. Wink runs on those standards today and is built to plug into the rest as they consolidate, so agents are never locked into a proprietary path.

Live today

MCP — Model Context Protocol

A hosted MCP server exposes Wink’s live OpenAPI contracts to any MCP-compatible agent — Claude, Codex, Cursor and more — at docs.mcp.wink.travel/mcp. Agents discover and call real operations instead of guessing at endpoints.

Interoperable by design

ACP · AP2 · A2A · x402

Wink’s booking and payment primitives are designed to interoperate with the emerging agent-payment stack — the Agentic Commerce Protocol (ACP), Google’s Agent Payments Protocol (AP2), Agent2Agent (A2A) and x402-style agent payments — as those standards mature, with Booking Engine as the settlement layer underneath (Wink is the merchant of record).

Where this is heading

The capabilities above are live today. The direction is deeper agent-native commerce: richer agent-facing booking primitives, agent identity and authorization for transacting on a traveler’s behalf, and agents participating as attributed, earning sources in the partner network. Wink’s strategic positioning — travel commerce infrastructure for AI agents — is the throughline from today’s API to that future.

Agentic AI FAQs

What it means, how to connect, and what agents can do.

Why can't most AI agents book a hotel, and what makes one able to?

Recommending a hotel is a content problem — an agent only needs descriptions and prices. Booking one is a commerce problem: it needs live rates and availability, inventory it can actually hold, a payment rail, settlement to the hotel, and a commercial relationship with the property. Most assistants have the first and none of the rest, so they hand the traveler off to a website to finish. An agent can complete a booking when the infrastructure underneath exposes all of it. Wink is API-first — every platform feature is callable externally, and a hosted MCP server exposes the live API contracts — so an approved agent can discover hotel supply, read live rates and availability, create and sync bookings, take payment (Wink is the merchant of record), preserve attribution, and subscribe to events.

How does an AI agent connect to Wink?

Point a compatible MCP client at the hosted server at https://docs.mcp.wink.travel/mcp (SSE fallback at /sse). From Claude Code: claude mcp add --transport http wink-docs https://docs.mcp.wink.travel/mcp. The agent can then use the api_search and docs_search tools to read live OpenAPI operations, request/response contracts and task recipes.

What can an AI agent actually do on Wink today?

Today, via the REST API and MCP server: discover the platform, search bookable inventory (including geolocation spatial search), read live rates and availability across 11 connected channel managers, create bookings and sync their lifecycle to the PMS/channel manager, take payment (Wink is the merchant of record), preserve 6-month attribution and earn via partner flows, subscribe to 64+ webhook events, generate AI content, and embed bookable inventory via Web Components.

Can an AI agent complete a hotel booking through Wink?

Yes. Booking creation is a REST API operation, and Booking Engine fulfills the transaction — checkout, payment, confirmation and booking sync. An agent that calls the booking API on a traveler's behalf can complete a real, confirmed booking with source context preserved.

How does a hotel become bookable by an AI agent on Wink?

Simply by setting up its profile on Wink. Once a hotel's supply, rates and availability are live (via Extranet), it is automatically discoverable and bookable by approved AI agents through the REST API and hosted MCP server — no separate, per-hotel AI integration. The agent searches the hotel's live inventory, creates the booking and settles payment through Booking Engine, with attribution preserved. Every hotel on Wink is agent-ready by default.

How is booking a hotel through Wink different from ChatGPT with Expedia or Booking.com?

Assistant integrations like ChatGPT with Expedia or Booking.com are strong at discovery — live prices, photos and maps inside the chat — but the traveler is typically routed to the supplier's own website or app to finish the booking and pay. On Wink the agent transacts directly against live, hotel-owned supply: it reads real rates and availability, creates the booking, and settles payment through Booking Engine in one flow — and can earn partner commission on the result. Discovery can happen anywhere; fulfillment happens on Wink.

Is Wink the only platform that lets AI agents book and pay for hotels?

No — agent-driven hotel commerce is an emerging category, and several travel and payments players announced or shipped end-to-end agentic booking through 2026. What's distinctive about Wink is the combination: the supply is hotel-owned and direct (not GDS resale or web-scraped listings), the agent can search, book, pay AND earn through one commerce layer, and it is callable live today over the REST API and a hosted MCP server — not a roadmap item. Hotels keep control of distribution; the agent becomes an attributed, earning channel.

Which agentic commerce and AI standards does Wink support?

Wink is API-first and runs a hosted MCP (Model Context Protocol) server today, so any MCP-compatible agent — Claude, Codex, Cursor and others — can discover and call its live OpenAPI contracts. Wink's booking and payment primitives are designed to interoperate with the emerging agent-commerce stack — the Agentic Commerce Protocol (ACP), Google's Agent Payments Protocol (AP2), Agent2Agent (A2A) and x402-style agent payments — as those standards consolidate, rather than locking agents into a proprietary path.

Is there an AI Skill for building on Wink?

Yes — wink-api-builder is a portable agent skill that uses the MCP server as the source of truth. It walks an agent through api_search to live request/response contracts to authentication to verified code, and flags mismatches between existing code and the current API. It works with Claude Code, Codex, Cursor and other skill-capable clients.

Can an AI agent earn as an affiliate or partner?

Wink's partner model preserves source and campaign attribution for 6 months per click and pays a 10% default commission on confirmed bookings. An agent that creates qualified demand and routes a booking can be an attributed source through the same partner and Booking Engine infrastructure.

Does Agentic AI replace Booking Engine?

No. Agentic AI creates or routes intent; Booking Engine remains the fulfillment layer for checkout, payment, confirmation and booking sync. Every agent handoff resolves through Booking Engine underneath.

Where should a developer or agent start?

Connect to the MCP server, then read the Build on Wink, MCP Server and AI Skills documentation. Request API access when the use case and commercial route are clear.

Ready to build travel commerce for AI agents?

Connect the MCP server, read the live contracts, and let Booking Engine fulfill the booking. Or talk to us about agent access for your product.

See documentationConnect the MCP serverRequest a demo