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.

B3IQ public model catalog

Profile gates
Fresh node heartbeat

The node must be online with recent signed control-plane state.

Public route ready

The node needs a broker-owned public inference route that is healthy.

Protocol ready

The node is protocol registered, protocol active, and stake-satisfied.

Runtime and install ready

The runtime is reachable and the profile status is installed.

Policy ready

network_eligible, benchmark_verified, paid_route_eligible, route tier, queue health, and observed benchmark evidence all pass.

Key Fields

FieldMeaning
statusLocal install and readiness state such as installed, ready_to_install, runtime_missing, or hardware_unsupported
runtime_kindRuntime family such as ollama, openai, vllm, or sglang
route_tierServing-policy class such as local_convenience, portable_local, network_beta, datacenter_optimized, or fleet_orchestrated
network_eligibleHost/profile policy allows network serving consideration
benchmark_verifiedHost/profile says benchmark proof exists
observed_benchmarkControl-plane-observed benchmark evidence used by hosted /v1/models and paid dispatch
paid_route_eligiblePolicy allows paid routing after all other gates pass
queue_healthRuntime queue posture. blocked or unhealthy fails closed for dispatch

Route Tiers

Route tierPaid route policy
local_convenienceBlocked for paid routing unless a future policy explicitly changes it
portable_localDispatchable only when installed, benchmarked, paid-route enabled, and policy-allowed
network_betaFirst intended paid network tier for vLLM, SGLang, or OpenAI-compatible hosts
datacenter_optimizedFuture dispatchable tier
fleet_orchestratedFuture dispatchable tier
unknownBlocked for paid routing

Common Blockers

Install the approved model profile and publish a fresh heartbeat after the runtime reports it is available.

Run the benchmark smoke command path so the control plane observes fresh evidence. 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, price, spend cap, 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.

Ask a question... ⌘I