analyze_site

Use this when the user asks whether one site suits a data center. Pass lat and lon, a candidate_id from get_refined_queue, or a market name as location; capacity_mw and state refine it. Returns a 0-100 score with power, gas, fiber, market and risk sub-scores. Example: lat=33.45 lon=-112.07. Full results need a paid DC Hub key.

read-only

Argument	Type	Description
lat	number	Site latitude in decimal degrees (-90 to 90; required unless candidate_id or location given), e.g. 33.45
lng	number	Alias for lon — either name works
lon	number	Site longitude in decimal degrees (-180 to 180; required unless candidate_id or location given), e.g. -112.07
state	string	US state abbreviation (optional) — improves the tax-incentive lookup, e.g. AZ
mpp_pay	boolean	Per-call payment quote (Stripe MPP): true returns a signed payment challenge instead of the free preview; no money moves. Set it only after your human has explicitly approved paying for this call.
latitude	number	Alias for lat — either name works
location	string	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.
longitude	number	Alias for lon — either name works
capacity_mw	number	Target power load for the build in megawatts (MW), e.g. 100 (typical 50-500)
candidate_id	string	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).
include_grid	boolean	Include grid-headroom / substation analysis (default true)
include_risk	boolean	Include water/drought/climate risk analysis (default true)
include_fiber	boolean	Include fiber-connectivity analysis (default true)
mpp_credential	string	Per-call payment (Stripe MPP): the Shared Payment Token for challenges[0]; pays that challenge for this one call. Send it only with your human's explicit approval of the charge.

Input schema (JSON)

{
  "type": "object",
  "properties": {
    "lat": {
      "type": "number",
      "description": "Site latitude in decimal degrees (-90 to 90; required unless candidate_id or location given), e.g. 33.45"
    },
    "lng": {
      "type": "number",
      "description": "Alias for lon — either name works"
    },
    "lon": {
      "type": "number",
      "description": "Site longitude in decimal degrees (-180 to 180; required unless candidate_id or location given), e.g. -112.07"
    },
    "state": {
      "type": "string",
      "description": "US state abbreviation (optional) — improves the tax-incentive lookup, e.g. AZ"
    },
    "mpp_pay": {
      "type": "boolean",
      "description": "Per-call payment quote (Stripe MPP): true returns a signed payment challenge instead of the free preview; no money moves. Set it only after your human has explicitly approved paying for this call."
    },
    "latitude": {
      "type": "number",
      "description": "Alias for lat — either name works"
    },
    "location": {
      "type": "string",
      "description": "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."
    },
    "longitude": {
      "type": "number",
      "description": "Alias for lon — either name works"
    },
    "capacity_mw": {
      "type": "number",
      "description": "Target power load for the build in megawatts (MW), e.g. 100 (typical 50-500)"
    },
    "candidate_id": {
      "type": "string",
      "description": "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)."
    },
    "include_grid": {
      "type": "boolean",
      "description": "Include grid-headroom / substation analysis (default true)"
    },
    "include_risk": {
      "type": "boolean",
      "description": "Include water/drought/climate risk analysis (default true)"
    },
    "include_fiber": {
      "type": "boolean",
      "description": "Include fiber-connectivity analysis (default true)"
    },
    "mpp_credential": {
      "type": "string",
      "description": "Per-call payment (Stripe MPP): the Shared Payment Token for challenges[0]; pays that challenge for this one call. Send it only with your human's explicit approval of the charge."
    }
  }
}

discover_tools

Use this when you are unsure which DC Hub tool fits: the full catalogue by family (facility, market, grid and power, gas, site, fiber, deals and news, saved work, account), optionally filtered by query. Every DC Hub tool can be called by name here.

read-only

Argument	Type	Description
query	string	Optional keyword to filter families/tools, e.g. "site selection", "grid queue", "fiber", "deals", "market"

Input schema (JSON)

{
  "type": "object",
  "properties": {
    "query": {
      "type": "string",
      "description": "Optional keyword to filter families/tools, e.g. \"site selection\", \"grid queue\", \"fiber\", \"deals\", \"market\""
    }
  }
}

execute_plan

Use this when a data center question spans several topics: markets and the Data Center Power Index (DCPI), grid power and headroom, interconnection queues, fiber, water and climate risk, tax incentives, deals. Pass the user's question as intent. A rule-based planner (no AI model) picks the lookups, runs them and returns each step's result with a replay of how the answer was built.

read-only

