Land Price API: what land actually sold for, from registered deeds
Yes. The LandLens Price Map API works out what land has actually sold for around a Tamil Nadu parcel, from the sale deeds registered on its survey number and the survey numbers beside it since 2001. You get the median price per square foot, the average, the 25th and 75th percentiles, the number of sales, the yearly median and growth rate, and a link to the full report with every transaction. The report is built in the background in about ten minutes and costs 4 credits, taken when it starts and returned if it fails or finds no comparable sales.
https://verified.realestate/api/v1/tools/pricemap- Price
- 4 credits when it starts, refunded if it fails
- Source
- Registered sale deeds, registration department
- Coverage
- Every revenue village in Tamil Nadu
- Answers in
- Queued at once; the report in about ten minutes
What it returns
The call answers queued at once, with a job_id. Poll job_status: when it reads done, data.payload.blocks.pricemap holds the figures below and data.message a plain summary.
| Field | What it holds |
|---|---|
median_per_sqft | The median price per square foot of the comparable sales. |
avg_per_sqft, p25, p75 | The average, and the 25th and 75th percentiles, which show the spread. |
count | How many sales the figures rest on. |
series[] | The median by year: year and value. |
cagr | The yearly growth rate of the median over the period, in per cent. |
period | The years the sales span. |
report_link | The full report: every transaction, the land and building split, and the guideline value comparison. |
survey | The survey number the report was built around. |
Inputs
The JSON body of the POST is the arguments. resolve_parcel gives the survey number for any point. Send the same lat and lng.
| Argument | Type | What to send |
|---|---|---|
latrequired |
number | Latitude in decimal degrees |
lngrequired |
number | Longitude in decimal degrees |
survey_numberrequired |
string | The parcel's survey number, from resolve_parcel. The report searches it and the four survey numbers on either side. |
sub_division |
string | The parcel's sub-division, kept on the report. The search itself covers every sub-division of each survey number. |
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/pricemap \
-H "Authorization: Bearer $LANDLENS_KEY" \
-H "Content-Type: application/json" \
-d '{}'
import os, requests
r = requests.post(
"https://verified.realestate/api/v1/tools/pricemap",
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/pricemap", {
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);
What is land really selling for around 12.9010, 80.2279 in Sholinganallur? Show me the trend over the last ten years.
Your AI finds the survey number, starts the Price Map report and reads you the median, spread and trend when it is ready.
Responses
Every answer has the same envelope. What status can say for this call:
| status | What it means |
|---|---|
queued | The report has started, with a job_id. Ask job_status every minute or so; it takes about ten minutes. |
done | In job_status data.status: data.payload.blocks.pricemap holds the figures, and credits_charged what was taken. |
failed | In job_status data.status: the report could not be built, with the reason in error. The credits taken when it started are returned. |
invalid_args | lat, lng or survey_number is missing. |
insufficient_credits | The balance does not cover the report when it starts. Nothing is taken. |
Where the data comes from
The encumbrance index of the Tamil Nadu Registration Department: the sale deeds registered on the parcel's survey number and its neighbours, with their consideration and extent.
Any surveyed parcel in Tamil Nadu. The search covers the parcel's survey number and the four survey numbers on either side of it, every sub-division of each, from 2001 to the present.
Live. Each report searches the department's index when it runs, so a sale shows as soon as the office has indexed it.
The deeds are searched in five-year ranges from 2001, narrowed to single years where the department will not show a range on screen. Each deed is read for its nature, consideration and extent; only sales with a price are kept, land and built property are separated, prices far from the rest are set aside as misreadings, and the yearly medians and growth rate are worked out from what remains. A report resting on fewer than five sales says it is indicative only.
Who uses it
Lenders and valuers
Put the registered sales around the security next to the valuation, with the count it rests on.
Buyers and their advisers
Test an asking price against what nearby land actually registered at.
Developers and investors
See how prices around a site have moved year by year before buying.
Limits and good practice
- Registered consideration is what the deed states. Land often registers near the guideline value, so a median can sit below what changed hands.
- A report on fewer than five sales is indicative only, and says so.
- Sales are read from the parcel's survey number and its neighbours, not a radius on the map.
- One report takes about ten minutes. It is meant for a parcel, not for bulk pricing of many points.
Pricing
A Price Map report costs 4 credits, taken when the report starts and returned automatically if it fails or finds no comparable sales. Reading its deeds afterwards with pricemap_transactions is free. Credits come from the same LandLens wallet as the chat and the minis. How billing works.
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.
Questions
Is there an API for land prices in Tamil Nadu?
Yes, this one. It works out the price per square foot from the sale deeds registered around the parcel, not from listings or asking prices.
How is this different from the guideline value?
The guideline value is the government's minimum rate for registration. This is what land around the parcel was actually registered at, from the deeds.
How long does it take?
About ten minutes. The call answers at once with a job_id; poll job_status until it reads done.
Can I see the individual sales?
Yes. report_link opens the full report, and pricemap_transactions returns the deeds behind a saved report as data.
What if there are no sales nearby?
The report says no comparable registered sales were found, and the credits are returned.
Updated 22 Oct 2026 · OpenAPI description