FERC · Arazzo Workflow
FERC open data — discover a dataset and retrieve it
Version 1.0.0
The full happy path against the FERC Open Data API: list the catalog, resolve a dataset ID from the nested data-sets array, read its metadata and record count, fetch the column dictionary so the rows can be interpreted, then pull the rows. Every operationId below exists verbatim in FERC's published OpenAPI. Requires a free FERC API key.
View Spec
View on GitHub
EnergyUnited StatesEnergy MarketsElectricityNatural GasGridRegulatorGovernmentOpen DataWholesale Power MarketsHydropowerOil PipelinesArazzoWorkflows
Provider
Workflows
discoverAndRetrieveFercDataset
Resolve a FERC dataset ID from the catalog and retrieve its dictionary and rows.
Dataset IDs are not stable — FERC states they may change over time — so this workflow always re-resolves the ID from the Data-Assets endpoint rather than accepting one as input. The dictionary step tolerates a 404, which FERC documents as meaning "no dictionary published for this dataset" rather than a bad ID.
1
listDataAssets
List every FERC data asset and its nested datasets. This is the only authoritative source of dataset IDs.
2
getDatasetDetails
Read the dataset's metadata — record count, industry, last updated timestamp and point of contact. Use the record count to decide whether the full data pull is viable, since the data endpoint returns everything with no filtering or paging.
3
getDatasetDictionary
Fetch the column dictionary so the untyped rows can be interpreted. A 404 is an expected outcome — FERC publishes dictionaries for some datasets only — so both 200 and 404 are accepted here and the workflow continues either way.
4
getDatasetData
Retrieve the full row set. There is no pagination and no filtering; the response is the entire dataset. Stream it rather than buffering when the record count from getDatasetDetails is large.
Source API Descriptions
openapi
openapi
openapi
Arazzo Workflow Specification
Work with this as data
Every workflow here is available over the APIs.io API and to AI agents over MCP.