Grid Accord

Product

Power-Service Evidence API

You send a bounded description of a proposed load. You get one envelope back, on the loopback API, the local MCP tool, or the demo on this page's sibling route. The envelope has a status, the comparisons that could be run, the claims they rest on, the obligations already visible in public documents, and the evidence still missing.

Input

The request names a schema version and an execution mode. It can name the utility and say whether that name is only the applicant's assertion, a described document, or unknown. It can state new or incremental megawatts, a load factor with an explicit percent or fraction, and a peak interval of 15 minutes or 30 minutes. It can list a short ramp and a requested service date. It can say the zone is unknown, which is the honest default, or name a zone only as an authoritative confirmation someone else already made.

It does not take a street address, an account number, a card, a signed agreement, or a free-form instruction. A county is not turned into a zone.

Output

Every result, including a refusal, uses the same envelope. capacity_status is not_determined. The service date, if you sent one, is labeled requested. Billing is off and charged units are 0. A request that asks for production mode returns production_disabled. Paid API access is coming soon.

Coverage

The screen covers US utilities one state at a time. Coverage is the live list. An approved ruleset is applied. A pending, appealed, not-yet-effective, or contract-only file is named and is not a finished tariff. A utility with no file returns not_covered. The Florida hub is an example.

Not the utility's process

The utility remains the authority for capacity and for a service commitment. A completed screen is a comparison of stated inputs with the registered rule. It is not an eligibility certificate.