17trust / 100
Energy Carbon Intensity
by GridPulse in AI models & inference
x402 APIFailing, checked 4 h ago
Live grid carbon intensity, deterministic. Answers "how clean is the grid right now", "gCO2 per kWh in Germany", "cleanest hour to run a job today". Current intensity + forward curve (to 48h) + cleanest and dirtiest slots, from NESO (GB national + 14 DNO regions) and energy-charts/Fraunhofer ISE (DE FR NL BE AT ES IT NO). No LLM, no key. Pair with /api/energy/compute-window for full job scheduling.
GET https://gridpulse.theaslangroupllc.com/api/energy/carbon-intensity
Last 30 days
All checks passedSome failedAll failedNot checked
- Uptime
- 0.0%
- Response time
- - typical, - slowest 5%
- Last check
- 4 h ago: Amount "0.01" is not in atomic token units
- Next check
- any minute now
How to call it
# See the payment challenge (nothing is charged)
curl -i -X GET "https://gridpulse.theaslangroupllc.com/api/energy/carbon-intensity?hours=24®ion=DE"import { wrapFetchWithPayment } from "@x402/fetch";
import { x402Client } from "@x402/core/client";
import { ExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";
const client = new x402Client().register(
"eip155:8453",
new ExactEvmScheme(privateKeyToAccount(process.env.AGENT_KEY)),
);
const pay = wrapFetchWithPayment(fetch, client);
// Not sure it's safe to pay? Preflight it first for $0.005:
// GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fgridpulse.theaslangroupllc.com%2Fapi%2Fenergy%2Fcarbon-intensity
const res = await pay("https://gridpulse.theaslangroupllc.com/api/energy/carbon-intensity?hours=24®ion=DE");
console.log(await res.json());Example input
{
"hours": "24",
"region": "DE"
}Example output
{
"deterministic": true,
"next_hours": {
"avg_gco2_per_kwh": 103,
"cleanest": {
"gco2_per_kwh": 41,
"start": "2026-07-15T02:30:00.000Z"
}
},
"now": {
"gco2_per_kwh": 96,
"start": "2026-07-14T15:30:00.000Z"
},
"region": "UK"
}Security scan
- No findings. We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.
Recent checks
| When | Result | HTTP | Time | Price |
|---|---|---|---|---|
| 4 h ago | Amount "0.01" is not in atomic token units | 402 | 4.0 s | $0.01 |
| 9 h ago | Amount "0.01" is not in atomic token units | 402 | 235 ms | $0.01 |
| 13 h ago | Amount "0.01" is not in atomic token units | 402 | 225 ms | $0.01 |
| 17 h ago | Amount "0.01" is not in atomic token units | 402 | 423 ms | $0.01 |
| 21 h ago | Amount "0.01" is not in atomic token units | 402 | 235 ms | $0.01 |
| 25 h ago | Amount "0.01" is not in atomic token units | 402 | 426 ms | $0.01 |
| 29 h ago | Amount "0.01" is not in atomic token units | 402 | 280 ms | $0.01 |
| 33 h ago | Amount "0.01" is not in atomic token units | 402 | 239 ms | $0.01 |
| 38 h ago | Amount "0.01" is not in atomic token units | 402 | 264 ms | $0.01 |
| 41 h ago | Amount "0.01" is not in atomic token units | 402 | 416 ms | $0.01 |
| 46 h ago | Amount "0.01" is not in atomic token units | 402 | 1.1 s | $0.01 |
| 2 days ago | Amount "0.01" is not in atomic token units | 402 | 271 ms | $0.01 |
| 2 days ago | Amount "0.01" is not in atomic token units | 402 | 486 ms | $0.01 |
| 2 days ago | Amount "0.01" is not in atomic token units | 402 | 253 ms | $0.01 |