Corrently APIs for AI Agents
IOTSensor DataJentic-Generated SpecsNo authbearer, apiKeyAgent Ready
Corrently API Catalog
2 APIs across 1 product group.
IOT2
Corrently.ioRead 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.~26 endpointsCorrently Energy APIForecast renewable energy availability, find the cleanest hour to run loads, and read CO2 and solar predictions for German postal codes.~7 endpoints
Which Corrently API should I use?
| I want to... | Use | 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. |
Install Jentic One Beta
Connect the Corrently APIs to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Corrently APIs, 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.
Why Jentic?
What agents get from Jentic-routed access to this vendor.
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 isolation
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.
FAQs
Specific to using Corrently APIs through Jentic.
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?
BOOK A DEMO
Start Connecting APIs to Your AI Agents
Browse thousands of APIs and connect them all to your agent with Jentic One. One layer, one credential — every API your agent needs.
