> ## 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.

# Node Dashboard

Tour of the local node dashboard served by the host agent: run, monitor, pause, and test your node from one command panel.

The node dashboard is the operator command panel for a running node. It is the
same local web app B3IQ set up your machine with, opened in its command view.
Use it to watch readiness, review activity and earnings, pause work, and test
runtime and model behavior locally.

After [setup](/operators/setup-wizard) completes, the host agent keeps serving
this app from the local listener at `http://127.0.0.1:8831`. It opens on the
**Overview** tab.

## Command view

The dashboard is a single command view with a row of tabs across the top. Each
tab is one job: watch the node, manage models, test inference, mint keys, or
adjust settings.

| Tab | Purpose |
| --- | --- |
| ` Overview ` | Node readiness, posture, and a summary of local activity |
| ` Models ` | Installed models and their per-profile readiness |
| ` Playground ` | Test runtime and model behavior against the local endpoint |
| ` API ` | Create, scope, and revoke local API keys, and review local usage |
| ` Benchmark ` | Run and review benchmark evidence for a model profile |
| ` Earnings ` | Lifetime earned, paid out, and pending totals plus recent payouts (shown once the node is enrolled) |
| ` Settings ` | Node configuration, including the Runtimes and Serving controls |
| ` Logs ` | Local request and service logs, redacted by default |

**Runtimes and Serving live under Settings**

Runtime install and the serving-mode toggle are Settings sub-tabs rather than
  top-level tabs. Everything else above is reachable directly from the tab row.

## Host & advanced controls

A single **Host & advanced controls** button in the top bar opens one takeover
covering node-level state and connectivity. Readiness, machine details, claim,
and network/tunnel overrides all live inside it:

**Readiness and details**

See whether the node is route-ready and open its detail panel for liveness,
    runtime, and model posture.
  **Claim**

Reach the claim flow for an enrolled node. Claiming binds the machine to
    your account so it serves your own API keys.
  **Network status**

Read local browser, LAN and control-plane connectivity at a glance.
  **Tunnel rotate and revoke**

Rotate or revoke the node's tunnel credential when you need to refresh or cut
    off the public route.

**Public route, not a generic proxy**

Tunnel rotate and revoke control the node's public inference route only.
  Rotating issues a fresh credential; revoking takes the node off the public
  route until you bring it back.

## Pause and resume work

Serving has its own dedicated **Pause / Resume** control: `POST
/v1/serving/pause` and `/v1/serving/resume` on the machine's local API. Pausing
stops the node from accepting new routed work while any in-flight job finishes;
enrollment, account link, and identity are all kept, so nothing needs
re-setting-up when you resume.

This is the right tool for maintenance, driver updates, or reclaiming the
  machine for a while. Resume puts it straight back into rotation.

A paused node reports its state through the same readiness surfaces, so it
shows as not currently taking routed work rather than as broken.

Separately, **Settings → Serving** carries the mode choice from setup
(**Serve inference locally** vs **Link to your account & earn**) for operators
who want to change their mind about whether the node reaches outside the
machine at all.

**Not the same as Earn mode**

Pause is a short, reversible break from routed work, and you control it
  directly. A machine's **Bare metal / Earn** mode is a different and more
  drastic switch, and one you request rather than perform: Earn mode removes the machine from B3IQ
  serving entirely (no SSH, no health telemetry, no inference, though a
  liveness heartbeat continues), so it can be offered to external GPU
  marketplaces.
  Reach for pause first; request Earn mode only if you want the machine off
  B3IQ inference altogether.

## Local playground

The **Playground** tab runs prompts against the local OpenAI-compatible endpoint
so you can confirm runtime and model behavior before trusting routed traffic.
Pick a model id from the local model list (`GET /v1/models`), send a prompt, and
watch the response.

**Request logs are redacted by default**

Local request logs are redacted by default so prompts and outputs stay out of
  the log view. Local request content stays local unless you send it to a runtime
  or explicitly use a routed workflow.

When testing from a script instead of the Playground, mint a local key from the
API tab and keep it out of shell history. Read it from an env var or a
`chmod 600` file rather than passing it on the command line. See the
[Host Agent](/operators/host-agent) page for safe local-CLI patterns.

## Your machine in the account dashboard

The local panel above is not the whole story once a machine is claimed. Its
primary home becomes the account dashboard at `b3iq.org/dashboard` (reachable
from any browser, not just the machine itself), where each machine gets its
own detail page. Its inspection and management tabs include:

**Overview**

Inline rename, the machine's environment and how to change it, uptime bars,
    and 24h request volume.
  **Health**

GPU/CPU/memory/disk telemetry and historical charts. The Lifecycle section
    contains agent version, update controls, and host maintenance diagnostics.
  **Models**

Install, remove, and serve models on this machine, with per-model status.
  **Access & controls**

Authorized SSH keys, a browser terminal, the native SSH lane toggle, and
    the machine's dedicated OpenAI-compatible endpoint.
  **Activity**

An owner audit log of key changes, terminal sessions, and commands.

The account dashboard is also where fleet-wide surfaces live: a Models page
that aggregates usage across every machine you own, org fleet SSH keys that
apply to every machine an organization owns, automatic health email alerts
(offline, GPU running hot, disk nearly full), a Support tab for filing
tickets, and the [account-level `b3iq` CLI](/developers/cli) for driving all
of it from a terminal. See [Host agent](/operators/host-agent) for how that
CLI differs from the local `b3iq-host` one.

## Check your machine's state

Sign in to [your machines](https://b3iq.org/dashboard/nodes), select a machine,
and use its Models and Health tabs to inspect installed profiles, runtime
health, and serving state. These account views require access to the machine.
The public [model guides](https://b3iq.org/models) describe model requirements;
they do not show which models your machine currently serves.

## Related

**[Setup wizard](/operators/setup-wizard)**

Walk through the operator setup flow that leads into this dashboard.
  **[Earnings](/operators/earnings)**

Claim a machine, and read what it earns from and how payouts settle.
  **[Host agent](/operators/host-agent)**

Learn what the local service does, and the local-vs-account CLI split.