India Electricity Tariff & Bill Verification API

Verified Indian electricity billing & regulatory intelligence API. State-wise tariff calculations, evidence traceability, ToD/FPPAS/FAC, solar/net-metering, bill-impact analytics and fail-closed regulatory updates.

PEI turns Indian electricity regulation into executable, source-traceable billing infrastructure.

API V1.2.0 Bihar · Production Maharashtra LIVE · MSEDCL Complete Payable V2 Gujarat live · 11-licensee statewide Telangana commercial verification · Verified Shadow Rajasthan · Verified Shadow Odisha · Verified Shadow 4 MH licensees routed 11 GJ licensees routed Tariff calculation + bill verification

View API Documentation Request Access

One central place for the PEI API

This portal combines release information, integration guidance, client onboarding, security requirements, legal terms and privacy disclosures. Technical endpoint details remain in the versioned API documentation and OpenAPI specification.

The production API remains under /v1/. This portal is synced to API V1.2.0 and Controller V2.2.8, but it does not execute or modify tariff calculations.

Coverage and release status

Bihar Production released

Maharashtra Verified base-tariff production

Gujarat Live · Guarded Residential V1

4 MH licensees routed

4 GJ DISCOMs routed

32 Bihar verified subcategories

34 Bihar verified tariff schedule rows

V1.2.0 Public API version

Bihar release ID: BR-2026-27-VERIFIED-STRICT-BASE-V1 · Runtime gates: 29/29 · Controller: V2.2.8

Maharashtra licensee coverage
MSEDCL Complete Payable V2 is production-active for approved profiles. TPC-D, AEML and BEST remain routed through the Maharashtra statewide verified base-tariff architecture. Verified base-tariff calculations are available through the public API for the released statewide scope. FAC/FPPPA, payable ToD and other bill components remain explicit, fail-closed or non-payable unless the applicable verified source and billing context are available.

Gujarat statewide verified coverage
Gujarat Electricity Tariff API 2026-27 →
FY 2026-27 coverage is live through POST /v1/calculate for DGVCL, MGVCL, PGVCL and UGVCL. Current scope covers DOMESTIC_URBAN and DOMESTIC_RURAL postpaid residential consumers with verified energy slabs and connected-load fixed charges. FPPAS, ToU, subsidy, electricity duty/taxes, prepaid and unresolved BPL/category semantics remain excluded or fail-closed.

Rajasthan Verified Shadow V1 — Public Calculation Live
FY 2026-27 Rajasthan coverage is live through POST /v1/calculate across 41 verified districts with explicit routing for JVVNL, AVVNL and JDVVNL. Release ID: RJ-2026-27-VERIFIED-SHADOW-V1. District/licensee mismatches fail closed and automatic licensee fallback is disabled. FPPAS and electricity duty remain verified shadow components; subsidy and regulatory-charge eligibility remain fail-closed where context is incomplete. Production payable remains disabled. Solar/net-metering is planned for Rajasthan V1.1+.

What verification status means
Released calculations and verification workflows use verified regulatory data and deterministic arithmetic. The API does not claim to reproduce an exact current utility bill. Bihar monetary subsidy, current FPPAS/FPPPA/FPPCA, Maharashtra FAC/FPPPA, Telangana current-period FCA/FPPAS, payable ToD where not explicitly released, statutory levies, taxes, duties, meter rent, arrears, rebates and other bill components remain excluded or fail-closed unless a response explicitly states otherwise.

Built for energy products, not tariff-table scraping

Solar platformsUse verified base electricity cost as an input to savings and proposal workflows.

Odisha Verified Shadow V1.0.0 — Public Calculation Live FY 2026-27 verified shadow calculation across OD_TPCODL, OD_TPNODL, OD_TPWODL and OD_TPSODL with explicit licensee routing, domestic calculation and gross-metering support. Gross-metering mechanism and generation quantity accounting are verified; generic OERC gross FiT remains under regulatory hold, so monetary export settlement and production payable activation remain disabled.

