--- name: pp-immoweb description: "Search Immoweb from the terminal with every site filter, then get the answers the site can't give: price cuts, days on market, commune medians and rental yield. Trigger phrases: `search immoweb`, `find an apartment to rent in Ixelles`, `is this house cheap for the area`, `which listings dropped their price`, `median rent in Ixelles`, `compare communes Ixelles and Saint-Gilles`, `what's new in my saved search`, `rental yield in Liège`, `use immoweb`, `run immoweb-pp-cli`." author: "sambassio" license: "Apache-2.0" argument-hint: " [args] | install cli|mcp" allowed-tools: "Read Bash" metadata: openclaw: requires: bins: - immoweb-pp-cli install: - kind: go bins: [immoweb-pp-cli] module: github.com/mvanhorn/printing-press-library/library/other/immoweb/cmd/immoweb-pp-cli --- # Immoweb — Printing Press CLI ## Prerequisites: Install the CLI This skill drives the `immoweb-pp-cli` binary. **You must verify the CLI is installed before invoking any command from this skill.** If it is missing, install it first: 1. Install via the Printing Press installer. It defaults binaries to `$HOME/.local/bin` on macOS/Linux and `%LOCALAPPDATA%\Programs\PrintingPress\bin` on Windows: ```bash npx -y @mvanhorn/printing-press-library install immoweb --cli-only ``` 2. Verify: `immoweb-pp-cli --version` 3. Ensure the reported install directory is on `$PATH` for the agent/runtime that will invoke this skill. If the `npx` install fails (no Node, offline, etc.), fall back to a direct Go install (requires Go 1.26.6 or newer). This installs into `$GOPATH/bin` (default `$HOME/go/bin`), so add that directory to `$PATH` instead: ```bash go install github.com/mvanhorn/printing-press-library/library/other/immoweb/cmd/immoweb-pp-cli@latest ``` If `--version` reports "command not found" after install, the runtime cannot see the binary directory on `$PATH`. Do not proceed with skill commands until verification succeeds. Talks to the same JSON endpoints the immoweb.be website uses, with no login and no browser, and exposes every search filter as a flag. Everything you look at lands in a local SQLite history, so `watch` shows what is new, cheaper or gone since last time, `deal` judges one listing against its neighbours, and `market` rebuilds the commune price statistics Immoweb no longer publishes. ## When to Use This CLI Use this CLI for Belgian property searches on Immoweb: finding houses, apartments, land or rentals by commune and criteria, reading one listing's full details, tracking saved searches over time, and answering price questions (is this listing cheap, what did it cost before, what yield does a commune give) from the locally recorded history. It needs no Immoweb account. ## Anti-triggers Do not use this CLI for: - Do not use it to contact agencies, book visits or post listings; those are Immoweb account or write actions it does not perform. - Do not use it for property outside Belgium or for other portals such as Zimmo, Immovlan or Biddit auctions. - Do not use it for official valuations, notary or registration-duty calculations; its figures are asking-price statistics, not appraisals. - Do not use it to read the user's Immoweb favourites or account saved searches; it keeps its own local saved searches instead. ## Unique Capabilities These capabilities aren't available in any other tool for this API. ### Market intelligence - **`market`** — Median asking price, €/m², price-cut share and recent disappearances for one or several communes, broken down by bedrooms, EPC, type or postcode. Student rooms and per-room lets are left out. Pulls missing areas on first use (--no-pull to stay offline). _Reach for this when an agent needs neighbourhood price levels or wants to compare communes before searching._ ```bash immoweb-pp-cli market ixelles saint-gilles --type apartment --deal rent --by bedrooms --agent ``` - **`yield`** — Estimates gross rental yield for a sale listing or a whole commune from comparable rents, and refuses when there are too few comparables. Pulls missing areas on first use (--no-pull to stay offline). _Use for investor questions about rental return before looking at individual listings._ ```bash immoweb-pp-cli yield --commune liege --type apartment --agent ``` ### Decision support - **`deal`** — Tells you whether one listing is cheap or expensive: €/m² percentile against comparable listings, days on market, price-cut history, demand and EPC gap. Pulls missing areas on first use (--no-pull to stay offline). _Use before advising on an offer or deciding whether a specific listing is worth a visit._ ```bash immoweb-pp-cli deal 21828249 --agent ``` - **`triage`** — Ranks the current matches of a saved search (or ad-hoc filters) by a transparent score: EUR/m2 percentile within the same postal code, freshness, price cut, private seller and EPC (with --enrich) so you know who to call first. _Use when a search returns too many listings and the user needs a prioritised short list with reasons._ ```bash immoweb-pp-cli triage --type apartment --deal rent --commune ixelles --max-price 1500 --min-bedrooms 2 --agent ``` ### Local state that compounds - **`drops`** — Lists stored listings whose asking price fell (from prices recorded by find/watch/pull and Immoweb's old-price field), with first and latest price, number of cuts, total % cut and days listed. _Use to find motivated sellers or negotiation leverage across everything the user has tracked._ ```bash immoweb-pp-cli drops --commune liege --since 30d --agent ``` ## Discovery Signals This CLI was generated with browser-observed traffic context. - Capture coverage: 12 API entries from 12 total network entries - Protocols: rest_json (75% confidence) ## Command Reference **listings** — Immoweb classifieds: search, count, map results, full details and similar listings - `immoweb-pp-cli listings count` — Exact number of listings matching the filters (search pages cap at 9,969) - `immoweb-pp-cli listings get` — Full details of one listing: EPC, cadastral income, surfaces, heating, agency contact, photos, views and bookmarks - `immoweb-pp-cli listings map` — Up to 200 listings per call with GPS coordinates (the bulk path used by the Immoweb map view) - `immoweb-pp-cli listings search` — Search listings with every Immoweb filter (30 per page, raw Immoweb result objects) - `immoweb-pp-cli listings similar` — Listings Immoweb considers similar to a given listing **locations** — Resolve commune names and postal codes to Immoweb location filters - `immoweb-pp-cli locations` — Look up a commune, locality or postal code; returns the postalCodes value to pass to search filters **Search, track and analyse** - **`immoweb-pp-cli find`** - Live search with friendly filters (`--type`, `--deal`, `--commune`/`--postcode`/`--province`, price, bedrooms, surfaces, `--epc`, `--garden`...), `--url` to start from a pasted Immoweb search, `--pages`, `--private-only`, `--hide-under-option`, `--near lat,lng --radius-km`. Results are stored locally. - **`immoweb-pp-cli show `** - Readable listing card: price, EUR/m2, EPC, cadastral income, surfaces, days online, demand, agency contact, recorded price history. - **`immoweb-pp-cli photos `** - Download photos (`--dir`, `--size small|medium|large|xl`) or only list their URLs (`--list`). - **`immoweb-pp-cli saved add|list|remove`** - Named local searches (same filters as `find`, or `--url`). - **`immoweb-pp-cli watch `** / **`watch --all`** - New listings, price changes (with the old price) and listings gone since the last run. The first run records a silent baseline. - **`immoweb-pp-cli pull`** - Harvest every listing of an area into the local store (`--commune`/`--postcode`, `--type`, `--deal`); splits the area into price bands of up to 200 listings so it needs only a few requests, and marks listings that disappeared as gone. - **`immoweb-pp-cli hide `** (`--undo`) - Dismiss listings so `find`, `watch` and `triage` skip them. - **`immoweb-pp-cli shortlist add|list|remove`** - Local shortlist with notes. - **`immoweb-pp-cli dump`** - Export stored listings as `--format csv|geojson|jsonl` (a JSON array with `--json`). - **`market`, `deal`, `triage`, `drops`, `yield`** - see Unique Features. `find`, `show`, `watch`, `pull` and the automatic pulls of `market`/`deal`/`yield`/`triage` fill the local store; `drops`, `dump`, `search` and `--no-pull` runs read it. Do not use the generic `sync` command to fill the store: it has no area filter and would page through listings for all of Belgium. Use `pull` instead. ## Known behaviours - The 19 Brussels communes resolve to their own postal codes (Ixelles = 1050), because Immoweb's "(all localities)" grouping adds neighbouring codes (Ixelles would include 1000, the City of Brussels). Elsewhere a commune follows Immoweb's grouping: check it with `immoweb-pp-cli locations --query `, and use `--postcode` or `market --by postcode` for a clean split. - Student rooms (kots) and per-room lets are left out of `market`, `yield` and `triage`, and `deal` compares rooms only with rooms; `--include-rooms` keeps them. - The first `market`, `deal` or `yield` on an area pulls it from Immoweb (a few seconds, up to ~20 s for large communes on a slow connection). The pull is reused for 24 h (`--refresh-after`); `--no-pull` or `--data-source local` stay offline. - Days on market come from Immoweb's publication date, which only the listing detail carries: they appear after `show`, `deal` or `triage --enrich`. Without it, `market` leaves the median out and says why, and `triage` scores freshness on the last update date. - Listings without a published price ("price on request") cannot be reached through price bands; `pull` reports them as `without_price`. - Immoweb soft-throttles by returning empty pages; the CLI turns that into exit code 7 instead of an empty result. Wait a minute and retry. - `triage` leaves out hidden listings and listings under option (`--include-under-option` keeps them). ### Finding the right command When you know what you want to do but not which command does it, ask the CLI directly: ```bash immoweb-pp-cli which "" ``` `which` resolves a natural-language capability query to the best matching command from this CLI's curated feature index. Exit code `0` means at least one match; exit code `2` means no confident match — fall back to `--help` or use a narrower query. `--json` (and other machine formats) keep that exit-2 contract and write `{"matches":[]}` on stdout so agents can inspect the envelope without treating a miss as success. ## Recipes ### Who to call first for a rental search ```bash immoweb-pp-cli triage --type apartment --deal rent --commune ixelles --max-price 1500 --min-bedrooms 2 --agent ``` Ranks current matches with the per-factor breakdown (EUR/m2 vs the same postal code, freshness, cut, private seller); add --enrich 5 to score EPC for the top five. ### Is this house fairly priced? ```bash immoweb-pp-cli deal 21828249 --agent ``` Returns the €/m² percentile against comparables, days on market and any recorded price cuts. ### Key facts from a listing, agent-sized ```bash immoweb-pp-cli listings get 21828249 --agent --select classified.price.mainValue,classified.property.netHabitableSurface,classified.transaction.certificates.epcScore,classified.statistics.viewCount ``` The raw detail JSON is about 20 KB; --select keeps only the dotted fields the agent needs. ### Compare commune rents ```bash immoweb-pp-cli market ixelles saint-gilles etterbeek --type apartment --deal rent --by bedrooms --agent ``` Median rent and €/m² per bedroom count, side by side, with sample sizes. ### Recent price cuts in what you have tracked ```bash immoweb-pp-cli drops --since 30d --agent ``` Reads the local store only: cuts come from prices recorded by find, watch and pull plus Immoweb's own old-price field, so pull an area first (immoweb-pp-cli pull --commune liege --type apartment --deal sale). ## Auth Setup No authentication required. Run `immoweb-pp-cli doctor` to verify setup. ## Agent Mode Add `--agent` to any command. Expands to: `--json --compact --no-input --no-color`. Global format flags share one contract on promoted, novel, sync, and `--deliver` paths: - `--json` — one JSON document on stdout (sync progress events go to stderr) - `--compact` — keep identity/status/timestamp fields; does not change the document vs stream shape - `--csv` / `--plain` — tabular rows (collection envelopes unwrap to the row array) - `--quiet` — one identity value per row, no envelope - **Pipeable** — JSON on stdout, errors on stderr - **Filterable** — `--select` keeps a subset of fields. Dotted paths descend into nested structures; arrays traverse element-wise. Critical for keeping context small on verbose APIs: ```bash immoweb-pp-cli listings get 21828249 --agent --select classified ``` - **Previewable** — `--dry-run` shows the request without sending - **Offline-friendly** — `drops`, `dump`, `search` and `--no-pull` runs read the local SQLite store filled by `find`, `show`, `watch` and `pull` (never `sync`, which has no area filter) - **Non-interactive** — never prompts, every input is a flag - **Read-only toward Immoweb** — it never contacts agencies or changes anything on immoweb.be; its only writes are the local store (saved searches, hidden listings, shortlist) and downloaded photos ### Response envelope Commands that read from the local store or the API wrap output in a provenance envelope: ```json { "meta": {"source": "live" | "local", "synced_at": "...", "reason": "..."}, "results": } ``` Parse `.results` for data and `.meta.source` to know whether it's live or local (for `market`/`deal`/`yield`, pass `--data-source local` rather than `--no-pull` when you need the envelope to say local). A human-readable `N results (live)` summary is printed to stderr only when stdout is a terminal AND no machine-format flag (`--json`, `--csv`, `--compact`, `--quiet`, `--plain`, `--select`) is set — piped/agent consumers and explicit-format runs get pure JSON on stdout. ## Paths and state Agents should treat the CLI's path resolver as part of the runtime contract: - Use `--home ` for one invocation, or set `IMMOWEB_HOME=` to relocate all four path kinds under one root. - Use per-kind env vars only when a specific kind must diverge: `IMMOWEB_CONFIG_DIR`, `IMMOWEB_DATA_DIR`, `IMMOWEB_STATE_DIR`, `IMMOWEB_CACHE_DIR`. - Resolution order is per-kind env var, `--home`, `IMMOWEB_HOME`, XDG (`XDG_CONFIG_HOME`, `XDG_DATA_HOME`, `XDG_STATE_HOME`, `XDG_CACHE_HOME`), then platform defaults. - `config` contains settings like `config.toml` and profiles. `data` contains `data.db` (listings, price history, saved searches). `state` contains persisted queries, jobs, and `teach.log`. `cache` contains regenerable HTTP/cache files. - Run `immoweb-pp-cli doctor --fail-on warn` to surface path warnings. `agent-context` exposes a schema v4 `paths` block for agents that need the resolved dirs. - For MCP, pass relocation through the MCP host config. The MCP binary does not inherit CLI flags: ```json { "mcpServers": { "immoweb": { "command": "immoweb-pp-mcp", "env": { "IMMOWEB_HOME": "/srv/immoweb" } } } } ``` Fleet precedence: an inherited per-kind env var overrides an explicit `--home` for that kind. Use `IMMOWEB_HOME` or per-kind vars as durable fleet levers, and use `--home` only for a single invocation. Relocation is not reversible by unsetting env vars; move files manually before clearing `IMMOWEB_HOME`, or `doctor` will not find the local store left under the former root. ## Automatic learning This CLI ships a self-capturing learning loop. The CLI does its own bookkeeping: every invocation is journaled locally, a failed flag followed by a corrected retry auto-derives a `flag_alias` candidate, and a `teach` on a query family without a playbook auto-synthesizes a `playbook_candidate` from the session's journal. Your job is judgment only: `recall` first, act on surfaced candidates, `teach` the final answer, `playbook amend` when you observe a correction. You never record failures by hand. ### Step 1: `recall` before any discovery Before list/search/drill commands on a new user question, pass the question as an argv or MCP tool argument to `recall --agent`. Do not interpolate user-controlled text into a shell command line. Quoted `recall ""` breaks on an apostrophe, which is ordinary English. A quoted heredoc breaks when a body line equals the delimiter, and that delimiter is published in these docs. Write the question with a non-shell file-writing tool, then read it back as data: ```bash # Write the question verbatim with your file-writing tool (no shell involved). # Command substitution on a file only ever yields data — the shell never # parses the file's bytes as syntax. QUERY=$(cat /path/to/question.txt) immoweb-pp-cli recall "$QUERY" --agent ``` Prefer MCP: pass the question as the tool's query argument. `"$QUERY"` after a file read is argv-safe; putting the question itself in the command text is not. The response envelope: ```json { "query": "...", "normalized": "", "query_entities": ["..."], "found": true | false, "match_score": 0.0, "results": [ { "resource_id": "...", "resource_type": "...", "venue": "...", "confidence": 2, "entity_match": "exact|partial|unknown", "source": "taught|preseed|pattern", "warnings": ["..."] } ], "mismatches": [ /* only when --debug-mismatches */ ], "warnings": [ /* top-level */ ], "candidates": [ { "id": 12, "class": "flag_alias | playbook_candidate", "summary": "...", "sightings": 3, "last_seen": "...", "rationale": "...", "next_action": ["", "immoweb-pp-cli learnings confirm 12"] } ], "playbook": { "query_family": "...", "playbook": { "steps": [ { "cmd": "", "purpose": "..." } ], "entity_slots": ["$ENTITY"], "expected_tool_calls": 3 }, "slots_resolved": { "$ENTITY": { "token": "", "canonical": "" } }, "notes": "" }, "notes": "" } ``` Empty-store short-circuit: if the store has no learnings, playbooks, or candidates yet (recall finds nothing and `learnings list` and `learnings candidates` are both empty), skip recall for the rest of this session instead of taxing every query; resume recall-first once something has been taught. ### Step 2: decision tree Read `candidates`, `playbook`, `notes`, `results[0]`, and warnings in that order: ``` if Candidates present (warnings include "candidates_present"): -> candidates are try-then-confirm, never facts. Follow each candidate's two-step next_action verbatim: run the trial command first, then run `learnings confirm ` only after the trial verified the behavior. Reject a wrong candidate with `learnings reject `. -> NEVER re-teach something recall surfaced as a candidate; confirm or reject that candidate instead of teaching a duplicate. -> candidates ride alongside playbooks and resource hits, not instead of them; continue with the branches below after acting on them. if Playbook present: -> READ Playbook.notes verbatim FIRST (workaround