PUBLIC API · VERSION 1

VMESH Asia SOLO REST API

Public, read-only JSON API for the VMESH-only solo mining pool in Japan. It reports the pool's CKPool telemetry and live VargaMesh Mainnet node data, not Bitcoin data.

Base URL: https://mining.asia.vargamesh.com/api/v1/
Methods: GET and HEAD · Auth: none · CORS: * · Rate limit: 12 requests/sec/IP, burst 24.

Combined Status

/api/v1/status

Chain, Stratum and CKPool summary

Health Check

/api/v1/health

200 when node and Stratum TCP respond; otherwise 503

Pool Statistics

/api/v1/pool

Hashrate, users, workers, shares, best difficulty

VMESH Network

/api/v1/network

Block height, difficulty, hashrate estimates and sync

Recent VMESH Blocks

/api/v1/blocks

Network-wide blocks, not specifically Asia pool finds

Pool Config

/api/v1/config

SOLO Stratum, fee and connection options

Miner Lookup

/api/v1/miners/{VMESH_ADDRESS}

Per-address stats and worker telemetry

Discovery

/api/v1/

Browse all endpoints

Examples

curl -fsS https://mining.asia.vargamesh.com/api/v1/status
curl -fsS https://mining.asia.vargamesh.com/api/v1/pool
curl -fsS https://mining.asia.vargamesh.com/api/v1/miners/YOUR_VMESH_ADDRESS

Data quality, units and limitations

All _hs hashrate fields are numeric hashes per second (H/s). Unavailable fields return null.
CKPool values are stale if not refreshed for 180 seconds (fresh:false).
Pool hashrate derives from CKPool accepted share telemetry; network hashrate is a node estimate.
pool_blocks_found:null means independently verified pool-found-block indexing is not available; it does not mean zero blocks.
/api/v1/blocks describes every VMESH network block, not just blocks attributed to the Asia pool.
Miner names and share statistics are address-based public data; the API does not expose wallet secrets or IP addresses.

Errors

{"error":"invalid_address"}     HTTP 400
{"error":"not_found"}           HTTP 404
{"error":"backend_unavailable"} HTTP 503

← Back to VMESH Asia SOLO