Telangana Commercial Verification — Live in Verified Shadow FY 2026-27 commercial electricity bill verification is live through the authenticated API using deterministic tariff components, actual-vs-expected comparison and fail-closed regulatory handling. Current payable completion remains held pending a verified current-period FCA/FPPAS regulatory rate source.

Jharkhand V1 — Live Verified Tariff Estimation Jharkhand FY 2026-27 is live through the authenticated API in VERIFIED_TARIFF_ESTIMATION_V1 mode with location-aware, fail-closed routing. JBVNL, TSL and TSUISL are active verified estimation paths; DVC-JH is active with component holds. SAIL-BSL remains held-unverified and TPCL is excluded from consumer retail routing. Current FPPAS and electricity duty remain HELD_UNVERIFIED, so complete payable and production payable remain disabled.

EV charging productsEstimate charging electricity cost with state, licensee and category-aware tariff logic.

Energy softwareReplace hard-coded tariff tables with structured, source-traceable responses.

Consultants & analyticsRun repeatable tariff scenarios with explicit calculation limitations.

Need Power Expert India tariff API access? Request a controlled multi-state pilot. Pricing is discussed against required states, routes, traffic and support scope rather than hidden behind an unlimited-use claim.

Request Pilot / Pricing

API Pricing

Start with a controlled pilot and move to production as your traffic, state coverage and support requirements grow.

Pilot — ₹0 14-day controlled pilot · multi-state tariff testing · dedicated API key · verified tariff endpoints · evidence/reference access · integration testing · no production SLA.

Request Pilot

Starter — ₹4,999/month 1 released state · production API access · calculate, categories, licensees and reference endpoints · standard rate limits · email support.

Choose Starter

Growth — ₹14,999/month Up to 3 released states · higher request and rate limits · evidence and traceability · usage visibility · priority support · SDK access.

Choose Growth

Business — ₹34,999/month All generally released states · higher production limits · IP allowlisting · tariff-change notifications · priority onboarding · SDK + MCP access.

Choose Business

Enterprise — Custom Typically from ₹75,000/month · custom traffic and state rollout · SLA · dedicated support · audit/evidence requirements · custom integration terms.

Contact Enterprise

Usage policy: Plans use controlled quotas and rate limits. Overage is not silently billed; capacity upgrades are agreed before limits are increased.

Quick start

Production requests use HTTPS and a dedicated API key supplied through a supported header. Query-string API keys are rejected.

Header authentication

X-API-Key: pei_live_... Authorization: Bearer pei_live_...

Health request

curl -sS \ -H "X-API-Key: YOUR_API_KEY" \ "https://powerexpertindia.com/v1/health"

Capability discovery

curl -sS \ -H "X-API-Key: YOUR_API_KEY" \ "https://powerexpertindia.com/v1/capabilities?state_code=TS"

Tariff calculation & bill verification

curl -sS \ -X POST \ -H "Content-Type: application/json" \ -H "X-API-Key: YOUR_API_KEY" \ -d '{ "state_code": "BR", "subcategory_code": "BR_DS_II", "energy_units": 126, "connected_load": "1", "billing_days": 30 }' \ "https://powerexpertindia.com/v1/calculate"

billing_days is optional and backward compatible. Executable values are currently 25, 30 and 40 only. For supported Bihar domestic calculations, POST /calculate may evaluate the frozen entitlement contract and apply the verified monetary subsidy core. An approved exact-month FPPAS version may also affect the verified monetary composition when its recovery-month and billing conditions match. The response preserves the base-tariff result separately and exposes final_payable, electricity-duty and ancillary-charge status. Resolve exact category codes and required fields through GET /categories before calculation.

Routes and least-privilege scopes

