Kent County, MI parcel and infrastructure data API

Korzy has about 270,000 parcel records for Kent County, Michigan, with source updates through October 2026. Nearly every record carries values; 69% include owner names and 69% include land use. In and around the county the API also maps 7 data-center projects (3 operating and 1 under construction); 8 power plants with about 70 MW of capacity, led by natural gas; and about 120 miles of active rail. Look up any parcel by address or coordinates, then check nearby data-center projects, utilities and grid context at the same point.

Parcel coverage in Kent County

About 270,000 parcel records with boundaries, situs addresses and parcel numbers, with the latest source update from October 2026. Each record has a stable korzy_id you can store and look up again with /v1/records/{id}. Share of records with each field:

FieldCoverageShare
Situs addressNearly all · 100%
Owner nameMany · 69%
Assessed or market valueNearly all · 96%
Year builtNot published
Building sizeNot published
Last saleNot published
Land useMany · 69%
ZoningNot published

Owner name and mailing address are returned by /v1/enrich with the owner group, at 2 credits per parcel instead of 1 credit. 69% of Kent County records carry an owner name.

Infrastructure in and around Kent County

Power plants

8 operable plants with about 70 MW of nameplate capacity; largest by capacity: natural gas, other fuels, battery and pumped storage.

Within 50 km: /v1/lookup section power; details: /v1/records/{id}

Substations and transmission

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

About 410 miles of transmission lines: about 20 mi at under 100 kV; about 230 mi at 100–161 kV; about 130 mi at 345 kV.

Water and sewer service

Service areas of about 45 community water systems cover about 26% of the county.

Sewer service areas of about 15 systems cover about 30%.

At an address or point: /v1/lookup section utilities

Data-center projects

7 tracked projects: 3 operating, 1 under construction, 3 proposed. Reported operating capacity: about 220 MW. Reported planned capacity: about 320 MW.

Within 10 km: /v1/lookup section datacenters

Flood zones and wetlands

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

Mapped wetlands cover about 10%.

At an address or point: /v1/lookup section environment

Rail, ports and freight

  • About 120 miles of active rail, about 85 of it main line
  • About 50 miles of national freight network highway

Within 25 km: /v1/lookup section logistics

Example requests for Kent County

The lookup response is a real production response, trimmed to the main fields. Every request needs an API key with api:read; see authentication and credits and limits.

1. Find a parcel and nearby data-center projects

/v1/lookup matches 400 76TH ST SW, BYRON CENTER, MI and returns the parcel's korzy_id and record, plus the data-center projects within 10 km, nearest first. 2 credits.

curl --fail-with-body -sS \
  -H "Authorization: Bearer $KORZY_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"address":"400 76TH ST SW, BYRON CENTER, MI","sections":["datacenters"]}' \
  https://api.korzy.co/v1/lookup
Python
import os
import requests

