Get in TouchTry Terra (opens in a new tab)

LANDEED API & MCP

Property records from every Indian state, through one integration.

Our API procures ECs, RTCs, 7/12s, Pattas, certified deeds and charge searches from every state we cover. Terra's MCP server gives your agents cited answers from them.

Request access

Access is reviewed. Every pilot runs on your own live files, on production terms.

Powering property decisions across India's enterprises.

WHERE IT RUNS

Inside the LOS, the site-approval workflow and the land desk.

For organisations deciding on property across hundreds of branches, sites or survey numbers. The record goes where the decision is made: inside the LOS, the site-approval workflow or the land desk.

  • Lenders

    EC, CERSAI, mutation and litigation checks inside your LOS: before sanction, again before disbursal, and after MODT. Your panel advocate gets a complete file on day one, and signs the opinion.

    LAP · Home loans · Secured MSME · Portfolio watch

  • Retail & expansion

    Landlord title, charges on the premises, sanctioned plan, OC and permitted commercial use, checked before the LOI. A lease on a defective title is a store you later close.

    Site screening · Lease diligence

  • Developers & land

    Title chain, co-owners and legal heirs, government, assigned or inam land flags, conversion and acquisition notifications, per survey number.

    Acquisition · Batch screening · Portfolio watch

  • Diligence at scale

    Law firms, insurers and funds running property opinions and portfolio reviews across multiple states.

    Title opinions · Portfolio review

THE GROUND WE COVER

Every state. One way or another.

India does not have one land record. Every state keeps its own, split across registration, revenue and the municipality, each with its own portal, its own script and its own counters. Some of it is online. Much of it is not.

Where a state's record is online, we read it at source. Where it isn't, our field team goes to the office and brings back the certified copy. Your integration is the same either way.

At source

Read from the state's own system. Same-day where the record is digital.

At the counter

Collected from the office by our field team, on a committed turnaround per document type.

12 OF OUR 28 STATESWHAT THE RECORD IS CALLED THERE
KarnatakaRTC (Pahani) · Mutation register · Khata / E-Swathu · EC
Maharashtra7/12 extract · Ferfar · Index II · Property card
Tamil NaduPatta-Chitta · A-Register · FMB sketch · EC
Telangana & Andhra PradeshPahani / Adangal · ROR-1B · Pattadar passbook · EC
Gujarat7/12 · 8A · Form 6 (Hakk Patrak) · Property card
Uttar PradeshKhatauni · Khasra · Dakhil-kharij · EC
RajasthanJamabandi · Khasra girdawari · Namantaran
Madhya PradeshKhasra · B-1 Khatauni · Bhu Naksha
Punjab & HaryanaJamabandi (Fard) · Intkal · Aks Shajra
West BengalKhatian (Porcha) · Plot information · Mutation certificate

Every state names, formats and stores its records differently. These are twelve of the 28 we work in. Name the state and the API returns that state's own record.

  • 28

    states_live

  • 1,500+

    registries_covered

  • 1.8B+

    records_reconciled

TWO INTERFACES

Documents through the API.
Intelligence through MCP.

Procurement and reasoning are different jobs with different controls. Your systems order records through REST. Your agents read what the records say through MCP. Both run under one contract.

LANDEED API · REST & WEBHOOKS

Document procurement

Order records by state, district, village and survey or document number. You get the record as issued, with structured fields where the record supports them, delivered to your system by webhook.

  • EC / registry search · 13 or 30 years
  • Certified copies of registered deeds
  • RTC · 7/12 · Patta · Khatauni
  • Mutation entries
  • Khata & property tax
  • Sanctioned plan · CC · OC
  • Layout & conversion orders
  • Survey sketch
  • CERSAI & ROC charge search
  • Court case search
# 30-year EC for a LAP file in Hoskote talukPOST /v1/orders{  "state": "KA",  "document": "encumbrance_certificate",  "sro": "Hoskote",  "hobli": "Anugondanahalli",  "village": "Samethanahalli",  "survey_no": "114/2",  "years": 30}→ 202 order.accepted  2004 onward: at source, same day  1996–2004: manual EC, ordered at SRO Hoskote  webhook: order.fulfilled

TERRA MCP · REMOTE SERVER · OAUTH 2.1

Property intelligence for your agents

Connect the agents your teams already use to Terra. They can resolve a property, read its ownership, mutations and encumbrances, search litigation and check land classification. Every answer comes back with the record it was read from.

  • Read-only
  • Cited finding by finding
  • Gaps declared
  • Any MCP-compatible agent
# Connect once, per tenant"landeed-terra": {  "transport": "streamable-http",  "url": "issued on approval",  "auth": "oauth2.1"}
# Your diligence agent, before sanctiontool get_encumbrances{ "property_id": "ka-bngr-hsk-samethanahalli-114-2", "years": 30 } → 3 registered charges · 2 releases found · 1 with no release  each with office, document number and date

