Product preview information

This page explains the status and proposed boundaries of OFFPEAK. It is not a set of adopted commercial service terms. Paid-service terms remain pending.

The website and console do not connect to live inference, custody, payment, or receipt-verification services. Demo interactions use illustrative records.

The current product description follows the supplied OFFPEAK version 1.0 overview and build specification dated October 12, 2026.

The proposed pilot targets one approved open-model revision, one region, vetted GPU capacity, one settlement token, EOA wallets, and non-streaming text.

The model license, supplier rights, weights revision, tokenizer, chat template, and workload quality must be established before paid use.

Extraction, classification, and summarization are candidate workloads. Each application must evaluate quality on representative inputs; no universal model performance is promised.

The proposed price responds to available serving capacity with a measured cost floor. A quote is not a guarantee that capacity will remain available until acceptance.

The planned quote lifetime is 30 seconds. It binds the prompt, model profile, output limit, rates, wallet, asset, and maximum charge. Changing the prompt requires a new quote.

The wallet signs a specific request and spending ceiling. Browser session access alone cannot authorize funds to be spent. The preview does not request wallet signatures.

The proposed P0 design uses custodial prepaid balances. OFFPEAK controls the pooled treasury and processes withdrawals; the registry does not hold customer funds.

Acceptance reserves funds and capacity before dispatch. Available, reserved, and withdrawal-pending amounts remain separate so the same funds cannot be spent twice.

The service is designed to persist a complete result before charging measured usage once. It releases the unused portion of the maximum reserve.

Failed requests are unbilled in the initial pilot design. Uncertain worker or chain outcomes require recovery and reconciliation rather than blind retries.

Available, unreserved paid funds are intended to return to the same owner wallet on the same network in the same token. This is not a bridge or fiat cash-out route.

The actual production asset configuration, identity, decimals, transfer behavior, and finality semantics must be verified. Mock examples are not production prices.

A signed receipt and committed batch can support independent checks of the billing record. They do not prove GPU execution, metering truth, or model-answer correctness.

The brief proposes no prompt logging, 24-hour encrypted result retention, and 90-day metadata/proof retention by default. Production policy and evidence remain pending.

Direct x402, streaming, tool calls, delegated budgets, broader suppliers, confidential serving, and stronger execution attestations are outside the initial pilot scope.

$OFPK is not required for the initial pilot. Issuance, allocation, utility, and launch remain undecided; this preview makes no token, yield, or redemption offer.

Third-party names identify intended technical compatibility only. The website does not imply affiliation or a completed integration.

The production operator, jurisdictions, custody obligations, supplier rights, signer controls, liability backing, and recovery reviews must be resolved before paid access.

The product guide and source PDFs describe the intended system. A working contact route and formal service terms must be supplied before commercial launch.

Product guide ↗ · Product overview PDF ↗ · Build specification PDF ↗