Operator Onboarding
How a machine joins the B3IQ fleet: invite-based onboarding, node registry state, owner binding, and route/runtime readiness.
B3IQ controls what enters the fleet: joining today is invite/manual onboarding, not a self-serve signup. A new machine enrolls with an onboarding code the B3IQ team issues; a machine that was pre-onboarded on your behalf is linked to your account by redeeming a claim code from your dashboard. Once a machine is onboarded and claimed, there is no separate approval step. It can serve routed work as soon as it is online and route-ready.
Earning is a property of the machine's hosting arrangement, not of an individual request: an earning machine's owner takes a revenue share on what that machine makes under B3IQ's offtake arrangements, accrued to its deal ledger and paid in USD.
Node registration
A node that is eligible to serve routed work needs:
The machine enrolled with a B3IQ onboarding code and is claimed to an account or organization.
The machine is in its default bare-metal mode. A machine switched to Earn mode is withdrawn from every B3IQ inference path.
Route, tunnel, runtime, model, and benchmark gates all pass before the node is route-ready.
Separately, node identity and owner binding are published to the node registry, so a third party can check who owns a machine without asking B3IQ.
B3IQ keeps node and model registry state (node ID, owner binding, and active status) so readiness and payouts attach to an owner you control. Public docs and explorer views keep this state explicit.
Model hosting
B3IQ separates model publisher commitments from node hosting capability:
- Model publisher commitments can include artifact hash, metadata URI, publisher status, and model-level policy boundaries.
- Node model-hosting capability can include node/model/runtime/benchmark/route commitments.
- Raw inventory, endpoints, filesystem paths, prompts, and outputs stay out of public commitments.
Capability commitments
The target b3iq-capability-v1 commitment is public-safe. It can hash:
- Node ID.
- Model class.
- Runtime class or runtime hash.
- Benchmark hash.
- Route class.
- Privacy class.
- Metadata URI.
It must not include raw local endpoints, runtime IDs, paths, private routes, prompts, outputs, or secrets.
Enforcement boundary
Withholding earnings is a last resort. Refund, release, withhold, suspension, and reputation paths should handle normal operational failures. Any enforcement action needs clear evidence standards, appeals, and public-safe reason strings.
See Reputation for dispute policy.