Metric Docs | API Metadata
Understand the pool, token, chain and configuration metadata needed to identify Metric liquidity correctly in an integration.
Understand the pool, token, chain and configuration metadata needed to identify Metric liquidity correctly in an integration.
Metric is built around Active Pools: liquidity pools that use a Price Provider to supply bid, ask and reference prices instead of relying only on reserve ratios. This page focuses on API Metadata and the practical checks that matter when using or integrating the protocol.
Metadata purpose
Metadata identifies chains, pools, tokens and configuration context so quote or route data can be interpreted correctly.
Cache policy
Addresses and token metadata change less often than prices, but deployments can still evolve. Cache with an invalidation strategy rather than hardcoding indefinitely.
Address normalization
Normalize EVM addresses consistently and preserve the original chain context; the same token symbol can map to different contracts on different networks.
Related Metric Docs
Last updated