Route Readiness
How B3IQ explains why a node or model is eligible or blocked for routed paid inference.
Route readiness is the public-safe diagnosis for whether a node can serve routed work. It combines node liveness, route health, protocol state, model profile policy, benchmark evidence, queue health, and customer gateway policy.
Public Diagnosis
Route readiness is surfaced on your node's page in the explorer and in the node dashboard. It is backed by a public-safe readiness endpoint:
textGET /v1/public/nodes/:node_id/route-readiness?model=<model>
The response can include route blockers, model blockers, next actions, and
operator prompts. For explicit consumer_edge profiles,
model_profiles[].consumer_edge reports model class, conservative concurrency
cap, benchmark age/freshness, uptime gates, recent error rate, blockers, next
actions, and earning status. It must not include tunnel IDs, local URLs, runtime
IDs, prompts, outputs, request IDs, API keys, customer IDs, raw tokens, route
secrets, or private tunnel details.
Gate Order
Blockers And Actions
| Blocker | Meaning | Operator action |
|---|---|---|
| Enrollment | Node is not fully enrolled | Complete managed enrollment |
| Heartbeat | Heartbeat is stale, missing, or offline | Bring host agent online and sync a fresh heartbeat |
| Runtime | Runtime is not ready or reachable | Start or configure runtime and rerun probe |
| Claim | Node is not linked to an owner account | Redeem the claim code from the node's setup screen in your dashboard |
| Route tier | Profile tier is blocked or paused for paid dispatch | Use or configure an approved route tier or resume the route-class incident control |
| Benchmark proof | Observed benchmark evidence is missing or stale | Keep the node online with a healthy runtime — B3IQ schedules a fresh benchmark automatically |
| Queue health | Queue is blocked or unhealthy | Clear runtime queue issue and publish heartbeat |
| Customer policy | Caller policy rejects model, price, route tier, or spend | Update policy or send an allowed request |
A machine switched to earn mode is excluded from every b3iq routing query —
it never appears as a candidate, so route readiness reports it as
route_missing until you switch it back to its dedicated mode from the
machine's dashboard page.
Earning Explanation
The operator-facing answer to "why am I not earning yet?" should be direct:
Paid routing requires more than an installed model. The node must be enrolled, online, route-ready, claimed, runtime-ready, model-installed, network-eligible, benchmark-observed, paid-route eligible, queue-healthy, and accepted by customer policy.
Stale Benchmark Prompts
benchmark.smoke is not an operator-runnable command. If an otherwise eligible
profile depends on stale observed benchmark evidence, keep the node online
with a healthy runtime after any runtime, driver, model artifact,
quantization, context, or queue-policy change — B3IQ re-benchmarks eligible
profiles that lack fresh observed evidence on its own schedule.