Metric Discovery

Discover exact on-chain metric IDs, fields, and asset availability through the status endpoint.

text
GET /api/v1/onchain/status?chain={asset_id}
GET /api/v1/onchain/all?chain={asset_id}

Both paths return the same discovery shape and require a Pro key with on-chain permission.

bash
Try in Playground
curl -H "x-api-key: YOUR_API_KEY" \
  "https://chartinspect.com/api/v1/onchain/status?chain=bitcoin"

#Response

json
{
  "success": true,
  "chain": "bitcoin",
  "totalMetrics": 294,
  "availableChains": ["bitcoin", "ethereum", "solana", "xrp", "cardano"],
  "metrics": [
    {
      "metric": "mvrv-z-score",
      "fields": ["date", "btc_price", "mvrv_z_score"],
      "file": "mvrv-z-score.json"
    }
  ],
  "timestamp": "2026-08-26T12:00:00.000Z"
}

The response above is abbreviated. V1 is additive: the production endpoint IDs remain present with their captured field contracts, and newly shipped manifest-backed metrics appear alongside them.

#Rules

  1. Pass an id returned by /api/v1/chains as chain.
  2. Use the returned metric ID verbatim in the data URL.
  3. Treat the returned fields as the wire contract for that asset and metric.
  4. Do not use partial names. Unknown metrics return 404 with valid choices.
  5. Check Data Resolutions separately, because discovery IDs are not a promise that every resolution exists.

There is no query-parameter version switch. Breaking changes require a future versioned path; additions ship directly on V1.

Was this page helpful?