Carbon-intensity & grid data for DER & VPP devices.
Distributed energy devices - batteries, inverters, EV chargers, demand-response controllers - act on grid signals, but a bare carbon or price number arriving over the wire is unverifiable. Dynamic Feed returns signed grid carbon-intensity and grid data over one keyless call, so a DER or VPP device can verify the signal against a published key on-device before it dispatches.
The call
One keyless call returns the signed grid signal a DER/VPP device verifies before dispatch:
curl -s -X POST https://dynamicfeed.ai/v1/batch \
-H 'Content-Type: application/json' \
-d '{"calls":[{"tool":"grid_carbon","args":{"region":"nsw"}}]}'Sample response
{ "results": [ { "tool": "grid_carbon", "ok": true,
"data": { "region": "nsw", "carbon_intensity_g_per_kwh": 612, "derived": true,
"method": "derived from live AEMO dispatch (not an official measurement)",
"freshness": { "state": "live", "age_seconds": 240 } } } ],
"signature": { "alg": "Ed25519", "key_id": "df-ed25519-...", "sig": "..." } }Why live data
Virtual power plants and DER fleets coordinate thousands of devices on grid signals, and those devices should be able to verify a signal rather than trust whatever arrives on the wire. Dynamic Feed returns signed grid carbon-intensity (AU, derived from live AEMO dispatch) and US electricity-grid data (EIA) over one keyless call, each datapoint Ed25519-signed and carrying its source, method and freshness - so an inverter or battery on a Pi-class controller verifies the record bytes on-device and can refuse stale data. The AU figure is explicitly derived, not an official emissions measurement, and the tool states that in its own fields. The signature establishes integrity and attribution under the published key; it does not independently prove time, objective truth, or safety. Your device's own stack owns every decision. Full integration guide: dynamicfeed.ai/iot.
Use it for
- Dispatch a battery or shift a load on a signed carbon/grid signal a device can verify
- Refuse to act on a stale signal by reading the freshness envelope on every datapoint
- Coordinate a VPP on one keyless feed instead of an unsigned scraped number
- Keep a verifiable record of the grid signal a device acted on for settlement disputes
FAQ
Is the carbon-intensity figure official?
The AU grid_carbon value is derived from live AEMO dispatch data - an estimate, not an accredited emissions measurement - and the tool labels it derived in its own fields. US energy_grid data is sourced from the EIA. Always read the method field.
Why does a device need a signature on a grid signal?
So it can act on data it can verify instead of trusting the connection. The device checks the Ed25519 signature against the published key on-device; a stale, swapped or tampered value fails the check.
Is there finance/price data?
These feeds carry grid carbon-intensity and grid operations data, not electricity market prices. We keep market-price data off the public surface.