Tarrant County, TX parcel and infrastructure data API
Korzy has about 750,000 parcel records for Tarrant County, Texas, with source updates through July 2026. Nearly every record carries values, last sale, year built and building size. In and around the county the API also maps about 10 data-center projects (2 operating and 1 under construction); about 25 power plants with about 1,500 MW of capacity, led by natural gas; and about 420 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 Tarrant County
About 750,000 parcel records with boundaries, situs addresses and parcel numbers, with the latest source update from July 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:
| Field | Coverage | Share |
|---|---|---|
| Situs address | Nearly all · 99% | |
| Owner name | Some · 1% | |
| Assessed or market value | Nearly all · 99% | |
| Year built | Nearly all · 99% | |
| Building size | Nearly all · 99% | |
| Last sale | Nearly all · 95% | |
| Land use | Some · 1% | |
| Zoning | Not published |
Owner name and mailing address are returned by /v1/enrich with the owner group, at 2 credits per parcel instead of 1 credit. 1% of Tarrant County records carry an owner name.
Infrastructure in and around Tarrant County
Power plants
About 25 operable plants with about 1,500 MW of nameplate capacity; largest by capacity: natural gas, battery and pumped storage, solar. Proposed generators add about 10 MW.
Within 50 km: /v1/lookup section power; details: /v1/records/{id}
Substations and transmission
About 140 in-service substations, about 15 rated 230 kV or higher.
About 750 miles of transmission lines: about 55 mi at under 100 kV; about 450 mi at 100–161 kV; about 250 mi at 345 kV.
Water and sewer service
Service areas of about 90 community water systems cover about 91% of the county.
Sewer service areas of about 10 systems cover about 55%.
At an address or point: /v1/lookup section utilities
Data-center projects
About 10 tracked projects: 2 operating, 1 under construction, 8 status not reported.
Within 10 km: /v1/lookup section datacenters
Flood zones and wetlands
Special flood hazard areas cover about 15% of the county on the current federal flood maps, published October 2026.
Mapped wetlands cover about 1%.
At an address or point: /v1/lookup section environment
Rail, ports and freight
- About 420 miles of active rail, about 240 of it main line
- About 150 miles of national freight network highway
Within 25 km: /v1/lookup section logistics
Example requests for Tarrant 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 3801 COLLEYVILLE BLVD, COLLEYVILLE, 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":"3801 COLLEYVILLE BLVD, COLLEYVILLE, TX","sections":["datacenters"]}' \
https://api.korzy.co/v1/lookupPython
import os
import requests
response = requests.post(
"https://api.korzy.co/v1/lookup",
json={"address": "3801 COLLEYVILLE BLVD, COLLEYVILLE, 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": -97.17277675220839,
"latitude": 32.8656922,
"address": "3801 COLLEYVILLE BLVD, COLLEYVILLE",
"match_type": "exact"
},
"parcels": {
"records": [
{
"id": "48439-85468463b14d91f8ae5a",
"korzy_id": "48439-85468463b14d91f8ae5a",
"parcelid": "1000002908",
"parceladdr": "3801 COLLEYVILLE BLVD",
"parcelcity": "COLLEYVILLE",
"situs_zip": "76034",
"statefp": "48",
"geoid": "48439",
"longitude": -97.17277675220839,
"latitude": 32.8656922,
"usedesc": "COMMERCIAL",
"yearbuilt": 1973,
"bldgsqft": 7000,
"taxacres": 0.2753,
"totalvalue": 900335,
"land_value_usd": 89955,
"improvement_value_usd": 900335,
"market_value_usd": 798000,
"updated": "2026-01-01"
}
],
"truncated": false
},
"sections": {
"datacenters": {
"status": "ok",
"data": {
"radius_km": 10,
"projects": [
{
"id": "datacenter:dc_33989ffcfc93945ee135",
"project_id": "dc_33989ffcfc93945ee135",
"name": "Amazon Web Services",
"operator": "Amazon Web Services",
"status": "unknown",
"state": "TX",
"longitude": -97.07025967865607,
"latitude": 32.85051835,
"location_precision": "footprint",
"source_count": 1,
"source_date": "2026-05-23T14:47:34Z",
"mapped": true,
"distance_km": 9.72319544986684
}
],
"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 48439-85468463b14d91f8ae5a, 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":"48439-85468463b14d91f8ae5a"}],"fields":["identity","sale","owner"]}' \
https://api.korzy.co/v1/enrich3. 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/48439-85468463b14d91f8ae5aJavaScript
const response = await fetch(`https://api.korzy.co/v1/records/${encodeURIComponent("48439-85468463b14d91f8ae5a")}`, {
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);Tarrant County data questions
- How many parcels in Tarrant County include year built?
- About 740,000 of about 750,000 parcel records (99%) include year built.
- Does the Korzy API return owner names for Tarrant County parcels?
- Yes. 1% of Tarrant 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 Tarrant County?
- Korzy tracks about 10 data-center projects in Tarrant County: 8 status not reported, 2 operating 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 Tarrant County?
- About 25 operable power plants in Tarrant County total about 1,500 MW of nameplate capacity, mainly natural gas, battery and pumped storage and solar.
- Which water systems serve Tarrant County?
- Service areas of about 90 community water systems cover about 91% of Tarrant County, and sewer service areas cover about 55%. A /v1/lookup with the utilities section returns the water and sewer matches at an address or point.
More featured counties
- Dallas County, TXBorders Tarrant County · about 840,000 parcels
- Denton County, TXBorders Tarrant County · about 380,000 parcels
- Bexar County, TXabout 710,000 parcels
- Harris County, TXabout 1.6 million parcels
- Travis County, TXabout 420,000 parcels
Build on Tarrant 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.