response = requests.post(
    "https://api.korzy.co/v1/lookup",
    json={"address": "400 76TH ST SW, BYRON CENTER, MI", "sections": ["datacenters"]},
    headers={"Authorization": f"Bearer {os.environ['KORZY_API_KEY']}"},
    timeout=60,
)
response.raise_for_status()
body = response.json()
parcel = body["parcels"]["records"][0]
print(parcel["korzy_id"], body["sections"]["datacenters"]["status"])
Production response (trimmed)
{
  "location": {
    "longitude": -85.6731833784784,
    "latitude": 42.82564305,
    "address": "400 76TH ST SW, BYRON CENTER",
    "match_type": "exact"
  },
  "parcels": {
    "records": [
      {
        "id": "26081-7f10deb906137c4c02a0",
        "korzy_id": "26081-7f10deb906137c4c02a0",
        "parcelid": "41-21-13-100-090",
        "parceladdr": "400 76TH ST SW",
        "parcelcity": "BYRON CENTER",
        "situs_zip": "49315",
        "statefp": "26",
        "geoid": "26081",
        "longitude": -85.6731833784784,
        "latitude": 42.82564305,
        "land_use_code": "201",
        "taxacres": 6.56216562,
        "totalvalue": 3555327,
        "assessed_value_usd": 1396000,
        "updated": "2026-10-30"
      }
    ],
    "truncated": false
  },
  "sections": {
    "datacenters": {
      "status": "ok",
      "data": {
        "radius_km": 10,
        "projects": [
          {
            "id": "datacenter:dc_6299c8c16781bb30b39f",
            "project_id": "dc_6299c8c16781bb30b39f",
            "name": "123NET DC4 Grand Rapids Data Center",
            "operator": "123NET",
            "status": "operating",
            "state": "MI",
            "city": "Byron Center",
            "address": "400 76th Street SW",
            "longitude": -85.67268596115,
            "latitude": 42.826202163837,
            "location_precision": "approximate",
            "source_count": 1,
            "source_date": "2026-09-21",
            "mapped": true,
            "distance_km": 0.07423466579114664
          },
          {
            "id": "datacenter:dc_c29da05973b3a165ebd6",
            "project_id": "dc_c29da05973b3a165ebd6",
            "name": "US Signal MI02 Grand Rapids Data Center",
            "operator": "US Signal",
            "status": "operating",
            "state": "MI",
            "city": "Byron Center",
            "address": "400 76th Street SW",
            "longitude": -85.67268596115,
            "latitude": 42.826202163837,
            "location_precision": "approximate",
            "source_count": 1,
            "source_date": "2026-09-21",
            "mapped": true,
            "distance_km": 0.07423466579114664
          },
          {
            "id": "datacenter:dc_317cfe44afea37e29810",
            "project_id": "dc_317cfe44afea37e29810",
            "name": "Switch Pyramid Campus",
            "operator": "Switch",
            "status": "under_construction",
            "state": "MI",
            "city": "Gaines Township",
            "address": "6100 East Paris Avenue SE",
            "longitude": -85.64,
            "latitude": 42.823,
            "location_precision": "exact",
            "operational_mw": 225,
            "planned_mw": 320,
            "source_count": 1,
            "source_date": "2026-09-21",
            "mapped": true,
            "distance_km": 2.722184140094121
          }
        ],
        "truncated": false,
        "note": "Straight-line distance to the reported project point; inspect location_precision. Projects merge supported source matches, not every nearby building. Approximate locations do not identify a parcel. Reported IT load, facility power, planned capacity and estimates remain separate source claims. No record or unknown status does not establish absence or inactivity."
      },
      "provenance": [
        {
          "dataset": "datacenters",
          "as_of": "2026-11-02",
          "data_version": "20261102T123021962884Z"
        }
      ]
    }
  },
  "credits": {
    "charged": 2,
    "refunded": 0
  }
}

2. Add owner and sale fields

/v1/enrich returns the fields you choose for up to 25 parcels per request; here the parcel 26081-7f10deb906137c4c02a0, with the owner group. 2 credits.

curl --fail-with-body -sS \
  -H "Authorization: Bearer $KORZY_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"items":[{"korzy_id":"26081-7f10deb906137c4c02a0"}],"fields":["identity","sale","owner"]}' \
  https://api.korzy.co/v1/enrich

3. Fetch the record again by ID

/v1/records/{id} returns the stored parcel's full record, without owner fields. 1 credit.

curl --fail-with-body -sS \
  -H "Authorization: Bearer $KORZY_API_KEY" \
  https://api.korzy.co/v1/records/26081-7f10deb906137c4c02a0
JavaScript
const response = await fetch(`https://api.korzy.co/v1/records/${encodeURIComponent("26081-7f10deb906137c4c02a0")}`, {
  headers: { Authorization: `Bearer ${process.env.KORZY_API_KEY}` },
});
if (!response.ok) throw new Error(`Korzy API ${response.status}`);
const { record } = await response.json();
console.log(record.parceladdr, record.usedesc);

Kent County data questions

How many parcels in Kent County include values?
About 260,000 of about 270,000 parcel records (96%) include values.
Does the Korzy API return owner names for Kent County parcels?
Yes. 69% of Kent County parcel records carry an owner name. Ask /v1/enrich for the owner group; each parcel then costs 2 credits instead of 1 credit. Lookups and records never include owner fields.
How many data-center projects are in Kent County?
Korzy tracks 7 data-center projects in Kent County: 3 operating, 3 proposed and 1 under construction. A /v1/lookup with the datacenters section lists projects within 10 km of any address or point.
How much power generation is in Kent County?
8 operable power plants in Kent County total about 70 MW of nameplate capacity, mainly natural gas, other fuels and battery and pumped storage.
Which water systems serve Kent County?
Service areas of about 45 community water systems cover about 26% of Kent County, and sewer service areas cover about 30%. A /v1/lookup with the utilities section returns the water and sewer matches at an address or point.

More featured counties

All featured Michigan counties

Build on Kent County parcel data

Lookups, enrichment and records work the same in every county Korzy covers. Credits are shared across parcels, utilities, environment, logistics, power, grid, data-center and terrain sections.