July 15, 2025

Metrics API V2: Trading Volume Analysis and On-Chain Metrics

featured image

Crypto markets no longer live only on centralized exchanges.

Stablecoins move across chains. Capital enters and leaves DeFi protocols. Liquidity shifts between ecosystems. On-chain trading activity can change while traditional exchange data tells only part of the story.

CoinAPI Metrics API V2 extends market metrics beyond traditional exchange data with asset-, chain-, and exchange-level analytics, including stablecoin supply, bridged stablecoins, TVL, protocol fees, and on-chain activity where available.

For teams already using trades, quotes, order books, or OHLCV, Metrics V2 adds another layer of context.

Metrics API V2 is part of the CoinAPI Market Data API.

It provides standardized metrics at the asset, blockchain, and exchange level, with a particular focus on stablecoin, DeFi, and blockchain ecosystem analytics.

Instead of processing multiple raw datasets independently, developers can query available metrics using standardized CoinAPI identifiers and retrieve historical metric series through REST.

Examples include:

  • TVL
  • STABLES_BRIDGED_USD
  • STABLES_CIRCULATING_USD
  • STABLES_MINTED_USD
  • Protocol fees
  • On-chain trading volume metrics where available

Metric availability depends on the asset, chain, exchange, source, and historical coverage.

Metrics V2 doesn't replace every other CoinAPI metric or market-data endpoint.

CoinAPI provides two complementary metrics frameworks:

Metrics V1Metrics V2
Primary focusTraditional market metricsOn-chain and ecosystem analytics
Exchange metricsYesYes, where available
Asset metricsYesYes
Symbol metricsYes—
Derivatives metricsYes—
Stablecoin metrics—Yes
Chain-level metrics—Yes
TVL / protocol metrics—Yes

Metrics V1 focuses on traditional exchange-, asset-, symbol-, and derivatives-related metrics.

This includes metrics such as derivatives mark price, funding information, open interest, implied volatility, and liquidation-related data where supported.

Metrics V2 adds a newer structure for asset-, chain-, and exchange-level analytics, particularly stablecoin and blockchain ecosystem data.

Many research systems can use both rather than treating V2 as a replacement for V1.

Stablecoins have become an important part of crypto liquidity and settlement.

Metrics V2 provides structured data that can help researchers monitor how stablecoin supply changes across assets and blockchain ecosystems.

Available metrics can include:

STABLES_MINTED_USD

Tracks minted stablecoin supply in USD terms where supported.

STABLES_CIRCULATING_USD

Provides information about circulating stablecoin supply.

STABLES_BRIDGED_USD

Tracks stablecoin value bridged across supported blockchain ecosystems.

Additional supply-related metrics may be available depending on the underlying dataset.

These metrics can help analysts study liquidity conditions and capital availability without assuming that a change in stablecoin supply automatically predicts a particular market outcome.

Metrics V2 also extends CoinAPI coverage into DeFi and protocol-level activity.

Depending on coverage, this can include:

TVL represents value locked in supported protocols or ecosystems.

TVL can be useful for evaluating protocol adoption, liquidity conditions, and changes in DeFi activity over time.

Fee metrics can provide another view into activity and economic usage within supported protocols.

On-chain volume metrics can help researchers compare activity across decentralized venues, protocols, and blockchain ecosystems where coverage is available.

Together, these datasets provide context that is difficult to obtain from centralized exchange trades alone.

This distinction is important.

Metrics V2 isn't a replacement for CoinAPI's core market data.

If you need individual trades, use Market Data API Trades.

If you need best bid and ask data, use Quotes.

If you need market depth, use Order Book data.

If you need candles, use OHLCV.

Metrics V2 adds higher-level asset, chain, exchange, stablecoin, and protocol analytics on top of these datasets.

For example, bid-ask spread analysis is generally built using normalized quote data rather than a Metrics V2 stablecoin or chain metric.

A research system could therefore combine:

Quotes and order books → centralized-market liquidity
Trades and OHLCV → price and trading activity
Metrics V1 → derivatives and traditional market metrics
Metrics V2 → stablecoin, chain, TVL, and protocol analytics

This creates a broader analytical dataset without mixing fundamentally different types of market information.

Metrics V2 provides listing endpoints that let you determine which metrics are actually available before requesting historical data.

For example:

1GET https://rest.coinapi.io/v2/metrics/chain/listing?chain_id=ETHEREUM

The response can return metric identifiers available for that chain, such as TVL, STABLES_BRIDGED_USD, or STABLES_CIRCULATING_USD.

This discovery step is useful because coverage can differ between chains and datasets.

Once you know a metric is available, you can request its history.

For example:

1GET https://rest.coinapi.io/v2/metrics/chain/history?chain_id=ETHEREUM&metric_id=TVL&period_id=1DAY

The history endpoint supports parameters including:

  • metric_id
  • chain_id
  • time_start
  • time_end
  • period_id
  • limit
  • time_format