Route	Method	Scope	Purpose
`/health`	GET	`health:read`	Service, version and release status
`/capabilities`	GET	`health:read`	State-aware enabled and blocked calculation features
`/states`	GET	`states:read`	Released states
`/categories`	GET	`categories:read`	Verified categories and required inputs across supported states; licensee-specific states require explicit routing context
`/tariffs`	GET	`tariffs:read`	Verified tariff rows across supported state and licensee scopes
`/subsidy-entitlement`	GET	`tariffs:read`	State-specific entitlement contract where available; monetary application is handled separately by POST /calculate
`/fppas-periods`	GET	`tariffs:read`	Verified FPPAS period evidence; only an approved exact-month version may be applied by POST /calculate
`/sources`	GET	`sources:read`	Public source traceability
`/calculate`	POST	`calculate:write`	Tariff calculation and bill-verification workflows across supported multi-state scopes, with state and licensee-specific routing, evidence traceability and fail-closed handling for unresolved regulatory components. Verified Shadow and Verified Tariff Estimation capabilities are exposed explicitly by state, including Jharkhand VERIFIED_TARIFF_ESTIMATION_V1.
`/solar-savings`	POST	`calculate:write`	Verified solar before/after tariff comparison where supported
`/category-resolver`	POST	`calculate:write`	Resolve caller-declared tariff context to a verified category where supported

Recommended integration flow

1. Confirm service Call /health and validate API and release identity.

2. Read capabilities Call /capabilities before enabling bill components.

3. Resolve catalogue Use /states and /categories.

4. Inspect evidence Use /tariffs, /sources and the verified evidence/contract routes.

5. Calculate Send validated inputs to /calculate; consume final_payable and honour all unresolved-component disclosures.

6. Preserve and monitor Retain request metadata; track 401, 403, 422, 429 and 5xx.

MCP Server V1

Connect AI agents and MCP-compatible clients directly to the tariff, bill-verification and regulatory-intelligence API without duplicating state-specific electricity logic.

Endpoint: https://powerexpertindia.com/api/mcp/index.php
Transport: Streamable HTTP
Authentication: X-API-Key: YOUR_API_KEY or Authorization: Bearer YOUR_API_KEY
Tools: health, capabilities, states, categories, tariffs, sources, calculate, solar_savings

MCP endpoint: https://powerexpertindia.com/api/mcp/index.php Header: X-API-Key: YOUR_API_KEY Transport: Streamable HTTP

MCP is a thin adapter. Tariff calculation, bill verification, regulatory evidence, release controls and billing logic remain server-side in the Power Expert India API.

MCP agent contract

Step	Purpose
`initialize`	Establish the MCP session and negotiate the client/server connection.
`tools/list`	Discover available PEI tools and their input schemas.
`tools/call`	Invoke a PEI tool such as capabilities, states, tariffs, sources or calculate.
`capabilities`	Read state-specific production, Verified Shadow and payable-hold status before monetary execution.

Fail-closed agent rule
Agents must not infer production-payable status from state availability alone. Use states and capabilities first and honour production_payable, verification status and unresolved-component disclosures. Authentication failures return 401, insufficient scopes/state access return 403, and invalid request contracts fail explicitly rather than falling back to another state or tariff.

Credential and security requirements

Store the key in a server-side secret manager or protected environment variable.
Do not expose a production key in browser JavaScript, mobile bundles or public repositories.
Never put a key in a URL, screenshot or support message.
Use the smallest required route scopes and approved state access.
Configure exact browser origins where CORS access is required.
Request immediate rotation after suspected exposure.

The protected registry stores SHA-256 key hashes. Dedicated API key plaintext is not intentionally written to request logs.

Rate limits and retries

The default production profile is 60 requests per minute per key with a 20-request burst allowance within 10 seconds. Limits are registry-driven and may differ by client plan.

Respect 429 and the Retry-After header.
Use bounded exponential backoff and request deduplication.
Do not retry validation or authentication errors without correcting the request.
Use caching for stable catalogue responses where appropriate.

Client testing checklist

Valid header authentication returns the expected response.
Missing credentials return 401.
Query-string credentials are rejected.
Unapproved scopes or states return 403.
Malformed JSON and invalid field types return documented errors.
Omitting billing_days preserves backward-compatible base calculation.
Unsupported subsidy billing days fail closed with 422.
Historical FPPAS percentages are never applied as the current bill rate.
The client respects rate-limit headers.
Money arithmetic uses integer paise values where provided.
The response request_id is retained for troubleshooting.
Consumer-facing output preserves all monetary-scope limitations.

Required consumer-facing disclosure

Applications displaying an estimated amount should clearly distinguish it from an official utility bill.

