Skip to content
RateBase

Data

Download RateBase v1 datasets in JSON or CSV, with schema and release metadata.

Published
Jul 24, 2026
Domain as of
Jul 24, 2026
Immutable release
2026-07-24
Technical metadata+
Database revision
6b2f9d1a4c70
Source base commit
34c7a76d79ac3e6d3c4c3f9c7dd9a0e1be8cbe4a
Source tree
c06b8b8c17e45132ccf4eb5e704d0078ec9b631dc0eaf151bd6dd4e91624f937
Builder SHA
162dd8667f9e47e57e3a9dc6e6d93d728890657840e8d3f8131dce419b4e71f6
Domain digest
952454d5494f5724fe2917a815e37e34cd9121aec523dd50c273d0ca39de514f

Core datasets

JSON preserves nested DTOs; CSV provides flat directory and outcome views.

DatasetDescriptionFormats
proceedingsProceeding identity, status axes, utility relationships, and next events
JSONCSV
eventsMaterial procedural events with date provenance and evidence links
JSONCSV
decisionsRequested and authorized outcome summaries
JSONCSV
material-changesInvestor-facing approved developments grouped into one regulatory update
JSONCSV
utilitiesOperating utility identity, ownership, jurisdictions, and coverage
JSONCSV
companiesParent company identity and operating utility counts
JSONCSV
commissionsCommission identity, source links, and coverage counts
JSONCSV
statesState regulatory profiles and linked normalized relationships
JSON
large-load-tariffsNormalized tariff instruments and current version status
JSONCSV
large-load-termsTyped large-load requirements linked to proceedings, tariffs, and sources
JSONCSV

Relational and technical datasets

Normalized relationships, evidence-bearing detail, publication QA, and adapter metadata.

DatasetDescriptionFormats
state-rate-frameworksRate-case cadence, test periods, applicability, and official sources
JSONCSV
state-adjustment-mechanismsCost and revenue mechanisms between full base-rate cases
JSONCSV
commission-membersCommission roles, selection methods, term dates, and official sources
JSONCSV
regional-market-linksState and utility-jurisdiction relationships to RTOs, ISOs, and balancing authorities
JSONCSV
field-coveragePer-proceeding and state-level completeness, explicit gaps, and review depth
JSONCSV
observationsStage-preserving economics, positions, explicit missing values, periods, and citations
JSONCSV
periodsNormalized test years, rate years, and other proceeding periods
JSONCSV
rate-stepsNormalized multi-year rate steps and effective-event links
JSONCSV
utility-jurisdictionsEffective-dated utility, commission, state, and service relationships
JSONCSV
utility-ownershipsEffective-dated operating utility and parent-company ownership relationships
JSONCSV
company-identifiersNormalized ticker and other parent-company identifiers
JSONCSV
utility-identifiersNormalized EIA and commission utility identifiers
JSONCSV
proceeding-relationshipsCompanion, cost-of-capital, and other typed proceeding relationships
JSONCSV
adapter-capabilitiesDeclared automation level, configured endpoints, and normalized proposal support
JSONCSV
audit-changesField-level approved audit changes with entity context and evidence
JSONCSV
Contract metadata
coverage.json

Current record counts and last verification time

schema.json

Machine-readable v1 DTO contract

manifest.json

Schema, migration, source commit, generation time, and table counts

Relational concepts

Stable identity

Companies, utilities, jurisdictions, proceedings, events, observations, documents, and citations have independent stable IDs.

Directory and detail

Compact directory files support browsing. Per-record JSON files contain timelines, observations, tariff terms, and citations.

Status axes

Commission record, procedure, economics, implementation, and review are separate dimensions.

Stage-preserving observations

Requested, staff, intervenor, settlement, recommended, and authorized values remain distinct records.

Evidence graph

Material events, observations, versions, and terms point to public citation records.

Detail records and compatibility

Proceeding, utility, company, commission, and tariff detail records are published under matching v1 subdirectories using stable IDs.

Version 1 is a static public-data contract, not a REST API. Consumers should pin the schema version, treat unknown values as unknown, and follow citation URLs to the controlling public source.