corrently.io valid

Corrently IO

Public developer and integrator documentation for Corrently/STROMDAO energy APIs, GrünstromIndex, market data, Energy Application Framework, and selected Cernion Energy Tools references.

For agents: Public developer documentation for Corrently/STROMDAO energy APIs, GrünstromIndex, CO2 advisor and market data, with fair use and rate-limit guidance.

energy apigrünstromindexco2 intensity forecastrenewable energy datadeveloper documentation

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-20T15:29:38.478Z. Cached copy · Source on corrently.io

# Corrently IO

> Public developer and integrator documentation for Corrently/STROMDAO energy APIs, GrünstromIndex, market data, Energy Application Framework, and selected Cernion Energy Tools references.

Corrently IO is the public BookStack documentation surface for developer-facing STROMDAO/Corrently resources. Use the links below as canonical entry points. API keys, rate limits, commercial terms, and legal or tariff interpretations are not defined in this file; follow the linked public documentation and policy pages.

## Developer entry points

- [Corrently Energy APIs](https://corrently.io/books/corrently-energy-apis): canonical BookStack index for public Corrently energy API documentation.
- [Public Corrently APIs](https://corrently.io/books/corrently-energy-apis/page/offentliche-corrently-apis): overview of public API families and links to the technical console documentation.
- [Corrently APIs shelf](https://corrently.io/shelves/corrently-apis): thematic collection for API-related books and implementation resources.
- [Fair Use Policy](https://corrently.io/books/stromdao-gmbh/page/fair-use-policy): usage policy and rate-limit guidance for public API access.

## API reference pages

- [CO2 Advisor API](https://console.corrently.io/co2advisor.html): CO2-intensity forecast and load-shifting guidance by location.
- [CO2 Meter API](https://console.corrently.io/co2meter.html): CO2-emission tracking for energy use.
- [Energy Schedule API](https://console.corrently.io/schedule.html): schedule-oriented energy application support.
- [GrünstromIndex API](https://console.corrently.io/gsi.html): regional green-electricity forecast data.
- [Marketdata API](https://console.corrently.io/marketdata.html): electricity market data and forecasts.
- [PHEV Charge Or Fuel API](https://console.corrently.io/phevChargeOrFuel.html): decision support for plug-in hybrid charging versus fuel use.
- [Photovoltaic Generation Forecast API](https://console.corrently.io/pvgeneration.html): photovoltaic generation forecast data.
- [Strommix API](https://console.corrently.io/strommix.html): German electricity generation mix data.
- [Corrently Token API](https://console.corrently.io/token.html): Corrently API authentication token documentation.

## Domain-specific documentation

- [Marktdaten - Strompreis](https://corrently.io/books/marktdaten-strompreis): regional electricity price and market-data documentation.
- [Öffentlicher Service: Marktdaten API](https://corrently.io/books/marktdaten-strompreis/page/offentlicher-service): public marketdata endpoint explanation and example usage.
- [GrünstromIndex](https://corrently.io/books/grunstromindex): regional green-electricity forecast concept and documentation.
- [Energy Application Framework DE](https://corrently.io/books/energy-application-framework-de): German documentation for the STROMDAO Energy Application Framework.
- [Energy Application Framework source](https://github.com/energychain/STROMDAO_EAFs): public source reposi
…

Related sites

Other listed sites in Developer tools. See the whole category →

Machine-readable: GET /v1/resolve?q=corrently.io · GET /v1/domain/corrently.io · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for corrently.io:
1. POST https://agentwebmap.com/v1/sites/corrently.io/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://corrently.io/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/corrently.io/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/corrently.io).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.