Claiming And Earnings
Link a machine to your B3 account with a claim code, then read earnings and payout history in USD.
This page explains how an operator links a machine to their B3 account, what a machine earns from, and how earnings and payouts surface on the dashboard. The short version: B3IQ onboards every machine in the fleet manually, claiming binds it to the account that gets paid, and a machine earns by having its capacity rented rather than by answering inference requests.
Claim a machine
Claiming binds a running machine to your B3 account so that readiness, routing, and payouts all attach to an owner you control.
Open the wizard and find the claim code
The setup wizard shows an 8-character claim code for the machine, as a QR code and as a manual code. It identifies this specific machine and expires 15 minutes after it is minted; mint a fresh one if it lapses.
Sign in to your B3 account on the dashboard
Open the dashboard and sign in with the B3 account you want to own this machine and its earnings.
Redeem the claim code
Scan the QR or enter the 8-character code at /dashboard/claim. Redeeming links the machine to your signed-in account.
Confirm the link
The machine now appears under your account, where you can see its readiness, reach it with your gateway keys, and read its earnings and payouts. Nothing to submit, nothing to wait on.
Claiming sets ownership. It does not by itself make the machine route-ready. That is a separate gate covered below.
Where earnings come from
Inference is free on B3IQ, and that includes inference B3IQ routes to your machine. A served request produces no payout line for anyone: it is not metered as earnings at any rate. What a machine earns from is its capacity being rented — GPU hours sold to someone else — and Earn mode is what frees a machine up for that, by taking it out of B3IQ serving entirely.
Serve yourself first, for free
A Bare-metal machine answers your own gateway keys with no charge and no quota beyond your account's. That is the default and it never costs you anything.
Expect a payout per request
Serving requests does not accrue money to the machine's owner. Readiness makes a machine routable; it does not make it paid.
Earnings, once accrued, are denominated in USD and settle to the payout account on the owner that claimed the machine. That is why claiming on the intended account the first time matters.
What routing readiness is for
Route and model readiness decide whether B3IQ can send inference to a machine. They are worth clearing — an unroutable machine is not serving your own keys either — but clearing them is not what produces earnings.
The machine is linked to your signed-in B3 account via its claim code.
The machine was onboarded by B3IQ and is registered against your owner identity. There is no separate approval step beyond onboarding.
The machine is in its default mode, not Earn. See Machine modes below.
The host agent is online with a fresh heartbeat and the machine passes route health.
At least one model profile is installed, benchmarked with fresh observed evidence, and on a dispatchable route tier.
See Route readiness for the full gate order and the direct answer to "why is nothing routing to my machine?".
Machine modes
Every machine has an operating mode you control from its page in the dashboard. The mode is enforced by the control plane on the machine's own record, never by what the machine reports about itself.
| Mode | What it does |
|---|---|
| Bare metal (default) | Serves your own inference, free. SSH access is available. |
| Earn | Withdraws the machine from every B3IQ routing query, so your own keys stop reaching it, and disables its SSH lane, so it is free to offer on external GPU marketplaces. |
Switching a machine back to bare metal puts it back in your serving pool and re-enables its SSH lane.
Earnings on the dashboard
The dashboard shows earnings in USD:
- Earnings (
/dashboard/earnings) shows gross, settled, and pending totals over a 7-day or 30-day window, alongside uptime, a per-machine breakdown, and projected monthly, per-online-hour, and per-request figures. Each machine's own page carries a 24-hour earned tile. - Payouts (
/dashboard/payouts) lists what has been paid to your payout account, with a status on each row.
The Earnings page also carries a Marketplace value of your machines panel: a live estimate, taken from the public inference rates, of what each machine's GPU currently rents for per month. That is an estimate of what the hardware could earn, not a record of what it has earned.
The earnings windows are accrual views of completed work. Settlement to your payout account happens in batches, so accrued earnings and finalized payouts will not always match at a given moment.
Payout history and status
Payouts are batched and settled to your payout account, and each batch records its settlement transaction publicly, so a settled batch can be checked independently rather than taken on trust.
A settlement batch moves through these states:
| Status | Meaning | Settled? |
|---|---|---|
| created | Payout rows are gathered into a batch, waiting to be submitted to the settlement network. | No |
| submitting | The batch is being submitted to the settlement network. | In progress |
| submitted | The batch is submitted and awaiting confirmation. | In progress |
| completed | Settlement evidence is verified and the rows are marked settled. | Yes |
Pending rows between settlement batches are normal. Batching exists for efficiency, so expect a delay between accrued earnings and a finalized payout.
Common blockers
That is how it works. Inference on B3IQ is free, so a served request — yours or one B3IQ routed — produces no payout line. A machine earns from its capacity being rented, which is what Earn mode offers it for.
Being claimed does not skip route, model, and benchmark readiness. The machine also needs a model profile that is installed, benchmarked, and on a dispatchable route tier, and it must not be in Earn mode. Check Route readiness for the exact blocker.
Earnings accrue continuously; payouts settle in batches. A pending payout simply has not been included in a submitted batch yet.
The claim binds the machine to whichever B3 account was signed in at redemption. Sign in to the intended account and re-run the claim with a fresh code from the wizard so earnings attach to the right owner.