---
title: "Zone and restriction check"
method: POST
path: "/api/v1/tools/zone_check"
---

# Zone and restriction check

`POST /api/v1/tools/zone_check`

## Request

- Base URL: `https://verified.realestate`
- URL: `https://verified.realestate/api/v1/tools/zone_check`
- Auth: HTTP bearer

Run one or more Tamil Nadu regulatory/environmental/infrastructure zone checks at a latitude/longitude, e.g. CRZ, Ramsar, eco-sensitive, flood, aquifer, reserve forest, road widening, airport NOC, HACA, temple/WAQF, land use, soil, nearest metro/railway/HT line/water body/quarry/burial/ASI, plus: "tod" (transit-oriented development corridor: premium FSI charges halved), "metrowater"/"sewage"/"water_pipeline" (CMWSSB piped services at the plot), "monuments" (protected-monument prohibited/regulated rings), "industry" (red/orange industry proximity), "master_plan" and "cmda_landuse" (planning-map land use zone at the point), "crz_improved" (higher-resolution CRZ layer), "building_footprint" (is a building mapped on the plot, Chennai only), "waterbody_survey" (is the SURVEY NUMBER ITSELF recorded as a waterbody/kulam/odai in the government register, as opposed to the water-body proximity layer), "commercial_activity" (commercial electricity connections and GST registrations recorded within 150 m, for "is this really residential" and occupancy evidence), "bhoodan" (is the SURVEY NUMBER recorded as held by the Tamil Nadu State Bhoodan Yagna Board: land donated under the Bhoodan Yagna Act 1958, whose transfer the Sub-Registrar must refuse under Registration Act s.22-A; use for "is this bhoodan / boomidhan / பூமிதான land", and say plainly that no indicator does not rule it out), "land_acquisition" (does a Tamil Nadu state gazette acquisition notice name the SURVEY NUMBER at this point: TN Highways Act, TN Industrial Purposes Act, the 2013 Act and the 1894 Act schedules; a notice is an intention to acquire, never a completed acquisition, and no notice found never rules acquisition out), "slum_area" (does a slum boundary on the Tamil Nadu state GIS slum boundary map meet the parcel or point: Chennai, Madurai, Coimbatore, Tiruppur and Erode corporations only, names, wards and zones for Chennai only; status warning = "inside a mapped slum boundary", safe = "no mapped slum boundary here" and NEVER "clear" or "not a slum", not_covered = "not assessed", outside those corporations, or with slum_status cannot_place when the parcel outline is not the plot and no pin on the plot was given (nothing concluded: ask for a pin on the plot); the map is NOT the list notified under the Slum Areas Act, so give the caveat and say to confirm with the Tamil Nadu Urban Habitat Development Board). Request ONLY the specific layers the question is about (usually 1 to 4). For a full multi-layer zone report (someone asking to check "everything" / "all zones" / "every restriction") ON A RESOLVED PARCEL, do NOT run every layer here: that is slow inline. The full report is Verify My Land, a separate tool that runs the complete check suite in the background queue and delivers a report. EXCEPTION: when no cadastral parcel resolves at the point, when the user explicitly asks to run it on the pin / here / in this chat, or when an inline zone sweep has ALREADY BEEN APPROVED, run the most material layers HERE (up to about 12: flood, waterbody, CRZ, reserve forest, swamp, aquifer, airport, HT line, master plan, road widening, monuments, catchment) and say which ran. An approved inline sweep is a commitment: RUN it, never convert it into a Verify My Land proposal after approval - offer Verify My Land afterwards as the deeper follow-up instead. Returns a verdict (safe/warning/found/info) per check. NOT for plain height-above-sea-level, slope or aspect questions: those belong to the free terrain height lookup, and running zone checks for them wastes the user's credits. Costs 1 to 6 credits per call. Priced by the layers requested: 1 credit for up to 7 layers, 1 more for each further 7, at most 6 (checks:["all"], all 40 layers, costs 6). Waived when nothing is found.

## Request body

- object
  - `lat` number, required: Latitude in decimal degrees
  - `lng` number, required: Longitude in decimal degrees
  - `checks` string[], required: Request ONLY the specific layers the question asks about, usually 1 to 4, e.g. ["crz","flood_inundation"] for a coastal/flood question or ["metro_line"] for a metro question. Do NOT pass ["all"]: for a full multi-layer zone report, Verify My Land, a separate background-queue tool, covers every layer instead of running them all here. "defence" flags proximity to a military / defence establishment.

## Response `200`

The envelope: ok, status, data, credits_charged, balance_after, request_id

## Other responses

- `401`: No valid credential
- `402`: Not enough credits
- `429`: Rate limit

---

[API](https://skmtc.dev/verified/apis/landlens-tool-api.md) · [All operations](https://skmtc.dev/verified/apis/landlens-tool-api/llms.txt) · [OpenAPI document](https://skmtc.dev/verified/apis/landlens-tool-api/revisions/7923c1c24431?raw)