Explore homes
open_explorerOpen the published vacation-home browser in ChatGPT. Search by destination, guests and amenities, inspect photos and save homes to the conversation shortlist. For a trip's mood, experience or visual preferences, pass the traveler's description as semantic, preserving their meaning and language. Keep destination, guests, bedrooms, pool and amenities in their structured filters. q is a literal name/location/text filter: do not duplicate the semantic description into q. Copy experiential preferences verbatim from semantic into semanticPreferences; copy essential experiential requirements with their qualifiers into semanticRequirements, without inventing needs. Keep those requirements when refining the search. Use reassessPropertyIds with semantic to reassess known homes against the current needs. Read the returned semantic.matches, assessments, coverage and limitations: similarity alone does not prove a fact, and source-based claims remain attributed. Do not infer availability from matching. If semantic search is unavailable, explain the failure; do not silently substitute a keyword search or relax requirements. Use English or neutral Latin American Spanish (tú).
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| q | No | Search public property names, locations and approved introduction text. | |
| city | No | ||
| page | No | ||
| pool | No | ||
| place | No | Place key from the live filter catalog. | |
| bounds | No | Map viewport as south,west,north,east in degrees; keeps homes whose public area center is inside it. West greater than east crosses the antimeridian. | |
| guests | No | Minimum sleeping capacity; required actual party size when requesting quote enrichment. | |
| locale | No | en | |
| region | No | ||
| arrival | No | ||
| country | No | ||
| feature | No | Collection key from the filter catalog. | |
| currency | No | ||
| semantic | No | Rank indexed, eligible homes by text and photo similarity. Does not establish hard facts; no lexical fallback when unavailable. | |
| amenities | No | Comma-separated amenity keys; every requested amenity must be explicitly present. | |
| departure | No | ||
| quoteMode | No | Optional price/availability enrichment. exact uses supplied dates and guests; estimate requires estimateWindowStart, estimateWindowEnd, estimateNights and guests for a clearly labeled sample within supplied flexible bounds. Search does not wait for every host or filter unknown homes out. | |
| relatedTo | No | Published property ID. Find other homes from its organization, same locality first, then region/country and other locations. Excludes the source property. Additional filters still combine with AND. | |
| minBedrooms | No | ||
| minBathrooms | No | ||
| organization | No | Exact organization slug returned on a property or in get_filters. Restricts results to that organization, across destinations. | |
| estimateNights | No | Sample-stay nights, required. Only with quoteMode:estimate. | |
| estimateWindowEnd | No | Latest sample departure (YYYY-MM-DD), paired with estimateWindowStart. Window must fit estimateNights (required), at most 150 days. | |
| estimateWindowStart | No | Earliest sample arrival (YYYY-MM-DD), paired with estimateWindowEnd. Only with quoteMode:estimate. Preserve the traveler's flexible month or date range. | |
| reassessPropertyIds | No | Up to four previously discussed public property IDs to reassess against this semantic request alongside fresh matches. Use when refining or comparing earlier suggestions. This reserves comparison slots only: current factual filters, indexed source ownership and every essential requirement still apply. It does not keep an old recommendation or establish fit. Omit for a new search without earlier candidates to reassess. | |
| semanticPreferences | No | Individual experiential preferences, each copied verbatim from semantic. Interpret the traveler in context: separate requested preferences without adding needs. Keep related words together when they describe one room, view or relationship. These are questions to assess, not property facts; omit for factual-only searches. | |
| semanticRequirements | No | Essential trip requirements, each copied verbatim from semantic with all relationship and provenance qualifiers. Every one must have source-backed support before a home is returned. Preserve these from the conversation; ordinary preferences belong in semanticPreferences. Omit when no essential experiential requirements were stated. Interpret semanticRequirements as conditions the accommodation or its setting must satisfy. Preserve essential support for the traveler's primary activity and access needs, including when expressed indirectly. Preserve the traveler's complete context in semantic. When the traveler states an explicit offering condition together with their own plans, circumstances or reasons, copy the complete offering condition as the essential; do not create an additional standalone proof obligation for the traveler's plan or circumstance. Keep any context necessary to understand the condition, its scope and relationships. Do not broaden a specific access requirement into proof of every aspect of the trip, and do not drop an actual offering condition because it is motivated by a traveler's circumstances. When a circumstance leaves the required accommodation or access condition ambiguous, ask one short clarifying question before searching; do not submit the circumstance itself as a property-proof requirement. If the offering condition itself is ambiguous, clarify it in the real conversation instead of inventing a stricter condition. |