Historical responses provide aggregated values over each requested period, including opening and closing values, minimum and maximum values, observation counts, and aggregated totals.

Historical depth varies by metric and source, so use the listing and history endpoints to confirm the coverage required for your research.

Metrics can also be discovered at the asset level.

For USDC, for example:

1GET https://rest.coinapi.io/v2/metrics/asset/listing?asset_id=USDC

Depending on current coverage, the response can include stablecoin-related metric IDs such as:

1STABLES_BRIDGED_USD
2STABLES_CIRCULATING_USD
3STABLES_MINTED_USD

You can then use the corresponding asset history endpoint to retrieve the historical series.

Metrics V2 also supports exchange-level metric discovery and historical queries.

For supported exchanges and decentralized protocols, available metrics can include values such as:

  • TVL
  • FEES
  • Trading-volume-related metrics
  • Trade-count metrics

The exact list depends on the exchange or protocol.

Rather than hard-coding assumptions about available metrics, applications can query the relevant listing endpoint first:

1GET https://rest.coinapi.io/v2/metrics/exchange/listing?exchange_id=UNISWAP-V3-ETHEREUM

This lets an application determine the available metrics dynamically.

Researchers can monitor minted, circulating, and bridged stablecoin values over time.

This can help identify changes in stablecoin availability and movement across supported blockchain ecosystems.

Stablecoin issuance should not be treated as a direct buy or sell signal. Changes can have many causes and are more useful when interpreted alongside exchange flows, prices, liquidity, and broader market conditions.

TVL, fees, and on-chain trading activity can help teams compare supported protocols and examine how activity develops over time.

This can support protocol research, ecosystem monitoring, and DeFi analytics dashboards.

Bridging metrics can help researchers monitor the movement of assets between blockchain ecosystems, subject to metric coverage and methodology.

Combined with chain-level stablecoin and TVL metrics, this can provide a broader picture of where crypto activity is moving.

Metrics V2 can also be combined with traditional market data.

A risk system might monitor:

  • Stablecoin supply and bridging
  • TVL
  • Protocol activity and fees
  • Centralized exchange trades
  • Quotes and spreads
  • Order book liquidity
  • Derivatives metrics from Metrics V1

This separates the underlying datasets while still allowing them to be analyzed together.

Metrics V2 historical series can also become features in quantitative or machine learning research.

For example, researchers can test whether changes in TVL, stablecoin circulation, bridging, or protocol activity have relationships with volatility, liquidity, volume, or price behavior.

The API provides the data inputs. Whether those metrics have predictive value is something that should be established through research and backtesting rather than assumed in advance.

Metrics V2 can provide useful context, but it isn't a finished trading-cost optimization or order-routing engine.

CoinAPI data can support customer-built trading-cost analysis when metrics are combined with:

  • Quotes
  • Order books
  • Trades
  • Exchange metadata
  • Relevant fee information
  • On-chain metrics

For actual order routing and execution workflows, CoinAPI EMS Trading API is the relevant CoinAPI product.

Keeping these products separate is important: Metrics provides analytical data, while EMS handles execution workflows.

Metrics V2 is most useful as part of a larger market-data architecture.

CoinAPI provides different products and datasets for different jobs:

NeedCoinAPI data/product
Trades, quotes, order books, OHLCVMarket Data API
Traditional exchange and derivatives metricsMetrics V1
Stablecoin, chain and on-chain ecosystem metricsMetrics V2
Reference and aggregated exchange ratesExchange Rates API
Crypto indexesIndexes API
Bulk historical datasetsFlat Files
Order routing and executionEMS Trading API

The goal isn't to force all crypto information into one metric family.

It is to make different types of data available through clearly defined datasets that can be combined when a research or trading workflow requires them.

Metrics availability varies by metric, asset, blockchain, exchange, protocol, and source.

CoinAPI normalizes metrics into consistent schemas and identifiers, but not every metric is available for every resource.

For that reason, integrations should use the listing endpoints to discover current coverage before requesting values or historical series.

Historical depth can also differ between metrics.

Avoid assuming that because one chain or asset has a particular metric today, the same metric has identical history or coverage everywhere else.

Centralized exchange data remains essential for understanding price formation, spreads, liquidity, and execution.

But it isn't the entire crypto market.

Metrics V2 adds another layer by making stablecoin supply, chain activity, TVL, protocol fees, and other ecosystem-level metrics available through standardized REST endpoints where supported.

Combined with Metrics V1 and CoinAPI's trades, quotes, order books, and OHLCV datasets, it gives researchers a way to study both traditional exchange activity and the broader blockchain ecosystem without confusing the two.

Use Metrics V2 to discover available asset, chain, and exchange metrics and retrieve historical series for supported datasets.

Explore the CoinAPI Market Metrics documentation →

Recent Articles

Crypto API made simple: Try now or speak to our sales team