---
title: "One facility's record"
method: GET
path: "/api/v1/facilities/{facility_id}"
tags: ["Public"]
---

# One facility's record

`GET /api/v1/facilities/{facility_id}`

## Request

- Base URL: `https://dchub.cloud`
- URL: `https://dchub.cloud/api/v1/facilities/{facility_id}`
- Auth: one of:
  - API key in header `X-API-Key`
  - none

Look up a single facility by the `id` or `slug` that searchFacilities returns. The response shape is decided by the caller's tier. Anonymous: id, name, city, state, country, status, slug, plus coordinates rounded to 2 decimal places (~1.1 km) and an `_upgrade` block. A free claimed key adds provider, operator, market and region at the same precision, plus exact coordinates and street address for up to 10 distinct facilities a month: a call for a new facility spends one, re-reading one is free, the allowance is shared with the website and MCP, and `_location_allowance` reports what was spent and what remains. A key on any paid DC Hub plan returns the full record: exact coordinates, power_mw, address and source, and no `_upgrade`. Branch on `_upgrade` being present rather than on whether you sent a key — a free key still carries it. `_coord_precision_dp` states the rounding applied (null when exact), so never treat a returned coordinate as exact without checking it. (Keys on the retired entry plan get the full record with location metered like a free key.)

## Path parameters

- `facility_id` string, required

## Response `200`

Facility record — basic preview plus _upgrade for anonymous and free callers, full record for a key on any paid DC Hub plan

## Other responses

- `404`: No facility with that id or slug

---

[API](https://skmtc.dev/dchub/apis/dc-hub-data-center-intelligence-api.md) · [All operations](https://skmtc.dev/dchub/apis/dc-hub-data-center-intelligence-api/llms.txt) · [OpenAPI document](https://skmtc.dev/dchub/apis/dc-hub-data-center-intelligence-api/revisions/15f74d15cdeb?raw)