Check data coverage
Confirm which domains and geographies are populated before using a Gridstate response.
Query the coverage contract before assuming that Gridstate has populated a domain for your geography.
Request the coverage contract
curl "$GRIDSTATE_API_BASE/v1/data-coverage" \
-H "Authorization: Bearer $GRIDSTATE_API_KEY" \
-H "Gridstate-Version: 2026-08-24"Read the coverage label
Each domain receives one of these labels:
| Label | Meaning |
|---|---|
national | The federal dataset covers its intended national reporting population |
national_coarse | Coverage is broad but too imprecise for parcel decisions |
national_synthesis | A documented compilation covers the country without operator-native authority |
pilot | Reviewed representative sources work, but broad population is incomplete |
missing | No canonical records exist for the domain |
Gridstate derives labels from content-hashed sources and minimum record populations. Registering a source or importing one row cannot create a national claim.
Check quality separately
Coverage reports whether records exist. Quality reports defects in the records that exist.
curl "$GRIDSTATE_API_BASE/v1/quality" \
-H "Authorization: Bearer $GRIDSTATE_API_KEY" \
-H "Gridstate-Version: 2026-08-24"The quality response counts missing geography, unresolved points of interconnection, conflicting status, retained encoding damage, and invalid capacity values.
Compare national and pilot surfaces
Current coverage differs by data surface:
| Coverage | Included surfaces |
|---|---|
| National | EIA utilities, county service presence, plants, generators, monthly generation, balancing-authority operations, and Census county geometry |
| National synthesis | Berkeley Lab’s interconnection-queue compilation |
| Texas pilot | ERCOT queue and transmission projects, PUCT service-territory and docket evidence, and the Oncor tariff |
| Tariff proof set | Two reviewed tariffs, not a national tariff library |
Coverage does not establish utility feasibility
A populated geography can support public-evidence screening. It cannot establish site capacity, engineering feasibility, upgrade cost, schedule, or tariff eligibility.
Check which claims are allowed
Query /v1/claim-policy to retrieve the claims supported by the active release and the claims Gridstate blocks.
The site-screening workflow abstains when its required evidence domains are missing.