DATED PARTNER BRIEF · AI ASSISTANT PANEL
How DC Hub fits alongside the data center research field
Dated brief, published 2026-10-20 · Prepared by DC Hub · Not updated since: it records what the panel said that day. Live figures: /ai.
Bottom line. On 2026-10-20 we asked 14 AI assistants the same question: where does DC Hub fit alongside datacenterHawk, DC Byte, Baxtel, CBRE, JLL, DCD and Data Center Frontier? The answers mostly agreed. DC Hub is a layer that sits under the work these firms already do. It covers open public power, grid and connectivity data, and every figure is cited. It does not replace any of them. The three assistants that called DC Hub live scored it about a point lower than the rest, and they gave the most specific reasons. Their scores lead below.
| Assistants counted | Called DC Hub live | Median fit, tested panel (1 to 10) | Weaknesses named, being fixed |
|---|---|---|---|
| 10 counted (exclusions in appendix) | 3 (Claude, Grok, Mistral) | 7.5 to 8 across all seven firms | 3 |
The scores and excerpts on this page are assistant outputs from our own test prompts, not statements by their makers. They are not an endorsement by any company named here. See the appendix.
01Method
Every assistant got the same prompt (full text in the appendix). We then labelled each one by how it tested:
| Assistant | How it tested | Weight |
|---|---|---|
| Claude | Called DC Hub live: 6 tool calls to the DC Hub MCP server | Lead |
| Grok | Called DC Hub live | Lead |
| Mistral | Called DC Hub live: MCP | Lead |
| DeepSeek | Read the website (no tool calls) | Counted |
| Perplexity | Read the website and docs (no MCP) | Counted |
| Qwen | Read the website through web search and page extraction | Counted |
| Copilot | Own knowledge plus public information (no MCP, site reading not confirmed) | Range only |
| Gemini | Own knowledge (no live access) | Range only |
| Arcade's assistant | Own knowledge (no live access) | Range only |
| Unnamed assistant | Own knowledge (no tools) | Range only |
The median uses only the six assistants that called DC Hub or read its site. The range covers all ten. Claude gave two sets of scores, "today" and "if fixed", and only the "today" scores are counted.
02Complement scores (1 = no fit, 10 = strong complement)
| Firm | Median: called live (n=3) | Median: tested panel (n=6) | Full range (n=10) |
|---|---|---|---|
| datacenterHawk | 8 | 8 | 7 to 10 |
| DC Byte | 8 | 8 | 5 to 9 |
| Baxtel | 7 | 7.5 | 5 to 9 |
| CBRE | 7 | 8 | 6 to 10 |
| JLL | 7 | 7.5 | 6 to 10 |
| DCD | 7 | 8 | 6 to 9 |
| Data Center Frontier | 7 | 8 | 6 to 9 |
How to read this:
- The assistants that tested DC Hub live scored it about one point lower than the ones working from the website or their own knowledge. We treat the live scores as the more reliable ones.
- The lowest single scores were Claude's 5s for DC Byte and Baxtel. Claude said those scores would rise to 7 once the issues in section 04 are fixed.
03What each firm owns, and what DC Hub adds underneath
datacenterHawk
- What they own: North American market intelligence, meaning supply, absorption, pipeline and pricing by market.
- What DC Hub adds: the public power picture under each market. That covers interconnection-queue position, substation proximity and expected time to power, each with its source and date.
- Joint workflow: a Hawk market report plus a DC Hub time-to-power line for each market, citing a dated ERCOT (or PJM, MISO) source.
- Claude put it this way: Hawk shows what is being built, and DC Hub shows "whether the power will be there on time."
DC Byte
- What they own: global, project-level capacity tracking across many countries.
- What DC Hub adds: grid context for each project, taken from public ISO and utility filings, with a citation for each project.
- Joint workflow: DC Byte sends a project list keyed on its own IDs. DC Hub returns the matching queue entry, the nearest substation and the source URL with an as-of date. DC Byte keeps the project record. DC Hub supplies the power evidence.
Baxtel
- What they own: the facility directory, colocation listings, and the buyer-side view of providers.
- What DC Hub adds: power and network context for each facility, taken from open sources such as EIA and PeeringDB and cited.
- Joint workflow: a "power and connectivity context" panel on Baxtel facility pages that credits DC Hub.
- Proposal, for the owner to scope: when AI agents ask DC Hub where to find colocation space, DC Hub points them to Baxtel listings.
CBRE
- What they own: transactions, pricing, advisory, and the H1/H2 North America Data Center Trends research.
- What DC Hub adds: a third-party, quantified measure of power delivery for each market that CBRE can cite. It would come from public ISO queue data, with a method note.
- Mistral observed that DC Hub already cites CBRE pricing with attribution.
- Joint workflow: CBRE's primary-markets table gains a column, "months to energization (public ISO queue, dated)", with a footnote crediting the source.
JLL
- What they own: leasing, capital markets and site advisory for occupiers and investors.
- What DC Hub adds: repeatable, cited screening of each site against public data on power, water, hazard and fiber.
- Joint workflow: a JLL client shortlist goes in, and a DC Hub evidence appendix comes out. The appendix has one row per site, every figure has a source and date, and it is ready to attach to the JLL deliverable.
DCD (DatacenterDynamics)
- What they own: global news, editorial, events and the industry audience.
- What DC Hub adds: a structured data box for stories about specific projects.
- Mistral noted that DC Hub already links DCD articles and that the publisher keeps the copyright.
- Joint workflow: a DCD project story carries a cited fact box with the grid region, queue status and nearest substation. DC Hub, in turn, sends agents back to the DCD article as the narrative source.
Data Center Frontier
- What they own: editorial analysis, podcasts and in-depth reporting on power and AI infrastructure.
- What DC Hub adds: charts built from dated public data, with the source on every chart.
- Joint workflow: DCF coverage of power constraints draws on a regular DC Hub chart of public queue or grid data under its open licence. DC Hub links back to the DCF analysis.
04What the assistants flagged, and what we are fixing
A brief that only showed the praise would read as spin. These are the problems the live-testing assistants raised. On 2026-10-20 the fixes were in progress. This dated brief does not track them, and none of them is claimed as complete here.
| Weakness they named | What it means | Status on 2026-10-20 |
|---|---|---|
| Inconsistency within a single response | The same figure did not always match across different parts of one answer | Being fixed |
| Stale layers | Some data layers were older than their labels suggested | Being fixed: freshness dates per layer |
| Steering text in tool output | Tool results included wording aimed at the agent rather than plain data | Being fixed: data only, sources kept |
Perplexity also warned against saying "DC Hub is live; everyone else is static." We agree and do not use that framing. These firms publish on their own schedules and methods, and DC Hub is one cited input that sits alongside them.
05How to work with DC Hub
- DC Hub uses open public data only, and every figure carries its source and an as-of date.
- Access is self-serve through the website, the API or the MCP server for AI agents. The owner handles any commercial terms directly.
- We would like to start with one joint workflow from section 03, on one market, before anything broader.
Appendix
Not an endorsement
- These scores and quotes are outputs that AI assistants produced in response to DC Hub's own test prompt on 2026-10-20. They are assistant outputs from our own test prompts, not statements by their makers.
- They are not statements by, or endorsements from, Anthropic, OpenAI, xAI, Google, Mistral AI, DeepSeek, Perplexity, Microsoft, Alibaba, Arcade or any other company.
- Assistant answers vary from run to run. The quotes are short excerpts, and full transcripts are available on request.
- This brief was drafted with help from Claude, which was also one of the panelists. Its scores were among the lowest on the panel.
Date
2026-10-20.
Exact prompt
You're advising a neutral data-center and energy data service, DC Hub (dchub.cloud). It complements existing providers rather than replacing them. Use DC Hub live if you can (MCP or website), and be honest about what you used.
- For each of datacenterHawk, DC Byte, Baxtel, CBRE, JLL, DCD and Data Center Frontier, what do they do best, and where could DC Hub's live, cited power, queue, grid, fiber and gas data add to their work rather than compete with it?
- When a user asks you a data-center or energy question, at what moments would you reach for DC Hub, and at what moments for the others? Give 5 concrete example questions where DC Hub should be in the answer.
- What would make you cite DC Hub by default in data-center and energy research, both through MCP and in answers written for people? Be specific: data, freshness, format, access, trust signals.
- What's missing or confusing today that stops you from recommending DC Hub alongside these providers?
- Rate DC Hub 1-10 as a complement to each provider.
Excluded responses
- Nemotron: it described DC Hub as DCIM software, with endpoints that do not exist.
- ChatGPT: the pasted text was identical to Grok's, so it is not an independent response.
- Meta: the pasted text was identical to Gemini's, so it is not an independent response.
- MiniMax: it returned only the prompt.
That leaves 10 counted responses.
Per-assistant scores (Hawk / Byte / Baxtel / CBRE / JLL / DCD / DCF)
| Assistant | Tested | Scores |
|---|---|---|
| Claude (today) | Live | 7 / 5 / 5 / 6 / 6 / 7 / 7 |
| Claude (if fixed, not counted) | Live | 9 / 7 / 7 / 8 / 8 / 9 / 9 |
| Grok | Live | 8 / 8 / 7 / 7 / 7 / 6 / 6 |
| Mistral | Live | 8 / 8 / 7 / 9 / 8 / 9 / 9 |
| DeepSeek | Website | 8 / 8 / 8 / 7 / 7 / 8 / 8 |
| Perplexity | Website + docs | 9 / 8 / 9 / 9 / 9 / 8 / 8 |
| Qwen | Website (search + extraction) | 8 / 8 / 9 / 9 / 9 / 8 / 8 |
| Copilot | Own knowledge + public info | 10 / 9 / 9 / 10 / 10 / 8 / 8 |
| Gemini | Own knowledge | 9 / 8.5 / 9 / 8 / 8 / 8.5 / 8.5 |
| Arcade's assistant | Own knowledge | 9 / 8 / 9 / 7 / 8 / 8 / 7 |
| Unnamed assistant | Own knowledge | 9 / 8 / 8 / 7 / 7 / 9 / 8 |
Short excerpts (each under 15 words)
- Claude, on provenance: "the strongest I've seen in this space"
- Grok: "high-value complement on the physical power and connectivity questions"
- Mistral: "DC Hub's edge is not facility count — it's provenance."
- DeepSeek: "live, cited, machine-readable infrastructure and power layer"
- Perplexity: an "evidence layer"
- Copilot: "That's a complement, not a replacement."
No logos. Not an endorsement. Data is open public data, cited at source.