Road Width API: road in front of a plot, Tamil Nadu

What it returns

One call, one plot. When no width can be measured (no road parcel abuts the plot, or it touches only at a corner) the answer is status not_found with the reason in note, and nothing is charged.

Field	What it holds
`roads[]`	Each road parcel sharing a boundary: survey, owners (the recorded holder, in English and Tamil) and, when measured, the fields below.
`width_at_frontage_start_m, width_at_frontage_end_m, width_typical_m`	The road width where the frontage begins, where it ends, and typical across it.
`frontage_m, in_feet`	The frontage length, and every figure again in feet.
`measured_at`	The start and end points where the crossings were taken, as lat and lng.
`road_name, road_name_source`	The road's name and that it is from Google Maps, only where Google agrees on one.
`single_reading, read_inset_m, average_across_parcel, frontage_runs`	Flags, each with a note, for a road read at one end only, read 1 m in from a corner, given as a whole-parcel average, or met in several stretches.
`street_gaps[]`	Open strips between parcels along the plot boundary, measured the same way. Usually a town street the map does not draw as a parcel; not a recorded road.
`source_survey, is_corner, road_count, road_parcels_no_width`	The plot measured, whether it touches more than one road, and the roads that touch only at a corner.
`map_features`	A GeoJSON FeatureCollection of the plot, the measured roads and any street gaps, to draw on a map.
`watercourse_parcels, unregistered_parcels, note`	When nothing is measurable: neighbouring parcels that are channels, and those no register classifies, with how to read that.

Inputs

The JSON body of the POST is the arguments. resolve_parcel gives the survey number and village code for any point.

Argument	Type	What to send
`lat`required	number	Latitude in decimal degrees (from a pin or resolved parcel)
`lng`required	number	Longitude in decimal degrees
`survey_number`	string	Send it whenever the plot is resolved, without the sub-division. Without it the plot is taken from the point alone, and a point near a boundary can measure the neighbour's road.
`sub_division`	string	Sub-division of the resolved plot, e.g. "114" for 1017/114
`village_code`	string	Village code of the resolved plot, when known

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/road_width \
  -H "Authorization: Bearer $LANDLENS_KEY" \
  -H "Content-Type: application/json" \
  -d '{}'

import os, requests

r = requests.post(
    "https://verified.realestate/api/v1/tools/road_width",
    headers={"Authorization": f"Bearer {os.environ['LANDLENS_KEY']}"},
    json={},
    timeout=30,
)
body = r.json()
print(body["status"], body["credits_charged"], body["data"])

const res = await fetch("https://verified.realestate/api/v1/tools/road_width", {
  method: "POST",
  headers: {
    Authorization: `Bearer ${process.env.LANDLENS_KEY}`,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({}),
});
const body = await res.json();
console.log(body.status, body.credits_charged, body.data);

How wide is the road in front of my plot at 13.0339, 80.2687 in Mylapore? Give it in feet.

Your AI measures every road the plot touches and gives you each width at both ends of the frontage.

Responses

Every answer has the same envelope. What status can say for this call:

status	What it means
`ok`	At least one usable width was measured. Charged.
`not_found`	No width could be measured: no road parcel abuts the plot, roads touch only at a corner, or the point is not in a mapped parcel. The note says which and what was found instead. Nothing is charged.
`invalid_args`	lat or lng is missing.
`insufficient_credits`	HTTP 402: the balance does not cover the call, with the credits needed and your balance.

Where the data comes from

Register

The state cadastral boundary layer (the FMB parcels) for the shapes, and the revenue registers for which neighbouring parcels are recorded as roads or streets and who holds them.

Coverage

Any surveyed plot in Tamil Nadu, village or town. The road must be a parcel of its own on the cadastral map, or an open strip between parcels; a private path or easement the map does not draw does not appear.

How current

The cadastral layer as last loaded. Road widenings since the survey are not reflected.

How we read it

The plot is fixed by the survey number when given, otherwise by the point. Each road parcel sharing a boundary is crossed at right angles at the start and end of the plot's frontage on it. Where a corner gives no clean crossing the end is read 1 m in, where only one end reads it says so, and where no crossing can be read the road's average width across the whole parcel is given and labelled. Road names come from Google Maps only when its answers agree at three points on the road.

Who uses it

Architects and builders

Get the abutting road width that decides FSI, setbacks and the building type before drawing a plan.

Buyers

Check a seller's "40 feet road" against the cadastral map before a site visit.

Advocates and lenders

Note the recorded road frontage and its holder in a title or security report.

Limits and good practice

Measured off the cadastral map, not a surveyed carriageway. For a legal width, a licensed survey or the FMB is the authority.
A road the map does not draw as a parcel appears, if at all, only as a street gap. A private path or easement does not appear.
No road parcel abutting is not proof that a plot is landlocked; the answer says so.
Tamil Nadu only. A point outside a mapped parcel is not measured.

Pricing

2 credits per answer

Each call costs 2 credits when a usable width comes back, and nothing otherwise. Credits come from the same LandLens wallet as the chat and the minis. How billing works.

Calling at volume?

For thousands of calls a month, a portfolio sweep or a platform built on these registers, we quote a customised bulk price, with invoicing to match.

WhatsApp 99961 29996

Questions

Is there an API to find the road width in front of a plot?

Yes, this one. Send the plot's lat and lng (and survey number) and get the width of every road it fronts, measured from the cadastral map.

Why two widths for one road?

Roads taper. The width is measured where the plot's frontage begins and where it ends, which is what matters for that plot. A width taken elsewhere on the road would not be this plot's.

Does it tell me if the plot has road access?

Not as a yes or no. It measures widths. The neighbours check answers whether a plot touches a road at all.

Where does the road name come from?

From Google Maps, asked at points along the road, and given only when those answers agree. Otherwise the road is named by its survey number.

Why was nothing measured for my plot?

No neighbouring parcel is recorded as a road, or it meets the plot only at a corner. The note lists what the neighbouring parcels are, and which no register classifies.