Assets and Networks

Discover every ChartInspect asset, its host network, current metric count, and data freshness.

On this page

text

GET /api/v1/chains

This route is public and returns the complete additive V1 asset inventory. The original success, chains, and total fields remain available, while richer network and freshness metadata is added alongside them.

bash

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

#Response

json

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

assets is an additive alias of chains; assetTotal and networkTotal provide explicit counts. Metric counts and freshness timestamps change as data is published.

#Field Meaning

Field	Meaning
`id`	Exact value for the on-chain `chain` parameter
`network`	Native network hosting the asset
`assetType`	Native asset or token classification
`tokenStandard`	Token standard when applicable
`metrics`	Current manifest-backed metric count
`dataThrough`	Newest data date represented by the manifest
`manifestGeneratedAt`	Manifest generation time
`lastUpdated`	Compatibility alias for manifest generation time, not data freshness

Use dataThrough to judge freshness, then follow endpoints.metrics. See Blockchains & Assets for the native-versus-token model.

available is true when the asset passes the same published-data gate as the on-chain routes. Registry-listed assets with available: false do not currently have a servable local export; listing an asset does not imply that every metric is published.

Was this page helpful?