Claiming And Earnings
Link a node to your B3 account with a claim code, then read earnings and payout history in USD.
This page explains how an operator links a node to their B3 account, what makes a node earn, and how earnings and payouts surface on the dashboard. The short version: B3IQ onboards every machine in the fleet manually, and once a claimed node is online and route-ready it earns automatically from any B3IQ-directed work it serves — there is no separate approval step.
Claim A Node
Claiming binds a running node 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 node, as a QR code and as a manual code. The code identifies this specific node.
Sign in to your B3 account on the dashboard
Open the dashboard and sign in with the B3 account you want to own this node and its earnings.
Redeem the claim code
Scan the QR or enter the 8-character code at /dashboard/claim. Redeeming links the node to your signed-in account.
Confirm the link
The node now appears under your account. From here you can see its readiness and watch earnings accrue once it reaches paid routing — nothing to submit, nothing to wait on.
Claiming sets ownership. It does not by itself make the node route-ready. That is a separate gate covered below.
Every Onboarded Node Earns
B3IQ onboards machines into the fleet manually — there is no self-serve join and no admin approval step layered on top of that.
Claimed, online, and route-ready
Once a node is claimed to your account, online with a fresh heartbeat, and passes route and model readiness, it can receive B3IQ-directed workloads — automatically.
Nothing to submit or wait on
There is no approval queue and no reviewer. A claimed, route-ready node in its default operating mode earns from any directed work it serves the moment it serves it.
Being claimed does not skip the route, model, and benchmark gates. See Route readiness for the full gate order and the direct answer to "why am I not earning yet?".
What Makes A Node Earn
A node earns from routed work only when every gate below is satisfied at once.
The node is linked to your signed-in B3 account via its claim code.
The node 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 (dedicated) mode, not earn mode. See Machine Modes below.
The host agent is online with a fresh heartbeat and the node passes route health.
At least one model profile is installed, benchmarked with fresh observed evidence, and eligible for a paid route tier.
Directed Workloads On Idle Machines
Where does earned work come from? Your own inference is free and does not pay you — earnings come from B3IQ-directed workloads: paid work that B3IQ places on onboarded machines when they are idle.
- When your machine is not busy serving your own requests, B3IQ can direct
paid workloads to it. Each served request accrues USD to the machine's
owner at the posted model rates (see
GET /v1/api/pricing). - A machine opts into this pool simply by being onboarded, claimed, online, route-ready, and model/benchmark-eligible in its default operating mode — there is no separate approval allowlist. Being offline, failing model or benchmark policy, or being switched to earn mode are what exclude a machine.
- Accrued earnings settle through the same batched payout pipeline described below; nothing about payouts changes based on where the work came from.
Your own traffic always has first claim on your hardware. Directed workloads fill idle capacity; they do not compete with the requests your own keys send.
Machine Modes
Every machine has an operating mode you control from its page in the dashboard:
| Mode | What it does |
|---|---|
| Bare metal (default) | Serves your own inference and can receive B3IQ-directed workloads. SSH access is available. |
| Earn | Withdraws the machine from all B3IQ inference — your own keys stop routing to it and it receives no directed workloads — and disables its SSH lane, so it is free to offer on external GPU marketplaces. |
Switching a machine back to bare metal restores both your own routing and its eligibility for directed workloads.
Earnings On The Dashboard
The dashboard shows earnings in USD:
- Earnings show gross, settled, and pending totals over a selectable 7-day or 30-day window, with a per-machine breakdown. Each machine's own page also shows a 24-hour earned total.
- Payout history lists settled batches with a status per batch.
Earnings are based on the real work routed to the node. The router selects supply by health and readiness; it does not pay for capacity that never serves a routed request.
These 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
The dashboard shows payout history with a status per batch. Payouts are batched and settled to your payout account, and each batch records a public proof.
A payout 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
Serving your own requests never generates earnings by itself — only B3IQ-directed workloads do. Confirm the machine is in its default (bare metal) operating mode, not earn mode, and that it passes route and model readiness. Check Route readiness for the exact blocker.
Being claimed does not skip route, model, and benchmark readiness. The node must also have a model profile that is benchmarked and paid-route eligible, and it must not be switched to 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 node 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.