此内容尚不支持你的语言。

For Platforms & AI

The transaction layer behind your travel experience.

AI assistants, LLMs, agents, banks, super apps and platforms generate the intent. Wink is the hotel inventory, booking, attribution, payment and settlement you plug into — one integration, hotel-controlled supply, your users book directly.

Request API access Read the docs

One integration Hotel-controlled supply Settlement & payouts handled

Your product brings the intent

AI assistant · LLM · agent · bank · super app

Wink handles the transaction

Inventory

Availability & rates

Booking

Attribution

Payments

Settlement

Confirmed, paid booking · hotel keeps control

Intent isn’t a booking

Your product can recommend the perfect hotel. Turning that into a confirmed, paid stay needs live inventory, availability, booking, attribution, payment, settlement and post-booking servicing — backed by real hotel relationships. Those are commerce-infrastructure problems, not AI problems. Wink already solves them, so you can focus on the intelligence and the experience.

Commerce infrastructure

Everything between intent and a confirmed, paid stay.

Connect once over REST or the hosted MCP server. Wink provides the full transaction layer for hotel-controlled supply.

Inventory access

Hotel-controlled supply across 11 connected channel managers — not web-scraped or resold.

Live availability & rates

Real-time availability, rates and inventory, including geolocation spatial search.

Booking & lifecycle

Create bookings and sync create / update / cancel to the PMS or channel manager.

Attribution

Source and campaign context preserved — 6-month-per-click attribution decides who gets credited.

Payments

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

Settlement & payouts

Commission management, payouts and cross-party settlement handled through one platform.

Fulfillment & servicing

Confirmation, booking sync and 64+ webhook events for post-booking servicing and reconciliation.

REST API + MCP server

OAuth2, official SDKs and a hosted MCP server so agents and coding clients read live contracts.

Built for every demand platform

Wherever travel intent is born.

AI assistants & agents

Conversational and agentic products that discover, recommend and now transact on a traveler's behalf.

LLMs

Models that recommend stays in-context and need a real, bookable path — not a dead-end link.

Search & answer engines

Surfaces that answer travel questions and want the answer to convert to a confirmed booking.

Banks & fintech

Add hotel commerce and rewards-driven travel to an existing customer base.

Super apps

Fold bookable hotel inventory into an everyday app without becoming a travel company.

Corporate travel & loyalty

Programs and platforms that route demand into controlled, attributed booking flows.

The economics

Hotel-controlled. You earn on what you send.

Hotels control supply, pricing, promotions and commissions. When your platform drives a booking you can earn up to a 10% commission — a total cost to the hotel of about 15% all-in, versus 15–25% on the OTAs. The demand source is rewarded; the hotel keeps control and the guest.

Hotel-owned

Supply, pricing and promotions — not resold

Up to 10%

Commission to the demand source you bring

~15% all-in

Platform-driven cost vs 15–25% on the OTAs

Why Wink

Don’t rebuild travel commerce. Plug into it.

Build it yourself

Hotel contracts and relationships
PMS / channel-manager connectivity
Payments, settlement and payouts
Attribution and servicing

Years of work.

OTA / bedbank APIs

Resold inventory, not hotel-controlled
No control of pricing or the guest
15–25% cost
You don't own the relationship

Resale economics.

Wink

One integration, live today
Hotel-owned, controlled supply
About 15% all-in — and you earn
Hotel keeps control and the guest

Plug in and transact.

Dig deeper

Where to go from here.

The developer docs, the hosted MCP server, and how AI agents discover, book and pay — everything you need to scope the integration.

Build on Wink MCP server Agentic AI

Platforms & AI FAQs

How platforms and AI products plug into Wink's commerce infrastructure.

Who is the Platforms solution for?

Any platform that generates travel intent and wants to turn it into confirmed, paid hotel bookings: AI assistants and agents, LLMs, search and answer engines, banks and fintech, super apps, and corporate-travel or loyalty platforms. You bring the demand; Wink provides the hotel inventory, booking, attribution, payment and settlement infrastructure behind it.

Does Wink resell inventory like a bedbank or OTA?

No. Wink does not own inventory. Hotels control their supply, rates, availability, promotions and commissions. Your platform transacts directly against hotel-controlled supply through Wink — the hotel keeps control and the guest relationship, and you avoid OTA resale margins.

How does a platform integrate with Wink?

Through one integration: a REST API (OAuth2, SDKs) for inventory search, availability, booking, payment, attribution and webhooks, plus a hosted MCP server so AI agents and coding clients can read the live contracts. Booking Engine fulfills the transaction underneath (Wink is the merchant of record). Request API access to get started.

How does my platform earn?

When your platform drives a booking, you can earn up to a 10% commission. Wink takes its 5.5% first, then the commission is calculated on the remainder, so the total cost to the hotel for a platform-driven booking is about 15% all-in — versus 15–25% on the OTAs. The demand source is rewarded and the hotel keeps control. See the Pricing page for the worked detail.

Can AI agents and LLMs transact, not just recommend?

Yes. An approved agent can search live hotel-owned supply, create a booking and take payment in one flow through the REST API and hosted MCP server — not just hand the traveler off to a website. See the Agentic AI page for how agents discover, book and pay.

Build travel commerce into your platform.

You bring the intent. Wink handles the booking, payment and settlement — one integration, hotel-controlled supply.

Request API access Read the docs