canonical: https://jentic.com/apis/corrently.io

# Corrently APIs

Corrently is STROMDAO's German energy platform, exposed to agents through two APIs. One covers renewable-energy forecasting: the GrünstromIndex green-power score, best-hour selection, CO2 emission intensity, solar generation, and electricity market data by German postal code. The other covers the broader platform: smart meter reads, TSE-signed electricity receipts (Strom-Quittung) with ZUGFeRD XML, Stromkonto customer accounts, energy tariff lookups, and easee wallbox, OCPP charger, and public OpenMeter session data.

## For AI agents

An agent can forecast the greenest hour, CO2 intensity, and solar output for a German postal code, then act on the wider platform by reading smart meters, generating TSE-compliant electricity receipts, and managing Stromkonto customer accounts and tariffs.

## Scope

Use for: German green-power forecasting (GrünstromIndex, CO2, solar, market data) and STROMDAO platform operations such as smart-meter reads, TSE-signed electricity receipts, and Stromkonto customer management

Not supported:
- non-German grids
- real-time streaming
- retail tariff selling
- generic IoT control
- carbon accounting standards

## APIs

| API | Category | Endpoints | Description |
| --- | --- | --- | --- |
| Corrently.io | iot | 26 | Read smart meter data, generate fiscal-grade electricity receipts with TSE signatures, manage Stromkonto customer accounts, and access green-energy dispatch and tariff data on the Corrently.io platform. |
| Corrently Energy API | iot | 7 | Forecast renewable energy availability, find the cleanest hour to run loads, and read CO2 and solar predictions for German postal codes. |

## Which API to use

| Need | API | Why |
| --- | --- | --- |
| Forecast the greenest hour, CO2 intensity, or solar output for a German postal code | corrently-energy-api | The energy API is the focused forecast surface: GrünstromIndex prediction, best-hour, CO2, solar, and market data with no other platform operations in the way. |
| Read meters, generate TSE-signed receipts, or manage Stromkonto customers | corrently.io | The broader platform API adds metering, Strom-Quittung receipts, tariffs, Stromkonto lifecycle, and wallbox/charger sessions that the energy API does not cover. |
| Find the best green-energy hour by postal code | corrently-energy-api | Both APIs expose /gsi/bestHour, but the energy API keeps it alongside the related CO2 and solar forecasts an agent usually needs together. |

## Cross-API use cases

### Green-hour scheduling with metered receipting

An agent picks the cleanest hour for a flexible load using the forecast surface, then records the resulting consumption on the platform: it reads the customer's smart meter and prepares a TSE-signed electricity receipt for the delivered energy.

Example prompt: Call GET /gsi/bestHour on corrently-energy-api for the postal code and window, trigger the load at that hour, then GET /metering/reading and POST /quittung/prepare on corrently.io to record and receipt the consumption.

### Prosumer energy dashboard

A prosumer assistant merges live forecasts with device history: it shows the coming solar and CO2 curve from the forecast API next to the customer's easee wallbox and OCPP charger sessions and current Stromkonto balance from the platform API.

Example prompt: Call GET /solar/prediction and GET /switchboard/gsiCO2 on corrently-energy-api, then GET /alternative/easee/lastSessions and GET /stromkonto/balances on corrently.io, and render both in one view.

### Carbon-aware batch job with audit trail

An operator shifts a batch workload to the lowest-emission hour using the CO2 forecast, then reads the meter afterward to log the actual energy used against that decision for reporting.

Example prompt: Call GET /switchboard/gsiCO2 on corrently-energy-api to find the minimum-emission hour, run the job then, and GET /metering/reading on corrently.io to capture consumption for the audit log.

## Why Jentic

- **Setup:** Wiring both Corrently APIs by hand means handling the energy API's dual auth, the platform API's per-operation session model, and the shared German-grid v2.0 host across two surfaces. Through Jentic you install once and add each Corrently API from the Jentic directory, then your agent calls them.
- **Permission scoping:** Corrently spans read-only forecasts and state-changing platform actions like committing a receipt or registering a Stromkonto. Your own rules scope the agent to just the operations it needs, so state-changing operations stay out of reach unless you add them.
- **Credential handling:** The forecast token and any Stromkonto session credential are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search the Jentic directory by intent such as 'find the greenest hour' or 'prepare an energy receipt', and Jentic returns the matching Corrently operation with its input schema so the agent calls the right endpoint across either API without browsing the reference docs.

## Related vendors

- **Octopus Energy** — UK retail energy API with smart-tariff and consumption endpoints, an alternative when the customer is outside Germany.
- **Climatiq** — Emission-factor API that pairs with Corrently meter readings to produce standardized, auditable CO2 numbers.
- **Electricity Maps** — Grid carbon-intensity forecasts covering many countries, useful where coverage beyond the German grid is needed.

## FAQ

### What can an agent do across the Corrently APIs?

It can forecast the greenest hour, CO2 intensity, solar output, and market prices for a German postal code, and it can read smart meters, produce TSE-signed electricity receipts with ZUGFeRD XML, look up tariffs, and register or manage Stromkonto customer accounts. Together the two APIs cover both prediction and platform operations.

### Which Corrently API should I use for a given task?

Use the Corrently Energy API for forecast-only work such as best-hour, CO2, and solar predictions. Use the broader Corrently.io API when the workflow needs metering, receipts, tariffs, Stromkonto lifecycle, or wallbox and charger session data. Both share the GrünstromIndex best-hour operation.

### Do both APIs use the same credential?

No. The energy API expects a bearer token or a token query parameter issued by console.corrently.io. The broader Corrently.io surface declares no global security scheme and reaches endpoints either anonymously or with a Stromkonto session token established through login, so credentials are handled per operation rather than with one shared key.

### What geographies do these APIs cover?

Coverage is centered on Germany. The GrünstromIndex, CO2, and solar endpoints take a German postal code (PLZ) as input, and the receipt and metering flows follow German fiscal (TSE) and process rules. For other countries a different carbon-intensity or retail-energy API is a better fit.

### Are these official Corrently specifications?

STROMDAO publishes Corrently documentation but not OpenAPI specifications. Jentic generates and maintains the specs for both surfaces, validates them against the live API, and keeps them up to date so agents can call Corrently through structured tooling.

### Can an agent both schedule for green energy and bill for it?

Yes. An agent can call the energy API to find the cleanest hour, then use the Corrently.io platform API to read the meter and prepare a TSE-signed Strom-Quittung receipt for the energy delivered, keeping scheduling and receipting in one workflow.