Receipts & Payouts
How B3IQ records signed receipts, metered usage, owner earnings, and public-safe settlement evidence.
B3IQ receipt and payout surfaces connect completed work to metered usage and public-safe settlement commitments.
Receipt role
A receipt is signed evidence of completed work. It can bind:
- Node identity.
- Model identity.
- Usage totals.
- Settlement 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.
An accepted receipt records a usage row and stands as signed evidence of the work. It is an accounting record, not a charge: hosted inference on your own machines is free.
Jobs that fail, timeout, or never produce accepted receipt evidence record the failure and settle nothing.
Owner earnings
A served request is metered and receipted; it does not itself pay the machine's owner. Owner earnings are a revenue share on what the machine makes under B3IQ's offtake arrangements, accrued to that machine's deal ledger and paid in USD.
B3IQ batches node payout rows into public-safe payout roots, publishes payout batch proof logs, and finalizes batches from real settlement receipt evidence. See Receipts and settlement for the protocol view.