Kent County, DE parcel and infrastructure data API

Korzy has about 81,000 parcel records for Kent County, Delaware, with source updates through November 2026. Nearly every record carries owner names, values and land use; 76% include year built. In and around the county the API also maps 1 data-center project (1 operating); about 15 power plants with about 660 MW of capacity, led by natural gas; and about 55 miles of active rail. Look up any parcel by address or coordinates, then check water, sewer and infrastructure context at the same point.

Parcel coverage in Kent County

About 81,000 parcel records with boundaries, situs addresses and parcel numbers, with the latest source update from November 2026. Each record has a stable korzy_id you can store and look up again with /api/parcel-record. Share of records with each field:

FieldCoverageShare
Situs addressNearly all · 100%
Owner nameNearly all · 99%
Assessed or market valueNearly all · 99%
Year builtMost · 76%
Building sizeNot published
Last saleNot published
Land useNearly all · 98%
ZoningNot published

Owner name and mailing address are returned with include_owner=true, which doubles a request's cost: a parcel record costs 2 credits instead of 1. 99% of Kent County records carry an owner name.

Infrastructure in and around Kent County

Power plants

About 15 operable plants with about 660 MW of nameplate capacity; largest by capacity: natural gas, battery and pumped storage, solar. Proposed generators add about 60 MW.

Plant details: /api/power/plants/{plant_id}

Substations and transmission

About 45 in-service substations, 2 rated 230 kV or higher.

About 210 miles of transmission lines: about 85 mi at under 100 kV; about 40 mi at 100–161 kV; about 85 mi at 220–287 kV.

Water and sewer service

Service areas of about 60 community water systems cover about 12% of the county.

Sewer service areas of 1 system cover about 18%.

At a point: /api/utilities/context

Data-center projects

1 tracked project: 1 operating. Reported planned capacity: about 25 MW.

Within 10 km of a point: /api/datacenters/context

Grid capacity data

2 utility-published grid capacity layers cover parts of Kent County, including load headroom.

Sources and dates: /api/grid/capacity/summary

Flood zones and wetlands

Special flood hazard areas cover about 22% of the county on the current federal flood maps, published May 2026.

Mapped wetlands cover about 26%.

Rail, ports and freight

  • About 55 miles of active rail, about 45 of it main line

Within 25 km of a point: /api/logistics/context

Example requests for Kent County

Real responses from the production API, trimmed to the main fields. Every request needs an API key with api:read; see authentication and credits and limits.

1. Find a parcel by address

/api/search matches 321 W BROAD ST, CAMDEN, DE and returns the parcel's korzy_id, coordinates and record. 1 credit.

curl --fail-with-body -sS --get \
  -H "Authorization: Bearer $KORZY_API_KEY" \
  --data-urlencode 'q=321 W BROAD ST, CAMDEN, DE' \
  https://api.korzy.co/api/search
Python
import os
import requests

response = requests.get(
    "https://api.korzy.co/api/search",
    params={"q": "321 W BROAD ST, CAMDEN, DE"},
    headers={"Authorization": f"Bearer {os.environ['KORZY_API_KEY']}"},
    timeout=30,
)
response.raise_for_status()
parcel = response.json()["results"][0]
print(parcel["korzy_id"], parcel["longitude"], parcel["latitude"])
Response (trimmed)
{
  "results": [
    {
      "korzy_id": "10001-93775a651c4e70ce9866",
      "address": "321 W BROAD ST",
      "city": "CAMDEN",
      "postcode": "19934.0",
      "county": "Kent",
      "statefp": "10",
      "longitude": -75.560338094418,
      "latitude": 39.12076985,
      "match_type": "exact",
      "parcelid": "7-20-09406-01-2300-00001",
      "parceladdr": "321 W BROAD ST",
      "parcelcity": "CAMDEN",
      "situs_zip": "19934.0",
      "usedesc": "Government - Municipality Owned",
      "yearbuilt": 2018,
      "taxacres": 0.49,
      "land_value_usd": 126800,
      "improvement_value_usd": 256700,
      "assessed_value_usd": 383500,
      "updated": "2026-11-03",
      "geoid": "10001"
    }
  ],
  "truncated": false
}

