Ancestral Land Search API: trace family land in Tamil Nadu
Yes. ancestral_search takes an ancestor's name and an area and, in one call, searches the Tamil Nadu revenue A-register and town survey register for parcels still recorded under that name (in English and Tamil, with spelling variants), groups them by village, and searches the Tamil Nadu archives catalogue for the native village's old settlement and inam registers. Every result is a name match, not proof of relation. It costs 3 credits per search that finds the name as written in the registers, and nothing otherwise.
https://verified.realestate/api/v1/tools/ancestral_search- Price
- 3 credits per answer
- Source
- Revenue registers and the state archives catalogue
- Coverage
- Tamil Nadu
- Answers in
- Usually 5 to 15 seconds
What it returns
Register matches grouped by village, then archive matches. found is false (status not_found) when no holder carries the name as written.
| Field | What it holds |
|---|---|
villages | One entry per village with parcels under the name: village_name, taluk_name, district_name, the revenue codes, register, and parcels (survey, owner_name, owner_name_ta, area_acres, patta_no, name_match, match_role). |
parcel_matches, exact_matches, similar_matches, total_register_matches, village_count | How many parcels matched, and how. |
archives | Archive groups: register (the volume series), count, and records. |
searched_variants, searched_as | The spellings searched. |
archive_query, archive_district | What the archives were searched for. |
message | On not_found: what to try next. |
Inputs
The JSON body of the POST is the arguments. Only the name is required. A district is enough for a first search.
| Argument | Type | What to send |
|---|---|---|
ancestor_namerequired |
string | The name as it may appear on the record, with initials if known. |
district_code |
string | Recommended. Any area is enough for a first search. |
taluk_code |
string | |
village_code |
string | |
village_name |
string | The native village exactly as the family names it, for the archives. The archives are filed by the old village name, not the current revenue name. |
district_name |
string |
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/ancestral_search \
-H "Authorization: Bearer $LANDLENS_KEY" \
-H "Content-Type: application/json" \
-d '{}'
import os, requests
r = requests.post(
"https://verified.realestate/api/v1/tools/ancestral_search",
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/ancestral_search", {
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);
Did my grandfather own land? His name was a Muthusamy from Adambakkam, Chennai.
Your AI says the price, searches the registers and the archives, and shows the trail village by village.
Responses
Every answer has the same envelope. What status can say for this call:
| status | What it means |
|---|---|
ok | At least one holder carries the name as written. Charged 3 credits. |
not_found | No holder carries the name as written in the area. Similar spellings and archive matches may still be listed. Nothing is charged. |
invalid_args | The name is missing. |
Where the data comes from
The Tamil Nadu revenue department's A-register and Town Survey Land Register, as held in our copy of both, and the catalogue of the Tamil Nadu archives: settlement registers, inam registers and other pre-independence volumes, filed by the old village and district names.
Village and town survey land across Tamil Nadu, as far as our copy of the registers reaches, and the archive volumes in our copy of the catalogue.
Our copy of the registers is refreshed in full about once a year. The archive catalogue is historical and does not change.
The name and its spelling variants are searched exactly first, then by similar spelling, the same way owner_properties_search does. The archives are searched by the native village when you name it, otherwise by the name.
Who uses it
Families
Find land still recorded under a grandparent's name before starting a legal heir or partition process.
Law firms
Map an estate's holdings across villages before drafting a partition deed.
Limits and good practice
- Results are name matches, never proof of relation. Two people can share a name.
- Old holdings often sit under a different spelling, the father's name or a joint patta. Try variants and widen the area.
- The archives use colonial spellings (Chingleput, Trivellore). tnahr_search searches them directly with the old spelling.
- Register rows are our copy of the registers. Read a parcel's current record with fetch_land_record.
Pricing
Each search that finds the name as written in the registers costs 3 credits; nothing otherwise. 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 to find ancestral land in Tamil Nadu?
Yes, this one. It searches the land registers and the state archives catalogue for an ancestor's name in one call.
How much does an ancestral land search cost?
3 credits per search that finds the name as written. Nothing otherwise.
Does a match prove the land was my grandfather's?
No. It is a name match. The patta history, the EC and the deeds establish who held the land and how it passed down.
Can I search in Tamil?
Yes. Send the name in Tamil or English; both scripts are searched.
Updated 22 Oct 2026 · OpenAPI description