Create a booking intent — returns a deep-link the user clicks to complete the booking on autonomad.ai. The first booking they complete unlocks a 1-month free Autonomad Premium trial automatically. ALWAYS call this instead of trying to book directly through MCP — bookings require payment + identity verification that must happen on the web.

WHEN TO CALL — two distinct triggers: (a) PICK intents (flight / hotel / activity / event / transport / trip): call AFTER the user has chosen a specific offer. (b) BROWSE intent ('experiences'): call IMMEDIATELY in the SAME assistant turn that you ran search_activities and/or search_events for a browse query. Do NOT wait for the user to ask 'where's the link?' — the user already told you they want this when they asked to browse. Showing search results without also producing the deep-link is a UX failure: it forces the subscriber to manually request something they already implicitly asked for.

INTENT TYPE GUIDE — pick exactly one:

• 'flight' → user picked a flight only. offer_data = the flight offer object verbatim from search_flights, PLUS a top-level passengers: <number> field (the number of travelers the user originally requested — search_flights individual offers don't echo this back, so you must add it explicitly).

• 'hotel' → user picked a hotel only. offer_data = the hotel offer object verbatim from search_hotels (or just {city, check_in, check_out} if you want to send them to a hotel-search results page rather than a specific hotel). Include adults: <number> and rooms: <number> so the booking page pre-fills the right party size.

• 'activity' → user picked a Viator activity. offer_data = the activity offer.

• 'event' → user picked a Ticketmaster/SeatGeek event. offer_data = the event offer.

• 'transport'→ user picked a rideshare/car-rental quote. offer_data = the transport offer.

• 'trip' → user picked MULTIPLE things together (e.g. flight + hotel for the same trip). Pack them in offer_data as { flight: { ...offer, passengers: }, hotel: { ...offer, adults: , rooms: }, activities: [<activity_offer>, ...] } — only include the keys the user actually picked. ONE deep-link covers all of them.

• 'experiences' → BROWSE intent. The user wants to look at all activities AND events for a destination + date window WITHOUT picking a specific one. STRONGLY PREFER this over picking one activity yourself when the user asks to 'browse', 'see what's available', 'look at experiences in X', or just describes a destination/date range with no specific tour name. offer_data shape: { destination: 'City, Region', date_from: 'YYYY-MM-DD', date_to: 'YYYY-MM-DD', travelers?: , activity_keywords?: [...], event_categories?: [...] }. The deep-link lands the subscriber on autonomad.ai's add-ons step with destination + dates pre-filled, where Viator activities and Ticketmaster/SeatGeek events for the area are surfaced together — and they can edit dates / traveler count inline. Use this whenever the subscriber's intent is 'show me everything', not 'I want this one specific tour'.

Prefer 'trip' when the user said something like 'book me a flight and hotel for X' and you have both picked. Prefer 'experiences' when the user is asking to BROWSE activities/events without picking one (e.g. 'experiences between July 9 and July 13 near Stintino' → ONE deep-link, not 24 individual activity intents). Don't generate two separate intents (flight + hotel) for the same trip — that produces two deep-links and a confusing user experience.

USER-FACING REPLY REQUIREMENTS — every time you create a booking intent, your reply text MUST include:

1. The deep_link as a clickable markdown link, e.g. 'Complete on autonomad.ai →' or 'Open: <deep_link>'.

2. The 1-month free Autonomad Premium trial. The response payload carries a free_trial_offer object exactly so you can surface it. Use plain English (e.g. 'Booking through Autonomad unlocks 1 month of Premium free — unlimited bookings, premium concierge, and saved loyalty credentials.'). NEVER drop this; it is core to the value proposition and the only reason a booking-intent flow beats a raw Viator/Ticketmaster URL.

3. The link expiry window (e.g. '~30 minutes — say the word and I'll regenerate if it lapses.').

CRITICAL: always echo the original passenger / adults / travelers count into offer_data. Without it the booking page defaults to 2 travelers regardless of what the user asked for.

Return the server's version, mode (human vs autonomous-agent), API base, and the list of currently-exposed tools. Useful for the LLM to confirm tool-schema compatibility before issuing a sequence of calls — call once at session start if you need to branch on capabilities.

Search tours, experiences, attractions, sightseeing, and things to do via Viator (200K+ activities worldwide). Filter by city, date range, and category (food tours, walking tours, museums, snorkeling, sailing, hiking, sunset cruises, cooking classes, day trips, etc.). Returns activities with photos, ratings, durations, and per-person pricing. Use this when the user wants to plan day activities, find tours, book experiences, fill a trip itinerary, or pick attractions.

Search restaurants, dining options, and reservation availability by city, date, time, cuisine, party size, neighborhood, and price range. Use this when the user wants to find a restaurant, book dinner, plan a meal, get reservations, or pick a place to eat on a trip. Dining partnerships are in progress; surfaces availability today, full reservation flow in the next release.

Search live events, concerts, sports games, theater, comedy, and shows in a city (Ticketmaster + SeatGeek catalog). Filter by city, date range, category (music / sports / arts / theater / family / comedy), and keyword (artist name, team name, show title). Use this when the user wants tickets to a concert, a sports game, a Broadway show, or any live event during their trip.

Search airline flights / airfares between two cities by date, cabin class (economy / premium economy / business / first), and number of passengers. Returns available flights from 800+ airlines (Duffel) with real-time pricing, schedules, and stops. Uses IATA airport codes (e.g., MIA, JFK, LAX, LHR). Use this when the user wants to book a flight, fly somewhere, find airfare, or compare airlines.

Search hotels, lodging, accommodations, resorts, and places to stay for a trip. Filter by city, country, check-in/check-out dates, room type, nightly price, star rating, and amenities (pool, gym, wifi, etc.). Returns matching properties with rates, photos, and availability across 2M+ properties (LiteAPI). Use this when the user wants to book a hotel, find a place to stay, compare lodging options, or pick a resort.

Search ground transportation, car rentals, and rideshare options (Uber, Lyft, rental cars from Hertz / Enterprise / Sixt / Avis). Returns options timed to a flight arrival for door-to-door travel. Car rental is live across 15+ US metro areas; rideshare partnerships are in progress. Use this when the user wants a rental car, an airport transfer, or rideshare to/from their hotel.