FERC
The Federal Energy Regulatory Commission (FERC) is the independent United States federal agency that regulates the interstate transmission of electricity, natural gas, and oil, licenses hydropower projects, and oversees the wholesale power markets run by the seven ISOs and RTOs. FERC sits on the wholesale side of the US energy value chain — it does not regulate retail utility service, retail rates, or the customer relationship, which remain with the fifty state public utility commissions. That jurisdictional line defines FERC's API posture exactly. FERC operates a real, self-serve open data API at api.data.ferc.gov, documented at data.ferc.gov with a published OpenAPI 3.0 description, a free 40-character API key issued from a sign-up form, a 1,000-request-per-hour rate limit, and X-Api-Key header or api_key query authentication on the api.data.gov API Umbrella stack — genuinely open market and regulatory data covering the Market-Based Rate Database, FERC Form No. 552 natural gas transactions, FERC Form 556 qualifying facility certifications, Company Registration, Annual Charges, Information Collections Management, and the NEPA infrastructure schedule. FERC also runs a credentialed OAuth2 XBRL submission API at ecollection.ferc.gov for the mandated eForms filings (Form Nos. 1, 2, 3-Q, 6, 60, 552, 714). What FERC does NOT do is any part of consumer energy data — there is no Green Button, no ESPI, no consumer data right, and no individual customer usage or billing API anywhere in FERC's surface, because retail customer data is outside its statutory reach. FERC is therefore an open-market-data, zero-consumer-data regulator, and it publishes a better documented API than most of the utilities it indirectly touches.
FERC publishes 8 APIs on the APIs.io network, including Data API, Data Assets API, Details API, and 5 more. Tagged areas include Energy, United States, Energy Markets, Electricity, and Natural Gas.
FERC’s developer surface includes authentication, code examples, changelog, sandbox, developer console, developer portal, documentation, and 35 more developer resources.
Kin Score
APIs 8
Individual APIs this provider publishes, each with its own machine-readable definition.
FERC Data API
The Data API from FERC — 1 operation(s) for data.
FERC Data Assets API
The Data-Assets API from FERC — 1 operation(s) for data-assets.
FERC Details API
The Details API from FERC — 1 operation(s) for details.
FERC Dictionary API
The Dictionary API from FERC — 1 operation(s) for dictionary.
FERC Filing API
Credentialed machine-to-machine submission of XBRL filings.
FERC Public Filings API
Anonymous read access to the public FERC eForms submission record.
FERC Reference API
Form lists and submission constraints.
FERC Taxonomy API
XBRL taxonomy versions, packages and sample forms for the FERC eForms.
Scroll for all 8
Open Collections 2
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
API Endpoints
OPEN COLLECTIONFERC eForms (eCollection) API
OPEN COLLECTIONArazzo Workflows 1
Multi-step API workflows described with the Arazzo specification.
FERC open data — discover a dataset and retrieve it
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 ...
ARAZZORate Limits 1
Documented rate limits and quota policies.
Ferc Rate Limits
RATE LIMITSSecurity Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
Recommended x-agentic-access execution contracts for AI agents.
Resources
Get Started 5
Portal, sign-up, and the first successful call
Documentation 6
Reference material describing how the API behaves
Agent Surfaces 3
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 6
Pagination, idempotency, versioning, errors, and events
Build 4
SDKs, sample code, and the tooling you integrate with
Access & Security 6
Authentication, authorization, and security posture
Operate 5
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 3
Properties that don't map to a standard resource type
Source (apis.yml)
Work with this as data
Every provider here is available over the APIs.io API and to AI agents over MCP.