Skip to main content
GET
/
openapi
/
v1
/
crypto
/
onchain
Crypto on-chain metrics
curl --request GET \
  --url https://api.hayinsights.com/openapi/v1/crypto/onchain \
  --header 'X-API-Key: <api-key>'
{
  "success": true,
  "statusCode": 200,
  "data": {
    "ethGas": {
      "safe": 0.084424998,
      "standard": 0.08533128,
      "fast": 0.093864408,
      "baseFee": 0.0843841,
      "unit": "gwei"
    },
    "btcHashrate": {
      "value": 1024.72,
      "unit": "EH/s"
    },
    "btcActiveAddresses": 503361,
    "whaleTxCount": 29766,
    "mvrv": {
      "value": 1.1772253837760067,
      "zone": "fair_value"
    },
    "nupl": {
      "value": 0.1586,
      "zone": "hope_fear"
    }
  },
  "meta": {
    "timestamp": "2026-06-19T08:50:01.004Z"
  }
}

Authorizations

​
X-API-Key
string
header
required

Your HayInsights API key (prefixed apk_). Create and manage keys in the HayInsights dashboard (Account → API keys).

Send it in the X-API-Key header on every request to /openapi/v1/*. Which data domains you may access and your request quota are both governed by the subscription plan attached to the key — see the Plans & features and Rate limits guides.

Response

On-chain network metrics snapshot.

Standard success envelope shared by every endpoint. Each operation's response wrapper extends this (via allOf) and adds a typed data property.

​
success
boolean
required

Always true for a successful response.

Example:

true

​
statusCode
integer
required

Mirrors the HTTP status code.

Example:

200

​
data
object
required

On-chain network metrics — Ethereum gas prices, Bitcoin hashrate and active addresses, whale transaction count and the MVRV / NUPL valuation indicators.

​
meta
object

Response metadata. Always present; timestamp is the server time the response was generated.