CUBI ESTATE

Search properties

Search Cubi Estate property listings across 14 European countries. Use this whenever the user asks to find or filter real estate: apartments, houses, villas, plots, by location, price range, bedrooms, area, or features like pool, balcony, sea view. Do NOT use for questions about a specific listing's details — that requires a separate fetch. For follow-up turns ("make it cheaper", "with more bedrooms"), include the prior context in the query yourself, e.g.: "prev

Get listing details

Fetch one Cubi Estate listing's full details. Use after a search when the user wants the long description, every feature/amenity, or the full image list for a specific result. Args: listing_id: Either the listing URL exactly as shown in a search result (e.g. https://www.example.com/property/123 — the simplest option, since every result card prints its URL), or a source-prefixed id from a prior result (e.g. `remax:12345`). Do not invent ei

Filter listings

Structured property filter — bypasses natural-language extraction. Use this when filters are already known (from prior turns or external state) and you want to skip the OpenAI NLU step. For free-text user queries like "cheap apartments near the beach", use `search_properties` instead. All list args are AND-combined; within a list, items are typically OR. Locations accept countries, regions, cities, neighborhoods. Types accept apartment/house/villa/townhouse/penthous

Corpus statistics

Day-by-day Cubi corpus activity — aggregate counts only, no listings. Use this for dashboards or "how is the corpus moving" questions: active listing totals, per-country breakdown, and per-day series of newly ingested listings, deactivated listings, and detected price drops. Args: days: Trailing window length in days (1-90, default 30). country: Optional full country name filter, e.g. "Portugal", "Spain". Case-insensitive. Omit for the whole cor

Data-layer coverage

Live coverage of Cubi's per-listing enrichment data layers. Use for a data-pipeline dashboard: how many active listings carry each environmental / accessibility layer, the flood-risk band split, and the per-country share of listings in a modelled High (1-in-20-year) river floodplain. Returns: JSON string. Warm cache (exact, ~6h fresh): {active_listings, cached: true, computed_at, coverage:{noise, air_quality, greenery, coastal, flood, drive_time, cam

Daily raise statistics

Daily-raise (new listings/day) for the Cubi corpus, SALE/RENT split — aggregate counts only, no listings. Complements corpus_stats (which has no transaction split). Table-ready: per-country today / yesterday / trailing-7-completed-day sale+rent, plus the top-15 providers by 7-day new-listing volume with their sale/rent split. (The 21-day per-country chart SERIES stays with corpus_stats — scanning 21 days of country/txn heap here is too slow for an interactive tool.)