Corrently provides a suite of APIs offering real-time and forecasted data on renewable energy availability, CO₂ emissions, and electricity pricing, enabling users to optimize energy consumption and reduce carbon footprints.
Corrently provides a suite of APIs offering real-time and forecasted data on renewable energy availability, CO₂ emissions, and electricity pricing, enabling users to optimize energy consumption and reduce carbon footprints. On Nagent, Corrently is exposed as a fully-configurable analytics integration that any agent can call — 23 actions, and API key authentication. No code is required to wire Corrently into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Corrently to automate the kinds of tasks analytics teams previously handled manually. Concrete examples — each one is a single agent step in Nagent — include:
Every action and trigger is paired with a structured input/output schema (visible in the sections below), so when you wire Corrently into Helix — our agentic agent builder — the editor knows exactly what each step expects and produces. Configure once, deploy anywhere across your Nagent agents.
Every operation an agent can call against Corrently, with input parameters and output schema. Drop these into any step of an agent built in Helix.
CORRENTLY_CO2_METER_UPDATE_READINGTool to create or update a CO₂ meter reading for emissions tracking. Use when sending new or updated electricity consumption readings to Corrently.
Input parameters
German 5-digit postal code indicating the meter's location.
Unix timestamp of the reading in seconds since epoch. Defaults to current server time if omitted.
New meter reading value (in watt-hours).
Unique identifier for the CO₂ meter.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CORRENTLY_COMMIT_QUITTUNGTool to finalize a Strom-Quittung (electricity receipt) after collecting transaction data. Use after gathering seller, buyer, and transaction details to create the final receipt.
Input parameters
Quittung session account identifier. Optional identifier for linking the receipt to a session.
Amount of energy transferred in the transaction in kWh.
Unique identifier for the transaction associated with this receipt.
Name of the buyer (energy consumer receiving the receipt).
Name of the seller (energy provider or entity issuing the receipt).
Duration of the transaction in seconds.
Email address of the seller for contact and receipt delivery.
Five-digit German postal code of the seller's location.
Yearly energy consumption of the seller in kWh.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CORRENTLY_GEOCODE_LOCATIONTool to geocode a free-text location into coordinates. Use when you need latitude and longitude from a place name.
Input parameters
Free-form location string (e.g., city, address, landmark).
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CORRENTLY_GET_ENERGY_SCHEDULECreate an optimized operation schedule for energy-consuming devices based on the GrünstromIndex (Green Power Index). This tool determines the best time slots to run energy-intensive devices (heat pumps, EV chargers, etc.) by analyzing regional renewable energy availability, electricity prices, and CO2 emissions forecasts. Use this after collecting: - German postal code (required for regional data) - Desired optimization goal (price, co2, or comfort) - Number of hours the device needs to run
Input parameters
German 5-digit postal code (Postleitzahl) for location-specific green energy scheduling. Example: '69168'.
Device energy usage requirements and optimization preferences.
Planning horizon in hours. Defaults to 24 hours (one day). Maximum typically 168 hours (one week).
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CORRENTLY_GET_METERING_READINGTool to retrieve metered electricity reading with green/grey energy split and CO2 emissions data. Use when you need to check current meter readings or analyze energy consumption patterns for a Stromkonto.
Input parameters
Account/Address (Stromkonto) to retrieve reading for. Must be a valid Ethereum address format.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CORRENTLY_GET_STROMKONTO_BALANCESRetrieve Stromkonto account balances from the energy blockchain ledger. Stromkonto is a ledger for green energy related transactions backed by Energychain blockchain to provide consensus of balances and transactions. Returns balance details across multiple sub-account types (green power bonus, generation, self-consumption, carbon offset, trees planted).
Input parameters
Ethereum style address referencing a valid account (AKA Stromkonto). If not provided, returns balances for all accounts or default account.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CORRENTLY_GET_STROMKONTO_CHOICESTool to get selectable contract choices for a Stromkonto customer. Use when you need to retrieve available balance and transaction options for an account.
Input parameters
Ethereum-style address referencing a valid Stromkonto account (e.g., 0x0000000000000000000000000000000000000000). This parameter is required to avoid 502 errors.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CORRENTLY_GET_WIM_PROCESS_STATUSRetrieve status information for WiM (Wechselprozesse im Messwesen) metering change processes. WiM processes handle meter changes and allocation workflows in the German electricity system. Use this tool to check the current status of ongoing or completed metering change processes, track process progress, or verify when a WiM process was initiated.
Input parameters
VID (Vorgangsidentifikation) key of the metering change process to query. If not provided, returns status for all processes accessible with the current authentication.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CORRENTLY_GRUNSTROM_INDEX_FORECASTTool to retrieve hourly green power forecast and CO2 data. Use after obtaining the user API key.
Input parameters
User/account identifier provided for API access.
Five-digit German postal code of the location to query.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CORRENTLY_GSI_BEST_HOURDetermines if now is the best time to turn on a device based on regional green energy (GrünstromIndex) forecasts in Germany. Returns true if the current hour has high renewable energy availability within the specified timeframe, false if waiting would be more sustainable.
Input parameters
Stromkonto account address or API key for personalized forecasts.
German 5-digit postal code (PLZ) for location-based green energy forecast. Required.
Number of consecutive hours the device needs to run.
Number of hours ahead to scan for the best green-energy window (default 24).
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CORRENTLY_LOGIN_STROMKONTOTool to initiate login to Stromkonto via email. Use when authenticating a user with their email address.
Input parameters
Email address for login to Stromkonto account.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CORRENTLY_MARKET_DATARetrieve real-time and forecast electricity pricing data for Germany by postal code (Postleitzahl). Returns wholesale market prices (EUR/MWh) and localized prices for specific grid areas. Data is provided in time intervals with timestamps in milliseconds since Unix epoch. Use this tool when you need current or forecasted electricity prices for energy optimization, cost analysis, or smart grid applications in Germany.
Input parameters
Five-digit German postal code (Postleitzahl) for electricity market data lookup. Example: '69168' for Wiesloch, '80331' for Munich, '10115' for Berlin.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CORRENTLY_PHEV_NAVIGATORTool to get PHEV charge-or-fuel recommendation for German locations. Compares real-time fuel prices at nearby stations with electricity costs to recommend whether charging or fueling is more economical and eco-friendly. Requires a German postal code (PLZ).
Input parameters
Optional Stromkonto account address or API key for authenticated access with higher rate limits.
Battery state of charge as percentage (0-100). Optional but recommended for accurate cost calculations.
German 5-digit postal code (PLZ) for the location. This is required to determine local fuel prices and electricity rates.
Vehicle fuel consumption in liters per 100 km. Used to calculate fuel costs per 100 km.
Vehicle electric power consumption in kWh per 100 km. Used to calculate electricity costs per 100 km.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CORRENTLY_POST_METERING_READINGTool to post a meter reading and get it decorated with green/grey energy split. Use when you need to split consumption readings into green power (1.8.1) and grey power (1.8.2) according to the local GreenPowerIndex value.
Input parameters
German postal code (5 digits) of the metered location.
Meter reading value in watt-hours (Wh). This is an alias for the '1.8.0' OBIS code field. Provide either 'energy' or '1_8_0', not both.
Private password for meter updates. Required if the meter is protected.
Stromkonto account (address) associated with this metering.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CORRENTLY_PREPARE_RECEIPT_DATATool to collect data for a receipt before finalizing. During the first call, an account parameter will be returned. Use this when you need to incrementally build receipt data through multiple requests. Call without an account parameter first to create a new session, then use the returned account identifier in subsequent calls to add more data.
Input parameters
Quittung session account identifier returned from the first call. Omit this parameter on the first request to create a new session. Include it in subsequent requests to extend or update the existing collection.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CORRENTLY_PV_GENERATION_GET_FORECASTGet hourly solar PV generation forecasts for a German location. Returns predicted energy output in watt-hours (Wh) for each hour over the specified forecast period. Use this tool when you need to optimize energy scheduling, estimate solar production, or plan energy storage based on expected PV generation.
Input parameters
Number of days to forecast (1-7). Defaults to 7 days if not specified.
Installed photovoltaic system capacity in watts (W). Typical residential systems range from 3000 to 10000 watts.
German postal code (PLZ) for the location. Must be a valid 5-digit German ZIP code.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CORRENTLY_REGISTER_STROMKONTOTool to register a new Stromkonto energy account in the Corrently system. Use when creating a new account with email, name, and location details. All balances are initialized to zero upon registration.
Input parameters
Email address for the new account holder.
Five-digit German postal code (Postleitzahl) for the account location.
Last name of the account holder.
First name of the account holder.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CORRENTLY_RENEWABLE_ENERGY_DISPATCHTool to get renewable energy flow and mix for a German ZIP code. Use when you need import/export and dispatch sources/destinations breakdown.
Input parameters
German postal (ZIP) code to analyze.
Optional access token for extended or paid access; if provided, sent as query parameter 'token'.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CORRENTLY_STROMMIXTool to retrieve real-time electricity generation mix in Germany. Use when you need the current breakdown of generation by source.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CORRENTLY_TARIFF_COMPONENTSRetrieve detailed German electricity tariff cost breakdown by postal code. Returns comprehensive cost components including: - Grundgebühr (base monthly fee) - Arbeitspreis (energy price per kWh) - Network fees (Netznutzungsentgelt) - Taxes (Stromsteuer, Mehrwertsteuer) - Levies (EEG, KWKG, Offshore-Netzumlage) - Renewable energy credits Use this tool to understand electricity pricing transparency in Germany.
Input parameters
Energy amount in watt-hours for a specific event. Requires 'milliseconds' to be set.
Annual energy consumption in kWh/year. Used to calculate total annual costs. Typical household: 2000-4000 kWh.
Email address for API request attribution (required by API). Can be any valid email format.
German postal code (5-digit PLZ) to get local tariff components. Example: '80331' for Munich.
Timeframe in milliseconds for scaling calculations. Use with 'wh' for specific energy events.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CORRENTLY_TARIFF_SLPH0Tool to retrieve standard load profile H0 tariff information. Use after providing a German postal code to get local SLPH0 tariffs.
Input parameters
German postal code (Postleitzahl) to scope the SLPH0 tariff (5 digits).
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CORRENTLY_WEATHER_FORECASTTool to retrieve hourly weather forecasts (wind speed and UV index) by geographic coordinates. Use when you need wind and UV data for a specific location. Returns up to 5 days of hourly forecasts.
Input parameters
Latitude in decimal degrees (-90 to 90). Required.
Longitude in decimal degrees (-180 to 180). Required.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CORRENTLY_WIM_STATUSCheck TyDID consent/grant status for an SSI (Self-Sovereign Identity). This tool queries the Corrently TyDID API to verify whether a given Ethereum-based identity has granted consent or if the consent has been revoked. Use cases: - Verify user consent before processing data - Check if a user has revoked access to their data - Monitor consent status changes in blockchain-based identity systems
Input parameters
Ethereum-based SSI (Self-Sovereign Identity) address to check consent status for. Format: 0x followed by 40 hexadecimal characters (e.g., '0x95Bee09c395c60883Fa8bb95F05404a71f7ee7F7').
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
No publicly available marketplace agent is found using this tool yet. There are 86 agents privately built on Nagent that already use Corrently.
Build on Nagent
Connect Corrently to any Nagent agent in minutes — no API key management, no boilerplate. Just configure and deploy.
The five questions agent builders ask before adopting a new integration.
Open the External Integrations panel inside Nagent (app.nagent.ai/externalIntegration), find Corrently, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Corrently is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Corrently is connected, you configure its 23 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Corrently steps into any workflow visually. Pick an action (e.g., one of those listed above), fill in the inputs (Helix knows the required vs. optional schema for each parameter), and connect it to upstream/downstream steps. Triggers run as the entry point of an agent, so when a Corrently event fires, the agent kicks off automatically.
Every Corrently action and trigger ships with a fully-typed schema — input parameters with name, type, required flag, and description, plus the output payload shape. The schemas are documented in the sections above. Helix uses these schemas to validate your configuration at build time and to type-check the data flowing between steps.
Yes. While Corrently ships with 23 pre-built analytics actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Corrently together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Corrently-based workflows tailored to your business.