realestate-in — Indian rentals, by locality or by point — openbash

Rental listings around a place in an Indian city, merged across backends and deduplicated.

realestate-in

realestate-in is a command on the openbash shell, reachable over HTTP, SSH and MCP with one key. It composes with the other programs through pipes; there is no per-program endpoint and no schema for the join.

realestate-in search bangalore --locality Whitefield --radius_km 5

help

realestate-in: rentals around a place in an Indian city, as JSON.

RETURNS
  One JSON object on stdout. Each listing carries what the publisher said,
  including amenities as an explicit yes/no rather than a mention: `false` is
  the publisher saying there is no gym, which is a stronger statement than any
  US listing makes.

OPTIONS
  A study run with no arguments prints its own — `realestate-in search` on a
  line by itself lists every flag it takes.

WHERE A SEARCH HAPPENS
  A locality is resolved by a neutral geocoder rather than by a listings
  vendor, so backends answer about one place — but a geocoder's idea of a
  neighbourhood is not a vendor's, and the two are measured about 2.9 km apart
  on Whitefield. So the point is yours to adjust:

    realestate-in search bangalore --locality Whitefield --radius_km 5
    realestate-in search bangalore --latitude 12.9698 --longitude 77.75

  Coordinates take precedence over `--locality` and skip the gazetteer
  entirely, which is the way to search a place a geocoder gets wrong.

WHAT A COORDINATE IS WORTH
  Some listings publish a FILL POINT instead of a location — one Whitefield
  search returned 24 of 26 listings on a single coordinate, and those were 24
  different properties. Those are detected and their coordinates dropped rather
  than passed off as locations, and `location_approximate_count` says how many.
  A caller putting pins on a map should read it before wondering where they
  went.

Studies:
  search <city>
      rental listings in an Indian city
  detail <url>
      everything known about one Indian listing, by its url

JSON to stdout, so it composes: pipe to `jq` to pick a field, or `> /tmp/…` to keep it.
Run a study with no arguments — `realestate-in search` — to see what it takes.

What it answers

realestate-in search — rental listings in an Indian city
realestate-in detail — everything known about one Indian listing, by its url