Model Readiness
How B3IQ model profiles move from local install state to benchmarked, network-eligible, paid-route capability.
Model profiles are the contract between local node capability, public network visibility, and paid router eligibility. A model being installed is necessary, but it is not enough for paid routing.
Choose the runtime from the machine, workload shape, and serving model. Portable local hosts can start with llama.cpp-compatible or local OpenAI-compatible routes, while network-beta and production paths should prove vLLM, SGLang, or equivalent serving behavior with observed benchmark evidence.
Paid Route Checklist
The node must be online with recent signed control-plane state.
The node needs a broker-owned public inference route that is healthy.
The machine was onboarded to the fleet by B3IQ and is linked to an owner account. There is no separate admin approval step beyond onboarding.
The runtime is reachable and the profile status is installed.
network_eligible, benchmark_verified, paid_route_eligible, route tier,
queue health, and observed benchmark evidence all pass.
Key Fields
| Field | Meaning |
|---|---|
| status | Local install and readiness state such as installed, ready_to_install, runtime_missing, or hardware_unsupported |
| runtime_kind | Runtime family such as llama-cpp, mlx, ollama, openai, vllm, or sglang |
| route_tier | Serving-policy class such as local_convenience, consumer_edge, portable_local, network_beta, datacenter_optimized, or fleet_orchestrated |
| network_eligible | Host/profile policy allows network serving consideration |
| benchmark_verified | Host/profile says benchmark proof exists |
| observed_benchmark | Control-plane-observed benchmark evidence used by hosted /v1/api/models and paid dispatch |
| paid_route_eligible | Policy allows paid routing after all other gates pass |
| queue_health | Runtime queue posture. blocked or unhealthy fails closed for dispatch |
Route Tiers
| Route tier | Paid route policy |
|---|---|
| local_convenience | Blocked for paid routing unless a future policy explicitly changes it |
| consumer_edge | Explicit opt-in, low-priority edge tier guarded by benchmark, persistence, queue, incident, and customer policy |
| portable_local | Dispatchable only when installed, benchmarked, paid-route enabled, and policy-allowed |
| network_beta | First intended paid network tier for vLLM, SGLang, or OpenAI-compatible hosts |
| datacenter_optimized | Dispatchable tier for datacenter-class hosts |
| fleet_orchestrated | Dispatchable tier for orchestrated fleets |
| unknown | Blocked for paid routing |
Common Blockers
Install the approved model profile and publish a fresh heartbeat after the runtime reports it is available.
B3IQ automatically re-benchmarks eligible profiles that lack fresh observed evidence once the node is online with a healthy runtime — there is no operator command to run. Host-provided summaries alone are not the billable proof gate.
Use a network-beta or portable endpoint profile, or define a future low-tier policy explicitly. Local convenience profiles do not enter paid pools today.
Clear queue state, runtime overload, or backend health issues, then publish a fresh heartbeat.
The caller's gateway policy can block by model allowlist, denylist, route tier, or account status.
Public Claims
Browser GPU preflight, static model fit, and installed model counts are not paid route proof. Public UI should only claim paid route readiness when the live model profile and router gates agree.