*** September 2026 Major Release ***Read and watch
Document type

Extracting data from residential leases

Each state's REALTOR association publishes a standard lease, and plenty of landlords write their own, so the same clause sits somewhere different on each. A property manager files one for every tenancy and a lender reads one to verify rental income. Large managers process thousands a year, arriving as e-signed PDFs and phone photographs.

A verifier needs the tenant, the property address, the term and the security deposit. A property management system opens the tenancy from those, and a bank accepts the same lease as proof of where an applicant lives.

Page 1 of a sample Residential Lease, with extracted values outlined
27,679Markdown characters
76parse blocks
30fields extracted
The problem

What makes residential leases hard

Values typed onto rule lines

A lease prints its blanks as underscores inside sentences, so a value lands mid-clause in bold italic with prose either side.

Terms are chosen by tick

A lease elects between options with checkboxes, so the term or the renewal depends on which box carries a mark.

One clause, several pages

Obligations run across numbered paragraphs on sheet after sheet, each initialed at the foot, with the signatures on the last.

How it works

Parse, extract, verify

1

Parse

Parse turns the document into reading-order Markdown and a hierarchy of blocks (text, tables, figures), and grounds each block to its exact location on the page.

2

Extract

You define the fields in a JSON schema, and Extract returns their values in a consistent, structured format, each linked back to where it appears in the Markdown.

3

Verify

Each value links back to where it appears, down to the character range in the Markdown, and the page and bounding box in the source document, so every result can be verified.

Worked example

One residential lease, end to end

About this document: A completed residential lease on the Arkansas REALTORS® Association's standard form, e-signed through a brokerage. Six portrait pages of numbered clauses, with every value typed on top of the form's own rule lines in bold italic. Page 1 is featured. The tenant's name was replaced before publication, including the typed signature, which was re-set in a handwriting font so it still reads as a signature.

Processing objective: The objective is to find values that were typed into sentences, where a form's blanks sit inside numbered clauses. The address and the deposit are each part of a paragraph of legal prose, and the term was chosen by ticking a box.

Demonstration fields: Property address, Tenant, Lease term, Security deposit

The document

4 of 6 pages
  • Page 1 of the sample Residential LeasePage 1shown below
  • Page 2 of the sample Residential LeasePage 2
  • Page 4 of the sample Residential LeasePage 4
  • Page 6 of the sample Residential LeasePage 6

Where each value came from

Page 1 of the sample Residential Lease, with every featured field outlined
Property addressproperty.address
909 Shall Court Studio Jacksonville AR 72076
The region of the sample Residential Lease containing Property address, with the extracted value outlined
extraction_metadata["property.address"]
{
  "value": "909 Shall Court Studio Jacksonville AR 72076",
  "page": 1,
  "range": {
    "end": 670,
    "start": 473
  },
  "box": {
    "xmin": 0.05401,
    "ymin": 0.21693,
    "xmax": 0.94615,
    "ymax": 0.28367
  }
}
Tenantparties.tenant
Jane Q Sample
The region of the sample Residential Lease containing Tenant, with the extracted value outlined
extraction_metadata["parties.tenant"]
{
  "value": "Jane Q Sample",
  "page": 1,
  "range": {
    "end": 471,
    "start": 178
  },
  "box": {
    "xmin": 0.04472,
    "ymin": 0.11286,
    "xmax": 0.94654,
    "ymax": 0.21316
  }
}
Lease termterm.length
12 Months
The region of the sample Residential Lease containing Lease term, with the extracted value outlined
extraction_metadata["term.length"]
{
  "value": "12 Months",
  "page": 1,
  "range": {
    "end": 703,
    "start": 671
  },
  "box": {
    "xmin": 0.05326,
    "ymin": 0.26533,
    "xmax": 0.94331,
    "ymax": 0.30077
  }
}
Security depositsecurity_deposit
700
The region of the sample Residential Lease containing Security deposit, with the extracted value outlined
extraction_metadata["security_deposit"]
{
  "value": 700,
  "page": 1,
  "range": {
    "end": 2357,
    "start": 2265
  },
  "box": {
    "xmin": 0.05384,
    "ymin": 0.55864,
    "xmax": 0.94563,
    "ymax": 0.57736
  }
}

How to try it yourself

Everything on this page is reproducible. The sample, its schema, and the Parse and Extract API outputs are published. You can repeat the same two calls from whichever surface you already build on.

  • Claude Skilldescribe the job; the agent writes it
  • CLIno code at all
  • MCPexpose ADE docs as an agent tool
  • REST APIany language
  • Pythonlandingai-ade
  • TypeScriptlandingai-ade
Why LandingAI?

Documents into data

Accurate

The best accuracy on the difficult documents other tools get wrong, such as messy scans, complicated tables, checkboxes and handwriting.

Auditable

Every answer cites its sources. Values come back with an audit trail (page, bounding box, character range) so a human can review them.

Agentic

Applies multi-step reasoning, and plans before it acts. Handles documents it has never seen before and adapts to variations.

API-first

Composable APIs that drop into any tech stack and can be called from anywhere. Easy to build on and embed in your pipelines and products.

Affordable

Cost-competitive rates with complete price transparency. Spend controls before you run, and every job reports its exact cost.

Enterprise-grade

Built for production and scale from day one. Fully observable and monitored, running securely in our cloud or yours.

Built for high-volume, high-throughput production

  • Zero data retention
  • Priority rate limits
  • Enhanced support
  • VPC and on-prem deployment

Available on Team and Enterprise plans.

Compare plans
Capabilities

Residential Lease processing highlights

Every state's standard form
Values typed on rule lines
Checkbox elections
Parties and property address
Term and renewal dates
Rent and deposit amounts
Clauses across many pages
Initials and e-signatures
Form serial numbers
Scanned and photographed leases
Bounding box for every value
Zero data retention available
FAQs

Questions, answered

Yes. Parsing works from the rendered page. A value typed onto a rule line inside a sentence is located the same way as one in a table cell, and comes back with its own coordinates.

Yes. A ticked box comes back as a boolean beside the option it elects. The term a lease runs for is read from the mark that selected it.

No. A schema names the fields you want. Where they sit in the lease is not part of it, so one schema reads a form it has never seen. A clause a particular lease omits comes back null.

Every value comes back with its page, a bounding box and the character range in the parsed Markdown. The box can be drawn onto the page image, so a reviewer sees the clause it was typed into.

A lease carries tenant and landlord names, a property address, signatures and financial terms, which is why a bank accepts one as proof of address. A schema can ask for the terms alone. Accounts are available with zero data retention, alongside SOC 2 Type II, GDPR and HIPAA compliance.

Start extracting residential lease data

Reliable, structured outputs with full traceability in minutes