Compose DC Hub in your gateway
as the data-center and power upstream.

Your users ask about data centers, power, grid queues and sites. Route those questions to DC Hub and keep your own tools for everything else. 94 tools over one endpoint. Public, cited data; every answer carries its source and as-of date.

1. Connect

Tools gateways route to most often:

• execute_plan: a multi-part data-center, power or siting question, passed through unchanged
• get_market_intel: one market: power verdict, grid context, recent activity
• get_grid_data: live ISO grid conditions
• get_interconnection_queue: interconnection queue depth by ISO, dated to the operator file
• search_facilities: facilities by place, operator or size
• source_capacity: available capacity, powered land and colocation space
• summarize_for_citation: a figure with its source and as-of date, ready to quote

2. Keyless previews

Every tool answers without a key. Keyless answers are previews; a gated result carries human_url and human_message for your user. Show your user the human_message and its link when a result is partial; do not invent withheld numbers.

The published free-tier rule, verbatim: Anonymous: previews, no key needed. Free key: previews plus 2 full answers per tool per day. Add an email: 50 calls/day (up to 10 full answers per tool per day). Grid/queue/market-intel tools: previews on free; an email adds 10 full answers/day each. Siting: no email, previews; an email adds every find_sites candidate and 1 full site_selection_canvas and execute_plan each a month.

3. Rate limits behind a shared IP

• Keyless calls are counted per source IP. Requests you relay from many users share your IP, so use keyless calls to evaluate and a partner key for production traffic.
• A partner key carries its own allowance, agreed when it is issued, and is not tied to your IP.
• A capped call still returns a preview with a human_url; it is not an error. Do not retry in a loop.

4. Attribution: tell us it came through you

Add your name to the connector URL, or send it as a header. DC Hub then counts traffic that arrives through your product separately from end-user clients. It changes nothing in access or results.

https://dchub.cloud/mcp?via=<your-name>
X-DCHub-Via: <your-name>

Name format: lowercase letters, digits, dot, dash or underscore; 1-40 characters.

5. Cite what you relay

Relay each result's cite_as, source and as_of to your user unchanged; keep human_url and human_message when a result is partial. Citation format: DC Hub (dchub.cloud), as of <date>. DCPI verdicts and composite scores are CC BY 4.0; each layer states its own licence on /data-sources.

6. Get a partner key

Email partnerships@dchub.cloud with your product, expected volume and a dedicated service address for the key (for example dchub@yourgateway.dev). Partner keys are issued to a dedicated service address, never to a personal login. Send it as X-API-Key: <partner key>.

More for partners (embed cards, evidence receipts, methodology): dchub.cloud/partners. Machine-readable: builders.json. Contact: partnerships@dchub.cloud.