Public fixture paths
All resources below are static files. Read them with HTTP GET on a normal static host. There is no authentication because they contain deliberately fictional public data, not because production telemetry should be public.
| Resource | File | Purpose |
|---|---|---|
| Fleet | fleet.json | Four-worker sample totals |
| Workers | workers.json | Per-worker states and measurements |
| History | telemetry.json | Three fixed illustrative chart windows |
| Prompt | ai-log-review-prompt.txt | Read-only AI review instructions |
Shared response fields
demo is always true. schema_version is 1.0. observed_at is 2026-09-21T12:00:00Z, the fictional sample observation time. notice states that there is no live telemetry or hardware connection. These fields describe the bundled fixture, not an uptime promise.
A successful HTTP response means the host served a file. It does not verify equipment health, upstream connectivity, or the age of any real system.
Fleet summary
fleet_id is silicon-lab; algorithm is sha256d. workers_total is 4, workers_reporting is 3, and workers_offline is 1. The aggregate hashrate_th_s is 600 and power_w is 12000.
efficiency_j_th is 20, calculated as 12000 divided by 600. This is a device-boundary example. It excludes external facility loads and cannot be used as an actual equipment benchmark.
Worker fields
| Field | Type | Meaning |
|---|---|---|
id |
string | Stable fictional worker identifier |
label |
string | Human-readable display label |
algorithm |
string | sha256d for this sample |
status |
string | online, warning, or offline |
hashrate_th_s |
number | Sample hashrate in TH/s |
power_w |
number | Sample device power in watts |
temperature_c |
number or null | Illustrative supported sensor reading, or unavailable |
The offline worker has zero observed sample hashrate and power, with no temperature reading. That specific fixture is not a general rule that offline equipment consumes no power. Warning status is an authored scenario, not a universal thermal threshold.
Telemetry windows
The series object contains 1h, 24h, and 7d arrays, each with twelve equally spaced illustrative readings ending at the shared snapshot time. The unit is TH/s. The chart keeps the same vertical scale when switching windows.
These arrays are neither forecasts nor measurements of a real network. The worker table remains the same fixed snapshot when the history view changes. The monitoring page makes both scopes visible.
Errors and unsupported operations
Missing files use the static host's normal not-found behavior. Invalid JSON handling belongs in the client. No server-side query filters, write operations, credentials, pagination, or streaming features are implemented. Do not infer additional endpoints from the filename structure.
Start with the quickstart for working client examples and the security checklist when planning a separate production service.