Denton County, TX parcel and infrastructure data API

Parcel coverage in Denton County

About 380,000 parcel records with boundaries, situs addresses and parcel numbers, with the latest source update from January 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:

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

Infrastructure in and around Denton County

Example requests for Denton 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 13833 STICE RD, KRUM, 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":"13833 STICE RD, KRUM, TX","sections":["datacenters"]}' \
  https://api.korzy.co/v1/lookup

import os
import requests

response = requests.post(
    "https://api.korzy.co/v1/lookup",
    json={"address": "13833 STICE RD, KRUM, 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"])

{
  "location": {
    "longitude": -97.36296046188875,
    "latitude": 33.311505499999996,
    "address": "13833 STICE RD, KRUM",
    "match_type": "exact"
  },
  "parcels": {
    "records": [
      {
        "id": "48121-1b03146da7c4e673b6ca",
        "korzy_id": "48121-1b03146da7c4e673b6ca",
        "parcelid": "60553",
        "parceladdr": "13833 STICE RD",
        "parcelcity": "KRUM",
        "situs_zip": "76249",
        "statefp": "48",
        "geoid": "48121",
        "longitude": -97.36296046188875,
        "latitude": 33.311505499999996,
        "usedesc": "R",
        "yearbuilt": 0,
        "bldgsqft": 0,
        "taxacres": 422.55,
        "totalvalue": 0,
        "land_value_usd": 2957850,
        "improvement_value_usd": 0,
        "market_value_usd": 2957850,
        "updated": "2026-01-01"
      }
    ],
    "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 48121-1b03146da7c4e673b6ca, 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":"48121-1b03146da7c4e673b6ca"}],"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/48121-1b03146da7c4e673b6ca

const response = await fetch(`https://api.korzy.co/v1/records/${encodeURIComponent("48121-1b03146da7c4e673b6ca")}`, {
  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);

Denton County data questions

How many parcels in Denton County include year built?

About 380,000 of about 380,000 parcel records (99%) include year built.

Does the Korzy API return owner names for Denton County parcels?

Yes. 91% of Denton 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 Denton County?

Korzy tracks 6 data-center projects in Denton County: 2 proposed, 2 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 Denton County?

About 10 operable power plants in Denton County total about 1,100 MW of nameplate capacity, mainly solar, natural gas and battery and pumped storage.

Which water systems serve Denton County?

Service areas of about 100 community water systems cover about 83% of Denton County, and sewer service areas cover about 56%. A /v1/lookup with the utilities section returns the water and sewer matches at an address or point.

More featured counties

• Dallas County, TXBorders Denton County · about 840,000 parcels
• Tarrant County, TXBorders Denton County · about 750,000 parcels
• Bexar County, TXabout 710,000 parcels
• Harris County, TXabout 1.6 million parcels
• Travis County, TXabout 420,000 parcels

All featured Texas counties