Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Elpriser i dag 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%2Felprisernaidag.se%2Felprisernaidag" | 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%2Felprisernaidag.se%2Felprisernaidag" | 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 Elpriser i dag API.
Fetch today's and tomorrow's 15-minute electricity spot prices for a Swedish bidding zone, with VAT and energy tax included
Read the reduced energy tax for the northern municipalities separately
List all 188 grid companies with a reference annual cost
Look up grid fees for one company across the six standard customer types and the years 2022 to 2026
GET STARTED
Create, look up, and delete an optional key that raises the request limit
Patterns agents use Elpriser i dag API for, with concrete tasks.
★ Agent electricity price lookup
An agent helping a Swedish household decide when to run appliances fetches today's and tomorrow's 15-minute spot prices for the relevant bidding zone, with VAT and energy tax already included so the figure matches the bill. It discovers the price operation through Jentic by intent and calls it with the zone code, no key required.
Fetch today's 15-minute spot prices for a bidding zone and return the cheapest window to run a high-draw appliance
Grid-fee comparison
Compare what different Swedish grid companies charge by listing all 188 companies with a reference annual cost, then reading one company's fees across the six standard customer types and the years 2022 to 2026. An agent can surface the fee a specific household faces for a given year.
List grid companies, then look up one company's fees for the standard customer type and report its 2026 reference cost
Higher-limit key management
A workflow that polls prices frequently creates an optional free key to raise its request limit, looks the key up when needed, and deletes it when finished. The key is only about throughput: reading prices and grid fees needs no credential.
Create an optional key to raise the request limit, confirm it by looking it up, and delete it when the batch job finishes
6 endpoints — the elpriser i dag api serves quarter-hourly electricity spot prices for the four swedish bidding zones, with vat and energy tax already added so the figure matches what a household actually pays, and the reduced northern-municipality energy tax given separately.
METHOD
PATH
DESCRIPTION
/v1/{elomrade}
Today's and tomorrow's 15-minute prices for one bidding zone
/v1/elnatsavgifter
All 188 grid companies with a reference annual cost
/v1/elnatsavgifter/{slug}
Grid fees for one company, per customer type and year
/nycklar
Create an optional higher-limit key
/nycklar/min
Look up your own key
/nycklar
Delete your own key
/v1/{elomrade}
Today's and tomorrow's 15-minute prices for one bidding zone
/v1/elnatsavgifter
All 188 grid companies with a reference annual cost
/v1/elnatsavgifter/{slug}
Grid fees for one company, per customer type and year
/nycklar
Create an optional higher-limit key
/nycklar/min
Look up your own key
/nycklar
Delete your own key
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Elpriser i dag API by hand means deciding whether to send an optional key as a bearer token or the nyckel query parameter, handling its Swedish field names, and tracking its request limit yourself. Through Jentic you install once, import the Elpriser i dag API from the API Directory, store the key once, and your agent calls it.
Permission scoping
The Elpriser i dag API is read-first: prices and grid fees need no credential, and an optional key only raises your request limit. A rule bounds which operations your agent may call, such as price and grid-fee lookups, so key creation and deletion stay off unless you add them.
Credential isolation
Your optional Elpriser i dag key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'get today's electricity price for a zone' or 'list grid fees', and Jentic returns the matching Elpriser i dag operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using Elpriser i dag API through Jentic.
What authentication does the Elpriser i dag API use?
Per its OpenAPI spec, no key is required to read prices and grid fees. An optional key raises the request limit and can be supplied either as a bearer token or as the nyckel query parameter. Through Jentic any key is stored encrypted by your own Jentic One instance and injected at execution time, so it never enters the agent's context.
Can I get Swedish electricity spot prices with the Elpriser i dag API?
Yes. The price operation returns today's and tomorrow's 15-minute spot prices for a chosen bidding zone, with VAT and energy tax already added so the figure matches what a household pays, and the reduced northern-municipality tax is given separately.
What are the rate limits for the Elpriser i dag API?
The OpenAPI spec sets an hourly limit of 120 requests without a key, which an optional free key raises to 2000 requests per hour. The data is free to use with a link back to elprisernaidag.se.
Is there an Elpriser i dag MCP server?
You don't need an MCP server to give your agent the Elpriser i dag API. Jentic connects it directly from the API Directory: import it, add an optional key if you need a higher limit, and your agent calls the price and grid-fee operations it needs.
Can I limit what my agent is allowed to do with the Elpriser i dag API?
Yes. Write a rule that allows only the read operations for prices and grid fees, so the agent can look up what a household pays but cannot create or delete keys. The key-management operations stay off unless you add them, and every call the agent makes is logged.
How do I get today's prices through Jentic?
Search Jentic for 'get today's electricity price for a zone', and it returns the Elpriser i dag price operation with its input schema; your agent supplies the bidding-zone code and calls it. To run it on your own infrastructure, install Jentic One from its GitHub repo.
For Agents
Read Swedish electricity spot prices for the four bidding zones (VAT and tax included) and grid fees for 188 companies across 2022 to 2026, and optionally manage a key that raises the request limit.
Use for: Get today's electricity spot price for a Swedish bidding zone, Check tomorrow's 15-minute prices for my area, List all Swedish grid companies and their reference annual cost, Look up grid fees for a specific grid company
Not supported: Does not sell electricity, switch suppliers, or forecast demand. Use for Swedish spot prices and grid-fee data only.
The Elpriser i dag API serves quarter-hourly electricity spot prices for the four Swedish bidding zones, with VAT and energy tax already added so the figure matches what a household actually pays, and the reduced northern-municipality energy tax given separately. It also returns grid fees (elnatsavgifter) for 188 grid companies for the years 2022 to 2026, sourced from Energimarknadsinspektionen. Prices come from Nord Pool via elprisetjustnu.se, field names are in Swedish, and no key is required to read the data.
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>