Receipts & Payouts
How B3IQ separates owner inference records, optional hourly earnings, current payments and historical settlement evidence.
B3IQ records work and usage evidence separately from optional capacity earnings. Inference on your own machines is free and produces no per-request payout. Historical request-payout proof batches do not describe the current hourly rental settlement process.
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.
Completion and usage evidence
Read completion and failure evidence separately from charges or owner payouts.
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, time out, or never produce accepted receipt evidence record the failure. Owner inference produces no rental income on success or failure.
Owner earnings
A served request is metered and receipted; it does not pay the machine's owner. Optional Earn mode offers eligible whole-machine capacity to external GPU marketplaces by the hour. Only rented capacity generates income; demand is not guaranteed. Under Managed Hosting, the owner receives 85% of gross rental revenue before hosting costs. The machine's inference and SSH access are unavailable during Earn.
Earnings are denominated in USD. Estimates, accrued revenue and paid funds are separate records; settlement follows the agreed terms. Current purchase payment rails, including USDC where offered, belong to a separate transaction lifecycle.
Historical proof batches
Earlier request-payout batches and their on-chain proof references remain as historical financial evidence. They do not establish the method or payment status of current hourly rental earnings. The dated historical settlement reference explains those preserved records; it is not a current public serving or payout offer.