Argument	Type	Description
iso	string	ISO/RTO code to pin geography, e.g. "PJM", "ERCOT".
lat	number	Latitude for a specific site.
lon	number	Longitude for a specific site.
state	string	US state code, e.g. "VA".
cohort	any	Optional experiment tag for adoption/retention measurement, e.g. "cohort.front_door". Has NO effect on routing, planning, geography or results — it is recorded only.
intent*	string	The user's infrastructure question, passed through UNCHANGED. Examples: "rank markets for a 200 MW AI campus" · "evaluate 100 MW power headroom for a GPU training cluster in PJM" · "compare Dallas vs Phoenix for a hyperscale campus" ·…
market	string	Metro slug or name to pin the analysis to, e.g. "ashburn". Beats any market the planner would mint.

get_changes

Use this when the user asks what changed since a date: DCPI 7-day market movers, new data center facilities, M&A deals and news; keyed callers with saved sites also get per-site changes. Pass since as ISO-8601 or "24h" / "7d" (default 24h) and pass the response's generated_at back next time. Keyless calls return a preview.

read-only

Argument	Type	Description
limit	integer	Max results to return (1-500; default varies by tool)
since	string	Return changes since this ISO-8601 timestamp (YYYY-MM-DD or full datetime) or shorthand "24h"/"7d"; default 24h

Input schema (JSON)

{
  "type": "object",
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 500,
      "minimum": 1,
      "description": "Max results to return (1-500; default varies by tool)"
    },
    "since": {
      "type": "string",
      "description": "Return changes since this ISO-8601 timestamp (YYYY-MM-DD or full datetime) or shorthand \"24h\"/\"7d\"; default 24h"
    }
  }
}

get_grid_intelligence

Use this when the user asks about grid capacity or time to power in one grid: "can I get N MW in this ISO, and how long will it take?". region_id is PJM, ERCOT, CAISO, MISO, SPP, NYISO, ISO-NE, or a US balancing authority. Supply-side signals, not a promise that a load can connect. Full results need a paid DC Hub key.

read-only

