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

Extracting data from certificates of occupancy

A city issues a certificate of occupancy when a building may lawfully be used, and every buildings department prints its own form. A lender will not close on new construction without one, and a landlord files it for each tenancy. Title companies read thousands a year, arriving as scans from municipal records.

A closer needs the address, the certificate number, whether it is temporary or final and the dates it runs between. A title system files it against the property record, and a temporary certificate goes on a diary to be chased before it expires.

Page 1 of a sample Certificate of Occupancy, with extracted values outlined
6,889Markdown characters
276parse blocks
203fields extracted
The problem

What makes certificates of occupancy hard

A scan with no text

A certificate is often filed as an image of paper, so every value has to be read from the picture.

Values packed into ruled cells

Lettered sections run down the form, each a grid of label and value pairs squeezed into narrow boxes.

Use tables run columns together

The permitted use table sets a floor number beside the number of persons allowed on it, close enough that position is what separates them.

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 certificate of occupancy, end to end

About this document: A New York City Department of Buildings temporary certificate of occupancy for a school building in the Bronx. Four portrait pages, scanned with no text layer: the certificate itself, two pages of the permissible use and occupancy table, and a closing page. Page 1 is featured. It names no private individual.

Processing objective: The objective is to read the certificate's identity and the window it covers: which building, which certificate, whether it is temporary and between which dates. Both dates are returned in ISO form, normalized from the month-first dates the certificate prints.

Demonstration fields: Property address, CO number, Certificate type, Effective date, Expiration date

The document

4 of 4 pages
  • Page 1 of the sample Certificate of OccupancyPage 1shown below
  • Page 2 of the sample Certificate of OccupancyPage 2
  • Page 3 of the sample Certificate of OccupancyPage 3
  • Page 4 of the sample Certificate of OccupancyPage 4

Where each value came from

Page 1 of the sample Certificate of Occupancy, with every featured field outlined
Property addressproperty.address
192 EAST 151ST STREET
The region of the sample Certificate of Occupancy containing Property address, with the extracted value outlined
extraction_metadata["property.address"]
{
  "value": "192 EAST 151ST STREET",
  "page": 1,
  "range": {
    "end": 651,
    "start": 621
  },
  "box": {
    "xmin": 0.10356,
    "ymin": 0.22887,
    "xmax": 0.46013,
    "ymax": 0.25006
  }
}
CO numberco_number
220152652T005
The region of the sample Certificate of Occupancy containing CO number, with the extracted value outlined
extraction_metadata["co_number"]
{
  "value": "220152652T005",
  "page": 1,
  "range": {
    "end": 84,
    "start": 60
  },
  "box": {
    "xmin": 0.55484,
    "ymin": 0.12076,
    "xmax": 0.8768,
    "ymax": 0.13901
  }
}
Certificate typecertificate_type
Temporary
The region of the sample Certificate of Occupancy containing Certificate type, with the extracted value outlined
extraction_metadata["certificate_type"]
{
  "value": "Temporary",
  "page": 1,
  "range": {
    "end": 602,
    "start": 575
  },
  "box": {
    "xmin": 0.66601,
    "ymin": 0.2079,
    "xmax": 0.89152,
    "ymax": 0.22889
  }
}
Effective dateeffective_date
2019-04-16
The region of the sample Certificate of Occupancy containing Effective date, with the extracted value outlined

Printed on the page as Effective Date: 04/16/2019, normalized on extraction.

extraction_metadata["effective_date"]
{
  "value": "2019-04-16",
  "page": 1,
  "range": {
    "end": 711,
    "start": 685
  },
  "box": {
    "xmin": 0.666,
    "ymin": 0.22889,
    "xmax": 0.8915,
    "ymax": 0.25011
  }
}
Expiration dateexpiration_date
2019-07-15
The region of the sample Certificate of Occupancy containing Expiration date, with the extracted value outlined

Printed on the page as Expiration Date: 07/15/2019, normalized on extraction.

extraction_metadata["expiration_date"]
{
  "value": "2019-07-15",
  "page": 1,
  "range": {
    "end": 862,
    "start": 835
  },
  "box": {
    "xmin": 0.66596,
    "ymin": 0.25008,
    "xmax": 0.89147,
    "ymax": 0.32101
  }
}

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

Certificate of Occupancy processing highlights

Every city's form
Scans with no text layer
Lettered form sections
Permitted use tables
Occupancy per floor
Temporary and final certificates
Effective and expiry dates
Zoning and district codes
Building and block numbers
Official signatures
Dates normalized to ISO
Bounding box for every value
FAQs

Questions, answered

Yes. Parsing works from the rendered page, so a certificate filed as an image reads the same way as one with a text layer, and grounding coordinates come back against the scan.

Yes. Define the floors as an array and each comes back with its permitted use and the number of persons allowed, for as many floors as the certificate lists.

Yes. The certificate type is a field like any other, so a temporary certificate returns its type alongside the expiry date that makes it temporary.

Every value comes back with its page, a bounding box and the character range in the parsed Markdown. A date returned in ISO form still points at the date the certificate printed, so a reviewer sees both.

No. A schema names the fields you want. Where they sit on the form is not part of it, so one schema reads a buildings department it has never seen.

Start extracting certificate of occupancy data

Reliable, structured outputs with full traceability in minutes