Suggested wording:

“This estimate uses the verified tariff components currently released for the selected category. Any subsidy entitlement shown is units-only and does not reduce the amount. Historical FPPAS evidence is not a current applied rate. Monetary subsidy, current fuel or power-purchase adjustments, taxes, duties, meter rent, arrears, rebates and other bill components may change the final payable amount.”

Request API access

Use the secure API access request form for pilot, pricing, production or partnership discussions. Tell us the states, licensees, routes and expected traffic you need. Do not include an API key or consumer account data.

Request Pilot / Pricing

Organisation or project Name of the client application or business.

Technical contact Person responsible for integration and incidents.

Use case Bill estimation, EV, AC, solar, analytics or another approved use.

Required routes Only the scopes genuinely needed by the client.

Expected traffic Typical and peak requests per minute.

Browser origins Exact HTTPS origins where browser CORS is required.

Access requests are manually reviewed. Approval does not automatically generate a key. Dedicated keys are created through the protected PEI key management console after scope and security review.

Maharashtra — State-Specific Developer Example

Explore one state-specific FY 2026–27 verified tariff implementation for MSEDCL, TPC-D, AEML and BEST using production-tested payloads.

Phase 1 scope: FAC/FPPPA/FPPAS and Time-of-Day adjustments are not applied to the payable total. Subsidy, electricity duty, taxes/cess, arrears, penalties and miscellaneous bill components are excluded. This example uses verified tariff components. Exact current utility-bill reproduction is claimed only when every required billing component is explicitly verified and released.

Choose licensee

MSEDCL Verified production payload

Request JSON

cURL

Authentication: replace YOUR_API_KEY with the API key issued to your organisation. Never place API keys in query strings or public source code.

View API Documentation Request API Access

Integrate Power Expert India

Use the same electricity tariff, bill-verification and regulatory-intelligence layer through REST, SDKs or MCP. Tariff logic, evidence, verification status and release controls remain server-side.

REST APIDirect production integration using the documented /v1 endpoints and OpenAPI contract.

JavaScript + Python SDKsThin client libraries for authentication, reference data, tariff calculation, bill verification and Solar Savings workflows.

MCP Server V1Connect MCP-compatible AI agents using Streamable HTTP and the same API key controls.

Regulatory evidence & verificationResponses preserve component-level verification status, source traceability and explicit unresolved-component disclosures.

REST: https://powerexpertindia.com/v1/ MCP: https://powerexpertindia.com/api/mcp/index.php OpenAPI: https://powerexpertindia.com/v1/openapi.json

Start a 14-day API pilot

Documentation, integration and policies

API Documentation Human-readable endpoint and response guide JavaScript SDK V1 Thin API client for authentication, health, states, categories, tariffs, sources and calculations JavaScript Examples Multi-state calculation examples across released, verified-shadow and verified-estimation scopes, including Rajasthan Verified Shadow V1, Odisha Verified Shadow V1.0.0 and Jharkhand VERIFIED_TARIFF_ESTIMATION_V1 Python SDK V1Dependency-free Python client for tariff calculations, reference endpoints and Solar Savings Python ExamplesMulti-state integration examples across released, verified-shadow and verified-estimation scopes, including Odisha Verified Shadow V1.0.0 and Jharkhand VERIFIED_TARIFF_ESTIMATION_V1 MCP Server V1 MCP 1.4.0 · Streamable HTTP MCP endpoint: health, capabilities, states, categories, tariffs, sources, calculate and solar_savings. Jharkhand V1 discovery is live in VERIFIED_TARIFF_ESTIMATION_V1 mode with production payable disabled. Authenticate with X-API-Key or Bearer token. OpenAPI 3.1 Machine-readable API contract Bihar State Client Handover Pack Quick start, 11 API routes, payable contract, pilot checklist and acceptance tests Terms of Use Acceptable use and commercial framework Privacy & Logging Operational metadata and retention disclosure Health Endpoint Authenticated production health check Power Expert India Main platform and contact channel

The earlier standalone onboarding page is superseded by this central portal. It may be redirected here after this page is verified.