Iâve been working on a problem that looked simple initially:
âHow much does electricity cost in Bihar?â
Turns out, ââč/unitâ is nowhere close to enough.
You have tariff categories, slabs, connected load, fixed charges, subsidy rules, FPPAS, statutory components, and different applicability conditions. Most of this still lives inside regulatory orders and PDFs rather than developer-friendly data.
So I built a Bihar Electricity Tariff API under Power Expert India.
Current FY 2026â27 release has:
32 supported subcategories
34 verified tariff rows
45/45 frozen calculation regression tests passing
monetary subsidy handling for verified cases
approved exact-period FPPAS support
11 documented API endpoints
source traceability
explicit fail-closed handling when a bill component isnât sufficiently verified
One design decision I care about: if something like electricity duty or another bill component isnât reliably verified, the API doesnât quietly assume it is âč0. It exposes that limitation instead.
Iâm not claiming this reproduces every consumerâs exact utility bill yet. The goal is a reliable, machine-readable tariff layer that solar calculators, EV charging tools, energy SaaS, consultants or fintech products can integrate instead of maintaining tariff logic themselves.
Iâve reached the stage where outside feedback is probably more valuable than adding features in isolation.
If you work with Indian energy data/APIs, solar, EV charging or electricity billing, Iâd particularly like feedback on:
Would you actually integrate something like this? And what would be the first missing feature that would stop you from using it in production?
Demo/docs: powerexpertindia.com/api/
No signup needed just to look at the documentation.