canonical: https://jentic.com/apis/elprisernaidag.se/elprisernaidag

# Elprisernaidag Se Elpriser i dag API

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.

## For AI 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.

## Scope

Does not sell electricity, switch suppliers, or forecast demand. Use for Swedish spot prices and grid-fee data only.

## Capabilities

- 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
- Create, look up, and delete an optional key that raises the request limit

## Use cases

### 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.

Example prompt: 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.

Example prompt: 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.

Example prompt: Create an optional key to raise the request limit, confirm it by looking it up, and delete it when the batch job finishes

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/v1/{elomrade}` | Today's and tomorrow's 15-minute prices for one bidding zone |
| GET | `/v1/elnatsavgifter` | All 188 grid companies with a reference annual cost |
| GET | `/v1/elnatsavgifter/{slug}` | Grid fees for one company, per customer type and year |
| POST | `/nycklar` | Create an optional higher-limit key |
| GET | `/nycklar/min` | Look up your own key |
| DELETE | `/nycklar` | Delete your own key |

## Key resources

- **Priser** — Quarter-hourly spot prices for the four Swedish bidding zones, VAT and tax included
- **Elnatsavgifter** — Grid fees for 188 companies across the six standard customer types and 2022 to 2026
- **Nycklar** — Create, look up, and delete an optional key that raises the request limit

## AI readiness

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.

- **Score:** 60 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 93 / 100
  - Developer Experience & Jentic Compatibility: 65 / 100
  - AI-Readiness & Agent Experience: 46 / 100
  - Agent Usability: 94 / 100
  - Security: 38 / 100
  - AI Discoverability: 65 / 100
- **View full report:** https://jentic.com/apis/elprisernaidag.se/elprisernaidag/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **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 handling:** 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.
- **Discovery method:** 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.

## Related APIs

- **EIA** — US Energy Information Administration energy prices and data
- **Data.gov** — Catalog of open government datasets

## FAQ

### 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.