Skip to main content
GET
Get all behind-the-meter gas plants
The BTM gas plant endpoints require the gas-plants scope on your API key. A key without it gets 403 INSUFFICIENT_SCOPE. Contact us to add it.

Overview

Data centers that can’t wait for the grid are building their own gas plants. This endpoint returns one record per behind-the-meter gas plant built to power a data center. A plant is behind the meter when its power goes straight to the data center instead of through a utility meter. Each record has the plant’s developer, status, capacity, the data center campus it powers, its location, its air permit, and the documents Cleanview archived for it. This is a “download link” style endpoint that returns all records in a single response. There is no pagination.

Plants and Units

A plant is one generation site. Its equipment is broken into units on Gas Plant Units, linked by plant_id. A unit is one equipment model at one stage of the build, with its own count, capacity, status and year. A plant with two engine models, each installed in two stages, has four units. The plant’s status and capacity on this endpoint are rolled up from its units. The campus it powers is on Data Center Campuses, linked by campus_id.

Status Values

Each unit has its own status. A plant shows the status of its most advanced unit that isn’t canceled, so a plant with an operating first stage and a second stage under construction is Operating. A plant is Canceled only when every unit is.

Capacity

nameplate_capacity_mw is the number of machines times the manufacturer’s rating for each machine, summed over the units that aren’t canceled. Manufacturers rate gas turbines at 59°F at sea level and engines at 77°F. So one machine has one rating wherever it’s installed, and nameplate adds up across plants and manufacturers. A plant’s real output on a hot day or at altitude is lower. operating_capacity_mw, under_construction_capacity_mw, permitted_capacity_mw and announced_capacity_mw split the nameplate capacity by unit status, so they add up to it. When capacity_is_partial is true, some units have no known capacity yet, and the capacity fields are a minimum. firm_output_mw is the power the plant is contracted, permitted or stated to deliver to its data center. It’s usually 55% to 85% of nameplate, because of heat, altitude, the plant’s own load and spare machines. It’s only given when a document states it, and never estimated. firm_output_basis names the kind of document:

Air Permits and Sources

air_permit_url is Cleanview’s copy of the plant’s issued air permit, or its latest amendment, once the plant is Permitted, Under Construction or Operating. sources lists every document Cleanview archived for the plant, newest first, including permit applications and drafts. Each url is Cleanview’s archived copy, so it keeps working if the original is taken down. original_url is where the document was first published.

Example Requests

Returns all gas plant records in a single response.

Response Schema

Response Fields

Metadata Section

Gas Plant Fields

Null Values: null means Cleanview doesn’t know the value yet, not zero. A capacity field is null when no unit in it has a capacity, including when the plant has no units with that status. campus_id is null when the campus the plant powers isn’t in Data Center Campuses; campus_name is still given. equipment_types and oems are null until the equipment is public.

Data Updates

Plant figures are computed from the unit records in Gas Plant Units on every request, so the two endpoints always agree.

Authorizations

x-api-key
string
header
required

API key authentication using x-api-key header

Response

Successful response with all gas plants

success
boolean
required

Always true for successful responses

Example:

true

metadata
object
required
customer
object
required

Customer information for the API key

data
object[]
required

Array of all gas plants