Dreamfare

Showing 25 of 44 from the live probe.

• Create a Dreamfare trip

  Save a travel plan as a Dreamfare trip the traveler can open, edit with their crew, and book. Pass the full day-by-day plan in one call via `days`. Stops are enriched shortly after creation (photos, map pins, booking links), so re-read with get_trip if the traveler asks to book. Before creating a plan for a destination, check list_saved_places for the traveler's saves there (they needn't mention them) and ask whether to include them — add_saved_places_to_trip carries them over with pins and link

• Add stops to a trip

  Add stops (places, activities, meals, stays, transport) to an existing Dreamfare trip. dayIndex is 0-based; read the trip first with get_trip if unsure of its days. Optional presentation controls customize the visible result without changing the action; use compact/full layout and only the sections or result selection advertised by this tool.

• Put saved places into a trip

  Turn the traveler's library into itinerary stops WITH their pins, photos, tips and partner links intact (re-adding by name via add_stops would lose those). Pick places by id (list_saved_places), a whole folder, or everything a video import found (importId from import_video — the video's own day hints place each stop). Whole-city entries are skipped. Places land on dayIndex unless spreadAcrossDays is set. Optional presentation controls customize the visible result without changing the action; use

• Edit a trip

  Edit anything on a trip in one batched call: trip details and notes (update_trip), stops (update_stop / remove_stop / move_stop, by stopId from get_trip), days (add_day / update_day / remove_day, by 0-based dayIndex), and the planning stage (finalize locks the trip for sharing and booking; reopen unlocks it). Omitted fields keep their value; null clears. finalize/reopen run AFTER the other actions — a finalized trip rejects edits, so reopen it in its own call first. Optional presentation control

• Delete a trip

  Delete a trip the traveler owns (also unpublishes it from Explore). Requires echoing the exact trip title as confirmTitle — only call this after the traveler explicitly asks to delete the trip. Optional presentation controls customize the visible result without changing the action; use compact/full layout and only the sections or result selection advertised by this tool.

• Read a trip

  Read one Dreamfare trip: days, stops (with stopIds for edit_trip), the packing list, and per-stop booking links. When the traveler wants to book a stop, give them its bookingUrl — bookings through it earn them commission back. Optional presentation controls customize the visible result without changing the action; use compact/full layout and only the sections or result selection advertised by this tool.

• List the traveler's trips

  List the traveler's Dreamfare trips (own and shared), newest first — a lookup for trip ids. To show a trip, follow with get_trip, which renders the trip card.

• Edit a trip's packing list

  Add, check off, uncheck, or remove packing-list items on a trip. Item ids come from get_trip's packing array (or this tool's response). Personal items are visible only to this traveler; shared items belong to the whole crew. Optional presentation controls customize the visible result without changing the action; use compact/full layout and only the sections or result selection advertised by this tool.

• Mark a stop as booked

  Record that the traveler completed a booking for a stop (on the partner site or elsewhere). When they booked through the stop's tracked bookingUrl this also opens the commission credit that pays their share back once the partner reports it. Optional presentation controls customize the visible result without changing the action; use compact/full layout and only the sections or result selection advertised by this tool.

• Re-check hotel prices on a trip

  Re-quote every upcoming partner-priced stay on the trip against live rates and report what moved (previous → current). At most once per stay per day. Returns the refreshed trip. Optional presentation controls customize the visible result without changing the action; use compact/full layout and only the sections or result selection advertised by this tool.

• Trip essentials: eSIM, rental car, transfers

  Tracked partner links for the trip's destination country: a travel eSIM (data the moment they land), rental cars, airport pickup and private transfers. Booking through these links earns the traveler's commission share, like stops. Optional presentation controls customize the visible result without changing the action; use compact/full layout and only the sections or result selection advertised by this tool.

• Plan a whole trip with Dreamfare's planner

  Build a complete day-by-day trip in one call using Dreamfare's own planner: real venues (with opening hours), a stay, activities from partner inventory, the traveler's saved places woven in, pins, photos and booking links — all server-side, in about 10 seconds. Costs Stardust credits like planning in the app (get_profile shows the balance). Prefer this for 'plan me N days in X' requests; use create_trip when the traveler has dictated the exact stops themselves. The traveler's SAVED places at the

• Search places to stay

  Live hotel/stay inventory with real prices for a destination and date window. Every amount includes taxes and fees; nightly is total ÷ nights, an average that reads higher than the room-only rate booking sites headline. The default order is partner relevance, NOT price: when the traveler wants something cheaper, names a budget, or asks to compare, re-run with maxNightly/minNightly and sort 'cheapest' (or 'rating') instead of repeating the same call — a plain repeat returns the same screen. price

