Corrently.io

Name: Corrently.io API
Brand: Corrently.io
Availability: InStock

★ Only Publicly Available OpenAPI DocumentIOTSensor Datanone26 EndpointsREST

Install Jentic One Beta

Connect the Corrently.io to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Corrently.io, 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.io API.

Read and submit meter readings to the metering endpoint for prosumer and grid-operator workflows

Create and finalise an electricity receipt (Strom-Quittung) with TSE-compliant signatures and ZUGFeRD XML output

GET STARTED

Start building with Corrently.io API

Explore with Jentic

View OpenAPI Document

For Agents

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.

Use for: Submit a new meter reading for my smart meter, Create an electricity receipt for a delivery in Germany, I need to retrieve the TSE signature for a Strom-Quittung, Get the ZUGFeRD XML for a finalised receipt

Not supported: Does not handle non-German grid operations, retail tariff selling, or generic IoT device control beyond easee/OCPP/OpenMeter - use for STROMDAO Corrently metering, receipts, Stromkonto, and green-energy data only.

Use Cases

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

★ TSE-Compliant Electricity Receipts

German energy resellers prepare, finalise, and archive electricity receipts (Strom-Quittung) that meet TSE fiscal requirements. The API offers a prepare/commit pattern with a separate signature-retrieval step plus ZUGFeRD XML output for downstream accounting systems.

Call POST /quittung/prepare with the receipt fields, POST /quittung/commit to finalise, then POST /quittung/tsesignature for the TSE signature and GET /quittung/zugferd for the archival XML.

Smart Meter and Wallbox Aggregation

Aggregate readings from a customer's smart meter, easee wallbox, and any OCPP-based charger into a single dashboard. The OpenMeter endpoints add public meter data for benchmarking, while the metering endpoint accepts new readings from a connected device.

Call GET /alternative/easee/lastSessions for wallbox sessions, GET /alternative/ocpp/lastSessions for public chargers, GET /metering/reading for the customer's meter, and merge the data into the dashboard.

Stromkonto Customer Lifecycle

Onboard new energy customers and manage their Stromkonto account end-to-end: register, log in via email, prepare a transaction such as a tariff change, and read balances on demand. The choices endpoint surfaces what options the customer can pick from at each step.

Call POST /stromkonto/register to create the account, POST /stromkonto/login to authenticate the user, GET /stromkonto/choices to render available options, and POST /stromkonto/prepareTransaction when the customer chooses one.

AI Agent for Prosumer Energy Operations via Jentic

An assistant for a German prosumer answers operational questions like 'when did my wallbox last charge?' or 'is my receipt registered with the TSE?' by routing each question to the right Corrently.io operation. The agent reasons over capabilities rather than memorising 26 endpoints.

Search Jentic for 'last easee wallbox session' or 'finalise Strom-Quittung receipt', load the matching operation, and execute it with the requested customer or receipt ID.

Key Endpoints

26 endpoints — jentic publishes the only available openapi specification for corrently.

METHOD

PATH

DESCRIPTION

POST

/quittung/prepare

Prepare a Strom-Quittung receipt

POST

/quittung/commit

Finalise a prepared receipt

POST

/quittung/tsesignature

Retrieve the TSE signature for a receipt

POST

/stromkonto/register

POST

/stromkonto/login

GET

/metering/reading

Read a smart meter

GET

/gsi/bestHour

Find the best hour for green-energy consumption

GET

/tariff/components

List energy tariff price components

POST

/quittung/prepare

Prepare a Strom-Quittung receipt

POST

/quittung/commit

Finalise a prepared receipt

POST

/quittung/tsesignature

Retrieve the TSE signature for a receipt

POST

/stromkonto/register

POST

/stromkonto/login

Why Jentic?

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

Credential isolation

This Corrently.io surface takes no credential; where a call needs a session, that value 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 'prepare an energy receipt' or 'read the latest meter value', and Jentic returns the matching Corrently.io 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.io API through Jentic.

Why is there no official OpenAPI spec for Corrently.io?

STROMDAO publishes Corrently documentation but not a single OpenAPI specification covering the full platform. Jentic generates and maintains this spec so that AI agents and developers can call Corrently.io 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.io API use?

The OpenAPI spec for this surface declares no global security scheme - endpoints are reached either anonymously or with a token tied to the customer Stromkonto, established via POST /stromkonto/login. Through Jentic the customer credential is stored encrypted and injected only on the operations that need it.

Can I create a TSE-signed electricity receipt with this API?

Yes. The /quittung group implements a prepare/commit/sign flow: POST /quittung/prepare collects data, POST /quittung/commit finalises the receipt, and POST /quittung/tsesignature plus POST /quittung/tsedata return the TSE artefacts, with GET /quittung/zugferd providing the archival XML.

How do I onboard a new Stromkonto customer?

Call POST /stromkonto/register with the customer details, then POST /stromkonto/login when the customer needs an authenticated session. GET /stromkonto/choices renders the options available to that customer and POST /stromkonto/prepareTransaction stages a chosen action.

What are the rate limits for the Corrently.io 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 read a customer's smart meter through Jentic?

Search Jentic for 'read smart meter' or 'meter reading', load GET /metering/reading, and execute with the meter identifier. Jentic returns the operation schema so the agent does not need to parse Corrently documentation.

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

Yes. Because you run Jentic One yourself, your own rules decide which Corrently.io operations the agent may call, and the credentials it may use. Since these operations post to collection paths like /quittung/prepare and /stromkonto/register with no resource id in the URL, you scope by operation: allow only what the agent needs, such as reading a meter value or preparing a receipt. State-changing operations like committing a receipt with POST /quittung/commit or registering a customer with POST /stromkonto/register stay out of reach unless you add them.

Corrently.io

Connect the Corrently.io to your agent

Capabilities

Start building with Corrently.io API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs