---
title: "How many plots a land can be cut into"
method: POST
path: "/api/v1/tools/plot_layout"
---

# How many plots a land can be cut into

`POST /api/v1/tools/plot_layout`

## Request

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

Plot-cutting / subdivision optimiser for raw land: how many plots the site can be cut into, at what size, with the passage or internal road, and whether it counts as a SUB-DIVISION or a LAYOUT under TNCDBR 2019, plus the OSR, EWS and scrutiny fee that come with it. Use for "how many plots can I cut from this 2 acre land", "how many house sites from 1 acre", "layout plan with roads and OSR", "divide my land into plots", "is this a subdivision or a layout". THE SHAPE DECIDES THE ANSWER, so this needs dimensions: give frontage_m (the road-facing width) and depth_m, or all four sides side_a to side_d in metres (A = front, then around). With only the extent it returns a labelled capacity ESTIMATE and asks for the frontage and depth, because the same 2 acres yields 3 large plots as a square and 20+ at a narrow frontage. Extent can be given in any unit via extent + extent_unit (acre, cent, ground, square_feet, hectare, square_meter). Optional: road_width_m (the EXISTING access road, decides subdivision vs layout), min_plot_size_sqm and max_plot_size_sqm (defaults 72 and 500, set max to about 111 sq.m for 1200 sq.ft house sites), location_type, abuts_highway. FSI, floors, setbacks and parking on a single building are the separate Build Scope report. The OSR fee in rupees is the separate OSR fee calculator. One rule figure on its own is the separate single-rule calculator. Free.

## Request body

- object
  - `frontage_m` number: Road-facing width of the land in metres
  - `depth_m` number: Depth of the land from the road in metres
  - `side_a` number: Front side in metres (use instead of frontage/depth for an irregular plot)
  - `side_b` number: Second side in metres, going around
  - `side_c` number: Third side (rear) in metres
  - `side_d` number: Fourth side in metres
  - `extent` number: Total land extent, in the unit given by extent_unit
  - `extent_unit` string: acre, cent, ground, square_feet, hectare, square_meter, kuli, veli (default square_meter)
  - `road_width_m` number: Width in metres of the EXISTING road the land abuts. Defaults to the service default of 7.0 m.
  - `min_plot_size_sqm` number: Smallest acceptable plot in sq.m (statutory floor and default 72)
  - `max_plot_size_sqm` number: Largest acceptable plot in sq.m (default 500). Lower it for house sites: 1200 sq.ft is about 111 sq.m.
  - `location_type` 'cma' | 'peri_urban' | 'corporation' | 'municipality' | 'town_panchayat' | 'village_panchayat' | 'industrial': Local body type; sets the minimum access road width (default corporation)
  - `abuts_highway` boolean: Land abuts a national or state highway (adds the service road requirement)

## 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/54f851c86cc1?raw)