With include_owner=true (2 credits) the record adds owner fields, shown here as placeholders:

{
  "owner_name": "EXAMPLE HOLDINGS LLC",
  "owner_mailing_address": "100 EXAMPLE ST, SAMPLE CITY, ST 00000"
}

2. Look up the parcel at a point

/api/query/point returns every parcel whose boundary covers the coordinates; here it returns the same record, 10001-93775a651c4e70ce9866, in records. 1 credit per 10 records requested.

curl --fail-with-body -sS --get \
  -H "Authorization: Bearer $KORZY_API_KEY" \
  --data-urlencode 'longitude=-75.560338' \
  --data-urlencode 'latitude=39.12077' \
  --data-urlencode 'limit=5' \
  https://api.korzy.co/api/query/point
JavaScript
const params = new URLSearchParams({"longitude": "-75.560338", "latitude": "39.12077", "limit": "5"});
const response = await fetch(`https://api.korzy.co/api/query/point?${params}`, {
  headers: { Authorization: `Bearer ${process.env.KORZY_API_KEY}` },
});
if (!response.ok) throw new Error(`Korzy API ${response.status}`);
const { records } = await response.json();
console.log(records.map((record) => record.korzy_id));

3. Check water and sewer service

/api/utilities/context returns the water and sewer service areas at the point and the nearest treatment plants. 1 credit.

curl --fail-with-body -sS --get \
  -H "Authorization: Bearer $KORZY_API_KEY" \
  --data-urlencode 'longitude=-75.560338' \
  --data-urlencode 'latitude=39.12077' \
  https://api.korzy.co/api/utilities/context
Python
import os
import requests

response = requests.get(
    "https://api.korzy.co/api/utilities/context",
    params={"longitude": "-75.560338", "latitude": "39.12077"},
    headers={"Authorization": f"Bearer {os.environ['KORZY_API_KEY']}"},
    timeout=30,
)
response.raise_for_status()
matches = response.json()["matches"]
print([area["name"] for area in matches["water"]])
Response (trimmed)
{
  "longitude": -75.560338,
  "latitude": 39.12077,
  "matches": {
    "water": [
      {
        "feature_id": "water:32643",
        "name": "CAMDEN PUMP DISTRICT",
        "boundary_basis": "Modeled"
      }
    ],
    "sewer": []
  },
  "nearby_treatment": [
    {
      "feature_id": "treatment:269",
      "name": "KENT COUNTY STP",
      "distance_km": 17.636644076584222
    },
    {
      "feature_id": "treatment:11764",
      "name": "Greensboro WWTP",
      "distance_km": 26.048675777755644
    }
  ]
}

Kent County data questions

How many parcels in Kent County include year built?
About 62,000 of about 81,000 parcel records (76%) include year built.
Does the Korzy API return owner names for Kent County parcels?
Yes. 99% of Kent County parcel records carry an owner name. Add include_owner=true to a point, search or parcel-record request; it doubles the request's cost, so a single parcel record costs 2 credits.
How many data-center projects are in Kent County?
Korzy tracks 1 data-center project in Kent County: 1 operating. /api/datacenters/context lists projects within 10 km of any point.
How much power generation is in Kent County?
About 15 operable power plants in Kent County total about 660 MW of nameplate capacity, mainly natural gas, battery and pumped storage and solar.
Which water systems serve Kent County?
Service areas of about 60 community water systems cover about 12% of Kent County, and sewer service areas cover about 18%. /api/utilities/context returns the water and sewer matches at a point.

Build on Kent County parcel data

Search, point and record lookups work the same in every county Korzy covers. Credits are shared across parcels, utilities, environment, logistics and data-center routes.