Legal Opinion Report API, verdict and title chain

Example

Request

curl -X POST https://verified.realestate/api/v1/tools/legal_opinion \
  -H "Authorization: Bearer $LANDLENS_KEY" \
  -H "Content-Type: application/json" \
  -d '{"action":"list"}'

Responsereal answer

{
  "ok": true,
  "status": "ok",
  "data": {
    "found": true,
    "count": 8,
    "opinions": [
      {
        "name": "S.No 101/2 - Mambalam",
        "status": "processing",
        "progress": "78%",
        "stage": "Running Verifications",
        "date": "10-09-2026",
        "detail_url": "https://verified.realestate/landlens/dashboard/workspace/97"
      },
      {
        "name": "Legal opinion - Survey 20, Palavakam",
        "status": "completed",
        "risk_score": 22,
        "stage": "Completed",
        "date": "16-08-2026",
        "detail_url": "https://verified.realestate/landlens/dashboard/workspace/63"
      }
    ]
  },
  "credits_quoted": 0,
  "credits_charged": 0,
  "credits_waived": 0
}

A real answer from a test account, trimmed to two of its eight opinions and with the note left out.

What it returns

Four actions. list, read and section read your reports; about explains how an opinion is obtained.

Field	What it holds
`opinions[] (list)`	Up to eight, newest first: name, status, risk_score, progress and stage while in preparation, date, and detail_url (the project page; its last path segment is the project id).
`verdict (read)`	verdict, label, risk_score, risk_level and the summary paragraph.
`top_findings, sections (read)`	Up to six findings, and every section with its status (warning and fail mark the ones to read).
`red_flags (read)`	How many critical, warning and informational flags, and the titles of the first eight.
`verified, needs_manual, recommendations (read)`	What was verified, what still needs checking by hand, and the steps before purchase, with counts for the deed and post-purchase steps.
`detail (section)`	One section in depth. title_chain returns chain[]: sequence, from, to, transaction, date, doc_reference, extent, survey_numbers and how each link was verified.
`in_progress, stage, progress, missing_docs, clarifying_questions`	For a report still being prepared: where it is and what it is waiting on.
`report_link`	The path of the full report on verified.realestate.

Ways to call it

Pick the action by what you need.

List your opinions

Newest first, with status and risk score.

{"action": "list"}

Read one opinion

Verdict, risk, sections, red flags and recommendations. Leave out project_id for the most recent completed one.

{"action": "read","project_id": 63}

One section in depth

Sections: property_identity, verify_my_land, title_chain, encumbrance, revenue_records, ownership_verification, fmb_tslr, planning_approvals, rera, taxes_utilities, company_checks, documents_analyzed, red_flags, title_story, recommendations.

{"action": "section","project_id": 63,"section": "title_chain"}

How to get one

The two ways to obtain a legal opinion, with links.

{"action": "about"}

Inputs

The JSON body of the POST is the arguments.

Argument	Type	What to send
`action`required	string: list, read, section, about	"list", "read", "section" or "about".
`project_id`	integer	read and section: the project id, the last number in a listed detail_url. Leave out for the most recent completed opinion.
`section`	string: property_identity, verify_my_land, title_chain, encumbrance, revenue_records, ownership_verification, fmb_tslr, planning_approvals, rera, taxes_utilities, company_checks, documents_analyzed, red_flags, title_story, recommendations	section: which part of the report to read in depth.

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

import os, requests

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

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

What did my legal opinion on survey 20 in Palavakam conclude? Show me the title chain and the red flags.

Your AI reads the opinion, gives the verdict and risk, and walks you through the title chain and the flags.

Responses

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

status	What it means
`ok`	The list, the report, the section, or the about answer.
`not_found`	No legal opinion on your account, or an unknown or empty section.
`free_limit_reached`	Your account has used its free calls for the hour or the day. retry_after says when they come back.

Where the data comes from

Register

Not a register: the legal opinion reports prepared on your account, each built from the documents you uploaded and the live checks the pipeline ran (EC, revenue records, CERSAI, court and revenue court searches, land verification).

Coverage

Every legal opinion project on your account and your team. Another account's report cannot be read.

How current

Live. A read returns the report as it stands, so a report still in preparation shows its current stage.

How we read it

The report is read from its stored form and compacted for an API answer: long text is cut, lists are capped, and the title chain keeps up to 45 links. The full report stays on its report page.

Who uses it

Banks and NBFCs

Pull the verdict, risk score and pre-disbursement conditions of each opinion into the loan file.

Law firms

Read the reconstructed title chain with document references, and the points that still need a manual check.

AI assistants

Answer "what did my opinion say" and "why is this flagged" from the report itself.

Limits and good practice

Reads only. An opinion is started with legal_opinion_order (from a map point) or legal_opinion_project (from your documents).
The list gives no separate id field; read the project id from the end of detail_url.
Text is cut and lists capped for an API answer. The full report is on its report page.
An opinion reads the documents and records it was given. What it lists under needs_manual has not been verified.

Pricing

Free

Reading your opinions costs nothing. Free calls are subject to the account's hourly and daily allowance. Preparing an opinion is priced on the ordering tools. Credits come from the same LandLens wallet as the chat and the minis. How billing works.

Calling at volume?

Free calls have an hourly and daily allowance. For more than that, or a platform built on these registers, we set up limits and a plan to match.

WhatsApp 99961 29996

Questions

Is there an API for property legal opinion reports?

Yes. LandLens returns your legal opinions as JSON: verdict, risk score, section statuses, red flags, title chain and recommendations, over plain HTTPS or as an MCP tool.

Can I start a legal opinion with this tool?

No. This reads opinions. Start one with legal_opinion_order from a map point, or legal_opinion_project with your documents.

What does a report in progress return?

Its stage, its progress, and any documents or answers it is waiting on, so you know what to send.

Does reading cost anything?

No. It costs nothing, within the account's allowance of free calls.