Partner with DC Hub
and make your own work sharper.
DC Hub is a neutral layer of public, cited data-center, power and grid data, refreshed daily. Brokers, publishers, operators and researchers can cite it, embed it and build on it beside their own research. We aggregate open public data and always name the upstream source, so using DC Hub never means handing over anything proprietary. Your research, deal flow and audience stay yours.
Brokers and advisors
Put a cited, dated power and queue figure next to your market view between report editions. Footnote DC Hub as a source; your research and deal flow stay yours.
Publishers and newsrooms
Embed a live market power card in a story or market page. Every card carries its as-of date and a source link, so readers can check the number themselves.
Operators and developers
Check a site's grid context (queue, substations, prices) against your own diligence, and show investors and lenders where each figure came from.
Researchers and analysts
Use the Data Center Power Index (DCPI) under CC BY 4.0 in reports and appendices, with each market's signal tier and input basis disclosed.
01Cite it
One citation format for every DC Hub figure. Each figure carries its own as-of date and upstream source; cite the date you read it.
DC Hub (dchub.cloud), as of <date>DCPI verdicts and composite scores are licensed CC BY 4.0. Daily dataset: /api/v1/data/dcpi-markets/latest.json (also CSV). Grid and queue figures name their operator source on every row.
02Embed a live market power card
A small card for any fully sourced market: the DCPI verdict and composite score, the grid operator's queue figure with its source, the as-of date, the cite line and a "Data: DC Hub" credit link. It updates itself daily; there is nothing to maintain.
03Show your work: evidence receipts
Every card traces to an evidence receipt: one keyless GET that lists each component of the answer with its value, upstream source, as-of date and basis, and says plainly when a value is withheld or unavailable.
/api/v1/receipt/dcpi/ashburn · /api/v1/receipt/queue (every ISO queue figure)
04Methodology
How the index is built, what is live and what is modeled, and how each grid operator's queue is read.
- DCPI methodology (page) and the methodology one-pager (PDF)
- Machine-readable methodology (JSON)
- Data sources: every upstream feed, its licence and cadence
05Only fully sourced markets
A number you repeat under your own name has to hold up. Partner cards and the partner market list offer only markets where every DCPI input is live or labelled and the grid operator's queue figure is current.
fully_sourced = not on the partner hold list, a BUILD/CAUTION/AVOID verdict, signal_tier 'full' (all three live grid layers), every input labelled live or modeled with at least one live input, scored in the last 72 hours, and a non-stale queue snapshot for the market's grid operator. Partner embeds and receipts offer only fully sourced markets.
Held from partner surfaces after an analyst-grade audit: Batam, Johor, Pune, Querétaro. Their public pages still show the score with its input basis.
/api/v1/partners/markets
lists every market with its flag and the reasons; add ?fully_sourced=1 for the partner list.
One-market brief to hand a colleague or a client:
/partners/brief/<market-slug>, with an optional
?for=<recipient> line. It prints to a one or two page PDF, every figure with its source and
receipt, and exists only for fully sourced markets.
06Build on it
REST and datasets
Base https://dchub.cloud/api/v1, described in
openapi.json. Keyless previews work with no key at all.
MCP for agents and gateways
One endpoint, https://dchub.cloud/mcp. Building a
gateway or aggregator? Start at /mcp/builders: composition, rate limits,
attribution and keyless previews.
Attribution convention: add ?via=<your-name>
or the header X-DCHub-Via: <your-name> so traffic through your product is counted
separately from end-user clients. It does not change access or results.
07Get a partner key
- Email [email protected] with your organisation, what you want to build or publish, and the markets you care about.
- Name a dedicated service address for the key, for example [email protected]. Partner keys are issued to a dedicated address, never to a personal login.
- We issue the key and send the endpoints and attribution name to use. Until then, keyless previews and the embed card work without any key.
Talk to us
Corrections, data partnerships, co-cited notes or a market you need covered: [email protected]. Corrections are logged publicly.
DC Hub aggregates open, public data and cites every upstream source. Third-party names on this site belong to their owners; their mention implies no endorsement.