Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the EIA Open Data API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Feia.gov%2Feia" | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Feia.gov%2Feia" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
What an agent can do with EIA Open Data API.
Browse the dataset hierarchy from top-level categories down to a specific series
Retrieve electricity retail sales figures with facet and period filters
Pull petroleum gasoline and diesel price data for a chosen period
Query natural gas price summaries and coal shipment receipt data
Resolve a legacy v1 series identifier against the v2 data surface
GET STARTED
List available facet values before building a filtered data request
Patterns agents use EIA Open Data API for, with concrete tasks.
★ Agent-Driven Energy Data Retrieval
An AI agent connected through Jentic answers energy questions by browsing the EIA route hierarchy, selecting the right dataset such as petroleum prices or electricity retail sales, and pulling the figures with facet and period filters. Because the API organises every fuel type under one versioned tree, the agent discovers what is available before it queries, instead of guessing dataset names.
Browse the electricity category, then retrieve retail sales data filtered to the most recent available period
Fuel Price Monitoring
Teams tracking energy costs retrieve gasoline, diesel, and natural gas price data on a schedule. The EIA API returns authoritative price summaries per fuel so a reporting pipeline can refresh a dashboard without scraping, and legacy series identifiers keep older reports pointed at the same underlying data.
Retrieve the latest gasoline and diesel price summary and compare it against natural gas price data
Electricity Market Analysis
Analysts studying electricity markets pull retail sales data and first list the facet values available so they can filter by the dimensions the dataset actually supports. The EIA API returns the facet list for a dataset, which lets an agent construct a valid, filtered query rather than requesting the whole series.
List the facet values for electricity retail sales, then request the sales data filtered by a chosen facet
9 endpoints — the eia open data api serves u.
METHOD
PATH
DESCRIPTION
/
List top-level data categories
/electricity
List electricity data subcategories
/electricity/retail-sales/data
Retrieve electricity retail sales data
/petroleum/pri/gnd/data
Retrieve gasoline and diesel prices
/natural-gas/pri/sum/data
Retrieve natural gas price summary data
/total-energy/data
Retrieve total energy statistics
/seriesid/{seriesId}
Retrieve data by legacy v1 series ID
/electricity/retail-sales/facet/{facetId}
List facet values for electricity retail sales
/
List top-level data categories
/electricity
List electricity data subcategories
/electricity/retail-sales/data
Retrieve electricity retail sales data
/petroleum/pri/gnd/data
Retrieve gasoline and diesel prices
/natural-gas/pri/sum/data
Retrieve natural gas price summary data
/total-energy/data
Retrieve total energy statistics
/seriesid/{seriesId}
Retrieve data by legacy v1 series ID
/electricity/retail-sales/facet/{facetId}
List facet values for electricity retail sales
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the EIA API by hand means registering for a key, learning the versioned route hierarchy, and threading the key through every query string. Through Jentic you install once, import the EIA Open Data API from the API Directory, store the key once, and your agent calls the data endpoints.
Permission scoping
Every EIA operation is read-only, so you choose exactly which ones your agent may call, such as listing categories and retrieving electricity or petroleum data. There are no write or delete operations to expose, and a rule keeps the agent to the datasets you intend.
Credential isolation
Your EIA API key is held by your own Jentic One instance, encrypted, and injected into the query string at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'get electricity retail sales' or 'retrieve gasoline prices', and Jentic returns the matching EIA operation with its input schema so the agent queries the right dataset without browsing the route tree by hand.
Alternatives and complements available in the Jentic catalogue.
Specific to using EIA Open Data API through Jentic.
What authentication does the EIA Open Data API use?
The EIA Open Data API authenticates with an API key passed as the `api_key` query parameter, per its OpenAPI spec. You register for a free key on the EIA Open Data site. Through Jentic the key is stored by your own Jentic One instance and attached to each request at execution time, so it never appears in your agent's prompt or logs.
Can I retrieve electricity and fuel prices with the EIA Open Data API?
Yes. The API returns electricity retail sales data, petroleum gasoline and diesel prices, natural gas price summaries, and coal shipment receipts, each under its own route in the dataset hierarchy. You can list the facet values for a dataset first and then request the data filtered to the facets and period you need.
What are the rate limits for the EIA Open Data API?
The OpenAPI spec does not specify rate limits. Check the EIA Open Data documentation at https://www.eia.gov/opendata/ for the current per-key limits before scheduling frequent pulls.
Is there an EIA Open Data MCP server?
You do not need an MCP server to give your agent the EIA Open Data API. Jentic connects it directly from the API Directory: import it, store your key once, and your agent calls the data endpoints on demand without loading an extra server's tool definitions into its context.
Can I limit what my agent is allowed to do with the EIA Open Data API?
Yes. Every operation here is a read, so you write a rule that allows only the dataset-listing and data-retrieval operations your agent needs, such as reading electricity retail sales and petroleum prices, and it can touch nothing else. Every call it makes is logged.
How do I pull EIA energy data through Jentic?
Install the Jentic One command line with `curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh`, then add the EIA Open Data API from the Jentic directory and search by intent such as 'retrieve electricity retail sales'. Jentic returns the matching operation with its input schema so your agent builds a valid query. To run it on your own infrastructure, install Jentic One from its GitHub repo.
For Agents
Query official U.S. energy statistics for electricity, petroleum, natural gas, and coal, browse the dataset hierarchy, discover facet values, and resolve legacy series identifiers.
Use for: Get the latest U.S. electricity retail sales figures, Retrieve gasoline and diesel prices from EIA, Find all natural gas price summary data for a given period, List the top-level energy data categories available
Not supported: Does not handle energy trading, utility billing, or grid control. Use for retrieving published U.S. energy statistics only.
The EIA Open Data API serves U.S. Energy Information Administration statistics across electricity, petroleum, natural gas, coal, and total energy from a single versioned query hierarchy. It exposes a browsable route tree where your agent lists top-level categories, drills into a dataset such as electricity retail sales, and pulls the data with facet filters applied. It also resolves legacy v1 series identifiers so existing dashboards keep working against the v2 surface.
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
Base layer of spec validity and structural soundness.
Aggregated quality score from linter diagnostics, weighted by severity.
Percentage of `$ref` references that resolve successfully.
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
Structural correctness score based on schema issues using logarithmic dampening.
Clarity, completeness, and ingestion readiness for developers and tooling.
How richly the API is illustrated with examples.
Percentage of examples that conform to their schemas.
Percentage of operations with complete response definitions (success, client error, server error).
Health of API ingestion, bundling, and resolution within Jentic pipelines.
Semantic breadth, depth, and agent comprehension for AI systems.
Coverage of descriptions across API elements.
Coverage of RFC 9457 Problem Details for error responses.
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
Coverage of summaries across operations/tags/info.
Functional utility, complexity comfort, and AI orchestration readiness.
Agent comfort level based on API operational and structural complexity.
Trust, risk posture, and security compliance.
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
Findability, semantic richness, and reasoning readiness.
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>