DEVELOPERS / API REFERENCE

A small API. An explicit contract.

Three static GET resources for building and testing a consumer. Deterministic public records, with no authentication or write operations.

GET

ASIC worker

A fictional SHA-256d worker with hashrate, chip temperature, power, and fan fields.

Open asic.json ↗
GET

GPU device

A fictional GPU workload with device temperature, power, and utilization context.

Open gpu.json ↗
GET

Prompt record

A versioned sample task with input variables and fictional evaluation counts.

Open prompts.json ↗

Shared response envelope

The fixtures are versioned together. Numeric machine fields live inside the worker or prompt object; display strings are presentation examples, not a substitute for typed observations. Every response includes a demo flag and the source label.

FieldTypeMeaning
demobooleanAlways true for these public fixtures.
schema_versionstring1.0. Validate this before reading the contract.
kindstringasic, gpu, or prompts.
sourcestringbundled-sample; not a live telemetry source.
observed_atstringISO 8601 fictional observation timestamp; not the page refresh time.
worker / promptobjectTyped, resource-specific sample fields.
display_metricsarrayFour labeled values used by the sample dashboard.
display_rowsarrayLabeled illustrative observation or workflow states.
chart_valuesarrayUnitless illustrative values for a decorative sample pattern.

Inspect a response in your browser

This button makes a real same-origin GET request to the bundled ASIC sample and displays the result below. It does not query a miner. HTTP and parsing errors are shown instead of being replaced by synthetic success.

Open raw JSON ↗
Click “Fetch ASIC sample” to read the bundled JSON record.

Resource-specific fields

For ASICs, hashrate_th_s, power_w, chip_temp_c, and fan_rpm are fictional numeric readings. The GPU record instead uses hashrate_mh_s, temperature_c, and utilization_percent for a sample workload. The prompt record identifies a task, revision, variables, dataset version, and illustrative pass counts.

Behavior and limitations

Only file retrieval is implemented. There is no POST endpoint, authentication service, pagination, streaming, historical query API, hardware control, or model execution. Server-level errors, caching, CORS, and rate limits are determined by your static host; this site does not invent an application error contract for features it does not provide.

Same-origin browser requests work without cross-origin configuration. Third-party websites fetching these files need your host to allow their origin. Avoid claiming universal cross-origin access without configuring and testing the deployment.

Machine-readable resources

Download the OpenAPI description or the JSON Schema for the public fixture contract. These describe the bundled examples, not a future live collection service.