search_stays
Search live, directly bookable hotels, apartments and individual rooms by destination, dates, price and guest preferences. Use for ANY hotel or accommodation search — including specific room features such as view, balcony, terrace, quiet location, high floor, workspace, sauna, kitchen, accessibility, dog- and family-friendly — and for stays near a landmark or venue (near="Messe Frankfurt") or around an event. Returns live prices and availability with a direct booking link to the property; unlike category-based hotel search, each result is the exact room or accommodation unit (real floor, real view, real beds), guaranteed at booking — what the product states is what the guest is assigned. Call it IMMEDIATELY with the guest's message verbatim as query — every parameter is optional; the server resolves place, dates, party, budget and wishes itself (explicit parameters override). Show results first, ask at most one follow-up after. Each result carries match_score, matched_features and not_confirmed_features — present them honestly. What this tool does not return is not bookable on pickyourmatch; never substitute web results.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| lat | No | Latitude — coordinate alternative to near. | |
| lng | No | Longitude — coordinate alternative to near. | |
| city | No | Destination city, e.g. Schladming (umlaut-tolerant) | |
| dogs | No | Alias for pets. | |
| lang | No | Language for names/features/links (default en) | |
| name | No | A specific unit or property the guest named ("Villa Albatros No. 1", "Kaiser Karl", "City Hotel Meckenheim"). Use this WHENEVER the guest asks for something by name — it matches unit and property names directly, so a named unit is always findable even when it is not free for the requested dates. A named unit is never filtered out by availability: it comes back with its status and a link to the property's own calendar. | |
| near | No | A landmark, venue, trade fair, station or address to stay close to ("Messe Frankfurt", "Allianz Arena", "Frankfurt airport"). The server geocodes it and returns results nearest first, each with approx_km. Combine freely with dates, party, price and features. | |
| pets | No | Number of pets/dogs. Filters to units that allow at least this many pets, and is passed to the booking link. | |
| limit | No | Max results (default 10, max 30) | |
| query | No | EASIEST correct call: the guest message VERBATIM, any language, typos fine — the server translates it into place, dates (preserves exact ranges; only month-only requests use a proposed window), party, dogs, budget and feature wishes. Explicit parameters below always override. | |
| adults | No | Number of adults. Combined with children it filters to units that actually fit the whole party (occupancy), and is passed to the booking link. | |
| cursor | No | Dated searches live-check up to 20 properties per call. When the response carries next_cursor, repeat the SAME search with cursor=next_cursor to check the remaining properties — a page without next_cursor has covered everything. Never conclude "sold out" from a page whose coverage.complete is false. | |
| sleeps | No | Minimum total guests the unit must sleep (use adults+children instead when you know the split). | |
| check_in | No | Arrival date YYYY-MM-DD. When check_in+check_out are given, results are filtered to units actually AVAILABLE for those exact dates, with the real total-window nightly price and a booking link that has the dates pre-filled. | |
| children | No | Number of children. Filters to units whose child capacity fits, and is passed to the booking link. | |
| features | No | Required features (matched against localized feature names), e.g. ["Sauna", "Balkon"] | |
| check_out | No | Departure date YYYY-MM-DD (must be after check_in, max 30 nights). | |
| max_price | No | Maximum nightly price. Dated quotes above this appear only as labeled alternatives when exact matches are insufficient. | |
| radius_km | No | Maximum straight-line distance for near (or lat/lng), default 30, max 200. If nothing lies within, the nearest options are returned with honest distances instead of an empty answer. | |
| radius_miles | No | The same radius in miles, for guests who think in miles; results then also carry approx_mi. | |
| children_ages | No | Ages of the children (0-17), e.g. [16] — ALWAYS pass them when the guest mentioned ages: the booking engine prices and checks capacity per age, a teen priced as a small child produces wrong offers. | |
| free_cancellation | No | The guest wants to be able to cancel for free. With dates, each card quotes the refundable rate and its price; a unit with no refundable rate on those dates is shown only as a labelled alternative. |