Maricopa County, AZ parcel and infrastructure data API
Korzy has about 1.8 million parcel records for Maricopa County, Arizona, with source updates through November 2026. Nearly every record carries owner names, values, land use and building size; 88% include year built and 51% include last sale. In and around the county the API also maps about 70 power plants with about 22,000 MW of capacity, led by natural gas; about 90 data-center projects (25 operating and 8 under construction); and about 370 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 Maricopa County
About 1.8 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:
| Field | Coverage | Share |
|---|---|---|
| Situs address | Most · 94% | |
| Owner name | Nearly all · 100% | |
| Assessed or market value | Nearly all · 99% | |
| Year built | Most · 88% | |
| Building size | Nearly all · 99% | |
| Last sale | Many · 51% | |
| Land use | Nearly all · 100% | |
| 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. 100% of Maricopa County records carry an owner name.
Infrastructure in and around Maricopa County
Power plants
About 70 operable plants with about 22,000 MW of nameplate capacity; largest by capacity: natural gas, battery and pumped storage, nuclear. Proposed generators add about 6,700 MW.
Within 50 km: /v1/lookup section power; details: /v1/records/{id}
Substations and transmission
About 370 in-service substations, about 65 rated 230 kV or higher.
About 3,300 miles of transmission lines: about 1,000 mi at under 100 kV; about 80 mi at 100–161 kV; about 1,100 mi at 220–287 kV; about 220 mi at 345 kV; about 560 mi at 500 kV.
Water and sewer service
Service areas of about 110 community water systems cover about 18% of the county.
Sewer service areas of about 20 systems cover about 10%.
At an address or point: /v1/lookup section utilities
Data-center projects
About 90 tracked projects: 25 operating, 8 under construction, 4 permitted, 8 proposed, 40 status not reported. Reported operating capacity: about 1,100 MW. Reported planned capacity: about 7,800 MW.
Within 10 km: /v1/lookup section datacenters
Flood zones and wetlands
Special flood hazard areas cover about 8% 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 370 miles of active rail, about 240 of it main line
- About 250 miles of national freight network highway
- 1 intermodal rail terminal
Within 25 km: /v1/lookup section logistics
Example requests for Maricopa 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 1313 E WELDON AVE, PHOENIX, AZ 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":"1313 E WELDON AVE, PHOENIX, AZ","sections":["datacenters"]}' \
https://api.korzy.co/v1/lookupPython
import os
import requests
response = requests.post(
"https://api.korzy.co/v1/lookup",
json={"address": "1313 E WELDON AVE, PHOENIX, AZ", "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": -112.054674675,
"latitude": 33.4899271,
"address": "1313 E WELDON AVE, PHOENIX",
"match_type": "exact"
},
"parcels": {
"records": [
{
"id": "04013-20171eae6364700d2e59",
"korzy_id": "04013-20171eae6364700d2e59",
"parcelid": "118-08-093",
"parceladdr": "1313 E WELDON AVE",
"parcelcity": "PHOENIX",
"situs_zip": "85014",
"statefp": "04",
"geoid": "04013",
"longitude": -112.054674675,
"latitude": 33.4899271,
"usedesc": "COMMERCIAL",
"land_use_code": "0325",
"yearbuilt": 1964,
"bldgsqft": 6249,
"taxacres": 6249,
"land_value_usd": 79400,
"improvement_value_usd": 317700,
"assessed_value_usd": 39710,
"market_value_usd": 397100,
"saledate": "2022-06-01",
"saleamt": 470000,
"updated": "2026-11-02"
}
],
"truncated": false
},
"sections": {
"datacenters": {
"status": "ok",
"data": {
"radius_km": 10,
"projects": [
{
"id": "datacenter:dc_7cf2e0c6ea3ec1ab5294",
"project_id": "dc_7cf2e0c6ea3ec1ab5294",
"name": "Unnamed data center",
"status": "unknown",
"state": "AZ",
"city": "Phoenix",
"address": "4010 North 3rd Street",
"longitude": -112.07054970780842,
"latitude": 33.49329025,
"location_precision": "footprint",
"source_count": 2,
"source_date": "2026-02-09",
"mapped": true,
"distance_km": 1.5188957444325144
},
{
"id": "datacenter:dc_7bfc06d9b7762557b6fd",
"project_id": "dc_7bfc06d9b7762557b6fd",
"name": "Lumen Phoenix 1",
"operator": "Lumen Technologies",
"status": "operating",
"state": "AZ",
"city": "Phoenix",
"address": "215 East Indian School Road",
"longitude": -112.0707915825171,
"latitude": 33.49435245,
"location_precision": "footprint",
"source_count": 3,
"source_date": "2026-07-23",
"mapped": true,
"distance_km": 1.5734830780631006
},
{
"id": "datacenter:dc_02af34dd705b24b90469",
"project_id": "dc_02af34dd705b24b90469",
"name": "QTS",
"operator": "Quality Technology Services",
"status": "unknown",
"state": "AZ",
"longitude": -111.99756037068683,
"latitude": 33.4647281,
"location_precision": "footprint",
"source_count": 2,
"source_date": "2026-02-09",
"mapped": true,
"distance_km": 5.9926724746724505
}
],
"truncated": true,
"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 04013-20171eae6364700d2e59, 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":"04013-20171eae6364700d2e59"}],"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/04013-20171eae6364700d2e59JavaScript
const response = await fetch(`https://api.korzy.co/v1/records/${encodeURIComponent("04013-20171eae6364700d2e59")}`, {
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);Maricopa County data questions
- How many parcels in Maricopa County include year built?
- About 1.6 million of about 1.8 million parcel records (88%) include year built.
- Does the Korzy API return owner names for Maricopa County parcels?
- Yes. 100% of Maricopa 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 Maricopa County?
- Korzy tracks about 90 data-center projects in Maricopa County: 40 status not reported, 25 operating and 8 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 Maricopa County?
- About 70 operable power plants in Maricopa County total about 22,000 MW of nameplate capacity, mainly natural gas, battery and pumped storage and nuclear.
- Which water systems serve Maricopa County?
- Service areas of about 110 community water systems cover about 18% of Maricopa County, and sewer service areas cover about 10%. A /v1/lookup with the utilities section returns the water and sewer matches at an address or point.
More featured counties
- Pima County, AZBorders Maricopa County · about 450,000 parcels
- Pinal County, AZBorders Maricopa County · about 280,000 parcels
Build on Maricopa 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.