> ## Documentation Index > Fetch the complete documentation index at: https://developer.hayinsights.com/llms.txt > Use this file to discover all available pages before exploring further. # Crypto on-chain metrics > On-chain network metrics — Ethereum gas prices, Bitcoin hashrate and active addresses, whale transaction count and the MVRV / NUPL valuation indicators. ## OpenAPI ````yaml /openapi.yaml get /openapi/v1/crypto/onchain openapi: 3.1.0 info: title: HayInsights Open API version: 0.1.0 description: > Programmatic access to the **HayInsights** financial-data hub — commodities, crypto, ETF, FX, macroeconomic and real-estate datasets, served from a single API surface under `/openapi/v1/*`. This specification is the **single source of truth** for the public API surface — shared by SDK codegen, the reference docs, and (later) the mock server / contract tests. ## Authentication Every request must carry your API key in the `X-API-Key` header. There is a single authentication tier — no request signing. Create and manage keys in the HayInsights dashboard (Account → API keys). See **Authentication**. ## Plans & quota Access to each data domain and your request quota are governed by the subscription plan attached to your key. Each endpoint consumes a **weighted** amount of your per-minute quota; every response carries `X-RateLimit-*` headers. See **Rate limits** and **Plans & features**. contact: {} servers: - url: https://api.hayinsights.com description: Production security: - HayInsightsApiKey: [] tags: - name: Commodities description: >- Spot prices, top movers, gold–DXY correlation and historical series for energy, metals and agricultural commodities. - name: Crypto description: >- Crypto market overview, dominance, bubble map, on-chain and derivatives metrics. - name: ETF description: >- Exchange-traded fund listings, performance & net-flow rankings, heatmap, holdings, NAV growth and fund composition. - name: FX description: >- Foreign-exchange summary, live table, 90-day correlation matrix and the emerging-market stress monitor. - name: Macro description: >- Macroeconomic indicators — GDP, CPI/PCE, exchange rates, population, central-government debt and policy rates / bond yields. - name: Real Estate description: >- Real-estate statistics, land prices, administrative geography (provinces / wards) and choropleth GeoJSON, by country. paths: /openapi/v1/crypto/onchain: get: tags: - Crypto summary: Crypto on-chain metrics description: > On-chain network metrics — Ethereum gas prices, Bitcoin hashrate and active addresses, whale transaction count and the MVRV / NUPL valuation indicators. operationId: cryptoOnchain responses: '200': description: On-chain network metrics snapshot. content: application/json: schema: $ref: '#/components/schemas/CryptoOnchainResponse' example: 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' '401': $ref: '#/components/responses/Unauthorized' '403': $ref: '#/components/responses/Forbidden' '429': $ref: '#/components/responses/RateLimited' '500': $ref: '#/components/responses/InternalError' components: schemas: CryptoOnchainResponse: allOf: - $ref: '#/components/schemas/EnvelopeBase' - type: object required: - data properties: data: $ref: '#/components/schemas/CryptoOnchain' EnvelopeBase: type: object description: > Standard success envelope shared by every endpoint. Each operation's response wrapper extends this (via `allOf`) and adds a typed `data` property. required: - success - statusCode properties: success: type: boolean const: true description: Always `true` for a successful response. example: true statusCode: type: integer description: Mirrors the HTTP status code. example: 200 meta: $ref: '#/components/schemas/Meta' CryptoOnchain: type: object description: > On-chain network metrics — Ethereum gas prices, Bitcoin hashrate and active addresses, whale transaction count and the MVRV / NUPL valuation indicators. required: - ethGas - btcHashrate - btcActiveAddresses - whaleTxCount - mvrv - nupl properties: ethGas: type: - object - 'null' description: Ethereum gas price tiers. required: - safe - standard - fast - baseFee - unit properties: safe: type: - number - 'null' description: Gas price for a low-priority (safe) transaction. example: 0.084424998 standard: type: - number - 'null' description: Gas price for a standard-priority transaction. example: 0.08533128 fast: type: - number - 'null' description: Gas price for a high-priority (fast) transaction. example: 0.093864408 baseFee: type: - number - 'null' description: Current network base fee. example: 0.0843841 unit: type: string description: Unit the gas prices are expressed in. example: gwei btcHashrate: type: - object - 'null' description: Bitcoin network hashrate. required: - value - unit properties: value: type: number example: 1024.72 unit: type: string description: Unit the hashrate is expressed in. example: EH/s btcActiveAddresses: type: - integer - 'null' description: Number of active Bitcoin addresses. example: 503361 whaleTxCount: type: - integer - 'null' description: Number of large ("whale") transactions observed. example: 29766 mvrv: type: - object - 'null' description: Market-Value-to-Realised-Value ratio and its valuation zone. required: - value - zone properties: value: type: number example: 1.1772253837760067 zone: type: string enum: - undervalued - fair_value - overheating - overvalued description: Valuation zone derived from the MVRV value. example: fair_value nupl: type: - object - 'null' description: Net Unrealised Profit / Loss and its sentiment zone. required: - value - zone properties: value: type: number example: 0.1586 zone: type: string enum: - capitulation - hope_fear - optimism - belief - euphoria description: Sentiment zone derived from the NUPL value. example: hope_fear ErrorBody: type: object description: Standard error envelope returned for every 4xx / 5xx response. required: - success - statusCode - error properties: success: type: boolean const: false description: Always `false` for an error response. example: false statusCode: type: integer description: Mirrors the HTTP status code. example: 401 error: $ref: '#/components/schemas/ErrorDetail' meta: $ref: '#/components/schemas/Meta' Meta: type: object description: >- Response metadata. Always present; `timestamp` is the server time the response was generated. required: - timestamp properties: timestamp: type: string format: date-time description: Server time when the response was generated (ISO 8601). example: '2026-06-19T08:31:59.478Z' additionalProperties: true ErrorDetail: type: object description: Error detail object carried under `error` in the error envelope. required: - code - message properties: code: type: string description: > Machine-readable error code. Specific for authentication / quota errors (e.g. `API_KEY_REQUIRED`, `API_KEY_INVALID`, `FEATURE_NOT_IN_PLAN`, `RATE_LIMIT_EXCEEDED`). For validation (400) and not-found (404) the code is currently `INTERNAL_ERROR` and the HTTP status carries the semantics. example: API_KEY_INVALID message: description: Human-readable message, or a list of validation messages (400). oneOf: - type: string - type: array items: type: string example: Invalid API key responses: Unauthorized: description: >- Missing, invalid, disabled or expired API key. Send a valid key in the `X-API-Key` header. content: application/json: schema: $ref: '#/components/schemas/ErrorBody' example: success: false statusCode: 401 error: code: API_KEY_INVALID message: Invalid API key meta: timestamp: '2026-06-19T08:34:08.023Z' Forbidden: description: >- Your subscription plan does not include this data feature, or your key's scope denies it. content: application/json: schema: $ref: '#/components/schemas/ErrorBody' example: success: false statusCode: 403 error: code: FEATURE_NOT_IN_PLAN message: Your plan does not include this feature meta: timestamp: '2026-06-19T08:34:08.100Z' RateLimited: description: > Rate limit exceeded — you have consumed your plan's per-minute weight budget. Wait until `X-RateLimit-Reset` (or `Retry-After` seconds) then retry. headers: X-RateLimit-Limit: $ref: '#/components/headers/XRateLimitLimit' X-RateLimit-Remaining: $ref: '#/components/headers/XRateLimitRemaining' X-RateLimit-Reset: $ref: '#/components/headers/XRateLimitReset' X-RateLimit-Weight-Used: $ref: '#/components/headers/XRateLimitWeightUsed' Retry-After: $ref: '#/components/headers/RetryAfter' content: application/json: schema: $ref: '#/components/schemas/ErrorBody' example: success: false statusCode: 429 error: code: RATE_LIMIT_EXCEEDED message: Rate limit exceeded meta: timestamp: '2026-06-19T08:34:09.000Z' InternalError: description: Unexpected server error. Retry after a short exponential backoff. content: application/json: schema: $ref: '#/components/schemas/ErrorBody' example: success: false statusCode: 500 error: code: INTERNAL_ERROR message: Internal server error meta: timestamp: '2026-06-19T08:34:10.000Z' headers: XRateLimitLimit: description: Your plan's request-weight budget per 1-minute window. schema: type: integer example: 1000 XRateLimitRemaining: description: Remaining request weight in the current 1-minute window. schema: type: integer example: 997 XRateLimitReset: description: Unix timestamp (seconds) when the current rate-limit window resets. schema: type: integer format: int64 example: 1781857979 XRateLimitWeightUsed: description: Request weight consumed by this call (see each endpoint's weight). schema: type: integer example: 3 RetryAfter: description: Seconds to wait before retrying. Present on 429 responses. schema: type: integer example: 30 securitySchemes: HayInsightsApiKey: type: apiKey in: header name: X-API-Key description: > 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. ````