Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we
store it to create your key and to recognise you if you sign in with another
provider. See our Privacy Policy and
Terms.
openapi: 3.2.0
info:
title: Cubi Estate Search API
version: 0.1.0
description: 'Operations tagged Search across 2 of this provider''s published API definitions: cubi-estate-openapi.json, cubi-estate-openapi.yml. Each path carries the servers of the definition it was published in.'
servers:
- url: https://mcp.cubi.estate
description: Host serving this spec (Swagger UI at https://mcp.cubi.estate/docs loads /openapi.json); also hosts the MCP endpoint https://mcp.cubi.estate/mcp
tags:
- name: Search
paths:
/search/map:
get:
summary: Embeddable multi-pin results map fragment (chat results iframe, §22)
description: 'Multi-pin sibling of `/listing/{id}/map`: renders the CURRENT search
result set (`?ids=` comma-separated listing ids) as one Leaflet map for the
web chat''s map toggle. Same public/no-auth iframe posture, `?theme=dark` and
`?lang=` contract as the §6 fragment. Invalid ids are dropped and the list
is soft-truncated to `_SEARCH_MAP_MAX_IDS`; 404 only when nothing valid or
known remains. One `filter_properties` hydration (id_in) — rows come back in
the scorer''s order, which a map doesn''t care about.'
operationId: search_map_fragment_search_map_get
responses:
'200':
description: Successful Response
content:
text/html:
schema:
type: string
tags:
- Search
x-refined-from:
- cubi-estate-openapi.json
- cubi-estate-openapi.yml