Land due diligence data for acquisitions and real estate

Answer the first land due diligence questions about a parcel in minutes: what the record says, whether public water and sewer are mapped there, and what sits nearby.

Get a Korzy API key See Korzy pricing Read the Korzy API docs

Land due diligence: the job to be done

Acquisition teams, land brokers and lenders look at far more parcels than they ever close on. Before paying for surveys, title work and a Phase I, they need a fast read on each one: the assessor record, utility service, environmental flags and access.

Korzy returns those answers from published records at a point or a parcel ID, as screening inputs for a human decision, not as a substitute for formal diligence.

Questions Korzy answers for land due diligence

What does the parcel record say: land use, acreage, building, values and last sale?
Is the parcel inside a mapped public water and sewer service area, and where is the nearest treatment plant?
Are there cleanup sites, protected areas or critical habitat nearby?
How far is the nearest rail line or freight corridor?

API routes and MCP tools for land due diligence

Each lookup is a REST route and, where named, a tool on the Korzy MCP server. Routes link to their section of the API reference; credits and rate limits covers what each request costs.

MCP tool	REST route	What it returns
`search_parcels`	`/api/search`	The parcel at an address, with the assessor fields Korzy publishes.
`get_parcel`	`/api/parcel-record`	A full parcel record by korzy_id; owner fields with include_owner=true.
`get_site_context`	`/api/utilities/context`	Water and sewer service areas at the point and the nearest treatment plants.
`get_environment_context`	`/api/environment/context`	Environmental layers at the point and cleanup sites nearby.
`get_logistics_context`	`/api/logistics/context`	Rail, ports and freight corridors within 25 km.
`get_parcel_terrain`	MCP only	Slope and elevation analysis over the parcel, by korzy_id.

Example requests and production responses

Real responses from the production API, captured November 5, 2026 and trimmed to the main fields. Every request needs an API key; see API authentication.

1. Water and sewer service at a parcel

Mapped service areas at 2304 Hillsborough St, Raleigh, and the nearest treatment plants. 1 credit.

curl --fail-with-body -sS --get \
  -H "Authorization: Bearer $KORZY_API_KEY" \
  --data-urlencode 'longitude=-78.666186' \
  --data-urlencode 'latitude=35.787588' \
  https://api.korzy.co/api/utilities/context

Response (trimmed)

{
  "longitude": -78.666186,
  "latitude": 35.787588,
  "matches": {
    "water": [
      {
        "feature_id": "water:29943",
        "name": "RALEIGH, CITY OF",
        "boundary_basis": "System Sourced"
      }
    ],
    "sewer": [
      {
        "feature_id": "sewer:2161",
        "name": "NEUSE RIVER RESOURCE RECOVERY FACILITY",
        "boundary_basis": "Sourced"
      }
    ]
  },
  "nearby_treatment": [
    {
      "feature_id": "treatment:7989",
      "name": "NORTH CARY WWTP",
      "distance_km": 11.327051931207679
    },
    {
      "feature_id": "treatment:7990",
      "name": "SOUTH CARY WWTP",
      "distance_km": 17.15015426882848
    },
    {
      "feature_id": "treatment:7988",
      "name": "APEX WWTP",
      "distance_km": 17.341396114306253
    }
  ],
  "truncated": {
    "water": false,
    "sewer": false
  }
}

2. Environmental screening around the same parcel

Layers at the point and cleanup sites within 2 km. 1 credit per 10 records requested.

curl --fail-with-body -sS --get \
  -H "Authorization: Bearer $KORZY_API_KEY" \
  --data-urlencode 'longitude=-78.666186' \
  --data-urlencode 'latitude=35.787588' \
  --data-urlencode 'radius_km=2' \
  --data-urlencode 'limit=3' \
  https://api.korzy.co/api/environment/context

Response (trimmed)

{
  "longitude": -78.666186,
  "latitude": 35.787588,
  "radius_km": 2,
  "limit": 3,
  "matches": {
    "superfund_sites": [],
    "protected_areas": [],
    "critical_habitat_areas": [],
    "critical_habitat_lines": [],
    "air_quality_areas": [
      {
        "feature_id": "air_quality_areas:0:103",
        "name": "Raleigh-Durham-Chapel Hill Area · Ozone 8-hr (1997 standard) · NC",
        "status": "Maintenance",
        "state": "NC",
        "category": "Ozone 8-hr (1997 standard)",
        "geometry_kind": "area"
      },
      {
        "feature_id": "air_quality_areas:10:64",
        "name": "Raleigh-Durham Area · Ozone 1-hr (1979 standard-revoked) · NC",
        "status": "Maintenance (NAAQS revoked)",
        "state": "NC",
        "category": "Ozone 1-hr (1979 standard-revoked)",
        "geometry_kind": "area"
      },
      {
        "feature_id": "air_quality_areas:9:38",
        "name": "Raleigh-Durham Area · CO (1971 Standard) · NC",
        "status": "Maintenance",
        "state": "NC",
        "category": "CO (1971 Standard)",
        "geometry_kind": "area"
      }
    ]
  },
  "nearby": {
    "superfund_npl": [],
    "brownfields": [
      {
        "feature_id": "brownfields:records:5117",
        "name": "FORMER TAO AUTO",
        "state": "NC",
        "city": "RALEIGH",
        "category": "Brownfields",
        "distance_km": 1.7380330849426944,
        "geometry_kind": "point"
      }
    ]
  },
  "truncated": {
    "superfund_sites": false,
    "superfund_npl": false,
    "brownfields": false,
    "protected_areas": false,
    "critical_habitat_areas": false,
    "critical_habitat_lines": false,
    "air_quality_areas": false
  }
}

County parcel data for land due diligence

Parcel coverage, infrastructure counts and example requests for counties where this work is common. Korzy covers parcel data in every U.S. county.

How Korzy compares with other parcel data APIs

More Korzy use cases

Put early diligence on autopilot

Run the same checks on every parcel in your pipeline through the API, or ask an AI assistant connected to the Korzy MCP server.

Get a Korzy API key See Korzy pricing Connect an AI agent to Korzy