TERRA MCP

Read-only by design.

The server exposes the questions a diligence desk asks, as tools. Every tool reads. None of them order, pay or change anything. Procurement stays on the API, behind your own approval flow.

TOOLRETURNSREAD FROM
IDENTIFY
resolve_propertyCandidate parcels for an address, survey, khata, patta, CTS or ULPIN, with the basis of each matchRevenue and municipal records
check_coverageWhat can and cannot be read for a state, district and document type, before you askLandeed coverage register
TITLE & CHARGES
get_ownershipOwner of record, the chain of registered transfers, and mutation entriesRegistration and revenue
get_encumbrancesRegistered charges, MODTs and releases, with the period searchedEC or Index II, CERSAI, ROC
list_transactionsRegistered transactions on the parcel, with consideration and market value as recordedRegistration
RISK
search_litigationCases matching the parties or the property description, with court, case number and stageDistrict courts, High Courts, DRT, NCLT; revenue courts where reachable
get_land_classificationRevenue class (agricultural, converted, government, assigned or inam), zoning, and notified-acquisition statusRevenue, planning authority, Gazette
EVIDENCE
get_source_documentThe underlying record, as issued, behind any findingIssuing office

WHAT COMES BACK

ILLUSTRATIVE

{  "finding": "Equitable mortgage (MODT) registered;    no registered release found in period searched",  "property_id": "ka-bngr-hsk-samethanahalli-114-2",  "source": {    "document": "Encumbrance Certificate, Form 15",    "office": "SRO Hoskote, Bengaluru Rural",    "document_no": "HSK-1-04512-2019-20",    "registered_on": "2019-11-06",    "period_searched": "2004-04-01 → 2026-09-27",    "retrieved_at": "2026-09-28T10:14:22+05:30"  },  "in_progress": [    "1996-04-01 → 2004-03-31: manual EC ordered at SRO Hoskote"  ],  "not_seen": [    "Unregistered MODTs do not appear on an EC. See CERSAI search."  ]}

Every finding names the office, the document number and the date it was read. What is still being collected, and what a record cannot show, come back as fields.

BEFORE YOU ASK

ILLUSTRATIVE

tool check_coverage{ "state": "KA", "district": "Bengaluru Rural",  "document": "encumbrance_certificate" } → at source    2004-04-01 onward · same day→ at counter   1996–2004 · SRO Hoskote · committed turnaround→ not held     before 1996 at this office

FOR YOUR RISK COMMITTEE

Every answer carries its source.

An integration that feeds a credit decision gets read by risk, compliance and information security before it goes live. These are the questions they will ask, and our answers. Security documentation and data processing terms are shared under NDA during scoping.

Evidence

Cited finding by finding

Every finding names the issuing office, the document number, the registration date and when it was retrieved.

Traceability

Interpretation is labelled

Where a tool reads meaning into a record, the output says so and points to the field it came from. The record itself is one call away.

Coverage

Gaps declared

If a record is out of reach, the response says which one and why. Nothing is filled in to look complete.

Control

Agents read, systems order

MCP cannot place an order or spend. Procurement runs only through the API, under your own approval rules.

Access

Scoped and revocable

OAuth 2.1 for agents. API keys scoped by team and environment, and revocable at any time.

Data

Terms before files

Data use, retention and model training are agreed in writing before the pilot. Your security questionnaire is answered before any file is shared.

IN THE CONTRACT

Turnaround committed by state and document type.

Before you sign, you get coverage for your states in writing: which records come same-day from source, which go to the counter, and what we cannot reach today.

HOW ACCESS WORKS

From request to production.

  1. 01

    Request

    Tell us your footprint, your monthly volume and the decision the record feeds.

  2. 02

    Review

    A solutions engineer reviews it and replies within two business days.

  3. 03

    Scoping

    Coverage for your states in writing, your security questionnaire, and commercial terms.

  4. 04

    Pilot

    Production records on a sample of your live files, on commercial terms, measured against your current turnaround and findings.

  5. 05

    Production

    Keys per environment, turnaround and uptime written into the contract.

REQUEST ACCESS

Scope an integration.

Every request is read by our solutions team. The more precisely you describe the decision and the volume, the faster we can scope it.

What you get back

A scoping call, and a coverage note for the states you operate in.

What we will ask for

Sample files, your target turnaround, and who signs off on the integration.

What it is not

A free trial or a self-serve key.

Already a Landeed customer? Your account manager can add API or MCP access to your contract.

Your details are used only to review this request.

Request access

GET STARTED

Put the record to work.

Unlock a Verifiable Record for Every Property

Build with usAsk Terra about a property ↗(opens in a new tab)