Agentic AI
Any hotel.
Bookable by AI agents.
AI assistants are starting to book and pay inside the conversation. Wink is the commerce rail behind them: any hotel on Wink can be found, quoted, booked and paid by an AI agent, at its own rate, with no tech stack.
Booking Engine MCP · Machine Payments Protocol · Stripe Shared Payment Tokens
Watch it book
From one chat message to a paid hotel booking.
Search
The agent searches live inventory and loads the hotel's own rates for the dates.
Quote
Wink returns a firm price for the room. The quote has an expiry time and charges nothing.
Pay
The traveler approves in their own wallet. No card details typed into the chat.
Book
Wink confirms the booking, returns the code and receipt, and syncs it to the hotel's systems.
See the demo and what a hotel needs: how any hotel becomes bookable by AI agents.
Why it matters now
Being found by AI is no longer enough.
Recommending a hotel is a content problem. Booking one is a commerce problem: live rates, inventory, payment, settlement and a contract with the hotel. A booking completes wherever an agent can transact, and that is where the payment, the confirmation and the guest relationship land.
An AI answer
Recommends the hotel.
Then sends the traveler somewhere else to finish. The thread breaks, and the price shown may not be bookable.
An AI agent on Wink
Books and pays, in the conversation.
At the hotel's own rate, under its rules. Payment is collected for the hotel, which stays merchant of record.
The hard part
Six things an agent needs to book a hotel. Wink provides all six.
Live rates and availability
Read from the hotel's own setup on Wink, entered in Extranet or synced from its channel manager.
A firm, bookable price
A quote with an expiry time and a payment request. Requesting it charges nothing.
A payment the traveler approves
Approved in the traveler's own wallet, such as Link, which issues a Stripe Shared Payment Token.
A confirmation that reaches the hotel
Confirmation code and receipt, with the booking synced to the hotel's PMS or channel manager.
Safe retries
Retrying the same payment returns the same booking. It never charges twice.
Clear terms before paying
Room, dates, guests, cancellation policy and total, for the agent to show before the traveler approves.
For hotels
Any hotel. No developers, no new software.
Wink hosts the agent connection, the booking engine and the payment collection. The hotel never builds an MCP server or signs a payment-processor contract.
Step 1
Sign up on Wink
One-click registration reads your website and drafts your descriptions for you to review.
Step 2
Load rooms and rates
In the free Extranet, or connect the channel manager you already use.
Step 3
Get approved
Wink reviews and approves your hotel before it goes live on any channel.
Step 4
Get booked by AI agents
Agents find your hotel, quote your rate, take payment and confirm.
What it costs
No setup fee, no monthly fee, no contract. You pay only when a booking is confirmed.
See pricingWhat you keep
Your rate, passed through unchanged with no markup. Your rules. Your guests and their data.
For builders and platforms
Connect an MCP client. Wink does the rest.
Add the hosted Booking Engine MCP server, sign in with a Wink account, connect a wallet that supports Stripe Shared Payment Tokens, and ask for a room.
One room per booking, priced in USD, adults only
Link is one wallet option; it currently supports US accounts
Tempo stablecoin payments coming soon
# Booking Engine MCP
https://api.wink.travel/mcp/booking-engine
# permissions
mcp.read · marketing.read · payment.write
# the booking flow
destination_lookup_search_suggestions
inventory_search_city → property_inventory_get
agentic_booking_quote → wallet approval
agentic_booking_pay → booking_receipt_get
Open standards
Built on the protocols agents already speak.
Model Context Protocol
Agents call Wink's tools directly: search, quote, pay, retrieve.
Machine Payments Protocol
The agent pays a firm quote with a token from the traveler's wallet.
ACP · AP2 · A2A · x402
Booking and payment built to interoperate as these standards consolidate.
Questions hotels ask
Can AI agents book hotels directly?
Yes. On Wink, an AI agent connected to the Booking Engine MCP server can read live rates, get a firm quote, take the traveler's approved payment and confirm the booking, in one conversation.
Do I need a developer or new software?
No. Wink hosts the agent connection, the booking engine and the payment collection. You set up rooms and rates in the free Extranet or connect your channel manager.
What does it cost my hotel?
No setup fee, no monthly fee and no contract. Fees apply only to confirmed bookings; the Pricing page has the details.
Who is the merchant of record?
The hotel. Payment is collected on the hotel's behalf, and Wink is never the merchant of record for a stay.
Which AI assistants can book through Wink?
Any assistant that can connect to remote MCP servers with sign-in, such as Claude. The traveler signs in with a Wink account and connects a wallet that supports Stripe Shared Payment Tokens.
Does my hotel keep control of its rates?
Yes. Agents book the rates, availability and policies you set. Wink passes your rate through unchanged, with no markup.
Questions builders and platforms ask
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 (collected for the hotel, which stays merchant of record), preserve attribution for six months from the traveler's first click and earn via partner flows, subscribe to 70 webhook events, generate AI content, and embed bookable inventory via Web Components.
Is Wink the only platform that lets AI agents book and pay for hotels?
No. Agent-driven hotel commerce is an emerging category. 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.
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 six months from a traveler's first click. The hotel sets the commission for its property, 10% by default, earned 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.
One inventory.
Every demand channel.
Hotels control supply. We power everything that sells it.