DCENT_OS API & Ports Reference — REST, WebSocket, 4028, MCP

DCENT_OS is local-first: the dashboard, REST + WebSocket APIs, a CGMiner-compatible API on port 4028, and a built-in MCP server all run on your LAN — no cloud, no account, no phone-home. This page maps that surface with an evidence status per row. It does not reproduce endpoint schemas: those live in the repository, and the deep links below are the authoritative reference.

Network surfaces

DCENT_OS (Antminer builds) — documented network surface
Surface	Port	What it's for	Evidence status
Web dashboard	HTTP (`http://<MINER_IP>/`)	Three-mode local UI (Space Heater / Mining / Hacker), setup wizard, config editing	Verified (surface) — first-boot instruction is "Open `http://<MINER_IP>/`" (docs/INSTALL/README.md §3) / Inferred (port 80 — implied by the URL's default scheme port, not stated)
REST API	not separately published in the docs fetched	Telemetry + configuration ("Edit it via the dashboard, the REST API, or directly over SSH" — docs/CONFIGURATION.md). The dashboard exercises ~70 API endpoints (TESTING.md mock server)	Verified (existence) / Unknown (dedicated port — see repo)
WebSocket API	not separately published in the docs fetched	Live telemetry streaming alongside REST (root README.md, "Local-first")	Verified (existence) / Unknown (port/paths — see repo)
CGMiner-compatible API	TCP 4028	Drop-in monitoring for existing tooling — explicitly `pyasic` / Home-Assistant friendly	Verified — root README.md ("CGMiner-compatible API (port 4028, pyasic/Home-Assistant friendly)")
MCP server	transport/port not published in the docs fetched	AI-native control surface: read-only monitoring for any agent; authenticated owner sessions for control. Present on both Antminer and ESP members	Verified (existence) / Unknown (transport — see repo)
SSH	TCP 22 (standard)	Management access; up from first boot ("dashboard, SSH, and API up; hash power off" — docs/INSTALL/README.md)	Verified (service) / Inferred (port number — not stated in the docs fetched)
Stratum V1/V2	outbound only (e.g. `:3333` in config examples)	Pool connection — an outbound client, not a listening service. Multi-pool failover with anti-flap failback on V1; native SV2 stack under an explicit readiness gate	Verified (root README.md; docs/CONFIGURATION.md pool examples)

Rows marked Unknown are honest depth limits of this page, not gaps in the firmware — the full surface is in the repo (links below). Nothing here phones home: all of these listen on your LAN only (source: docs/FAQ.md, "Does it phone home").

The MCP server, precisely

DCENT_OS ships a built-in MCP (Model Context Protocol) server so a local AI agent can monitor — and, with owner authentication, control — the miner. The trust boundary as the repo states it: read-only monitoring for any agent; authenticated owner sessions for control. The dashboard's Companion pairs this with your own local LLM (LM Studio / Ollama) — your model, your machine, no cloud — and proposes guarded actions you explicitly approve.

Works with your existing tooling

pyasic / Home Assistant: point them at the CGMiner-compatible API on port 4028 — the compatibility target the README names explicitly.
Prometheus: fleet metrics come from the bench side, not the miner — DCENT_Toolbox's dcent serve daemon exposes /metrics (binds 127.0.0.1 by default) plus a /status JSON endpoint on the machine running the toolbox (source: DCENT_Toolbox README.md, "Headless fleet service").
Anything that speaks cgminer JSON: existing dashboards and monitors built for stock/cgminer-era APIs can read DCENT_OS through the same 4028 socket.

Try the API without a miner

The dashboard's mock server replays ~70 API endpoints with realistic data on your own machine:

cd DCENT_OS_Antminer/dashboard
npm ci && npm run build
python3 scripts/preview-with-mocks.py --port 4173
# http://127.0.0.1:4173 — the same UI, backed by mock telemetry

Source: TESTING.md (Tier 0, "Drive the dashboard with mock telemetry"). The mock definitions themselves are the fastest map of the real API surface. Guided walkthrough: Run DCENT_OS in 15 minutes.

Full endpoint schemas — the authoritative sources

This page intentionally stops at the surface map. Endpoint paths, payload schemas and API contracts live in the repository:

Surface map compiled from the DCENT_OS root README.md, docs/INSTALL/README.md, docs/CONFIGURATION.md and TESTING.md (main branch, fetched 2026-08-13). Rows are labeled Verified / Inferred / Unknown per the project's locked evidence vocabulary; no endpoint has been invented for this page. The site's own /wp-json/dc/v1/* API is a different surface (the WordPress data API), not the firmware's. Last reviewed: August 13, 2026.

Related products, repair, and setup paths

Last reviewed August 13, 2026.