Find Sites
find_sitesIdentify candidate data center search areas by substation voltage and nearby gas or fiber distance, using a state or lat/lon center when no site coordinates exist yet.
Instructions
Use this when the user has no data center site yet and wants candidate search areas (site selection by substation voltage, gas and fiber distance); execute_plan covers a multi-part siting question. THE INVERSE QUERY: every other DC Hub siting tool needs a coordinate you already have — analyze_site scores one, get_composite_site_score grades one, rank_sites orders candidates YOU already enriched, find_alternatives needs a seed facility. This one answers "where should I even be looking?". Returns candidate SEARCH AREAS anchored on real HIFLD substations at or above min_voltage_kv, spatially de-duplicated by cluster_km so a dense metro yields distinct areas instead of 40 near-identical rows, each carrying measured distance to the nearest gas pipeline and fiber route plus state-grain moratorium context, and a next_calls handoff. Answers "where should I even be looking for 200 MW in Ohio" and "which areas near Dallas sit on 230kV with gas within 5 miles". Try: find_sites state=OH min_voltage_kv=230 max_gas_km=8 — or find_sites lat=39.04 lon=-77.48 radius_km=60 min_voltage_kv=500.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| lat | No | Latitude of a search centre, e.g. 39.04 — use with lon (+ radius_km) instead of state | |
| lng | No | Alias for lon — either name works | |
| lon | No | Longitude of a search centre, e.g. -77.48 | |
| limit | No | Max results to return (1-500; default varies by tool) | |
| state | No | 2-letter US state to search, e.g. OH — required unless you pass lat + lon | |
| latitude | No | Alias for lat — either name works | |
| longitude | No | Alias for lon — either name works | |
| radius_km | No | Search radius in km around lat/lon (default 80, clamped 5-400); ignored in state mode | |
| cluster_km | No | Collapse anchors within this many km into one candidate area (default 8, max 100). Raise it for broader coverage, lower it for denser results | |
| max_gas_km | No | Drop candidates farther than this from the nearest gas pipeline. Applied ONLY if the gas layer answers — check constraint_coverage | |
| max_fiber_km | No | Drop candidates farther than this from the nearest fiber route (CHORD approximation — see fiber_distance_basis). Applied ONLY if the fiber layer answers | |
| min_voltage_kv | No | Only anchor on substations at or above this voltage in kV (default 115). 230+ for hyperscale, 500 for the largest campuses | |
| exclude_moratorium | No | true = drop candidates in a state with a published data-center moratorium. STATE grain, not jurisdiction grain |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||