Cian Connector

Reads Cian through the site's own JSON API, called from inside the operator's Chrome over CDP: the search endpoint answers an in-page POST, and the offer card embeds its whole state in window._cianConfig. No HTML is parsed. Plain HTTP is blocked by Cian's WAF on IP reputation (a 403 «Обнаружен подозрительный трафик» page, no captcha), so there is no anonymous tier.

When to use

• Find offers by filters: deal (sale / long-term rent / daily rent), property type, region, rooms, price range, total area
• One offer's price, its price history, layout, building, address, metro, description and publisher
• Real estate only. For goods use the marketplace connectors; for price comparison across shops use compare_prices — Cian takes no part in it

Tools available

• cian_search(deal, offer_type="flat", region=None, rooms=None, price_min=None, price_max=None, area_min=None, area_max=None, page=1) — offers via search-offers-desktop, 28 per page. deal is sale, rent (long-term) or daily (посуточно); offer_type is flat, room, house or commercial. price_rub is None for an offer without a stated price — never 0, and price_unit says what it buys.
• cian_card(offer_id_or_url) — one offer: price, price_history, rooms, areas, floor, building, address, metro[], description, views, agent.

Not an MCP tool: cian_selfcheck() is a tri-state drift canary. It is CLI-only — marketplace-mcp doctor runs every connector's canary at once.

Region is an id, not a name

Cian addresses regions by its own numeric ids. The connector knows only the four below (KNOWN_REGIONS, used in error messages); any other id must come from cian.ru. Known and verified live:

Anything else needs the Cian id (visible as region= in a cian.ru search URL). Do not guess an id: a wrong one returns another region's offers with correct-looking prices. Default is CIAN_REGION (1, Moscow).

Filters: what the search does and does not do

• No text search. There is no query string; "двушка у метро Сокол" has to become rooms=[2] plus a region and a price range. Metro and street filters are not exposed; filter the returned rows by address / metro yourself.
• rooms applies to flats only: any of 1–6, plus Cian's codes 7 (свободная планировка) and 9 (студия) — verified live, and easy to get backwards. Rooms (offer_type="room") are searched as flats with Cian's room code 0 — the caller's rooms is ignored there.
• price_min / price_max are rubles, in whatever unit the deal implies: total for sale, per month for rent, per night for daily.
• total_count is Cian's aggregatedCount — the de-duplicated figure the site shows, usually below the raw offerCount.

Long-term and daily are two markets, never one page

deal="rent" and deal="daily" are separate on Cian and the connector keeps them separate (for_day "!1" vs "1"). Measured live in Moscow on 2026-09-10: 25 411 long-term flats, 53 441 daily ones, and dropping the flag entirely returns a mixture, which is why the connector never does.

• A daily price is per night. price_unit is "day", and the category comes back as dailyFlatRent / dailyRoomRent / dailyHouseRent. Cian leaves price_period and lease_term null there, so price_unit is the only honest signal — do not rank a 5 000 ₽ night against a 90 000 ₽ month.
• Daily covers flat, room and house only. offer_type="commercial" with deal="daily" is refused as a bad request: Cian accepts that query upstream and answers zero, which would read as "nothing free today" rather than "this market does not exist".
• For a stay of about a month, both markets are worth a look: long-term with lease_term == "fewMonths" (снять на несколько месяцев), and daily where a monthly discount is usually negotiated in the description rather than published as a field.

What a row carries and how to read it

Confirmed against live payloads captured 2026-09-09 (fixtures in the package):

• Price comes from bargainTerms.priceRur, then bargainTerms.price, then priceTotalRur. A new-building card has only the latter two, and a daily offer has no priceRur at all — the parser reads all three, so a null price means Cian shows none, not a missed key.
• price_unit is computed by the connector, not Cian: total, month or day. Quote it whenever you show a price, and never average across units.
• title is Cian's own only on some offers; otherwise the short info line ("1-комн.кв. · 12/22 этаж") or a composed "rooms, area, floor" stands in. Do not treat the title as a marketing name.
• metro on a search row is the station Cian marks as the tile's own (isDefault), not the shortest travel time — a 7-minute bus ride does not outrank a 10-minute walk. The card returns every station in that order, with mode walk or transport.
• category tells the market: newBuildingFlatSale is a developer's primary offer (agent.user_type = developer, saleType fz214), flatSale is resale, roomSale, houseSale, officeSale and friends for the rest.
• Long-term rent rows add price_period (monthly), lease_term (longTerm / fewMonths) and deposit_rub. is_by_homeowner is True only when the owner publishes without an agent; None means Cian did not say.
• created_at is Cian's local ISO time without a zone; updated_at on the card is UTC. Do not compare them as if they were in one zone.
• views on the card is parsed from Cian's own text («12907 просмотров, 98 за сегодня»): the first number, total views.

What the source cannot do (and the connector does not pretend)

• No agent/agency tool: /agents/<id>/ renders profile facts only as page text, with no structured state, so no tool reads it. The publisher's name, type, id, offer count and account age ship inside the card's agent field.
• No reviews — real estate has no per-offer review pool.
• No geo-suggest: regions and metro are ids, not names (see above).
• No phone numbers: the card knows how many phones the offer has, not their values.

Gotchas

• 403 inside the browser session (transport_down with "WAF block") means Cian challenged the scraping profile: open cian.ru in that Chrome, pass the check if one is shown, retry. From a datacenter IP a cold session can start blocked; a warmed-up session answered 8 requests in a row with no 429.
• Pace is deliberate: 1.5 s between requests, one tab at a time. Do not hammer pages 1–10 in a loop; ask for what is needed.
• parser_drift means the envelope or _cianConfig shape changed — the connector will not hand back a half-parsed card as if it were data. Run the canary, then fix the parser.
• A removed offer may render as "объявление не найдено" → not_found.
• Verification story: a green selfcheck proves the transport answered and the parser found ids, prices and addresses. It does not prove a particular price is current — Cian's price_history on the card is the evidence to quote when it matters.

DSH activation

In DeepSeek Harness, the default profile exposes only compare_prices and compare_sources through the cheap compare mount. Per-marketplace tools and marketplace_sources require RU_MARKETPLACE_MCP_FULL=1 and a profile restart; do not call them in the default mode. Cian is never part of the compare mount, so it is only reachable in the full profile. In standard MCP clients (Claude, Cursor, Codex, Gemini CLI, OpenCode), Cian tools require mounting the unified marketplace-mcp server (--profile full, configured by default in .mcp.json and gemini-extension.json) or the standalone cian-mcp server — they are not exposed by compare-mcp or decision-mcp.