Introduction

The ChartInspect API exposes on-chain analytics, certified chart datasets, crypto prices, economic series, market indicators, exchange reserves, derivatives, and live market ticks. Coverage is catalog-driven and changes as data is published, so discovery is part of the normal integration flow.

#Base URL

https://chartinspect.com/api/v1

#Access Tiers

#First Request

The asset list is public and does not require a key:

curl "https://chartinspect.com/api/v1/chains"

Abridged response:

{
  "success": true,
  "chains": [
    {
      "id": "bitcoin",
      "symbol": "BTC",
      "name": "Bitcoin",
      "network": "bitcoin",
      "assetType": "native",
      "metrics": 294,
      "dataThrough": "2026-08-28",
      "lastUpdated": "2026-08-29T00:00:00.000Z",
      "endpoints": {
        "metrics": "/api/v1/onchain/status?chain=bitcoin",
        "data": "/api/v1/onchain/{metric}?chain=bitcoin"
      }
    }
  ],
  "total": 71
}

The response is the complete additive V1 inventory, including network metadata and dataThrough.

#Discover Metrics

On-chain discovery requires a Pro key because it exposes the paid metric surface:

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

Each entry reports the exact metric ID, response fields, and backing file name. Use those IDs verbatim. The API resolves documented compatibility aliases, but it does not perform partial or substring matching.

#Fetch Data

curl -H "x-api-key: YOUR_API_KEY" \
  "https://chartinspect.com/api/v1/onchain/mvrv?chain=bitcoin&days=30&limit=500"

Most time-series endpoints return success, data, and metadata. Snapshot, CSV, discovery, Socket.IO, and some source-specific endpoints intentionally use different shapes. See the endpoint reference before parsing a new endpoint.

#Next Steps

1. Create and protect an API key.
2. Review query parameters and rate limits.
3. Test a request in the Playground.
4. Use Errors for retry and failure handling.