> ## Documentation Index > Fetch the complete documentation index at: https://docs.b3iq.org/llms.txt > Use this file to discover all available pages before exploring further. # 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](https://b3iq.org/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 suitable gateway keys on its owner's account with no per-request B3IQ charge. Account rate limits and token quotas still apply, and hosting is a separate cost. **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. Optional Earn capacity is rented by the whole machine and by the hour. Income accrues only when capacity is rented; demand is not guaranteed. Under Managed Hosting, the owner receives 85% of gross rental revenue before hosting costs. Earnings are denominated in **USD**, and settlement follows the owner's agreed terms. 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. **Routing-eligibility checklist** **Claimed to your account** The machine is linked to your signed-in B3 account via its claim code. **Onboarded to the fleet** The machine was onboarded by B3IQ and is registered against your owner identity. There is no separate approval step beyond onboarding. **Bare metal mode** The machine is in its default mode, not Earn. See [Machine modes](#machine-modes) below. **Online and route-ready** The host agent is online with a fresh heartbeat and the machine passes route health. **Model and benchmark ready** At least one model profile is installed, benchmarked with fresh observed evidence, and on a dispatchable route tier. **Readiness is a routing gate, not a payment gate** See [Route readiness](/operators/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 shown on its page in the dashboard. Request a change with the B3IQ team after running work finishes. 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 recorded earnings over a 7-day or 30-day window, with a per-machine breakdown and settlement status. An hourly market reference or a modeled monthly figure is an estimate, not income already accrued or paid. Serving your own inference creates no payout. - **Payouts** (`/dashboard/payouts`) lists what has been paid to your payout account, with a status on each row. Use the signed-in [Earnings page](https://b3iq.org/dashboard/earnings) for your account's figures. Marketplace reference estimates, when shown, describe what similar GPUs rent for elsewhere. They are not your machine's realized earnings or a guarantee of future income. The earnings windows are accrual views of rented capacity. Settlement follows your agreed terms. Accrued revenue and finalized payouts will not always match at a given moment; an accrual is not proof of payment. ## Payout history and status Use your account's Payouts page to distinguish pending, processing, paid and failed records, and inspect the evidence attached to a specific payment. Estimated earnings and accrued revenue are not funds already paid to you. Earlier request-payout settlement batches are historical records. Their on-chain references and status fields remain interpretable through the [historical settlement reference](/protocol/receipts-settlement), but do not establish the settlement method or payment status of current hourly rental revenue. Current purchase payment rails, including USDC where offered, are a separate transaction lifecycle. ## Common blockers **My machine is serving requests but shows no earnings.** 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. **My machine is claimed and online but nothing routes to it.** Being claimed does not skip connection, runtime, installed-model and key-scope checks. An observed benchmark is not required for owner inference. 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](/operators/route-readiness) for the exact blocker. **Earnings show, but my payout is still pending.** An accrued balance is not a completed payment. Inspect the payout status and evidence in your account and the settlement terms in your agreement; do not infer the cause of a pending record from its label alone. **I redeemed the claim code on the wrong account.** 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. ## Related **[Route readiness](/operators/route-readiness)** Diagnose why a machine or model is routable or blocked. **[Model readiness](/operators/model-readiness)** Understand model profile fields, route tiers, and the dispatch gates. **[Receipts and payouts](/developers/receipts-billing)** Separate current usage evidence, optional hourly income and historical proof batches.