Analyze Site
analyze_siteRead-onlyIdempotent
Score a specific site or market for data center suitability. Returns a 0-100 composite, verdict, power/gas/fiber/risk sub-scores, nearby infrastructure and power cost.
Instructions
Use this whenever the user asks whether a specific site or coordinate works for a data center. Call when the user has one location (lat/lon, or a market name for a market-level read) and asks if it suits a data center. Returns a 0-100 composite, verdict, power/gas/fiber/market/risk sub-scores, nearby infrastructure and power cost; capacity_mw adds a capacity_context block and does NOT move overall_score. Keyless returns the verdict band and weakest factor; a free key adds factor bands and substation distance bands; scores and figures are Pro. Ex: "Score 33.45,-112.07 for 100 MW."
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| lat | No | Site latitude in decimal degrees (-90 to 90; required unless candidate_id or location given), e.g. 33.45 | |
| lng | No | Alias for lon — either name works | |
| lon | No | Site longitude in decimal degrees (-180 to 180; required unless candidate_id or location given), e.g. -112.07 | |
| state | No | US state abbreviation (optional) — improves the tax-incentive lookup, e.g. AZ | |
| latitude | No | Alias for lat — either name works | |
| location | No | Market NAME or metro slug instead of coordinates, e.g. "ashburn", "northern-virginia", "dallas". Resolved to that market's PUBLISHED CENTROID through the DCPI market row, and the answer carries a resolved_from block saying so. This is a MARKET-level read, not the parcel you named — pass lat/lon for a specific site. Not an alias for lat/lon: a place name is not a coordinate. | |
| longitude | No | Alias for lon — either name works | |
| capacity_mw | No | Target power load for the build in megawatts (MW), e.g. 100 (typical 50-500) | |
| candidate_id | No | PREFERRED for queue survivors: a cand_… id from get_refined_queue — coordinates come from the FROZEN mint (lat/lon args are ignored; zero transcription drift; expired ids fail closed with candidate_expired). See dchub.cloud/docs/candidate-lifecycle | |
| include_grid | No | Include grid-headroom / substation analysis (default true) | |
| include_risk | No | Include water/drought/climate risk analysis (default true) | |
| include_fiber | No | Include fiber-connectivity analysis (default true) |
Output Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| fiber | No | Fiber read: {connectivity_score, nearest_carrier_km, near_net_bucket, top_carriers[], single_carrier_risk} (full payload) | |
| quota | No | Caller quota state (remaining calls, tier) when available. | |
| locked | No | Which sections are Pro-locked on the free headline: {per_factor_breakdown, nearby_infrastructure, power_cost, fiber_carriers, site_analysis_report} | |
| nearby | No | Nearby infrastructure counts: {substations_50km, power_plants_80km, gas_pipelines_50km, facilities_100km, fiber_carriers_in_state, generation_capacity_mw, total_capacity_mw} (full payload) | |
| scores | No | Per-factor breakdown (full/paid payload) | |
| _entity | No | Payload class discriminator (e.g. facility|market|iso_grid|queue_results|deal|report|response) — branch on this before parsing the rest. | |
| preview | No | Headline preview line (free tier) | |
| verdict | No | Verdict string, e.g. "Excellent site" / BUILD-CAUTION-AVOID read | |
| citation | No | Machine-readable citation: how to attribute DC Hub (dchub.cloud) for this payload. Normally an OBJECT {source, url, license, cite_as, retrieved_at}; a bare string is accepted and carries the attribution line itself. | |
| location | No | Echo of the analyzed location (full payload) | |
| power_cost | No | Power cost read: {industrial_cents_kwh, commercial_cents_kwh, period, basis} (full payload) | |
| provenance | No | Collection-level provenance block: {source, method, as_of, verification_counts, cite_url_template, license, cite_as}. Quote the verification level when citing. | |
| _front_door | No | In-band front-door hint (first workflow-entry tool of a session): call plan_query(intent) first for the ordered multi-step plan. | |
| _return_loop | No | Suggested next-session delta call (get_changes since=24h) so you pull only what changed. | |
| overall_score | No | Alias of composite_score on the full payload | |
| site_headline | No | true when this is the free citable HEADLINE (score + verdict + limiting factor) | |
| interpretation | No | Verdict prose on the full payload | |
| composite_score | No | 0-100 composite site suitability score (free HEADLINE tier and full tier) | |
| limiting_factor | No | Single top limiting factor (the lowest sub-score) — always present on the free headline | |
| site_evaluation_handoff | No | Pre-built follow-up calls (analyze_site / get_water_risk args) when the payload carries coordinates — an array of {tool, parameters, why} entries. |