Public API
Free JSON API over the monitoring network. No key required at current rate limits; keyed tiers with higher limits are planned.
Endpoints
GET /api/pools all pools with status + reported stats
GET /api/pools/{id} one pool, including 48h history snapshots
GET /api/chains chains aggregated across Blockle pools
GET /api/chains/{id} one chain
GET /api/stats network summary
GET /api/health service health
GET /api/chain BLOCK chain snapshot (height, lanes, recent blocks)
GET /api/mps/{solo|pplns} live pool stats (MiningPoolStats-compatible)
GET /api/explorer emission totals by coin and algorithm
GET /api/explorer/mints recent mint events (full provenance)
GET /api/explorer/mint/{hash} one mint event
POST /api/register register a pool {name, chain, algorithm, stratum, pool_fee, website?}
→ {pool_id, token}
POST /api/heartbeat {pool_id, token, timestamp, pool_hashrate, miners, workers,
blocks_found, block_height, network_hashrate,
network_difficulty, shares_submitted, blocks:[{chain,height,hash}]}
GET /api/moonpay/sign?url= sign a MoonPay buy-widget URL
POST /api/moonpay/sign {url} → {url, signed} (same, URL in the JSON body)
MoonPay URL signing for the wallets' "Buy with card" flow. A pk_test_
publishable key uses the MoonPay sandbox, whose widget URLs work unsigned; when no
server-side secret is configured this endpoint returns the URL unchanged with
"signed": false. A signature is only required for production (pk_live_)
URLs: configure the MoonPay secret server-side (env MOONPAY_SECRET or
/var/lib/blockle-biz/moonpay-secret) and the endpoint appends
&signature= (base64 HMAC-SHA256 of the query string). The secret never leaves
the server and is never logged.
Data honesty
Responses separate verified (heartbeat recency, stratum reachability probes) from operator_reported (hashrates, miner counts). Heartbeats are token-authenticated, schema- and range-validated, freshness-checked, and rate limited.