Jouli CockpitThe rebate data, with its corrections on show.
Australian solar and electrification rebates, resolved per postcode, with a public record of every correction we have made. It is the dataset the Jouli engine prices against, published as a feed.
The rebate data, and what we got wrong.
Most rebate tables are a snapshot somebody pasted and stopped maintaining. Schemes change mid-quarter, tiers step down on dates that are easy to miss, and a figure that was right in August quietly becomes wrong in October. The feed is the dataset Jouli itself prices against, which means it is maintained because our own quotes depend on it.
By postcode, not by capital city
Certificate zones come from the full CER table of 137 postcode ranges. Where a postcode is missing the feed falls back to the state and says that it did.
A public ledger
Every correction is published with the date and what changed. A feed that silently rewrites history is worse than no feed, because you cannot tell which quotes were built on the old number.
Federal and state
STC and the Cheaper Home Batteries Program with its scheduled step-downs, plus the state schemes we have verified. Where we have not verified a scheme, it is absent rather than guessed.
What it is not
It is not legal or financial advice, it is not a guarantee of eligibility, and it does not replace reading the scheme. It is a maintained dataset with its mistakes on show.
Free to read. Paid if you depend on it.
The data is public. What costs money is depending on it in production: higher request limits, a freshness commitment, webhooks when a figure changes, and access to history so you can tell what a quote was built on.
Read it
Public endpoint, rate limited, no commitment on freshness. Fine for checking a number or building something small.
Depend on it
Higher limits, a freshness commitment, change webhooks and history. Included with the Retailer plan. Plus GST.
Billing for the feed is arranged by hand today — there is no self-serve checkout yet, and the commercial tier is gated on a shared key rather than a per-customer one. Both are on the list; neither is pretended otherwise.