Data center site selection data: parcels, power and projects
Data center site selection starts with the land. Check, at each candidate parcel, which projects are already planned nearby, where the power is and how the site connects to water, rail and highways.
Data center site selection: the job to be done
Site selection teams and the brokers, developers and utilities who work with them compare dozens of parcels before a single one gets an engineering study. For each one they need the parcel itself, the data-center projects already proposed, permitted or operating around it, and the generation and transmission context that decides whether power is realistic.
Korzy answers those questions at a point or a parcel ID, so a screening script or an AI agent can run the same checks across a whole list of candidates.
Questions Korzy answers for data center site selection
- Which data-center projects are within 10 km, and what stage is each at: proposed, permitted, under construction, operating or cancelled?
- What capacity has a nearby project reported, and as of when?
- Which power plants and generators are in the area, and what is the regional transfer capability?
- Is the parcel inside a mapped water and sewer service area? How close are rail lines and freight corridors?
API routes and MCP tools for data center site selection
Each lookup is a REST route and, where named, a tool on the Korzy MCP server. Routes link to their section of the API reference; credits and rate limits covers what each request costs.
| MCP tool | REST route | What it returns |
|---|---|---|
get_site_context | /api/datacenters/context | Data-center projects within 10 km of a point, nearest first, with status and reported capacity. |
get_data_center | /api/datacenters/projects/{project_id} | One project with dated capacity evidence and its timeline. |
get_power_plant | /api/power/plants/{plant_id} | A power plant and its generators, with nameplate capacity. |
get_transfer_capacity | /api/grid/transfers | Regional interface transfer capability for a date and market. |
get_logistics_context | /api/logistics/context | Rail lines, crossings, freight corridors and ports within 25 km. |
search_parcels | /api/search | The parcel at an address, with its korzy_id, land use, acreage and values. |
Example requests and production responses
Real responses from the production API, captured November 5, 2026 and trimmed to the main fields. Every request needs an API key; see API authentication.
1. Data-center projects near a candidate site
Projects within 10 km of 606 Cassville Rd, Cartersville, Georgia, nearest first. 1 credit per 10 records requested.
curl --fail-with-body -sS --get \
-H "Authorization: Bearer $KORZY_API_KEY" \
--data-urlencode 'longitude=-84.826966' \
--data-urlencode 'latitude=34.197397' \
--data-urlencode 'radius_km=10' \
--data-urlencode 'limit=5' \
https://api.korzy.co/api/datacenters/contextResponse (trimmed)
{
"projects": [
{
"project_id": "dc_1767dd571cfa7ce1f285",
"name": "DataBank Project Indo",
"operator": "DataBank",
"status": "proposed",
"state": "GA",
"city": "Cartersville",
"address": "",
"longitude": -84.7996,
"latitude": 34.1651,
"location_precision": "exact",
"planned_mw": 200,
"distance_km": 4.385679537550114
},
{
"project_id": "dc_ffe867c31f4843497f58",
"name": "Atlas Development Stiles Road Data Center (Euharlee Road)",
"operator": "Atlas Development LLC",
"status": "cancelled",
"state": "GA",
"city": "Cartersville",
"address": "208 and 329 Stiles Road SW",
"longitude": -84.89,
"latitude": 34.1354,
"location_precision": "approximate",
"distance_km": 9.008701089317189
},
{
"project_id": "dc_3dcca9124f9e764bd039",
"name": "Oakley Real Estate Partners Brown Farm Road Data Center",
"operator": "Oakley Real Estate Partners",
"status": "proposed",
"state": "GA",
"city": "Cartersville",
"address": "Brown Farm Road SW (west end)",
"longitude": -84.8698,
"latitude": 34.1181,
"location_precision": "approximate",
"distance_km": 9.658210117856397
}
],
"radius_km": 10,
"limit": 5,
"truncated": false
}2. Rail and freight access from the same point
Nearby rail lines, crossings and freight corridors within 25 km, one record per layer shown. 1 credit per 10 records requested.
curl --fail-with-body -sS --get \
-H "Authorization: Bearer $KORZY_API_KEY" \
--data-urlencode 'longitude=-84.826966' \
--data-urlencode 'latitude=34.197397' \
--data-urlencode 'radius_km=25' \
--data-urlencode 'limit=2' \
https://api.korzy.co/api/logistics/contextResponse (trimmed)
{
"longitude": -84.826966,
"latitude": 34.197397,
"radius_km": 25,
"limit": 2,
"nearby": {
"rail_lines": [
{
"feature_id": "rail_lines:records:290771",
"name": "W&A",
"status": "M",
"state": "GA",
"category": "M",
"boundary_basis": "Published source feature",
"railroad_parties": "CSXT",
"distance_km": 0.20835828364602418,
"geometry_kind": "line"
}
],
"rail_crossings": [
{
"feature_id": "rail_crossings:records:38706",
"name": "IRON BELT ROAD",
"operator": "GEORGIA",
"state": "GA",
"city": "CARTERSVILLE",
"category": "Public",
"boundary_basis": "Published source feature",
"distance_km": 0.6191833061525501,
"geometry_kind": "point"
}
],
"freight_corridors": [
{
"feature_id": "freight_corridors:records:5622",
"name": "I75",
"state": "GA",
"category": "1",
"boundary_basis": "Published source feature",
"distance_km": 5.611037039742042,
"geometry_kind": "line"
}
],
"roads": [
{
"feature_id": "roads:fhwa2024:row-3ji4.hbrt.y79x",
"name": "Cassville Rd;",
"state": "GA",
"category": "Minor arterial",
"distance_km": 0.13966242738112242,
"geometry_kind": "line"
}
]
}
}County parcel data for data center site selection
Parcel coverage, infrastructure counts and example requests for counties where this work is common. Korzy covers parcel data in every U.S. county.
How Korzy compares with other parcel data APIs
More Korzy use cases
Screen your next data-center site
Every plan includes the data-center, power, utilities and logistics routes, through the API and the MCP server.