How do AI assistants book trips and activities, and what makes a booking system agent-bookable?

Planning comes easily to an assistant: it can search, compare and draft a day out. Booking is where it usually stops. 69% of travelers have used AI to plan or book a trip, but only 17% have used it to book activities (GetYourGuide, Apr 2026). In the US, 56% of travelers used AI for travel in the past year (Phocuswright, Mar 2026).

Without an official way in, an assistant is left sending the guest a link, or clicking through a booking page built for people, hoping the times it saw are still open.

As of October 2026, besides daybag, only four booking platforms used by outdoor operators give an AI agent an official way to book: Bókun, TicketingHub, EquipDash and Twice Commerce.

The Model Context Protocol (MCP) is an open standard for connecting AI assistants to outside tools. A server lists its tools, each with a name, a description and the inputs it takes. The assistant decides when to call one and shows the person what it did.

The spec dated 2026-07-28 makes MCP stateless: anything that has to last between calls, such as a hold, travels as a handle the server mints and the assistant passes back (MCP spec, Jul 2026).

An assistant books for someone else, so it should hold before it books. The hold keeps the place while the assistant shows the price and details, and it expires on its own if the person walks away.

It should also send an idempotency key, a unique ID per booking. Connections drop and assistants retry; with the key, a repeated request returns the booking already made instead of a second one. Here's how holds and keys stop double bookings.

OCTO, the open booking standard that resellers connect through, works the same way: a booking stays on hold until it's confirmed or expires, and a UUID from the client prevents duplicates (OCTO docs).

The gap between 69% and 17% (GetYourGuide, Apr 2026) is partly plumbing: an assistant can only book where the booking system lets it. When it can, the guest gets a confirmed booking in the conversation instead of a link and a form.

It counts most at the last minute. 46.5% of leisure activity bookings are made 0–3 days ahead (GetYourGuide, Nov 2025), when there's little time for back and forth.

Every operation in daybag's API is also a tool on its MCP server, for the outfitter's own assistant or one their developer builds.

• Check availability with the availability_get tool.
• Hold with bookings_create and hold_minutes, then confirm with bookings_confirm. Holds expire on their own.
• Pass an idempotency_key, and a retry returns the same booking.
• Claude Code and Cursor connect with an API key; claude.ai and ChatGPT connect by signing in to the outfitter's daybag account with OAuth.

Travelers book on the outfitter's website or hosted booking page, from the same live availability. MCP comes with every plan, including Free: see how to connect and pricing.