Land Owner by Location API: owner from lat/lng, Tamil Nadu

What it returns

data.status says what happened: named, subdivision_ambiguous, no_parcel, no_record or unavailable. Only named is charged.

Field	What it holds
`status`	named (an owner is named), subdivision_ambiguous, no_parcel, no_record or unavailable.
`parcel`	The parcel under the point: survey_number, sub_division, register, the district, taluk and village with their codes, the town, ward and block for town land, extent_hectares, lat and lng.
`owner_name, owners`	The recorded owner in English, and one line per holder with the register's own Tamil (ta) beside its English (en).
`extent_hectares, land_type, address`	What the register records for the holding.
`ownership`	The register's own entry for the parcel.
`summary`	A short written reading of the entry.
`source, fetched_at`	Which register answered, and when it was read when the answer is our stored copy.
`subdivision_count, subdivision_options`	On subdivision_ambiguous: the sub-divisions to choose from. Call again with sub_division.
`caveat, message`	What the answer does and does not establish, in words you can show.

Inputs

The JSON body of the POST is the arguments. A point in decimal degrees, placed well inside the plot.

Argument	Type	What to send
`lat`required	number	Latitude in decimal degrees.
`lng`required	number	Longitude in decimal degrees.
`sub_division`	string	Only after a subdivision_ambiguous answer: the sub-division the land is, e.g. 1C.

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

import os, requests

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

const res = await fetch("https://verified.realestate/api/v1/tools/owner_at_point", {
  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);

Who owns the land at 12.9010, 80.2279?

Your AI says the price, finds the parcel under the point and reads its recorded owner, and asks you to pick a sub-division if the pin cannot tell.

Responses

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

status	What it means
`ok`	data.status is named: the register names an owner. Charged 2 credits.
`not_found`	data.status is subdivision_ambiguous, no_parcel, no_record or unavailable. Nothing is charged.
`invalid_args`	lat or lng is missing.

Where the data comes from

Register

The state cadastral boundary layer (FMB) to find the parcel, then the Tamil Nadu revenue department's patta register for village land or its Town Survey Land Register for town land, for the owner.

Coverage

Tamil Nadu, wherever the cadastral map covers the spot and the register holds a digitised record for the parcel.

How current

The owner is read from the government register at the moment you ask. When it does not answer, our stored copy of the register may be used, and source and fetched_at say so.

How we read it

The parcel whose boundary contains the point, then the register entry for that survey and sub-division. For town survey land, the town, ward and block are carried through so the right entry is read.

Who uses it

Brokers and buyers

Drop a pin on a plot seen on a site visit and see who the register names as its holder.

Lenders

Check that the borrower is the recorded holder of the land the valuer actually visited.

Property platforms

Show the recorded holder on a map-based listing without asking the user for survey numbers.

Limits and good practice

The owner named is what the register records, not clear title. Check the encumbrance history (the EC) before relying on it.
When a survey is split into sub-divisions the pin cannot tell apart, no owner is named. Pick the sub-division and call again.
no_record means the register holds no digitised ownership for the parcel, not that the land has no owner. The taluk office holds the paper record.
unavailable means the register could not be reached. Nothing is concluded and nothing is charged; try again.
A point near a boundary can fall in the neighbouring parcel.

Pricing

2 credits per answer

Each call that names an owner costs 2 credits; every other answer is free. 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 land owner from a location in Tamil Nadu?

Yes, this one. Send a latitude and longitude; it finds the parcel and reads its recorded owner from the patta or TSLR in one call.

How much does it cost?

2 credits when an owner is named. Nothing when the pin is ambiguous, unmapped, unrecorded or the register is down.

Why did it not name an owner?

Read data.status. subdivision_ambiguous means pick a sub-division and call again; no_parcel means move the pin onto the plot; no_record means the register holds no digitised entry; unavailable means try again later.

Is the owner it names the legal owner?

It is the holder the revenue register records. Title is established from the deeds and the encumbrance history, which ec_transactions reads.