Harris County, TX parcel and infrastructure data API

Korzy has about 1.6 million parcel records for Harris County, Texas, with source updates through November 2026. Nearly every record carries values and land use; 92% include building size and 87% include year built. In and around the county the API also maps about 85 power plants with about 10,000 MW of capacity, led by natural gas; about 850 miles of active rail; and 7 data-center projects (1 operating). 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 Harris County

About 1.6 million 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 /v1/records/{id}. Share of records with each field:

FieldCoverageShare
Situs addressNearly all · 100%
Owner nameMost · 84%
Assessed or market valueNearly all · 96%
Year builtMost · 87%
Building sizeMost · 92%
Last saleMost · 84%
Land useNearly all · 99%
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. 84% of Harris County records carry an owner name.

Infrastructure in and around Harris County

Power plants

About 85 operable plants with about 10,000 MW of nameplate capacity; largest by capacity: natural gas, battery and pumped storage, other fuels. Proposed generators add about 1,600 MW.

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

Substations and transmission

About 360 in-service substations, about 20 rated 230 kV or higher.

About 2,000 miles of transmission lines: about 45 mi at under 100 kV; about 1,500 mi at 100–161 kV; about 370 mi at 345 kV.

Water and sewer service

Service areas of about 700 community water systems cover about 64% of the county.

Sewer service areas of about 250 systems cover about 42%.

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

Data-center projects

7 tracked projects: 1 operating, 6 status not reported. Reported operating capacity: about 25 MW.

Within 10 km: /v1/lookup section datacenters

Flood zones and wetlands

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

Mapped wetlands cover about 5%.

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

Rail, ports and freight

  • About 850 miles of active rail, about 370 of it main line
  • About 270 miles of national freight network highway
  • 1 port area with reported cargo tonnage
  • 6 intermodal rail terminals

Within 25 km: /v1/lookup section logistics

Example requests for Harris 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 1511 W 34TH ST, HOUSTON, TX 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":"1511 W 34TH ST, HOUSTON, TX","sections":["datacenters"]}' \
  https://api.korzy.co/v1/lookup
Python
import os
import requests

response = requests.post(
    "https://api.korzy.co/v1/lookup",
    json={"address": "1511 W 34TH ST, HOUSTON, TX", "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": -95.42579272060283,
    "latitude": 29.8167694,
    "address": "1511 W 34TH ST, HOUSTON",
    "match_type": "exact"
  },
  "parcels": {
    "records": [
      {
        "id": "48201-144cc4eda70e4f9814cd",
        "korzy_id": "48201-144cc4eda70e4f9814cd",
        "parcelid": "0580930000018",
        "parceladdr": "1511 W 34TH ST",
        "parcelcity": "HOUSTON",
        "situs_zip": "77018",
        "statefp": "48",
        "geoid": "48201",
        "longitude": -95.42579272060283,
        "latitude": 29.8167694,
        "usedesc": "Office Bldgs. Low-Rise (1 to 4 Stories)",
        "land_use_code": "8002",
        "yearbuilt": 1975,
        "bldgsqft": 16765,
        "taxacres": 1.0682966023875116,
        "totalvalue": 2512721,
        "land_value_usd": 1861400,
        "improvement_value_usd": 762058,
        "assessed_value_usd": 3049757,
        "market_value_usd": 2623458,
        "saledate": "2005-05-05",
        "updated": "2026-10-13"
      }
    ],
    "truncated": false
  },
  "sections": {
    "datacenters": {
      "status": "ok",
      "data": {
        "radius_km": 10,
        "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 48201-144cc4eda70e4f9814cd, 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":"48201-144cc4eda70e4f9814cd"}],"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/48201-144cc4eda70e4f9814cd
JavaScript
const response = await fetch(`https://api.korzy.co/v1/records/${encodeURIComponent("48201-144cc4eda70e4f9814cd")}`, {
  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);

Harris County data questions

How many parcels in Harris County include year built?
About 1.4 million of about 1.6 million parcel records (87%) include year built.
Does the Korzy API return owner names for Harris County parcels?
Yes. 84% of Harris 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 Harris County?
Korzy tracks 7 data-center projects in Harris County: 6 status not reported and 1 operating. A /v1/lookup with the datacenters section lists projects within 10 km of any address or point.
How much power generation is in Harris County?
About 85 operable power plants in Harris County total about 10,000 MW of nameplate capacity, mainly natural gas, battery and pumped storage and other fuels.
Which water systems serve Harris County?
Service areas of about 700 community water systems cover about 64% of Harris County, and sewer service areas cover about 42%. A /v1/lookup with the utilities section returns the water and sewer matches at an address or point.

More featured counties

All featured Texas counties

Build on Harris 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.