Plot Subdivision and Layout API for Tamil Nadu
Yes. The LandLens plot layout API takes the size and shape of a piece of raw land (its road frontage and depth, or its four sides, or only its extent) and works out how many plots it can be cut into under the Tamil Nadu Combined Development and Building Rules 2019: plot sizes, the internal road or passage, whether it counts as a sub-division or a layout, and the open space reservation (OSR), EWS share and scrutiny fee that go with it. With only the extent it returns a labelled estimate and asks for the dimensions. It costs nothing.
https://verified.realestate/api/v1/tools/plot_layout- Price
- Free
- Source
- TNCDBR 2019 rule engine
- Coverage
- Tamil Nadu, by local body type
- Answers in
- Instant
Example
curl -X POST https://verified.realestate/api/v1/tools/plot_layout \
-H "Authorization: Bearer $LANDLENS_KEY" \
-H "Content-Type: application/json" \
-d '{"frontage_m":40,"depth_m":50,"road_width_m":9,"max_plot_size_sqm":250,"location_type":"peri_urban"}'
{
"ok": true,
"status": "ok",
"data": {
"found": true,
"mode": "layout",
"plot_area_sqm": 2000,
"plot_area_cents": 49.42,
"plot_area_acres": 0.4942,
"sides_m": {
"A": 40,
"B": 50,
"C": 40,
"D": 50
},
"access_road_width_m": 9,
"access_road_width_assumed": false,
"location_type": "peri_urban",
"location_type_assumed": false,
"plot_size_range_sqm": {
"min": 72,
"max": 250
},
"classification": {
"type": "subdivision",
"explanation": "Qualifies as Sub-division: 8 plots with existing road access",
"theoretical_max_plots_at_72sqm": 27,
"existing_road_adequate": true,
"min_access_road_width_m": 7.2
},
"best_plot_count": 8,
"scenarios": [
{
"goal": "max_plots",
"name": "Central Road Grid (4×2)",
"strategy": "central_road",
"plot_count": 8,
"regular_plots": 8,
"avg_plot_area_sqm": 205,
"avg_plot_area_sqft": 2207,
"plot_width_m": 16.4,
"plot_depth_m": 12.5,
"internal_road_or_passage_width_m": 7.2,
"usable_area_sqm": 1640,
"efficiency_percent": 82,
"description": "7.2m central road with plots on both sides. Street up to 120m long: 7.2m (Rule 47(3))"
}
],
"osr": {
"required": false,
"area_sqm": 0,
"can_pay_instead_of_land": false,
"must_gift_land": false,
"rule": "No OSR required for plots <3,000 sqm"
},
"ews": {
"required": false,
"plots": 0,
"area_sqm": 0,
"rule": "EWS not required for layouts ≤10,000 sqm"
},
"scrutiny_fee_rs": 3000,
"note": "Computed as a rectangle from the frontage and depth given. If the land is irregular, pass the four measured sides for the real figure. The optimiser stops at 8 plots for a sub-division and at 20 for the central-road grid, so a large site can hold more plots than the count shown here. Treat the count as the engine's scenario, not the ceiling. These are TNCDBR 2019 planning scenarios from the same engine as the Build Scope subdivision tool, not a sanctioned layout. The sanctioning authority fixes the final plot pattern, road widths, OSR handover and fees, and the site survey (FMB) can change the sides, so tell the user to confirm before committing money."
},
"credits_charged": 0
}
A real answer from the API (22 Oct 2026). Three scenarios came back, identical for this site; one is shown.
What it returns
One call, one site. mode says whether it is a layout from dimensions or a capacity estimate from the extent alone.
| Field | What it holds |
|---|---|
mode | layout (from the frontage and depth, or four sides) or capacity_estimate (from the extent only). |
best_plot_count | The most plots any scenario cut. |
scenarios[] | The best scenario for each goal (max_plots, max_usable, optimised): plot_count, avg_plot_area_sqm and sqft, plot_width_m, plot_depth_m, internal_road_or_passage_width_m, usable_area_sqm, efficiency_percent and a description citing the rule. |
classification | sub-division or layout, with the reason, the theoretical maximum at the minimum plot size, whether the existing road is wide enough, and the minimum access road width. |
osr | Whether open space must be reserved, its area, and whether it can be paid for or must be gifted as land, with the rule. |
ews | Whether an EWS share applies, its plots and area, with the rule. |
scrutiny_fee_rs | The scrutiny fee in rupees. |
plot_area_sqm, plot_area_cents, plot_area_acres, sides_m | The site's area and sides as calculated. |
access_road_width_assumed, location_type_assumed | true when a default was used because the input was not given. |
estimate, need | For a capacity estimate: plots at the smallest and largest size after OSR, and the dimensions needed for a real layout. |
Ways to call it
Give the shape for a real layout, or only the extent for an estimate.
From frontage and depth
A rectangular site. For an irregular one give side_a to side_d instead.
{"frontage_m": 40,"depth_m": 50,"road_width_m": 9,"max_plot_size_sqm": 250,"location_type": "peri_urban"}
From the extent only
Returns a labelled estimate and asks for the frontage and depth, because the shape decides the answer.
{"extent": 2,"extent_unit": "acre"}
Inputs
The JSON body of the POST is the arguments. Nothing is strictly required, but give the frontage and depth (or four sides) for a real answer.
| Argument | Type | What to send |
|---|---|---|
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 or veli (default square_meter). |
road_width_m |
number | Width in metres of the existing road the land faces. It decides sub-division against layout. Default 7 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). For 1,200 sq.ft house sites use about 111. |
location_type |
string: 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) |
Code
Set LANDLENS_KEY to your key. In an AI app, connect https://verified.realestate/mcp once and ask in plain words instead. In Postman, download this API's collection, import it (File, Import) and set apiKey.
curl -X POST https://verified.realestate/api/v1/tools/plot_layout \
-H "Authorization: Bearer $LANDLENS_KEY" \
-H "Content-Type: application/json" \
-d '{"frontage_m":40,"depth_m":50,"road_width_m":9,"max_plot_size_sqm":250,"location_type":"peri_urban"}'
import os, requests
r = requests.post(
"https://verified.realestate/api/v1/tools/plot_layout",
headers={"Authorization": f"Bearer {os.environ['LANDLENS_KEY']}"},
json={
"frontage_m": 40,
"depth_m": 50,
"road_width_m": 9,
"max_plot_size_sqm": 250,
"location_type": "peri_urban"
},
timeout=20,
)
body = r.json()
print(body["status"], body["credits_charged"], body["data"])
const res = await fetch("https://verified.realestate/api/v1/tools/plot_layout", {
method: "POST",
headers: {
Authorization: `Bearer ${process.env.LANDLENS_KEY}`,
"Content-Type": "application/json",
},
body: JSON.stringify({
"frontage_m": 40,
"depth_m": 50,
"road_width_m": 9,
"max_plot_size_sqm": 250,
"location_type": "peri_urban"
}),
});
const body = await res.json();
console.log(body.status, body.credits_charged, body.data);
I have 2 acres with 60 m on the road and 135 m deep. How many 1,200 sq.ft plots can I cut, and will it need OSR?
Your AI runs the layout rules and shows the plot count, road and reservations. It is free.
Responses
Every answer has the same envelope. What status can say for this call:
| status | What it means |
|---|---|
ok | A layout or an estimate was worked out. Read mode. |
not_found | The inputs do not fix the land (a frontage without a depth, or nothing at all), or the smallest plot is larger than the largest. error and need say what is missing. |
free_limit_reached | The account has used its free calls for the hour or the day. retry_after says how many seconds to wait; paid calls keep working. |
Where the data comes from
The Tamil Nadu Combined Development and Building Rules, 2019: the sub-division and layout rules on minimum plot size, access and internal road widths, open space reservation, EWS reservation and scrutiny fees.
Land anywhere in Tamil Nadu that the 2019 rules govern, by local body type: Chennai Metropolitan Area, peri-urban, corporation, municipality, town panchayat, village panchayat and industrial.
The TNCDBR 2019 rules as coded in our rule engine. Calculations run at the moment of the call; nothing is read from outside.
The engine tries several cutting strategies (plots along the existing road, a central internal road with plots on both sides) and reports the best for most plots, most usable area, and a balance of the two. With only the extent, the plots are the extent less the OSR divided by the plot size, with roads and corners not deducted, and the answer says so.
Who uses it
Landowners
See how many plots a piece of family land can become before talking to a developer.
Layout promoters
Compare scenarios for a site in seconds, with the OSR and fees each one carries.
Valuers
Value raw land by the plots it can yield, not only by its extent.
Limits and good practice
- These are planning scenarios, not a sanctioned layout. The approving authority fixes the final plot pattern, road widths, OSR handover and fees.
- The engine stops at 8 plots for a sub-division and 20 for the central-road grid, so a large site can hold more than the count shown. The note says so when a scenario reaches a cap.
- An extent-only answer does not deduct roads or corners. Give the frontage and depth for a real figure.
Pricing
The plot layout calculator costs nothing. Free calls have their own allowance per hour and per day. Credits come from the same LandLens wallet as the chat and the minis. How billing works.
Free calls have an hourly and daily allowance. For more than that, or a platform built on these registers, we set up limits and a plan to match.
Questions
Is there an API to calculate how many plots I can make from my land in Tamil Nadu?
Yes, this one. Send the frontage and depth (or the four sides) and you get the plot count, sizes, internal road, OSR, EWS and scrutiny fee under TNCDBR 2019.
What is the difference between a sub-division and a layout?
In the rule engine, up to 8 plots served by an adequate existing road is a sub-division; more plots, or a new internal road, make it a layout. The classification field says which, and why.
When is OSR required?
It depends on the site area and the rules for the local body. The osr field says whether it applies here, how much, and whether it can be paid instead of gifted.
What does it cost?
It costs nothing, within the account's free call allowance.
Updated 22 Oct 2026 · OpenAPI description