ϟ INSTANTMEGAWATT
API PUBLICATION · PRE-RELEASE

Integrate by contract, scope and evidence.

The API boundary is organization-scoped, role-authorized, idempotent and provider-neutral. Activation requires a reviewed data contract and sandbox validation.

AUTHORIZATION

Authentication is not permission.

Server policy resolves organization membership, role, consent scope and resource ownership. Client-side controls never grant access.

RESOURCE MAP

Staged interface catalog

ResourcePurposeStatus
GET /meIdentity, memberships and role contextImplemented
POST /charging-requestsSubmit fleet demand with idempotencyFoundation implemented
GET /dashboardOrganization-scoped operationsFoundation implemented
POST /support-casesCreate auditable support caseFoundation implemented
Provider event ingressSigned, deduplicated event receiptActivation gated
Telemetry observationsFreshness-checked operational inputsPartner contract required
REQUEST SEMANTICS

Charging-request contract

PARTNER LIFECYCLE

From candidate to production

Data contractResources, purpose, direction and retention.
ConsentIdentify who authorizes each scope.
SandboxTest stale data, replay and revocation.
Limited pilotConstrain assets, geography and actions.
Evidence reviewVerify logs and runbooks.
ActivationPromote explicit, revocable scopes.