Booking.com and Flight Deals — Plan the Stay and the Flight Without Picking the Destination First

September 10, 2026

Two travel tools land together. Booking.com searches stays anywhere Booking covers — hotels, apartments, guest houses — for a real date range and a real set of guests, then opens any one of them in full: what guests actually say, which rooms are left, when check-in opens. Flight Deals answers the question the other way round: you know where you're leaving from and roughly when, and you want to be told where's worth going. Ask for a hotel and you get a hotel. Ask for flights and you get flights. Ask Alfrada OS to plan a week somewhere and it does both.

What you can do

• Search stays by describing the place — query takes plain text ("Lisbon", "Lisbon City Centre", "Shoreditch"), and Booking matches it to its own destination in the same call. No ids to look up, no extra round trip; the matched destination comes back with the results so a follow-up search can reuse it.
• Search a real stay, not a vague one — check_in_date with check_out_date, or check_in_date with nights when the user says "three nights". Set adults, rooms, and children_ages — ages matter, because Booking prices and filters rooms by them, so "5,8" and "15,16" return genuinely different inventory.
• See nightly and total price side by side — every result carries both, plus taxes and charges, the pre-discount price where there is one, and flags for free cancellation, no prepayment and current deals.
• Sort the way you're actually deciding — popularity, price_low_to_high, review_score, stars_high_to_low, stars_low_to_high or distance.
• Open one property in full — operation: "property" on any result's link returns the description, address, check-in and check-out times, room types with prices, amenities, house rules, what's nearby, and a review breakdown by category (staff, location, cleanliness and so on).
• Read what guests say, in aggregate — instead of a handful of individual reviews, you get the recurring themes across every review with a mention count: "Location: central setting near Praça do Comércio — 435 mentions". More useful than three opinions, and nobody's name is attached.
• Find flights when the destination is still open — Flight Deals takes an origin (a city, an airport name, or an IATA code — or nothing, in which case your nearest airport is used, the same way Google Flights already does) and returns ranked round-trip deals to wherever is currently good value, each with the dates, the price, the typical price for that route, stops, duration and a booking link.
• Steer the deals in plain language — prompt takes a free-text brief: "somewhere warm in November", "beaches and islands", "cheap city breaks". This is how you ask for a month or a mood.
• Or filter them precisely — max_price, stops, travel_class, included_airlines and passenger counts, when you know exactly what you want.
• Know when a deal is genuinely a deal — each result is compared against Google's typical price for that route, so "£380 to Dubai" is labelled 36% above typical and "£919 to Sydney" is labelled 23% below typical. A low number and a good price aren't the same thing.

Where this shows up

• You need a hotel and nothing else. "Find me a hotel in Lisbon for 3 nights in March, two adults, under €200 a night." No flight lookup happens; you get stays with prices.
• You want to go somewhere but don't know where. "Cheap flights from Lahore, anywhere, in November." Deals come back ranked, with the November dates Google found.
• You're planning the whole trip. "Plan me a week in Lisbon in March." Stays come back priced for March, and flight deals come back from your nearest airport.
• You're deciding between two hotels. "Compare these two Booking listings — which has better reviews for cleanliness, and which has free cancellation?" Paste both links.
• You're travelling with kids. "Family room in Paris, 4 nights in May, two adults and children aged 5 and 8." The ages go through to Booking, so the rooms and prices you see are the ones you can actually book.
• You have a budget and a long weekend. "Where can I fly from London for under £250, nonstop?"

Try it

• "Find me a hotel in Lisbon for 3 nights in March, two adults."
• "Cheap flights from Lahore anywhere in November."
• "Cheap flights anywhere next month." (no origin needed — your nearest airport is used)
• "Plan me a week in Lisbon in March — flights and somewhere to stay."
• "Where can I go from London for under £300, nonstop?"
• "What do guests actually complain about at this hotel?" (paste a booking.com link)
• "Best-rated hotels in Paris under €250 a night, 1–4 May, with free cancellation."
• "Somewhere warm to fly to from Karachi in December."

Heads up

• Always give dates when you want prices. Booking will return properties without them, but every price comes back empty — so a dateless search tells you what exists, not what it costs. Alfrada says so explicitly rather than showing you blank prices.
• Check-in can't be in the past. If you say "March" and March has already gone, Alfrada uses next March. A genuinely past date is refused with an explanation instead of a confusing upstream error, and the same goes for a check-out before check-in, or a stay over 90 nights — Booking's limit.
• Flight Deals is origin-to-anywhere only. It cannot price a specific route: there is no destination parameter, and Google ignores one if you force it, quietly returning deals to entirely different airports. Ask for "Lahore to Lisbon on 12 March" and Alfrada uses the Google Flights tool instead. Flight Deals is asked to refuse rather than answer wrongly.
• Flight Deals has no date parameters at all. Google picks the dates for each deal. The only way to steer timing is through prompt — "in November", "over Christmas". Dates you pass are ignored upstream, so Alfrada refuses them and tells you how to ask instead.
• A prompt and filters are mutually exclusive — Google's rule, not ours. Combining a free-text prompt with max_price, included_airlines, a non-default stops or travel_class, or a passenger count above one adult, is rejected outright with an error. So "anywhere warm in November under $400" can't be answered in a single search: the month needs the prompt, the price cap needs filter mode. Alfrada picks the one that matters more, tells you which constraint it applied, and can filter the rest for you afterwards. It catches the clash before spending a call and names the exact parameter at fault.
• Individual guest reviews are deliberately not returned. Booking's property page includes named reviews — a first name, a country, and whether they travelled solo, as a couple or as a family with young children. That's personal data about identifiable guests, and it never reaches the assistant, the interface or any log. You get the aggregated pros and cons across all reviews instead, which is both more representative and cheaper to read. Alfrada will not tell you "Nancy from the US said…", because it never sees that.
• A city resolves to its main airport, the same way Google Flights already resolves it — so both flight tools agree on what a place means. If you want a different airport, name it ("flights from Gatwick") or pass the code directly. Google's deals engine only accepts a specific airport once you add a prompt or a filter; a city-wide code silently returns nothing there, so Alfrada never uses one.
• Prices are per stay unless the field says nightly. The total is for the whole booking; the nightly figure is per night. Alfrada shows both and says which is which, because the difference across a week is the whole decision.