• Search activities and tours

  Bookable activities, tours and experiences for a destination. Attach one with add_option_to_trip (kind 'activity'). Plain activity stops added via add_stops also get matched to partners automatically, so search here only when the traveler wants options. Default order is partner relevance: for budget or 'cheaper' asks set maxPrice/minPrice and sort 'cheapest' instead of repeating the search; priceRange summarizes what was found. Say what kind of experience with q ('food tour', 'sunset cruise', 'd

• Discover real places

  Real venues for a destination — restaurants, activities, hotels, landmarks, shopping — with ratings, pins, and photos (partner inventory + cached Google Places, the app's own Explore surface). Use it to ground a plan in real places. Each result carries an itemDraft: attach one to a trip with add_option_to_trip (kind 'place', echoing the itemDraft unchanged) to keep its pin, photo, and any partner bookability. For hotels pass checkIn/checkOut (or use search_stays): without them prices are for a s

• Attach a searched option to a trip

  Attach one search result to a trip as a stop: kind 'stay' / 'activity' takes the option/offer object from the matching search tool; kind 'place' takes a search_places result's itemDraft. Echo objects exactly as returned. Stays need checkIn/checkOut. Say which day with dayIndex or date (a stay defaults to its check-in date) and, when the traveler has one in mind, the start time. The stop's bookingUrl (in this result and get_trip) is the link to present for booking. Optional presentation controls

• Find airport codes

  Resolve a city or airport name to IATA codes for search_flights ('Lisbon' → LIS; 'London' → LON, the metro code covering LHR/LGW/STN/LTN, plus each airport). Call it whenever the traveler names a place rather than a code — never guess a code. A city (kind 'city') code searches every airport in that city and is the right pick unless a specific airport was named.

• Search and compare flights

  Search real flights for a route and date from the configured sources, including direct Kiwi.com search. Set limit to the requested number: 1 for one flight, 3 for three (the default); never pad missing results. Keep the requested sort order. Compare returned itineraries with `comparison.cheapest`, `fastest` and `best`, and their price/time differences. Prices by booking site exist only when that site actually supplied a quote; never imply that an unlisted vendor was searched. `bookingUrl` opens

• Refine and compare a flight search

  Read an existing search_flights board without another scrape. Use presentation.limit:1 or 3 for one or three fares; presentation.ids selects and orders exact offerId values before comparison. Keep the original searchId. Price, airline, stops, bags, local-time and duration filters narrow the retained candidates; sort changes their order. The original route, dates, party, cabin, currency and source constraints remain fixed. Start search_flights again to broaden the original search or change those

• Put a searched fare on a trip

  Attach one fare from search_flights to a trip as a flight stop. Pass the searchId and the fare's id exactly as returned. The stop lands on the day matching its departure date. It is a plan, not a booking: the traveler books through the stop's Book button, which opens the site that quoted the price.

• Research one option

  Everything known about ONE hotel, tour or place, researched: a photo gallery, what's good about it (editorial summary, what reviewers say), key facts (stars, guest score, capacity, cancellation and instant-book policies; duration, languages, meeting point, inclusions and exclusions, itinerary; opening hours, price level, phone, website), features/amenities, the exact location, and prices — per booking site for hotels, tours & tickets with prices at landmarks. Use it when the traveler asks about

• Compare options side by side

  Two to five options of one kind (stays, activities or places) in one table: price (per night / per person / total), rating and reviews, distance, duration, stops, cancellation, features — the best cell in each row is marked and `verdict` names the winners (cheapest, best rated, closest, fastest). Each is researched like get_details, so the table is exact, not a summary of the search screen. Use it whenever the traveler is weighing a few ('which of these', 'A or B', 'the cheapest that's still wel

• Import places from a video or post

  Extract the real places from a TikTok, Instagram, YouTube, Facebook, or Reddit travel link — watched, transcribed, and geocoded. When the traveler shares such a link, call this tool with the URL directly: the DREAMFARE SERVER fetches and watches the video, so never claim you cannot open links or ask for an upload. Runs asynchronously (~30–90s): poll get_import for the results. Found places (with their tips) land in the traveler's saved-places library; once done, drop them into a trip with add_sa

• Import places from pasted text

  Extract the real places from text the traveler pastes — notes, a friend's list, a blog post, an itinerary email — and save them (with any tips) to their library, exactly like a video import. Runs asynchronously: poll get_import. Costs Stardust credits like importing in the app (failed imports refund). Needs at least 40 characters. Optional presentation controls customize the visible result without changing the action; use compact/full layout and only the sections or result selection advertised b

• Import places from a screenshot or PDF

  Read a traveler-provided screenshot or travel PDF into saved places and tips. Supply raw base64 bytes (maximum 8,000,000 characters). Uses the same membership and import credits as import_video. Poll get_import using the returned id. Optional presentation controls customize the visible result without changing the action; use compact/full layout and only the sections or result selection advertised by this tool.