> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cleanview.co/llms.txt
> Use this file to discover all available pages before exploring further.
# Data Centers
> Retrieve comprehensive data center project information including capacity, location, and development status
## Overview
The Data Centers endpoint provides access to a curated database of data center projects across the United States. This dataset includes information about planned, operating, and cancelled data center facilities, with details on power capacity, land usage, capital expenditure, and geographic location.
This is a "download link" style endpoint that returns all audit-approved records in a single response. There is no pagination - all approved data center records are returned at once.
### Common Status Values
| Status | Description |
| ----------- | ------------------------------------------ |
| `Planned` | Project is planned but not yet operational |
| `Operating` | Data center is currently operational |
| `Cancelled` | Project has been cancelled or postponed |
### Geographic Coverage
Data centers are tracked across multiple states with the highest concentrations in:
* **Virginia (VA)** - Northern Virginia data center corridor
* **Texas (TX)** - Major metro areas including Dallas-Fort Worth, Austin, San Antonio
* **Georgia (GA)** - Atlanta metro area
* **Arizona (AZ)** - Phoenix metro area
* **California (CA)** - Bay Area and Los Angeles
All records returned have been audit-approved by our data team to ensure accuracy and completeness.
## Example Requests
```bash theme={null}
curl -H "x-api-key: your_api_key_here" \
"https://api.cleanview.co/api/v1/data-centers"
```
Returns all audit-approved data center records in a single response.
## Response Schema
```json Example Response theme={null}
{
"success": true,
"metadata": {
"total_count": 1176,
"generated_at": "2024-12-12T10:00:00.000Z"
},
"customer": {
"id": "test_user_001",
"name": "Test Developer"
},
"data": [
{
"project_name": "Stream Data Center: Genesse County",
"developer": "Stream Data Centers",
"status": "Planned",
"operating_year": null,
"capacity_mw": 250.0,
"land_acres": null,
"building_square_footage": 900000,
"cap_ex": 6300000000,
"county": "Genesse",
"state": "NY",
"latitude": null,
"longitude": null,
"source_1": "https://www.datacenterdynamics.com/en/news/stream-proposes-large-data-center-in-genesee-county-new-york/",
"source_2": null,
"source_3": null
},
{
"project_name": "Core Scientific: Cottonwood 1 & 2",
"developer": "Core Scientific",
"status": "Planned",
"operating_year": null,
"capacity_mw": 250.0,
"land_acres": 100,
"building_square_footage": 125000,
"cap_ex": null,
"county": "Reeves",
"state": "TX",
"latitude": 31.54923296,
"longitude": -103.8337321,
"source_1": "https://corescientific.com/high-density-data-centers/pecos-tx/",
"source_2": null,
"source_3": null
}
]
}
```
## Response Fields
### Metadata Section
| Field | Type | Description |
| -------------- | ------- | ---------------------------------------------- |
| `success` | boolean | Indicates if the request was successful |
| `total_count` | number | Total number of data center records returned |
| `generated_at` | string | ISO 8601 timestamp when response was generated |
### Data Center Fields
| Field | Type | Description |
| ------------------------- | ------ | ----------------------------------------------------------- |
| `project_name` | string | Name of the data center project |
| `developer` | string | Developer or operator of the data center |
| `status` | string | Project status (Planned, Operating, Cancelled, etc.) |
| `operating_year` | number | Year the facility began or will begin operations (if known) |
| `capacity_mw` | number | Power capacity in megawatts (MW) |
| `land_acres` | number | Land area in acres |
| `building_square_footage` | number | Building area in square feet |
| `cap_ex` | number | Capital expenditure (investment amount in USD) |
| `county` | string | County where the data center is located |
| `state` | string | Two-letter state code where data center is located |
| `latitude` | number | Latitude coordinate of the facility |
| `longitude` | number | Longitude coordinate of the facility |
| `source_1` | string | Primary source URL for the data center information |
| `source_2` | string | Secondary source URL (if available) |
| `source_3` | string | Tertiary source URL (if available) |
**Null Values**: Many fields may contain `null` values when specific information is not available. This is particularly common for `operating_year`, `capacity_mw`, `latitude`, and `longitude` fields on newly announced projects.
## Data Quality Notes
* All returned records have `audit_approved = true`, indicating they have been reviewed and validated by our data team
* Source URLs are provided for transparency and verification
* Geographic coordinates (latitude/longitude) are included when available and accurate
* Capacity and financial data (capacity\_mw, cap\_ex) may be estimates based on public announcements
* Some projects may have multiple source URLs for cross-verification
**Large Response Size**: This endpoint returns all approved records in a single response. The response size can be 500KB or more depending on the current dataset. Ensure your application can handle this payload size.
## Use Cases
This endpoint is ideal for:
* **Market Analysis**: Understanding data center development trends by region, developer, or capacity
* **Location Intelligence**: Mapping data center locations and analyzing geographic clustering
* **Competitive Research**: Tracking which developers are active in specific markets
* **Energy Planning**: Analyzing power capacity requirements and grid impact
* **Real Estate Analysis**: Understanding land and building size requirements for data center projects
## Data Updates
The data center database is continuously updated as new projects are announced or existing projects reach new milestones. All updates go through an audit approval process before being exposed via the API.
## OpenAPI
````yaml GET /data-centers
openapi: 3.0.0
info:
title: Cleanview Public API
version: 0.1.0
description: >-
RESTful API for accessing clean energy data including EIA capacity and ISO
queue information
contact:
name: Cleanview Energy
url: https://cleanview.co/demo
servers:
- url: https://api.cleanview.co/api/v1
description: Production server
security:
- ApiKeyAuth: []
paths:
/data-centers:
get:
tags:
- Data Centers
summary: Get all data centers
description: >-
Returns all audit-approved data center records as a single JSON
response. This is a download link style endpoint with no pagination -
all records are returned in a single response.
parameters: []
responses:
'200':
description: Successful response with all data centers
content:
application/json:
schema:
type: object
required:
- success
- metadata
- customer
- data
properties:
success:
type: boolean
description: Always true for successful responses
example: true
metadata:
type: object
properties:
total_count:
type: integer
description: Total number of data center records
example: 1176
generated_at:
type: string
format: date-time
description: Timestamp when the response was generated
example: '2024-12-12T10:00:00.000Z'
customer:
type: object
description: Customer information for the API key
properties:
id:
type: string
name:
type: string
data:
type: array
items:
$ref: '#/components/schemas/DataCenter'
description: Array of all audit-approved data center records
'401':
description: Unauthorized
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
'500':
description: Internal server error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
security:
- ApiKeyAuth: []
components:
schemas:
DataCenter:
type: object
description: Data center project record
properties:
project_name:
type: string
description: Name of the data center project
developer:
type: string
nullable: true
description: Developer or operator of the data center
status:
type: string
nullable: true
description: Project status (Planned, Operating, Cancelled, etc.)
operating_year:
type: integer
nullable: true
description: Year the facility began or will begin operations
capacity_mw:
type: number
nullable: true
description: Power capacity in megawatts (MW)
land_acres:
type: integer
nullable: true
description: Land area in acres
building_square_footage:
type: integer
nullable: true
description: Building area in square feet
cap_ex:
type: number
nullable: true
description: Capital expenditure (investment amount in USD)
county:
type: string
nullable: true
description: County where the data center is located
state:
type: string
nullable: true
description: Two-letter state code
latitude:
type: number
nullable: true
description: Latitude coordinate
longitude:
type: number
nullable: true
description: Longitude coordinate
source_1:
type: string
description: Primary source URL
source_2:
type: string
nullable: true
description: Secondary source URL
source_3:
type: string
nullable: true
description: Tertiary source URL
Error:
type: object
description: Standardized error response structure
required:
- error
- message
properties:
error:
type: string
description: Error code identifier for programmatic handling
enum:
- INVALID_API_KEY
- API_KEY_NOT_FOUND
- INVALID_LIMIT
- INVALID_OFFSET
- INVALID_STATUS
- INVALID_CAPACITY
- INVALID_TECHNOLOGY
- INVALID_STATES
- INVALID_DATE
- INVALID_DATE_RANGE
- INVALID_BOOLEAN
- DATABASE_ERROR
- INTERNAL_ERROR
example: INVALID_LIMIT
message:
type: string
description: Human-readable error description
example: Limit must be at least 50 records per request
securitySchemes:
ApiKeyAuth:
type: apiKey
in: header
name: x-api-key
description: API key authentication using x-api-key header
````