Corrently Energy API

Name: Corrently Energy API
Brand: Corrently Energy API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentIOTSensor Databearer, apiKey7 EndpointsREST

Install Jentic One Beta

Connect the Corrently Energy API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Corrently Energy 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

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

Capabilities

What an agent can do with Corrently Energy API.

Read the GrünstromIndex prediction for a German postal code to know the hourly green-energy score over the next horizon

Find the best hour for energy consumption inside a given window so that flexible loads run when the grid is greenest

Pull current electricity market data including prices to drive demand-response or dynamic-tariff logic

GET STARTED

Start building with Corrently Energy API

Explore with Jentic

View OpenAPI Document

For Agents

Forecast renewable energy availability, find the cleanest hour to run loads, and read CO2 and solar predictions for German postal codes. Bearer-token or query-token authentication.

Use for: Get the GrünstromIndex prediction for postal code 69256, Find the cleanest hour today to run my dishwasher in Germany, Retrieve current German electricity market prices, Forecast CO2 emissions per kWh for the next 24 hours in my zip code

Not supported: Does not handle metering reads, receipt generation, tariff selection, or non-German grid data - use for German green-energy, CO2, and solar forecasts only.

Use Cases

Patterns agents use Corrently Energy API for, with concrete tasks.

★ Smart Home Green-Hour Scheduling

A home automation hub queries the GrünstromIndex prediction or best-hour endpoint each morning and schedules flexible loads - heat pump, dishwasher, EV charging - to run during the greenest window. The forecast covers a multi-hour horizon, so the agent can pre-cool a heat pump before peak fossil generation kicks in.

Call GET /gsi/bestHour with the postal code and a 24-hour window, then publish the returned hour to the home automation MQTT topic that triggers the EV charger.

Dynamic Carbon-Aware Batch Jobs

Batch workloads - backups, ML training, data transformations - read the CO2 prediction endpoint and shift execution to the lowest-emission hour in the next 24 hours. This pulls carbon-aware computing into reach without needing a custom forecasting model.

Call GET /switchboard/gsiCO2 for the data centre's postal code, find the hour with minimum gCO2/kWh in the next 24 hours, and submit the job to start at that timestamp.

Solar Self-Consumption Optimisation

A residential PV operator queries the solar prediction endpoint each evening to estimate the next day's generation curve, then a battery management system pre-charges or discharges to maximise self-consumption against the forecast. The market data endpoint can layer in price arbitrage when the battery is full.

Call GET /solar/prediction for the household location and feed the hourly curve into the battery scheduler so it discharges before the forecast solar peak.

AI Agent Energy Advisor via Jentic

An assistant answers questions like 'when should I charge my EV tomorrow to use the most green electricity?' by searching Jentic for the Corrently best-hour operation, calling it for the user's postal code, and returning a clear time window. The agent never needs to handle the bearer token or read the German documentation directly.

Search Jentic for 'find the cleanest hour for energy consumption', load GET /gsi/bestHour, execute it for the user's postal code and time window, and reply with the hour plus its GrünstromIndex score.

Key Endpoints

7 endpoints — jentic publishes the only available openapi specification for corrently energy api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/gsi/prediction

Get the GrünstromIndex prediction

GET

/gsi/bestHour

Find the best hour for energy consumption

GET

/gsi/marketdata

Get current electricity market data

GET

/switchboard/gsiCO2

Get CO2 emission predictions

GET

/solar/prediction

Get solar energy production predictions

GET

/stromkonto/balances

Get Stromkonto balances

GET

/tree/calculateCO2

Calculate tree-based CO2 offset

GET

/gsi/prediction

Get the GrünstromIndex prediction

GET

/gsi/bestHour

Find the best hour for energy consumption

GET

/gsi/marketdata

Get current electricity market data

GET

/switchboard/gsiCO2

Get CO2 emission predictions

GET

/solar/prediction

Get solar energy production predictions

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Your Corrently token 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 'find the greenest hour to charge' or 'get a German grid CO2 forecast', and Jentic returns the matching Corrently operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Time to first call

FAQs

Specific to using Corrently Energy API through Jentic.

Why is there no official OpenAPI spec for Corrently Energy API?

STROMDAO publishes Corrently documentation but not a single OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Corrently Energy API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the Corrently Energy API use?

The API supports two schemes: an HTTP bearer token issued by console.corrently.io, and an apiKey passed as a query parameter named token. Through Jentic the credential is stored encrypted and injected at call time, so the agent never sees the raw token.

Can I find the cleanest hour to run a load with this API?

Yes. GET /gsi/bestHour takes a postal code and a time window and returns the hour with the highest forecast share of regional green electricity, which is the canonical primitive for green-hour scheduling.

Which countries does this API cover?

Coverage is centred on Germany - the GrünstromIndex, CO2 forecast, and solar prediction endpoints take a German postal code (PLZ) as input. For other geographies a different carbon-intensity API is more appropriate.

What are the rate limits for the Corrently Energy API?

The OpenAPI spec does not declare numeric rate limits. Treat HTTP 429 responses as authoritative, back off using the Retry-After header where present, and consult console.corrently.io for plan-specific limits.

How do I get the GrünstromIndex prediction through Jentic?

Search Jentic for 'GrünstromIndex prediction' or 'best hour green energy', load GET /gsi/prediction or GET /gsi/bestHour, and execute with the German postal code as input. Jentic returns the operation schema so the agent does not need to parse Corrently docs.

Can I limit what my agent is allowed to do with the Corrently Energy API?

Yes. Because you run Jentic One yourself, your own rules decide which Corrently operations and credentials the agent may use. These endpoints are read-only forecast and market lookups with no resource id in the path, so you scope by operation: allow only the calls the agent needs, such as fetching a GrünstromIndex prediction, the best charging hour, or a solar forecast. Anything you do not add, like the CO2 prediction, Stromkonto balances, or tree-offset calculation, stays out of reach.