Department of Energy
The U.S. Department of Energy provides REST APIs for energy consumption data, renewable energy statistics, fuel prices, electric vehicle infrastructure data, nuclear facility information, and scientific research publications. Primary API programs include the EIA Open Data API for energy time-series data, the NREL/NLR Developer Network for renewable energy and transportation data, and the OSTI APIs for DOE-funded research records.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Department of Energy the way a machine reads it — 51 machine-readable artifacts across 22 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Department of Energy scores 46.2/100 (developing), with a separate agent-readiness read of 48/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Department of Energy
Each block below is one kind of artifact we hold for Department of Energy. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 22
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
NLR Electricity APIs
NREL/NLR Developer Network electricity APIs covering utility rates, electricity costs, generation, transmission, delivery, and monitoring. Includes OpenEI Utility Rates API prov...
NLR Solar Resource APIs
Solar resource data and analysis APIs from NREL/NLR Developer Network, including NSRDB (National Solar Radiation Database) data access. Sponsored by the U.S. Department of Energy.
NLR Wind Resource APIs
Wind resource data and analysis APIs from NREL/NLR Developer Network providing wind speed and direction data for energy planning. Sponsored by the U.S. Department of Energy.
NLR Transportation & Alternative Fuels APIs
Alternative fuel station locator, alternative fuel vehicles database, EV infrastructure (EVI-Pro Lite), battery policies, transportation laws and incentives, and route energy op...
NLR Buildings Energy APIs
APIs for energy efficiency and use of renewable technologies in residential and commercial buildings from NREL/NLR Developer Network. Sponsored by the U.S. Department of Energy.
DOE Data Explorer API
The DOE Data Explorer API allows querying the Department of Energy's repository of research datasets resulting from DOE research funding. Built on REST architecture providing pr...
Department of Energy AEO API
Access to Annual Energy Outlook Data
Department of Energy COAL API
Access to Coal Data
Department of Energy CRUD_IMPORTS API
Access to Crude Oil Imports Data
Department of Energy DBF API
Access to Densified Biomass Data
Department of Energy ELEC API
Access to Electricity Data
Department of Energy EMISS API
Access to CO2 Emissions Data
Department of Energy IEO API
Access to International Energy Outlook Data
Department of Energy INTL API
Access to International Data
Department of Energy NG API
Access to Natural Gas Data
Department of Energy NUC_STATUS API
Access to Nuclear Outages Data
Department of Energy Root API
Available EIA API Datasets
Department of Energy RTO API
Access to Daily Electricity Data
Department of Energy SEDS API
Access to State Energy Data Systems (SEDS) Data
Department of Energy SEP API
Access to State Electricity Profiles
Department of Energy STEO API
Access to Short Term Energy Outlook Data
Department of Energy TOTAL API
Access to Total Energy Data
Scroll within the panel for all 22 ·
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Doe Plans Pricing
PLANSRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Doe Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Doe Finops
FINOPSSemantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Doe Context
JSON-LDSpectral Rules 1
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Department of Energy API Rules
SPECTRALJSON Schema 18
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
DataParams
JSON SCHEMADataResponse
JSON SCHEMADataResponseContainer
JSON SCHEMAFacet
JSON SCHEMAFacetDetails
JSON SCHEMAFacetDetailsContainer
JSON SCHEMAFacetMetaData
JSON SCHEMAFacetOptionList
JSON SCHEMAFacetOptionListContainer
JSON SCHEMAFinalRoute
JSON SCHEMAFinalRouteResponse
JSON SCHEMAFinalRouteResponseContainer
JSON SCHEMAFrequency
JSON SCHEMARouteRequest
JSON SCHEMARouteResponse
JSON SCHEMARouteResponseContainer
JSON SCHEMARoutes
JSON SCHEMASort
JSON SCHEMAScroll within the panel for all 18 ·
Examples 3
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Eia Data Response Example
EXAMPLEEia Facet Response Example
EXAMPLEEia Route Response Example
EXAMPLESecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Department of Energy — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/doe · machine-readable index on apis.io