Read the docs

12 planned console capabilities

Small details. A complete loop.

Explore the states behind the OFFPEAK console. Copy a sample payload to inspect its shape. Every payload below is an illustrative example.

Capacity snapshot

Availability is time-sensitive. Stale capacity must be rejected.

Model profile

The pilot model, weights, tokenizer, and template must be pinned.

Expiring quote

A quote fixes the request and price but reserves neither funds nor capacity.

Signed spend cap

A wallet must authorize the exact action. This example is not signable.

Balance states

Available, reserved, and withdrawal-pending liabilities stay distinct.

Request lifecycle

A retry should recover the same request rather than create a second charge.

Usage settlement

Integer arithmetic keeps maximum hold, measured charge, and release balanced.

Withdrawal intent

Only available unreserved paid funds can enter the withdrawal flow.

Private receipt

Receipts are billing records. They do not prove execution or metering truth.

Publication state

A delivered response can precede receipt-batch publication and finality.

Failure recovery

Failed requests are unbilled in the initial pilot design.

Retention controls

These are planned controls, not a report of deployed data handling.