saascode
climate, energy & agtech·run 101 · May 2026

GridReceipt

A normalized multi-operator grid-intensity API that emits signed, versioned receipts for sub-hourly energy and emissions calculations.

Genesis score7.69/10
Make GridReceipt real.0/500
500 more votes and GridReceipt is authorized for build.
0%500 to authorize
Backing is the vote. When an idea crosses 500, we pull it into the build pipeline and ship it for real — the votes decide what gets built next, not an editor.
The opportunity
4Grid402 operators
$0.005Observed API call
5 minUpdate granularity
The case

Developers can obtain grid mix and carbon-intensity data, but audit work begins when someone asks which operator record, interval, normalization rule, and software version produced a reported number. A new open-source API validates developer demand while covering only four operators. The opening is not another chart: it is broader normalization plus a receipt that makes each answer reproducible, while leaving each regulatory program's accounting sufficiency to qualified reviewers.

Who pays — and why

The engineering, sustainability-data, or product leader building hourly energy matching, carbon reporting, procurement, or border-adjustment workflows across more than one grid operator.

Market signal$0.005 per callobserved Grid402 call price, set your own
What it unlocks
One versioned schema across grid operators with visible source and freshness differences
Reproducible calculations bound to interval data, methodology, code version, and signing identity
Program-specific exports assembled from receipts without declaring regulatory acceptance
How Genesis scored it
7.69across seven criteria
tension 8temporal 9blindspot 5buyer 8leverage 9convergence 5why-not 8
9
Temporal window

Multiple emerging reporting programs create current demand for interval-level evidence.

9
Asymmetric leverage

Connectors, schemas, signatures, and exports scale primarily through code.

5
Convergence

Several links support the family, but the stored score remains modest.

Why it scored well

A real open-source primitive, sub-hourly data demand, and a concrete reproducibility mechanism support a highly leveraged developer product.

What's holding it back

The regulatory-fit claims are not independently validated, direct pricing evidence is limited, source licenses and coverage vary, and no structural incumbent handicap is established.

Signals detected5 sources crossed
Signalgithub.com/carbonsteward/grid402

SignalGrid402 README

SignalSigstore and npm project research

Signalcompetitor scan carried in Genesis

SignalGrid402 comparison

Direction briefgridreceipt.md
gridreceipt.md
Want this pointed at your vertical?Point Genesis at your own market and constraints — it invents adjacent, fork-ready ideas, private to you before they hit the public feed.

Discussion

?

No comments yet — be the first to weigh in.