Radar

Radar produces district-level context and states its decision boundary at the same time.

This is not just commentary. Coverage, freshness, source lineage, and serving limits are kept visible in one structure so users can distinguish between sufficient context and fields that still require property-level verification.

What this surface does

  • Shows district-level market activity, coverage, and source freshness under one shared contract.
  • Makes clear which fields are supported, partial, or unsupported before a decision workflow continues.
  • Shares the same snapshot discipline as Verify, Analyst, and API outputs.

Operating frame

Radar is not a landing page. It is an institutional research serving layer.

Output type district intelligence surface
Decision boundary does not issue a property verdict
Evidence discipline coverage + freshness + source references
Product parity Radar / Verify / API use one data contract

City rollouts

Live and upcoming geographies.

active

Istanbul

Kadikoy is live. Besiktas, Uskudar, and additional districts are in evidence-package preparation.

queued

Ankara

Identity, zoning, and market batches for Cankaya, Kecioren, and Mamak are in staging.

queued

Izmir

Coverage audits for Konak, Karsiyaka, and Bornova are complete; serving parity is next.