Argument	Type	Description
iso	string	Alias for region_id — the ISO/RTO or balancing-authority code
market	string	Market NAME or metro slug instead of a grid code, e.g. "Ashburn", "northern-virginia", "dallas". Resolved to its ISO through the published DCPI market row before the brief is built; the answer carries a resolved_from block naming what it…
region	string	Alias for region_id — the ISO/RTO or balancing-authority code
mpp_pay	boolean	Per-call payment quote (Stripe MPP): true returns a signed payment challenge instead of the free preview; no money moves. Set it only after your human has explicitly approved paying for this call.
region_id	string	Grid region (required): one of the 7 US ISOs (PJM, ERCOT, CAISO, MISO, SPP, NYISO, ISO-NE), an EIA balancing-authority code (e.g.
mpp_credential	string	Per-call payment (Stripe MPP): the Shared Payment Token for challenges[0]; pays that challenge for this one call. Send it only with your human's explicit approval of the charge.

get_grid_scoreboard

Use this when the user asks how power grids compare right now: US operators (PJM, ERCOT, CAISO, MISO, SPP, NYISO, ISO-NE, BPA, TVA), Great Britain, European bidding zones, Taiwan, Japan, South Korea and Brazil, ranked on each feed's latest reading: renewable share, gas share, fuel mix in MW and demand. Freshness differs by feed: read each row's mix_age_hours. No arguments. Full guide: read resource dchub://tool-guides/get_grid_scoreboard

read-only

No arguments.

Input schema (JSON)

{
  "type": "object",
  "properties": {}
}

get_hosting_capacity

Use this when the user asks how many MW a distribution feeder can take: utility-published hosting capacity (named utilities in the Northeast, Mid-Atlantic and Midwest, not nationwide). Call with lat and lon (radius_km, default 25), a utility or market, or no arguments for the covered markets. Check capacity_type before quoting; count distinct_feeders, not rows.

read-only

Argument	Type	Description
lat	number	Latitude of the point to search around, decimal degrees. Must be paired with lon.
lng	number	Alias for lon — either name works
lon	number	Longitude of the point to search around, decimal degrees. Must be paired with lat.
limit	integer	Max results to return (1-500; default varies by tool)
market	string	Alias for utility — either name works (e.g. "Northern Virginia · Richmond", "New York City · Westchester").
min_mw	number	Only return feeders whose published capacity is at or above this many MW.
utility	string	Utility or market name, case-insensitive substring — e.g. "Ameren Illinois", "Con Edison", "Providence". Searches that utility's whole published territory instead of a point radius. Call with NO arguments to list every covered utility.

get_market_dcpi_rank

Use this when the user asks where a data center can get grid power, how fast, or whether a market is a BUILD, CAUTION or AVOID (e.g. "Where can a 100 MW data center get power fastest?"): DCPI scores 300+ markets daily on Excess Power and Grid Constraint, CC BY 4.0. DCPI rank for one market: BUILD/CAUTION/AVOID verdict, 0-100 composite_score (verdict-aware), excess_power_score, constraint_score, time_to_power_months. INCLUDES a `narrative` block with a ~100-word analyst read on the market, quote it directly with attribution to DC Hub (CC-BY-4.0). Keyless calls return a preview.

read-only

Argument	Type	Description
market_slug*	string	Market slug (metro), e.g. northern-virginia, dallas, phoenix — valid slugs come from rank_markets / get_market_dcpi_rank

Input schema (JSON)

{
  "type": "object",
  "required": [
    "market_slug"
  ],
  "properties": {
    "market_slug": {
      "type": "string",
      "description": "Market slug (metro), e.g. northern-virginia, dallas, phoenix — valid slugs come from rank_markets / get_market_dcpi_rank"
    }
  }
}

get_power_availability_timeline

Use this when the user asks when power will be available (time to power) in a US state, year by year: new generation (EIA-860M, under construction, testing and planned kept apart), scheduled retirements, and interconnection-queue depth as context. Arguments: state (required), years, mw. Supply-side signals, not a promise that a load can connect.

read-only

Argument	Type	Description
mw	number	Optional target MW for CONTEXT ONLY — echoed back with an explicit note; never converted into an energize-by date, which this data cannot honestly state
state*	string	2-letter US state code (required), e.g. OH, GA, TX — the timeline grain; a state can span ISOs and the response reports ISO membership as context
years	number	Window in years from now, 1-6 (default 5)

Input schema (JSON)

{
  "type": "object",
  "required": [
    "state"
  ],
  "properties": {
    "mw": {
      "type": "number",
      "description": "Optional target MW for CONTEXT ONLY — echoed back with an explicit note; never converted into an energize-by date, which this data cannot honestly state"
    },
    "state": {
      "type": "string",
      "description": "2-letter US state code (required), e.g. OH, GA, TX — the timeline grain; a state can span ISOs and the response reports ISO membership as context"
    },
    "years": {
      "type": "number",
      "description": "Window in years from now, 1-6 (default 5)"
    }
  }
}

search_facilities

Use this when the user asks which data centers exist or who operates where: DC Hub's global data-center facility map (170+ countries) by text query, country, state, city, operator, or capacity range (min_capacity_mw, max_capacity_mw); limit and offset page. Returns name, provider, location and capacity. For power, fiber or risk context as well, execute_plan covers it. Keyless calls return a preview.

read-only

Argument	Type	Description
city	string	City name to filter facilities, e.g. Ashburn, Dallas
tier	integer	Uptime Institute tier filter (1-4)
limit	integer	Max results to return (1-500; default varies by tool)
query	string	Free-text search over facility name/operator/location (mapped to the backend `q` param), e.g. "hyperscale Ashburn"
state	string	US state abbreviation or region, e.g. VA, TX
offset	integer	Pagination offset, 0-based (skip this many results)
country	string	ISO 3166-1 alpha-2 country code, e.g. US, GB, SG
mpp_pay	boolean

source_capacity

Use this when the user needs data center or colocation capacity to buy or lease: DC Hub Capacity Source by size (min_kw or min_mw) and location (region, country, state, market). Size is matched against contiguous_kw (largest contiguous block) and min_contract_kw (smallest contractable chunk). Filters: delivery_type, available_by. Returns listing teasers.

read-only

Argument	Type	Description
slug	any	One listing: its slug or numeric id exactly as items[].slug / items[].id return it. Omit to browse teaser cards
limit	integer	Max results to return (1-500; default varies by tool)
state	string	Browse filter: two-letter US state, e.g. "TX"
market	string	Browse filter: market name as it appears on a listing, e.g. "Dallas"
min_kw	number	Browse filter: the size your human needs, in kW (min_mw is the same filter in MW). Matched against what a listing can ACTUALLY deliver, not just its headline total: contiguous_kw is the largest single contiguous block available and…
min_mw	number	Browse filter: the size your human needs, in MW (min_kw is the same filter in kW). Matched against what a listing can ACTUALLY deliver, not just its headline total: contiguous_kw is the largest single contiguous block available and…

DC Hub — Data Center Energy, Electricity & Power Grid Data: Site Selection, Colocation, Gas, Fiber

Try it

analyze_site

DC Hub — Data Center Energy, Electricity & Power Grid Data: Site Selection, Colocation, Gas, Fiber

Try it

analyze_site

Tools (11)