Receipts & Payouts
How B3IQ records signed receipts, usage rows, node payout rows, and settlement evidence.
B3IQ receipt and payout surfaces connect completed work to metered usage, node payout rows, and public-safe settlement commitments.
Receipt Role
A receipt is signed evidence of completed work. It can bind:
- Node identity.
- Model identity.
- Usage totals.
- Payout rate references.
- Receipt hash.
- Optional private-job
tee_attestation_hashcommitment.
Public receipt payloads must not expose raw prompts, outputs, customer tokens, exact private routes, raw request logs, local URLs, or raw TEE quotes.
Accounting Flow
Customer APIs
| Method | Path | Purpose |
|---|---|---|
| GET | /v1/api/billing/jobs/{job_id} | Job and settlement state for a private job |
| GET | /v1/api/receipts/{receipt_hash} | Receipt lookup by hash |
The billing/* reads authenticate with X-B3IQ-Customer-ID and
X-B3IQ-Customer-Token. Receipt lookup by hash is public. See
Usage & Quotas for the metering model.
Settlement Determinism
Routed work should be deterministic around completion, payout accrual, and timeout.
Accepted receipts record a usage row and, for B3IQ-directed workloads on approved machines, create node payout evidence.
Jobs that fail, timeout, or never produce accepted receipt evidence accrue no payout and settle nothing.
Payout Settlement
B3IQ batches node payout rows into public-safe payout roots. The settlement pilot publishes payout batch proof logs and lets the control plane finalize batches from real settlement receipt evidence.
See Receipts and settlement for the protocol view.