Point-In-Time
Definition. 25 Delta Skew Normalized (1 Month) is the relative richness of put versus call implied volatility on options expiring in roughly one month, computed as the difference between a 25-delta put's implied volatility and a 25-delta call's implied volatility, normalized by the at-the-money implied volatility.\n\nTechnical. A 25-delta put has a delta of -25, sampling the option surface at symmetric points either side of the money to expose the put-versus-call asymmetry in implied volatility.\n\nInterpretation. Positive readings mean puts are richer than equivalent-delta calls, negative readings mean calls are richer than puts.\n\n\nThis is the Point-in-Time (PiT) variant of 25 Delta Skew Normalized (1 Month). PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 10m, 1h, 24h
format - csv, json
jsonPossible values: exchange name - binance, bybit, deribit, okex
timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/derivatives/options_25delta_skew_1_month_pit?a=text&e=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. 25 Delta Skew Normalized (1 Week) is the relative richness of put versus call implied volatility on options expiring in one week, computed as the difference between a 25-delta put's implied volatility and a 25-delta call's implied volatility, normalized by the at-the-money implied volatility.\n\nTechnical. A 25-delta put has a delta of -25, sampling the option surface at symmetric points either side of the money to expose the put-versus-call asymmetry in implied volatility.\n\nInterpretation. Positive readings mean puts are richer than equivalent-delta calls, negative readings mean calls are richer than puts.\n\n\nThis is the Point-in-Time (PiT) variant of 25 Delta Skew Normalized (1 Week). PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 10m, 1h, 24h
format - csv, json
jsonPossible values: exchange name - binance, bybit, deribit, okex
timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/derivatives/options_25delta_skew_1_week_pit?a=text&e=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. 25 Delta Skew Normalized (3 Months) is the relative richness of put versus call implied volatility on options expiring in roughly three months, computed as the difference between a 25-delta put's implied volatility and a 25-delta call's implied volatility, normalized by the at-the-money implied volatility.\n\nTechnical. A 25-delta put has a delta of -25, sampling the option surface at symmetric points either side of the money to expose the put-versus-call asymmetry in implied volatility.\n\nInterpretation. Positive readings mean puts are richer than equivalent-delta calls, negative readings mean calls are richer than puts.\n\n\nThis is the Point-in-Time (PiT) variant of 25 Delta Skew Normalized (3 Months). PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 10m, 1h, 24h
format - csv, json
jsonPossible values: exchange name - binance, bybit, deribit, okex
timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/derivatives/options_25delta_skew_3_months_pit?a=text&e=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. 25 Delta Skew Normalized (6 Months) is the relative richness of put versus call implied volatility on options expiring in roughly six months, computed as the difference between a 25-delta put's implied volatility and a 25-delta call's implied volatility, normalized by the at-the-money implied volatility.\n\nTechnical. A 25-delta put has a delta of -25, sampling the option surface at symmetric points either side of the money to expose the put-versus-call asymmetry in implied volatility.\n\n\nThis is the Point-in-Time (PiT) variant of 25 Delta Skew Normalized (6 Months). PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 10m, 1h, 24h
format - csv, json
jsonPossible values: exchange name - binance, bybit, deribit, okex
timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/derivatives/options_25delta_skew_6_months_pit?a=text&e=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. 25 Delta Skew Normalized (All) is the relative richness of put versus call implied volatility on options, computed as the difference between a 25-delta put's implied volatility and a 25-delta call's implied volatility, normalized by the at-the-money implied volatility. The individual series cover option contracts expiring 1 week, 1 month, 3 months, and 6 months from now.\n\nTechnical. A 25-delta put has a delta of -25, sampling the option surface at symmetric points either side of the money to expose the put-versus-call asymmetry in implied volatility.\n\nInterpretation. Negative readings mean calls trade at a higher implied volatility than puts. Positive readings mean puts trade at a higher implied volatility than calls.\n\n\nThis is the Point-in-Time (PiT) variant of 25 Delta Skew Normalized (All). PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 10m, 1h, 24h
format - csv, json
jsonPossible values: exchange name - binance, bybit, deribit, okex
timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/derivatives/options_25delta_skew_all_pit?a=text&e=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. 90D Coin Days Destroyed (CDD-90) is the 90-day rolling sum of Coin Days Destroyed (CDD), age-adjusted by normalizing for time to account for the increasing destructible-coin-age baseline as the network ages.\n\n\nThis is the Point-in-Time (PiT) variant of 90D Coin Days Destroyed (CDD-90). PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 24h
format - csv, json
jsonPossible values: timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/indicators/cdd90_age_adjusted_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. The amount of each token currently available to be borrowed on version 3 of the Aave platform — supplied reserve minus outstanding borrows, per listed token.\n\nInterpretation. Provides insight into per-token lending-pool capacity and the available-to-utilized split that drives borrow-rate dynamics.\n\n\nThis is the Point-in-Time (PiT) variant of Aave V3: Available Liquidity Volume by Token. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 1h, 24h
format - csv, json
jsonPossible values: timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/protocols/aave_v3_available_liquidity_sum_by_token_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. The number of unique accumulation addresses. Accumulation addresses are defined as addresses that have at least 2 incoming non-dust transfers and have never spent funds.\n\nTechnical. Exchange addresses and addresses receiving from coinbase transactions (miner addresses) are discarded. To account for lost coins, addresses that were last active more than 7 years ago are omitted as well.\n\n\nThis is the Point-in-Time (PiT) variant of Accumulation Addresses. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 24h
format - csv, json
jsonPossible values: timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/addresses/accumulation_count_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. The total amount of funds held in accumulation addresses.\n\nTechnical. Accumulation addresses are defined as addresses with at least 2 incoming non-dust transfers that have never spent funds. Exchange addresses and addresses receiving from coinbase transactions (miner addresses) are discarded. To account for lost coins, addresses last active more than 7 years ago are also omitted.\n\nNotes. This is the Point-in-Time (PiT) variant of Total Balance in Accumulation Addresses. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.\n
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 24h
format - csv, json
jsonPossible values: currency - native, usd
timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/addresses/accumulation_balance_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. Accumulation Trend Score is an indicator that reflects the relative size of entities actively accumulating coins on-chain in terms of their BTC holdings. The scale combines the size of an entity's balance (its participation score) with the amount of new coins it has acquired or sold over the last month (its balance change score).\n\nTechnical. Miner and exchange entities are excluded.\n\nInterpretation. Values near 1 indicate that, on aggregate, larger entities (or a large part of the network) are accumulating. Values near 0 indicate they are distributing or not accumulating.\n\nNotes. For more information, see the metric description in Glassnode Academy.\n\n\nThis is the Point-in-Time (PiT) variant of Accumulation Trend Score. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 24h
format - csv, json
jsonPossible values: timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/indicators/accumulation_trend_score_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. The 30-day Accumulation Trend Score broken down by wallet-size cohort. The score reflects the relative size of entities actively accumulating coins on-chain over the past 30 days, combining each entity's balance size (participation score) with the amount of new coins it acquired or sold over that window (balance-change score).\n\nTechnical. Miner and exchange entities are excluded.\n\nInterpretation. A score near 1 indicates that on aggregate, larger entities within the cohort are accumulating, a score near 0 indicates they are distributing or not accumulating.\n\n\nThis is the Point-in-Time (PiT) variant of Accumulation Trend Score by Wallet Size (30d). PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 24h
format - csv, json
jsonPossible values: timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/indicators/accumulation_trend_score_by_wallet_size_30d_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. The 7-day Accumulation Trend Score broken down by wallet-size cohort. The score reflects the relative size of entities actively accumulating coins on-chain over the past 7 days, combining each entity's balance size (participation score) with the amount of new coins it acquired or sold over that window (balance-change score).\n\nInterpretation. A score near 1 indicates that on aggregate, larger entities within the cohort are accumulating, a score near 0 indicates they are distributing or not accumulating.\n\n\nThis is the Point-in-Time (PiT) variant of Accumulation Trend Score by Wallet Size (7d). PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 24h
format - csv, json
jsonPossible values: timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/indicators/accumulation_trend_score_by_wallet_size_7d_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. The number of unique addresses active in the network as a sender or receiver.\n\nTechnical. Only addresses active in successful transactions are counted.\n\n\nThis is the Point-in-Time (PiT) variant of Active Addresses. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
network values - aggregated, arb, base, bnb, eth, opt, sol, ton, trx, xrp. Defaults to eth when omitted.
since, unix timestamp
until, unix timestamp
frequency interval - 10m, 1h, 24h, 1w, 1month
format - csv, json
jsonPossible values: timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/addresses/active_count_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. The number of unique addresses that were active in the network as a sender, a receiver, or by calling a smart contract.\n\nTechnical. Only addresses active in successful transactions are counted.\n\n\nThis is the Point-in-Time (PiT) variant of Active Addresses (with contracts). PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
network values - aggregated, arb, eth. Defaults to eth when omitted.
since, unix timestamp
until, unix timestamp
frequency interval - 10m, 1h, 24h, 1w, 1month
format - csv, json
jsonPossible values: timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/addresses/active_count_with_contracts_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. The number of unique entities that were active either as a sender or receiver. Entities are defined as a cluster of addresses that are controlled by the same network entity and are estimated through advanced heuristics and Glassnode's proprietary clustering algorithms.\n\nTechnical. Entities are clusters of addresses estimated to be controlled by the same actor, identified through advanced heuristics and Glassnode's proprietary clustering algorithms. Entity-based metrics rely on statistical and data-science methods that are refined over time. The series is therefore mutable: its established history is stable, but recent data points may revise as clustering improves. For methodology, see our article on account-based metrics.\n\nNotes. For more information, see our article on how many entities hold Bitcoin.\n\n\nThis is the Point-in-Time (PiT) variant of Active Entities. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 24h
format - csv, json
jsonPossible values: timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/entities/active_count_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. The count of active validators.\n\nTechnical. Active validators are validators that have completed the activation queue, are not in an exit queue, and carry an effective balance greater than 32 ETH.\n\n\nThis is the Point-in-Time (PiT) variant of Active Validators. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 10m, 1h, 24h
format - csv, json
jsonPossible values: timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/eth2/active_validators_count_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. Activity Retention Rate is the percentage of addresses that were active, through sending or receiving transactions, in the previous 30-day period and remained active in the current one. For example, a 70% retention rate means that 7 out of 10 previously active addresses continued transacting in the following period.\n\nInterpretation. Higher retention reflects sustained user participation and is an indication of the asset's utility, with frequently-used assets such as stablecoins often exhibiting higher rates. A drop in retention may reflect reduced on-chain interaction, though it does not necessarily signal waning interest as users may shift to holding rather than transacting.\n\nNotes. Based on the Activity Retention chart in Glassnode Studio. For more information, see Understanding Retention on Glassnode Insights.\n\n\nThis is the Point-in-Time (PiT) variant of Activity Retention Rate. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 24h
format - csv, json
jsonPossible values: timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/addresses/activity_retention_rate_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. Relative Address Supply Distribution reports the share of circulating supply held by addresses falling within each balance band.\n\nTechnical. Every on-chain address is binned by its native-unit balance, and the metric reports the share of total supply controlled by each band.\n\n\nThis is the Point-in-Time (PiT) variant of Address Supply Distribution. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
network values - aggregated, arb, base, eth, opt. Defaults to eth when omitted.
since, unix timestamp
until, unix timestamp
frequency interval - 10m, 1h, 24h, 1w, 1month
format - csv, json
jsonPossible values: timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/addresses/supply_distribution_relative_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. The number of unique addresses whose holdings have an average buy price higher than the current spot price.\n\nTechnical. Buy price is the price at the time coins were transferred into an address.\n\n\nThis is the Point-in-Time (PiT) variant of Addresses in Loss. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 1h, 24h
format - csv, json
jsonPossible values: timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/addresses/loss_count_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. The number of unique addresses currently in loss, segmented by holding-period age cohort. An address is in loss when the current price is below its average acquisition price. Cohorts span from hot addresses (coins acquired more recently) to cold addresses (older, dormant coins).\n\nTechnical. Breakdown metrics use an address-based approach, analyzing transactions and holdings at the individual wallet-address level to facilitate comparability across digital assets and to ensure consistent analysis across blockchain architectures. This contrasts with the UTXO-based approach used for chains like Bitcoin, where unspent transaction outputs are analyzed to categorize asset properties. Metrics for UTXO-based assets may show slight deviations when compared across these methods.\n\n\nThis is the Point-in-Time (PiT) variant of Addresses in Loss by Age. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 1h, 24h
format - csv, json
jsonPossible values: timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/breakdowns/addresses_loss_count_by_age_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. The number of unique addresses whose funds have an average buy price below the current spot price.\n\nTechnical. "Buy price" is defined as the price at the time coins were transferred into an address.\n\n\nThis is the Point-in-Time (PiT) variant of Addresses in Profit. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 1h, 24h
format - csv, json
jsonPossible values: timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/addresses/profit_count_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. The number of unique addresses currently in profit, segmented by holding-period age cohort. An address is in profit when the current spot price is above its average acquisition price. Cohorts span from hot (most recently acquired) to cold (long dormant).\n\nTechnical. Breakdowns use an address-based approach, analyzing transactions and holdings at the wallet-address level to facilitate comparability across digital assets and to ensure consistent analysis across various blockchain architectures. This contrasts with the alternative UTXO-based approach for chains like Bitcoin, where unspent transaction outputs are analyzed to categorize asset properties. Metrics for UTXO-based assets may show slight deviations if compared across these different computational methods.\n\n\nThis is the Point-in-Time (PiT) variant of Addresses in Profit by Age. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 1h, 24h
format - csv, json
jsonPossible values: timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/breakdowns/addresses_profit_count_by_age_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. The number of unique addresses holding at least a value of $1 USD.\n\n\nThis is the Point-in-Time (PiT) variant of Addresses with Balance ≥ $1. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 24h
format - csv, json
jsonPossible values: timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/addresses/min_1_usd_count_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. The number of unique addresses holding at least a value of $10 USD.\n\n\nThis is the Point-in-Time (PiT) variant of Addresses with Balance ≥ $10. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 24h
format - csv, json
jsonPossible values: timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/addresses/min_10_usd_count_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. The number of unique addresses holding at least a value of $100 USD.\n\n\nThis is the Point-in-Time (PiT) variant of Addresses with Balance ≥ $100. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 24h
format - csv, json
jsonPossible values: timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/addresses/min_100_usd_count_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. The number of unique addresses holding at least a value of $100k USD.\n\n\nThis is the Point-in-Time (PiT) variant of Addresses with Balance ≥ $100k. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 24h
format - csv, json
jsonPossible values: timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/addresses/min_100k_usd_count_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. The number of unique addresses holding at least a value of $10k USD.\n\n\nThis is the Point-in-Time (PiT) variant of Addresses with Balance ≥ $10k. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 24h
format - csv, json
jsonPossible values: timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/addresses/min_10k_usd_count_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. The number of unique addresses currently holding at least $1,000 worth of .\n\n\nThis is the Point-in-Time (PiT) variant of Addresses with Balance ≥ $1k. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 24h
format - csv, json
jsonPossible values: timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/addresses/min_1k_usd_count_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. The number of unique addresses holding at least a value of $1M USD.\n\n\nThis is the Point-in-Time (PiT) variant of Addresses with Balance ≥ $1M. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 24h
format - csv, json
jsonPossible values: timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/addresses/min_1m_usd_count_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. The number of unique addresses holding at least 0.01 coins.\n\n\nThis is the Point-in-Time (PiT) variant of Addresses with Balance ≥ 0.01. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
network values - aggregated, arb, base, eth, opt, sol, ton, trx. Defaults to eth when omitted.
since, unix timestamp
until, unix timestamp
frequency interval - 10m, 1h, 24h, 1w, 1month
format - csv, json
jsonPossible values: timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/addresses/min_point_zero_1_count_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. The number of unique addresses holding at least 0.1 coins.\n\n\nThis is the Point-in-Time (PiT) variant of Addresses with Balance ≥ 0.1. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
network values - aggregated, arb, base, eth, opt, sol, ton, trx. Defaults to eth when omitted.
since, unix timestamp
until, unix timestamp
frequency interval - 10m, 1h, 24h, 1w, 1month
format - csv, json
jsonPossible values: timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/addresses/min_point_1_count_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. The number of unique addresses holding at least 1 coin.\n\n\nThis is the Point-in-Time (PiT) variant of Addresses with Balance ≥ 1. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
network values - aggregated, arb, base, eth, opt, sol, ton, trx. Defaults to eth when omitted.
since, unix timestamp
until, unix timestamp
frequency interval - 10m, 1h, 24h, 1w, 1month
format - csv, json
jsonPossible values: timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/addresses/min_1_count_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. The number of unique addresses holding at least 10 coins.\n\n\nThis is the Point-in-Time (PiT) variant of Addresses with Balance ≥ 10. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
network values - aggregated, arb, base, eth, opt, sol, ton, trx. Defaults to eth when omitted.
since, unix timestamp
until, unix timestamp
frequency interval - 10m, 1h, 24h, 1w, 1month
format - csv, json
jsonPossible values: timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/addresses/min_10_count_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. The number of unique addresses whose current native-asset balance is at least 100.\n\n\nThis is the Point-in-Time (PiT) variant of Addresses with Balance ≥ 100. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
network values - aggregated, arb, base, eth, opt, sol, ton, trx. Defaults to eth when omitted.
since, unix timestamp
until, unix timestamp
frequency interval - 10m, 1h, 24h, 1w, 1month
format - csv, json
jsonPossible values: timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/addresses/min_100_count_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. The number of unique addresses holding at least 10k coins.\n\n\nThis is the Point-in-Time (PiT) variant of Addresses with Balance ≥ 10k. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
network values - aggregated, arb, base, eth, opt, sol, ton, trx. Defaults to eth when omitted.
since, unix timestamp
until, unix timestamp
frequency interval - 10m, 1h, 24h, 1w, 1month
format - csv, json
jsonPossible values: timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/addresses/min_10k_count_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. The number of unique addresses holding at least 1k coins.\n\n\nThis is the Point-in-Time (PiT) variant of Addresses with Balance ≥ 1k. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
network values - aggregated, arb, base, eth, opt, sol, ton, trx. Defaults to eth when omitted.
since, unix timestamp
until, unix timestamp
frequency interval - 10m, 1h, 24h, 1w, 1month
format - csv, json
jsonPossible values: timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/addresses/min_1k_count_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. Number of unique addresses holding at least 32 ETH. This is the number of potential validators for ETH 2.0.\n\nTechnical. Only Externally Owned Addresses (EOAs) are counted, contracts are excluded.\n\n\nThis is the Point-in-Time (PiT) variant of Addresses with Balance ≥ 32 ETH. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
network values - aggregated, arb, base, eth, opt. Defaults to eth when omitted.
since, unix timestamp
until, unix timestamp
frequency interval - 10m, 1h, 24h
format - csv, json
jsonPossible values: timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/addresses/min_32_count_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. The number of unique addresses holding a positive (non-zero) amount of coins.\n\n\nThis is the Point-in-Time (PiT) variant of Addresses with Non-Zero Balance. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
network values - aggregated, arb, base, eth, opt, sol, ton, trx. Defaults to eth when omitted.
since, unix timestamp
until, unix timestamp
frequency interval - 10m, 1h, 24h, 1w, 1month
format - csv, json
jsonPossible values: timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/addresses/non_zero_count_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. Adjusted Circulating Supply is the circulating supply with an estimate of lost coins removed.\n\nTechnical. The amount of lost coins is estimated as all coins that have not moved in over seven years.\n\n\nThis is the Point-in-Time (PiT) variant of Adjusted Supply. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 10m, 1h, 24h
format - csv, json
jsonPossible values: currency - native, usd
timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/supply/current_adjusted_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. The Altcoin Cycle Signal measures whether the market favors bitcoin versus all altcoins. It is based on price data of the top 250 altcoins by market capitalization (excluding stablecoins) and is meant to be largely agnostic to which altcoins in particular an investor holds.\n\nTechnical. The metric is updated daily at 10:15 UTC, providing the previous day's data point at this time.\n\nInterpretation. During Bitcoin Season, bitcoin is likely to outperform the basket of all altcoins, during Altcoin Season this dynamic inverts.\n\nNotes. For more information on its interpretation and methodology, see this dashboard.\n\n\nThis is the Point-in-Time (PiT) variant of Altcoin Cycle Signal. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 24h
format - csv, json
jsonPossible values: timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/signals/altcoin_index_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. Altcoin Market Cap (network value) is the product of the current supply and the current USD price of all assets except BTC.\n\n\nThis is the Point-in-Time (PiT) variant of Altcoin Market Cap. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 24h
format - csv, json
jsonPossible values: timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/market/marketcap_altcoins_usd_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. The 30-day change in the regional price series constructed from price movements that occur during Asian working hours, between 8am and 8pm China Standard Time (00:00-12:00 UTC).\n\nTechnical. Regional prices are constructed in a two-step process. First, price movements are assigned to regions based on working hours in the US, Europe, and Asia. Regional prices are then derived by taking the cumulative sum of the price changes over time for each region.\n\n\nThis is the Point-in-Time (PiT) variant of Asia Month-over-Month Price Change. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 24h
format - csv, json
jsonPossible values: timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/market/apac_30d_price_change_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. The estimated year-over-year change in the share of Bitcoin supply held or traded in Asia.\n\nTechnical. Geolocation of supply is performed probabilistically at the entity level. The timestamps of all transactions created by an entity are correlated with the working hours of different geographical regions to determine the probability that each entity is located in the US, Europe, or Asia. Working hours are defined as:\n* US: 8am to 8pm Eastern Time (13:00-01:00 UTC)\n* EU: 8am to 8pm Central European Time (07:00-19:00 UTC)\n* Asia: 8am to 8pm China Standard Time (00:00-12:00 UTC)\nAn entity's balance contributes to a region's supply only when its location can be determined with high certainty. Supply held on exchange wallets is excluded.\n\nInterpretation. Positive values mean Asia's attributed share of supply is expanding relative to a year ago, negative values that it is contracting.\n\n\nThis is the Point-in-Time (PiT) variant of Asia Year-over-Year Supply Change. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 24h
format - csv, json
jsonPossible values: timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/supply/apac_1y_supply_change_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. Average Spent Output Lifespan (ASOL) is the average age, in days, of spent transaction outputs.\n\nTechnical. Computed count-weighted across spent outputs, not weighted by coin volume. Outputs with a lifespan of less than one hour are discarded.\n\n\nThis is the Point-in-Time (PiT) variant of ASOL. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 1h, 24h
format - csv, json
jsonPossible values: timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/indicators/asol_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. Adjusted SOPR (aSOPR) is SOPR computed with all outputs whose lifespan is less than one hour ignored.\n\nInterpretation. Readings above 1 mean the average coin moved that day was sold at a profit, readings below 1 mean it was sold at a loss.\n\n\nThis is the Point-in-Time (PiT) variant of aSOPR. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 10m, 1h, 24h
format - csv, json
jsonPossible values: timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/indicators/sopr_adjusted_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. The number of "yes" votes cast by the validator committee attesting to the validity of the block produced in each slot.\n\nTechnical. Each epoch, up to 64 committees of at least 128 validators are algorithmically selected per slot for block production and attestation. For each slot, one validator from the committee is selected to propose a block, while the remaining committee members are responsible for casting attestation votes.\n\n\nThis is the Point-in-Time (PiT) variant of Attestation Count. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 10m, 1h, 24h
format - csv, json
jsonPossible values: timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/eth2/attestation_count_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. The mean total ETH balance per active Beacon Chain validator, calculated as total balance divided by the count of active validators.\n\nTechnical. Active validators are those that have completed the activation queue, are not in an exit queue, and have an effective balance greater than 32 ETH. The metric is bounded above by reward overhang on top of the 32 ETH effective cap and below by the 16 ETH ejection floor at which a validator is forcibly removed.\n\n\nThis is the Point-in-Time (PiT) variant of Average Validator Balance. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 10m, 1h, 24h
format - csv, json
jsonPossible values: currency - native, usd
timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/eth2/validator_balance_mean_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. Active-Value-to-Investor-Value (AVIV) Ratio is a Cointime-adjusted aggregate-profitability oscillator, the ratio of Active Market Cap to Investor Cap, equivalently spot price divided by the True Market Mean Price. The True Market Mean Price, or Active-Investor Price, is a representative cost-basis model for all coins acquired on secondary markets and is calculated as the ratio of Investor Cap to Active Supply.\n\nTechnical. Active Supply represents the economically active supply region. AVIV is proposed as a Cointime variant of MVRV comparing Active Market Cap to Investor Cap.\n\nInterpretation. The long-term mean and median sit very close to 1.0, consistent with the True Market Mean Price acting as a market-wide cost-basis anchor. Readings above 1 place the active-investor cohort in aggregate unrealized profit, readings below 1 place it in aggregate unrealized loss.\n\nNotes. Developed within the Cointime Economics framework for Bitcoin, a joint venture between Glassnode and ARK Invest. Full details are available as an overview primer (Version I, ARK) and a specialist guide (Version II, Glassnode).\n\n\nThis is the Point-in-Time (PiT) variant of AVIV. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 24h
format - csv, json
jsonPossible values: timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/indicators/aviv_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. Balanced Price is the difference between Realized Price and Transfer Price. Transfer Price is the cumulative sum of Coin Days Destroyed in USD, adjusted by circulating supply and total time since Bitcoin's inception. The model aims to detect major cycle bottoms.\n\nNotes. Created by David Puell. For more information, see Experiments on Cumulative Destruction.\n\n\nThis is the Point-in-Time (PiT) variant of Balanced Price. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 24h
format - csv, json
jsonPossible values: timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/indicators/balanced_price_usd_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. Beta to BTC (7D) is a 7-day rolling beta coefficient measuring an asset's sensitivity to Bitcoin's price movements, quantifying how much the asset tends to move relative to BTC.\n\nInterpretation. A beta of 1 means the asset moves in line with BTC, values greater than 1 indicate higher volatility relative to BTC (a beta of 1.5 means a 10 asset move), and values less than 1 indicate lower volatility. Negative beta indicates the asset tends to move opposite to BTC.\n\n\nThis is the Point-in-Time (PiT) variant of Beta to BTC (7D). PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 10m, 1h, 24h
format - csv, json
jsonPossible values: timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/market/beta_btc_7d_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. The amount of BTC held in addresses controlled by Druk Holding and Investments (DHI), the investment arm of the Royal Government of Bhutan.\n\n\nThis is the Point-in-Time (PiT) variant of Bhutan Government Balance. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 10m, 1h, 24h
format - csv, json
jsonPossible values: currency - native, usd
timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/distribution/balance_bhutan_government_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. Binary Coin Days Destroyed (Binary CDD) is the regime-flag transform of Supply-Adjusted CDD, computed by thresholding Adjusted CDD against its long-run average, asking whether more Adjusted CDDs were destroyed today than on average.\n\nTechnical. Thresholding against the long-run mean minimizes the impact of exchange movements, which do not accurately reflect long-term holder behavior.\n\nInterpretation. Readings of 1 mark days of above-average lifespan destruction, readings of 0 mark days of below-average lifespan destruction.\n\nNotes. Developed by Hans Hauge and Ikigai. For more information, see the post on Bitcoin days destroyed.\n\n\nThis is the Point-in-Time (PiT) variant of Binary CDD. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 10m, 1h, 24h
format - csv, json
jsonPossible values: timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/indicators/cdd_supply_adjusted_binary_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. Bitcoin Risk Signal gauges the risk of a major drawdown in the Bitcoin price.\n\nTechnical. Built from a set of proprietary indicators, including Bitcoin price data, on-chain data, and a selection of other trading metrics.\n\nNotes. For interpretation and methodology, see the signals dashboard, or explore Bitcoin Vector, a market regime framework.\n\n\nThis is the Point-in-Time (PiT) variant of Bitcoin Risk Signal. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 1h, 24h
format - csv, json
jsonPossible values: timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/signals/btc_risk_index_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. Bitcoin Sharpe Signal is a machine-learning long-entry signal for BTC, trained on on-chain data with the design goal of minimizing downside risk while capturing rising trends and enhancing risk-adjusted returns.\n\nTechnical. The model output is a confidence score rendered as a color ramp, with green indicating the highest confidence and orange through red indicating reduced confidence. The signal is refreshed daily at 04:00 UTC, finalizing the previous day's timestamp. The standard version carries a one-day lag. Disclosed foundational inputs include Percent of Entities in Profit and Short Term Holder SOPR.\n\nInterpretation. Readings above 0.5 have historically been associated with improved risk-adjusted Bitcoin performance.\n\nNotes. For interpretation and methodology, see the signal dashboard. Enterprise clients interested in same-day data or the underlying methodology can contact the Institutional team.\n\n\nThis is the Point-in-Time (PiT) variant of Bitcoin Sharpe Signal. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 24h
format - csv, json
jsonPossible values: timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/signals/btc_sharpe_signal_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. Bitcoin Sharpe Signal - Indicator I is derived directly from entities' profit, offering a nuanced view of entities profit momentum. It is used as one of the main features of the BSS model.\n\n\nThis is the Point-in-Time (PiT) variant of Bitcoin Sharpe Signal - Indicator I. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 24h
format - csv, json
jsonPossible values: timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/signals/btc_bss_indicator_1_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. Bitcoin Sharpe Signal - Indicator II is a refined version of the MVRV ratio that employs statistical techniques to amplify its predictive power, highlighting periods of potential overvaluation or undervaluation. It is used as one of the main features of the BSS model.\n\n\nThis is the Point-in-Time (PiT) variant of Bitcoin Sharpe Signal - Indicator II. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 24h
format - csv, json
jsonPossible values: timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/signals/btc_bss_indicator_2_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. Bitcoin Sharpe Signal - Indicator III draws from recent STH_SOPR data, offering insights into the market's short-term holder steadiness. It is used as one of the main features of the BSS model.\n\n\nThis is the Point-in-Time (PiT) variant of Bitcoin Sharpe Signal - Indicator III. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 24h
format - csv, json
jsonPossible values: timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/signals/btc_bss_indicator_3_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. Bitcoin Sharpe Signal - Indicator IV is a momentum reading on the percentage of circulating supply in profit, derived from a transformation applied to that base series.\n\nNotes. Used as one of the main features of the BSS model.\n\n\nThis is the Point-in-Time (PiT) variant of Bitcoin Sharpe Signal - Indicator IV. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 24h
format - csv, json
jsonPossible values: timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/signals/btc_bss_indicator_4_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. Bitcoin Sharpe Signal Short is a machine-learning short-entry signal for BTC, trained on on-chain data to anticipate periods of market turmoil and identify opportunities to short Bitcoin with reduced downside risk.\n\nTechnical. The model output is a confidence score rendered as a color ramp, with red indicating the highest confidence in a coming market sell-off and yellow through green indicating reduced confidence.\n\nInterpretation. Readings above 0.5 have historically been associated with imminent market downturns.\n\n\nThis is the Point-in-Time (PiT) variant of Bitcoin Sharpe Signal Short. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 1h, 24h
format - csv, json
jsonPossible values: timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/signals/btc_bss_short_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. The total number of blocks ever created and included in the main chain, i.e. the current block height.\n\n\nThis is the Point-in-Time (PiT) variant of Block Height. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 10m, 1h, 24h, 1w, 1month
format - csv, json
jsonPossible values: timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/blockchain/block_height_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. The mean time, in seconds, between mined blocks.\n\n\nThis is the Point-in-Time (PiT) variant of Block Interval (Mean). PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 10m, 1h, 24h, 1w, 1month
format - csv, json
jsonPossible values: timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/blockchain/block_interval_mean_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. The median time, in seconds, between mined blocks.\n\n\nThis is the Point-in-Time (PiT) variant of Block Interval (Median). PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 10m, 1h, 24h, 1w, 1month
format - csv, json
jsonPossible values: timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/blockchain/block_interval_median_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. The mean size, in bytes, of all blocks created within the time period.\n\n\nThis is the Point-in-Time (PiT) variant of Block Size (Mean). PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 10m, 1h, 24h, 1w, 1month
format - csv, json
jsonPossible values: timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/blockchain/block_size_mean_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. The total size, in bytes, of all blocks created within the time period.\n\n\nThis is the Point-in-Time (PiT) variant of Block Size (Total). PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 10m, 1h, 24h, 1w, 1month
format - csv, json
jsonPossible values: timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/blockchain/block_size_sum_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. The number of blocks created and included in the main blockchain in the given time period.\n\n\nThis is the Point-in-Time (PiT) variant of Blocks Mined. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 10m, 1h, 24h, 1w, 1month
format - csv, json
jsonPossible values: timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/blockchain/block_count_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. The USD value deposited into bridge smart contracts on Ethereum, flowing out of the Ethereum blockchain and into target blockchains, segmented by destination chain. Bridges are protocols that enable digital assets to be transferred from one blockchain to another. When an asset is transferred out of Ethereum, it is deposited and locked into a bridge smart contract. When the asset is transferred back to Ethereum, it is withdrawn and released from the contract.\n\nTechnical. Deposit Volume is computed daily by multiplying the number of tokens deposited into bridges by the latest daily price of each token. The metric only includes bridge contracts on the Ethereum side, covering bridge deposits into both L1 and L2 blockchains, providing information on the value transferred to both L1 competitors and L2 scaling solutions. Each bridge represents a single blockchain, except the ones labeled as multichain. That label is used to represent bridges that allow transferring assets across multiple different chains.\n\nNotes. This is the Point-in-Time (PiT) variant of Bridges Deposits By Chain. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.\n
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 24h
format - csv, json
jsonPossible values: timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/bridges/deposits_by_chain_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. The net USD value flowing into or out of Ethereum bridge smart contracts, computed as bridge deposits minus bridge withdrawals. Equivalently, the net USD value moving in or out of the Ethereum blockchain via bridges.\n\nTechnical. Only bridge contracts on the Ethereum side are included. Coverage spans bridge deposits into both L1 and L2 destinations, capturing value transferred to L1 competitors and to L2 scaling solutions. Each bridge represents a single destination chain, except those labeled `multichain`, which transfer assets across several chains. Bridges are protocols that move digital assets between blockchains: when an asset leaves Ethereum it is deposited and locked into a bridge contract, and when it returns it is withdrawn and released.\n\nInterpretation. Positive values mean more value is being deposited into bridges, i.e. a net outflow from Ethereum. Negative values mean more value is being withdrawn from bridges, i.e. a net inflow back to Ethereum.\n\nNotes. This is the Point-in-Time (PiT) variant of Bridges Net Flow By Chain. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.\n
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 24h
format - csv, json
jsonPossible values: timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/bridges/net_volume_by_chain_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. The number of transactions on the Ethereum network by contracts that allow transfer of tokens between different blockchains.\n\n\nThis is the Point-in-Time (PiT) variant of Bridges Transactions (Absolute). PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 24h
format - csv, json
jsonPossible values: timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/transactions/transfers_count_bridges_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. The share of transactions on the Ethereum network by contracts that allow transfer of tokens between different blockchains.\n\n\nThis is the Point-in-Time (PiT) variant of Bridges Transactions (Relative). PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 24h
format - csv, json
jsonPossible values: timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/transactions/transfers_count_bridges_relative_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. The total USD value locked inside the Ethereum side of bridge smart contracts, broken out per destination blockchain. Locked tokens are unavailable on Ethereum and available on the target chain.\n\nTechnical. TVL is computed daily by multiplying the number of tokens locked in each bridge smart contract by the latest daily price for each token. Bridges are protocols that transfer digital assets from one blockchain to another. When an asset leaves Ethereum, it is deposited and locked into a bridge smart contract, and when it returns to Ethereum it is withdrawn and released. This metric only includes bridge contracts on the Ethereum side, covering deposits into both L1 and L2 blockchains. Each bridge represents a single destination chain, except those labeled multichain, which fan out across multiple chains.\n\nInterpretation. A rising series means value is flowing out of Ethereum into the target chain, and a falling series means value is flowing back into Ethereum.\n\nNotes. This is the Point-in-Time (PiT) variant of Bridges TVL. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.\n
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 24h
format - csv, json
jsonPossible values: timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/bridges/total_value_locked_by_chain_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. The TVL dominance of each target-blockchain bridge, expressed as that bridge's TVL divided by the total TVL across all bridges.\n\nTechnical. Per-bridge TVL is computed daily by multiplying the number of tokens locked in each bridge smart contract by the latest daily price for each token, then divided by the total TVL across all bridges. Bridges are protocols that transfer digital assets from one blockchain to another. When an asset leaves Ethereum, it is deposited and locked into a bridge smart contract, and when it returns to Ethereum it is withdrawn and released. This metric only includes bridge contracts on the Ethereum side, covering deposits into both L1 and L2 blockchains. Each bridge represents a single destination chain, except those labeled multichain, which fan out across multiple chains.\n\nInterpretation. A rising relative TVL means the target blockchain is gaining USD-denominated dominance inside the bridge economy, and a falling one means it is losing it.\n\nNotes. This is the Point-in-Time (PiT) variant of Bridges TVL Relative. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.\n
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 24h
format - csv, json
jsonPossible values: timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/bridges/total_value_locked_by_chain_relative_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. The total USD value withdrawn from bridge smart contracts on Ethereum and therefore flowing back into Ethereum and out of the target blockchains, broken out per destination chain.\n\nTechnical. Withdrawal volume is computed daily by multiplying the number of tokens withdrawn from bridges by the latest daily price of each token. Bridges are protocols that transfer digital assets from one blockchain to another. When an asset leaves Ethereum, it is deposited and locked into a bridge smart contract, and when it returns to Ethereum it is withdrawn and released. This metric only includes bridge contracts on the Ethereum side, covering deposits into both L1 and L2 blockchains. Each bridge represents a single destination chain, except those labeled multichain, which fan out across multiple chains.\n\nNotes. This is the Point-in-Time (PiT) variant of Bridges Withdrawals By Chain. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.\n
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 24h
format - csv, json
jsonPossible values: timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/bridges/withdrawals_by_chain_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. BSS Goldilocks Short Signal is the signal decision extracted from the Goldilocks Zone, marking a prime area to be short on Bitcoin according to the Bitcoin Sharpe Signal Short.\n\n\nThis is the Point-in-Time (PiT) variant of BSS Goldilocks Short Signal. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 1h, 24h
format - csv, json
jsonPossible values: timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/signals/btc_bss_goldilocks_short_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. The BSS Goldilocks Signal is derived from the heuristics of the ML model used to construct the Bitcoin Sharpe Signal. It activates when the conditions of the Goldilocks zone are met, identifying prime opportunities to enhance the risk-adjusted return on Bitcoin.\n\nTechnical. Conditions of the Goldilocks zone: BSS Indicator I is between 52 and 65, and BSS Indicator III is below 4%.\n\n\nThis is the Point-in-Time (PiT) variant of BSS Goldilocks Signal. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 24h
format - csv, json
jsonPossible values: timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/signals/btc_bss_goldilocks_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. BTC Dominance (Bitcoin Dominance) is Bitcoin's market capitalization expressed as a percentage of the total market capitalization of all cryptocurrencies.\n\nTechnical. Calculated by dividing Bitcoin's market cap by the total cryptocurrency market cap. The metric is updated daily at 10:15 UTC, providing the previous day's data point at this time.\n\nInterpretation. Higher readings indicate capital is concentrated in Bitcoin, while lower readings indicate capital is distributed across altcoins and stablecoins.\n\n\nThis is the Point-in-Time (PiT) variant of BTC Dominance. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 24h
format - csv, json
jsonPossible values: timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/market/btc_dominance_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. Burn Rate (Base Fee) is the ongoing pace at which ETH is destroyed by the EIP-1559 base-fee mechanism introduced by the London Hard Fork.\n\nTechnical. EIP-1559 established a per-transaction base fee that is sent to a burn address rather than to the block producer, reducing the overall ETH supply at a rate set by blockspace demand and per-block fullness.\n\nInterpretation. Tracks the deflationary pressure on the ETH supply base.\n\n\nThis is the Point-in-Time (PiT) variant of Burn Rate (Base Fee). PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 10m, 1h, 24h, 1w, 1month
format - csv, json
jsonPossible values: currency - native, usd
timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/supply/burn_rate_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. Burned Supply is the cumulative sum of ETH destroyed by the EIP-1559 base-fee mechanism since the London Hard Fork activated it.\n\nTechnical. EIP-1559 established a per-transaction base fee that is sent to a burn address rather than to the block producer, reducing the overall ETH supply.\n\nInterpretation. Indicates the cumulative deflationary pressure on Ethereum.\n\n\nThis is the Point-in-Time (PiT) variant of Burned Supply. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 10m, 1h, 24h, 1w, 1month
format - csv, json
jsonPossible values: currency - native, usd
timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/supply/burned_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. The model-interpolated implied volatility of 10-delta call options by tenor. Each data point reports the IV at target delta 10 for the selected asset, exchange, and quote currency.\n\nTechnical. Values are obtained by interpolation across delta and maturity onto standard tenors.\n\n\nThis is the Point-in-Time (PiT) variant of Call IV Delta 10. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 10m, 1h, 24h
format - csv, json
jsonPossible values: exchange name - binance, bybit, deribit, okex
timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/options/iv_call_delta_10_pit?a=text&e=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. The model-interpolated implied volatility of 15-delta call options by tenor. Each data point reports the IV at target delta 15 for the selected asset, exchange, and quote currency.\n\nTechnical. Values are obtained by interpolation across delta and maturity onto standard tenors.\n\n\nThis is the Point-in-Time (PiT) variant of Call IV Delta 15. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 10m, 1h, 24h
format - csv, json
jsonPossible values: exchange name - binance, bybit, deribit, okex
timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/options/iv_call_delta_15_pit?a=text&e=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. The model-interpolated implied volatility of 20-delta call options by tenor. Each data point reports the IV at target delta 20 for the selected asset, exchange, and quote currency.\n\nTechnical. Values are obtained by interpolation across delta and maturity onto standard tenors.\n\n\nThis is the Point-in-Time (PiT) variant of Call IV Delta 20. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 10m, 1h, 24h
format - csv, json
jsonPossible values: exchange name - binance, bybit, deribit, okex
timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/options/iv_call_delta_20_pit?a=text&e=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. The model-interpolated implied volatility of 25-delta call options by tenor. Each data point reports the IV at target delta 25 for the selected asset, exchange, and quote currency.\n\nTechnical. Values are obtained by interpolation across delta and maturity onto standard tenors.\n\n\nThis is the Point-in-Time (PiT) variant of Call IV Delta 25. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 10m, 1h, 24h
format - csv, json
jsonPossible values: exchange name - binance, bybit, deribit, okex
timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/options/iv_call_delta_25_pit?a=text&e=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. The model-interpolated implied volatility of 5-delta call options by tenor. Each data point reports the IV at target delta 5 for the selected asset, exchange, and quote currency.\n\nTechnical. Values are obtained by interpolation across delta and maturity onto standard tenors.\n\n\nThis is the Point-in-Time (PiT) variant of Call IV Delta 5. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 10m, 1h, 24h
format - csv, json
jsonPossible values: exchange name - binance, bybit, deribit, okex
timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/options/iv_call_delta_5_pit?a=text&e=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. The time series of model-interpolated 50-delta call implied volatility by tenor.\n\nTechnical. Each data point represents the IV at target delta 50 for the selected asset, exchange and quote currency, obtained via interpolation across delta and maturity onto standard tenors.\n\n\nThis is the Point-in-Time (PiT) variant of Call IV Delta 50. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 10m, 1h, 24h
format - csv, json
jsonPossible values: exchange name - binance, bybit, deribit, okex
timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/options/iv_call_delta_50_pit?a=text&e=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. Call-Put Delta Skew (Delta 10) is the model-interpolated implied-volatility skew between 10-delta calls and 10-delta puts, reported by tenor. Each datapoint is the difference between call IV and put IV at target delta 10 for the selected asset, exchange, and quote currency.\n\nTechnical. Values are taken from a single interpolated IV surface across delta and maturity, then projected onto standard tenors. The skew is unnormalized and expressed directly in IV points as call minus put.\n\n\nThis is the Point-in-Time (PiT) variant of Call-Put 10 Delta Skew. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
frequency interval - 10m, 1h, 24h
format - csv, json
jsonPossible values: exchange name - binance, bybit, deribit, okex
timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/options/10delta_skew_call_put_all_pit?a=text&e=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. Call-Put Delta Skew (Delta 15) is the model-interpolated implied-volatility skew between 15-delta calls and 15-delta puts, reported by tenor. Each datapoint is the difference between call IV and put IV at target delta 15 for the selected asset, exchange, and quote currency.\n\nTechnical. Values are taken from a single interpolated IV surface across delta and maturity, then projected onto standard tenors. The skew is unnormalized and expressed directly in IV points as call minus put.\n\n\nThis is the Point-in-Time (PiT) variant of Call-Put 15 Delta Skew. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
frequency interval - 10m, 1h, 24h
format - csv, json
jsonPossible values: exchange name - binance, bybit, deribit, okex
timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/options/15delta_skew_call_put_all_pit?a=text&e=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. Call-Put Delta Skew (Delta 20) is the model-interpolated implied-volatility skew between 20-delta calls and 20-delta puts, reported by tenor. Each datapoint is the difference between call IV and put IV at target delta 20 for the selected asset, exchange, and quote currency.\n\nTechnical. Values are taken from a single interpolated IV surface across delta and maturity, then projected onto standard tenors. The skew is unnormalized and expressed directly in IV points as call minus put.\n\n\nThis is the Point-in-Time (PiT) variant of Call-Put 20 Delta Skew. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
frequency interval - 10m, 1h, 24h
format - csv, json
jsonPossible values: exchange name - binance, bybit, deribit, okex
timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/options/20delta_skew_call_put_all_pit?a=text&e=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. Call-Put Delta Skew (Delta 25) is the difference between call and put implied volatility at target delta 25, published as a time series across constant-maturity tenors for the selected asset, exchange and quote currency.\n\nTechnical. Each data point is sampled from the same model-interpolated IV surface across delta and maturity, projected onto standard tenors. The skew is unnormalized and expressed directly in IV points (call minus put).\n\nInterpretation. Positive readings mean calls trade richer than equivalent-delta puts. Negative readings mean puts trade richer than calls.\n\n\nThis is the Point-in-Time (PiT) variant of Call-Put 25 Delta Skew. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
frequency interval - 10m, 1h, 24h
format - csv, json
jsonPossible values: exchange name - binance, bybit, deribit, okex
timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/options/25delta_skew_call_put_all_pit?a=text&e=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. Call-Put Delta Skew (Delta 5) is the model-interpolated implied-volatility skew between 5-delta calls and 5-delta puts, reported by tenor. Each datapoint is the difference between call IV and put IV at target delta 5 for the selected asset, exchange, and quote currency.\n\nTechnical. Values are taken from a single interpolated IV surface across delta and maturity, then projected onto standard tenors. The skew is unnormalized and expressed directly in IV points as call minus put.\n\n\nThis is the Point-in-Time (PiT) variant of Call-Put 5 Delta Skew. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
frequency interval - 10m, 1h, 24h
format - csv, json
jsonPossible values: exchange name - binance, bybit, deribit, okex
timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/options/5delta_skew_call_put_all_pit?a=text&e=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Time series of model-interpolated 50-delta call–put implied volatility skew by tenor.\nEach data point represents the difference between call and put IV at target delta 50 for the selected asset, exchange and quote currency, obtained from the same interpolated IV surface (across delta and maturity) projected onto standard tenors. This skew is unnormalized (expressed directly in IV points, call minus put).\n\nThis is the Point-in-Time (PiT) variant of Call-Put 50 Delta Skew. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/options/50delta_skew_call_put_all_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]The amount of BTC held in addresses controlled by Cash App. Note that this metric is based on address labels that we constantly keep updating. The values shown here provide an estimate and may not necessarily reflect the full balance.\n\nThis is the Point-in-Time (PiT) variant of Cash App Balance. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 10m, 1h, 24h
format - csv, json
jsonPossible values: currency - native, usd
timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/distribution/balance_cashapp_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. The total amount of futures contracts open interest that is margined in USD or USD-pegged stablecoins.\n\nTechnical. Stablecoins include USDT, USDC and BUSD.\n\n\nThis is the Point-in-Time (PiT) variant of Cash-Margined Futures Open Interest. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 10m, 1h, 24h
format - csv, json
jsonPossible values: currency - native, usd
exchange name - aggregated, binance, bitfinex, bitget, bybit, coinbase-international, crypto.com, deribit, dydx, gate.io, huobi, hyperliquid, kraken, kucoin, okex
timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/derivatives/futures_open_interest_cash_margin_sum_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. The mean value of a transfer, adjusted by change volume.\n\nTechnical. Only successful transfers are counted.\n\n\nThis is the Point-in-Time (PiT) variant of Change-Adjusted Volume (Mean). PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 10m, 1h, 24h, 1w, 1month
format - csv, json
jsonPossible values: currency - native, usd
timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/transactions/transfers_volume_adjusted_mean_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. The median value of a transfer, adjusted by change volume.\n\nTechnical. Only successful transfers are counted.\n\n\nThis is the Point-in-Time (PiT) variant of Change-Adjusted Volume (Median). PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 10m, 1h, 24h, 1w, 1month
format - csv, json
jsonPossible values: currency - native, usd
timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/transactions/transfers_volume_adjusted_median_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. The total amount of coins transferred on-chain, adjusted by change volume.\n\nTechnical. Change adjustment drops outputs whose receiving address also appears as a sender on the same transaction, the obvious within-transaction change. Only successful transfers are counted.\n\n\nThis is the Point-in-Time (PiT) variant of Change-Adjusted Volume (Total). PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 10m, 1h, 24h, 1w, 1month
format - csv, json
jsonPossible values: currency - native, usd
timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/transactions/transfers_volume_adjusted_sum_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. The total amount of all coins ever created or issued, i.e. the circulating supply.\n\n\nThis is the Point-in-Time (PiT) variant of Circulating Supply. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 10m, 1h, 24h, 1w, 1month
format - csv, json
jsonPossible values: currency - native, usd
timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/supply/current_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. Coin Blocks Created (CBC) is the cumulative tally of coinblocks accumulated by the network, computed by multiplying the value of each coin that has ever existed by the number of blocks the coin was unspent.\n\n\nThis is the Point-in-Time (PiT) variant of Coin Blocks Created (CBC). PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 10m, 1h, 24h
format - csv, json
jsonPossible values: timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/indicators/coin_blocks_created_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. Coin Blocks Destroyed for any given transaction is calculated by taking the number of coins in a transaction and multiplying it by the number of blocks it has been since those coins were last spent.\n\n\nThis is the Point-in-Time (PiT) variant of Coin Blocks Destroyed. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 10m, 1h, 24h
format - csv, json
jsonPossible values: timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/indicators/coin_blocks_destroyed_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. Coin Days Destroyed (CDD) measures the volume-weighted age of coins spent on a given day.\n\nTechnical. For any given transaction, CDD is calculated by taking the number of coins in the transaction and multiplying it by the number of days since those coins were last spent.\n\n\nThis is the Point-in-Time (PiT) variant of Coin Days Destroyed (CDD). PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 10m, 1h, 24h
format - csv, json
jsonPossible values: currency - native, usd
timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/indicators/cdd_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. Coin Years Destroyed (CYD) is the 365-day rolling sum of Coin Days Destroyed (CDD), the amount of coin days destroyed over the trailing year.\n\nInterpretation. CYD is indicative of long-term holder behaviour.\n\nNotes. First put forward by ARK Invest.\n\n\nThis is the Point-in-Time (PiT) variant of Coin Years Destroyed (CYD). PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 24h
format - csv, json
jsonPossible values: timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/indicators/cyd_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. The relative price gap between on Coinbase (USD) and the multi-exchange global price, expressed as a percentage of the global price.\n\nInterpretation. A positive value means trades at a premium on Coinbase, often associated with buying pressure from US-based investors. A negative value means a discount, often associated with selling pressure.\n\nThis is the Point-in-Time (PiT) variant of Coinbase Premium. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 10m, 1h, 24h
format - csv, json
jsonPossible values: timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/market/coinbase_premium_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. The total count of indistinguishable outputs in coinjoin transactions.\n\nTechnical. The metric is an aggregate of different coinjoin providers. Coinjoin metrics rely on heuristics and statistical methods that are refined over time. The series is therefore mutable: its established history is stable, but recent data points may revise as detection improves.\n\n\nThis is the Point-in-Time (PiT) variant of Coinjoin Output Count. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 24h
format - csv, json
jsonPossible values: timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/transactions/transfers_from_coinjoins_count_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. The total amount of indistinguishable outputs in coinjoin transactions, representing the volume of coins mixed by different coinjoin providers.\n\nTechnical. Coinjoin metrics rely on heuristics and statistical methods that are refined over time. The series is therefore mutable: its established history is stable, but recent data points may revise as detection improves.\n\n\nThis is the Point-in-Time (PiT) variant of Coinjoin Output Volume. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 24h
format - csv, json
jsonPossible values: currency - native, usd
timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/transactions/transfers_volume_from_coinjoins_sum_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. The total number of smart contract calls on the Ethereum network initiated by Externally Owned Addresses (EOAs), i.e. external transactions.\n\nTechnical. Only successful transactions are counted.\n\n\nThis is the Point-in-Time (PiT) variant of Contract Calls (External). PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 1h, 24h
format - csv, json
jsonPossible values: timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/transactions/contract_calls_external_count_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. The total number of internal smart contract calls on the Ethereum network, i.e. contract calls initiated by other contracts (internal transactions).\n\nTechnical. Only successful transactions are counted.\n\n\nThis is the Point-in-Time (PiT) variant of Contract Calls (Internal). PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 1h, 24h
format - csv, json
jsonPossible values: timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/transactions/contract_calls_internal_count_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. Correlation to BTC (7D) is the 7-day rolling correlation coefficient between 's returns and Bitcoin's returns, measuring how closely the asset's price movements track Bitcoin over a weekly period.\n\nInterpretation. Values range from -1 to 1: 1 indicates perfect positive correlation (the asset moves in the same direction as BTC), -1 indicates perfect negative correlation (opposite direction), and 0 indicates no correlation.\n\n\nThis is the Point-in-Time (PiT) variant of Correlation to BTC (7D). PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 10m, 1h, 24h
format - csv, json
jsonPossible values: timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/market/correlation_btc_7d_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. The Cost Basis Distribution (CBD) Heatmap is a price-versus-time visualization of supply density across cost-basis levels over a specified period (e.g. 1 month, 1 year). The y-axis represents the cost basis on a log scale, set from 1 above the maximum price within the chosen period, and each pixel's color intensity reflects the concentration of supply at that price level.\n\nTechnical. All CBD metrics use an address-based approach, analyzing holdings based on individual wallet addresses for consistency across digital assets and comparability across blockchain architectures. This contrasts with the UTXO-based approach used in metrics like URPD, which categorizes supply based on unspent transaction outputs and is typically used for chains like Bitcoin, so metrics for UTXO-based assets may show slight differences across these distinct computational methods.\n\nInterpretation. Dense bands identify price levels where significant portions of supply were acquired, informing where historical accumulation may act as support or resistance.\n\n\nThis is the Point-in-Time (PiT) variant of Cost Basis Distribution Heatmap. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 24h
format - csv, json
jsonPossible values: timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/indicators/cost_basis_distribution_heatmap_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. Cost Basis Distribution (CBD) Heatmap for Long-Term Holders visualizes supply density across price levels over a selected period (e.g. 1 month, 1 year). The y-axis represents cost basis on a log scale, set from 1 above the maximum price within the chosen period. Each pixel's color intensity reflects the concentration of LTH-held supply at that price level, allowing identification of where significant portions of the asset's supply were acquired and of potential support and resistance areas based on historical acquisition levels.\n\nTechnical. All CBD metrics use an address-based approach, analyzing holdings at the individual wallet-address level for consistency across digital assets and comparability across blockchain architectures. This contrasts with a UTXO-based approach (used in metrics like URPD), which categorizes supply based on unspent transaction outputs and is typically used for chains like Bitcoin. Metrics for UTXO-based assets may therefore show slight differences when compared across these distinct computational methods.\n\n\nThis is the Point-in-Time (PiT) variant of Cost Basis Distribution Heatmap (LTH). PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 24h
format - csv, json
jsonPossible values: timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/indicators/cost_basis_distribution_lth_heatmap_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. The Short-Term Holder Cost Basis Distribution (CBD) Heatmap is a price-versus-time visualization of STH supply density across cost-basis levels over a specified period (e.g. 1 month, 1 year). The y-axis represents the cost basis on a log scale, set from 1 above the maximum price within the chosen period, and each pixel's color intensity reflects the concentration of STH supply at that price level.\n\nTechnical. All CBD metrics use an address-based approach, analyzing holdings based on individual wallet addresses for consistency across digital assets and comparability across blockchain architectures. This contrasts with the UTXO-based approach used in metrics like URPD, which categorizes supply based on unspent transaction outputs and is typically used for chains like Bitcoin, so metrics for UTXO-based assets may show slight differences across these distinct computational methods.\n\nInterpretation. Dense bands identify price levels where significant portions of STH supply were acquired, informing where recent cohort acquisition may act as support or resistance.\n\n\nThis is the Point-in-Time (PiT) variant of Cost Basis Distribution Heatmap (STH). PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 24h
format - csv, json
jsonPossible values: timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/indicators/cost_basis_distribution_sth_heatmap_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. Cost Basis Distribution (CBD) Quantiles is the distribution of realized prices for unspent digital assets, divided into 100 quantiles (percentiles) for each day. It provides a granular view of where total supply was acquired, supports identification of the share of supply acquired below the current market price (and therefore potentially at a loss), and surfaces price levels with denser supply concentration as denser clustering of the quantile lines over a given time range.\n\nTechnical. All CBD metrics use an address-based approach, analyzing holdings at the individual wallet-address level for consistency across digital assets and comparability across blockchain architectures. This contrasts with a UTXO-based approach (used in metrics like URPD), which categorizes supply based on unspent transaction outputs and is typically used for chains like Bitcoin. Metrics for UTXO-based assets may therefore show slight differences when compared across these distinct computational methods.\n\n\nThis is the Point-in-Time (PiT) variant of Cost Basis Distribution Quantiles. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 24h
format - csv, json
jsonPossible values: timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/indicators/cost_basis_distribution_quantiles_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. The total amount of futures contracts open interest that is margined in the native coin (e.g. BTC) and not in USD or stablecoin.\n\nTechnical. For Ethereum, contracts can be margined both in ETH or BTC.\n\n\nThis is the Point-in-Time (PiT) variant of Crypto-Margined Futures Open Interest. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 10m, 1h, 24h
format - csv, json
jsonPossible values: currency - native, usd
exchange name - aggregated, binance, bitfinex, bitget, bybit, coinbase-international, crypto.com, deribit, dydx, gate.io, huobi, hyperliquid, kraken, kucoin, okex
timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/derivatives/futures_open_interest_crypto_margin_sum_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. Cumulative Value-Days Destroyed (CVDD) is the ratio of the cumulative USD value of Coin Days Destroyed to the market age in days.\n\nInterpretation. Historically, CVDD has been an accurate indicator for global Bitcoin market bottoms.\n\nNotes. Created by Willy Woo. For more information, see his article on experiments on cumulative destruction.\n\n\nThis is the Point-in-Time (PiT) variant of CVDD. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 24h
format - csv, json
jsonPossible values: timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/indicators/cvdd_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. The number of transactions on the Ethereum network by on-chain financial instruments and protocols implemented as smart contracts, including decentralized exchanges (DEXs).\n\n\nThis is the Point-in-Time (PiT) variant of DeFi Transactions (Absolute). PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 24h
format - csv, json
jsonPossible values: timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/transactions/transfers_count_defi_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. The share of transactions on the Ethereum network by on-chain financial instruments and protocols implemented as smart contracts, including decentralized exchanges (DEXs).\n\n\nThis is the Point-in-Time (PiT) variant of DeFi Transactions (Relative). PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 24h
format - csv, json
jsonPossible values: timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/transactions/transfers_count_defi_relative_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. Delta Cap is the difference between Realized Cap and Average Cap, where Average Cap is the life-to-date moving average of Market Cap. The per-coin form, Delta Price, is Realized Price minus the life-to-date moving average of price. It is designed to detect major market bottoms in Bitcoin cycles.\n\nNotes. Originally proposed by David Puell. For more information, see his introductory article.\n\n\nThis is the Point-in-Time (PiT) variant of Delta Cap. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 10m, 1h, 24h, 1w, 1month
format - csv, json
jsonPossible values: timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/market/deltacap_usd_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. The number of unique addresses that appeared as a sender in a transaction sending funds to exchanges.\n\nTechnical. Exchange metrics are based on Glassnode's continually updated set of labeled exchange addresses, together with statistical and data-science methods that are refined over time. The series is therefore mutable: its established history is stable, but recent data points may revise as labels update. For methodology and limitations, see our article on exchange metrics and Exchange Data Transparency Notice.\n\n\nThis is the Point-in-Time (PiT) variant of Depositing Addresses. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 10m, 1h, 24h, 1w, 1month
format - csv, json
jsonPossible values: timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/addresses/sending_to_exchanges_count_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. The current estimated number of hashes required to mine a block.\n\nTechnical. difficulty is often denoted as the relative difficulty with respect to the genesis block, which required approximately 2^32 hashes. For better comparison across blockchains, values here are denoted in raw hashes.\n\n\nThis is the Point-in-Time (PiT) variant of Difficulty. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 10m, 1h, 24h, 1w, 1month
format - csv, json
jsonPossible values: timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/mining/difficulty_latest_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. Difficulty Ribbon is an indicator built from seven simple moving averages (200d, 128d, 90d, 60d, 40d, 25d, 14d) of Bitcoin mining difficulty, stacked as a ribbon.\n\nInterpretation. Historically, periods when the ribbon compresses have been considered favourable buying opportunities.\n\nNotes. Created by Willy Woo. For more information, see the introductory article.\n\n\nThis is the Point-in-Time (PiT) variant of Difficulty Ribbon. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 24h
format - csv, json
jsonPossible values: timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/indicators/difficulty_ribbon_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. Difficulty Ribbon Compression is a market indicator that uses a normalized standard deviation to quantify compression of the Difficulty Ribbon.\n\nTechnical. The compression threshold is set here at 0.05.\n\nInterpretation. Low values mark zones of high compression in the ribbon, historically associated with buying opportunities.\n\n\nThis is the Point-in-Time (PiT) variant of Difficulty Ribbon Compression. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 24h
format - csv, json
jsonPossible values: timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/indicators/difficulty_ribbon_compression_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. Donald Trump Balance is the amount of ETH held in addresses controlled by Donald Trump.\n\n\nThis is the Point-in-Time (PiT) variant of Donald Trump Balance. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 10m, 1h, 24h
format - csv, json
jsonPossible values: currency - native, usd
timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/distribution/balance_donald_trump_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. Average Coin Dormancy is the average number of days destroyed per coin transacted, defined as the ratio of coin days destroyed to total transfer volume.\n\nNotes. Created by Reginald Smith and David Puell. See Bitcoin Average Dormancy for the introduction.\n\n\nThis is the Point-in-Time (PiT) variant of Dormancy. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 10m, 1h, 24h
format - csv, json
jsonPossible values: timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/indicators/average_dormancy_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. Dormancy Flow is the ratio of the current market capitalization to the annualized dormancy value (measured in USD).\n\nInterpretation. The metric can be used to time market lows and to assess whether a bull market remains in relatively normal conditions, helping confirm whether an asset is in a bullish or bearish primary trend.\n\nNotes. Put forward by David Puell. For more information, see his introductory article.\n\n\nThis is the Point-in-Time (PiT) variant of Dormancy Flow. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 24h
format - csv, json
jsonPossible values: timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/indicators/dormancy_flow_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. Downside Implied Volatility measures downside-focused implied volatility derived from OTM puts, integrated across strikes and time-weighted to fixed tenors. In aggregate, it captures the premium the options market is paying for protection against falling prices. It is one of the two core components that underpin the Glassnode Skew Index.\n\nInterpretation. Use alongside Upside Implied Volatility and the Glassnode Skew Index to diagnose whether call-demand (upside tails) or downside hedging is driving market asymmetry.\n\nNotes. For further details, see Measuring Market Asymmetry: The Glassnode Skew Index.\n\n\nThis is the Point-in-Time (PiT) variant of Downside IV. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 10m, 1h, 24h
format - csv, json
jsonPossible values: exchange name - binance, bybit, deribit, okex
timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/options/skew_dnvol_pit?a=text&e=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. The L1 Momentum Signal evaluates the propensity of a Layer 1 ecosystem to move into an exponential trend, either positive or negative. It can be used to gauge the likelihood of a short-term exponential price momentum continuing and intensifying.\n\nTechnical. Based on a proprietary statistical method that identifies whether the underlying distribution of an asset's returns has departed from its usual structure. Data at 1-hour resolution is updated every 6 hours due to a data-source limitation for this metric.\n\nNotes. For more information, see the signals dashboard.\n\n\nThis is the Point-in-Time (PiT) variant of Ecosystem Momentum Signal. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 1h, 24h
format - csv, json
jsonPossible values: timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/signals/ecosystem_momentum_index_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. El Salvador Government Balance is the on-chain BTC balance attributed to the government of El Salvador, as reported by the National Bitcoin Office (ONBTC).\n\nNotes. For additional context, see the official government website.\n\n\nThis is the Point-in-Time (PiT) variant of El Salvador Government Balance. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 10m, 1h, 24h
format - csv, json
jsonPossible values: currency - native, usd
timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/distribution/balance_el_salvador_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. The net growth of unique entities in the network, defined as the difference between new entities and 'disappearing' entities (entities with a zero balance that had a non-zero balance at the previous timestamp).\n\nTechnical. Entities are clusters of addresses estimated to be controlled by the same actor, identified through advanced heuristics and Glassnode's proprietary clustering algorithms. Entity-based metrics rely on statistical and data-science methods that are refined over time. The series is therefore mutable: its established history is stable, but recent data points may revise as clustering improves. For methodology, see our article on account-based metrics. The computation requires statistical information from several days and is therefore only available with a lag of one week.\n\nNotes. For more information, see our article on how many entities hold Bitcoin.\n\n\nThis is the Point-in-Time (PiT) variant of Entities Net Growth. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 24h
format - csv, json
jsonPossible values: timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/entities/net_growth_count_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. The relative distribution of the circulating supply held by entities, broken down by balance band.\n\nTechnical. Exchange-labelled and miner-labelled entities are excluded from the band totals and treated as separate clusters.\n\nNotes. This is the Point-in-Time (PiT) variant of Entities Supply Distribution. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.\n
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 10m, 1h, 24h
format - csv, json
jsonPossible values: timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/entities/supply_distribution_relative_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. Entity- and Supply-Adjusted Coin Years Destroyed is the 365-day rolling sum of Coin Days Destroyed (CDD), computed on the entity-clean spending stream and normalized by circulating supply.\n\nTechnical. Entity-adjustment discards transactions within addresses controlled by the same network participant. Supply-adjustment divides by circulating supply to account for the increasing baseline of the metric over time.\n\nInterpretation. CYD is indicative of long-term holder behaviour.\n\nNotes. First put forward by ARK Invest and further developed by Glassnode by adjusting for the circulating supply. For more information on entity-adjustment and account-based metrics, read our articles here and here.\n\n\nThis is the Point-in-Time (PiT) variant of Entity- and Supply-Adjusted CYD. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 24h
format - csv, json
jsonPossible values: timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/indicators/cyd_account_based_supply_adjusted_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. Entity-Adjusted 90D Coin Days Destroyed (eCDD-90) is the 90-day rolling sum of Coin Days Destroyed (CDD), with transactions between addresses controlled by the same network participant discarded and the result normalized by time to account for the increasing destructible-coin-age baseline.\n\nTechnical. Same-entity reshuffles are filtered at the daily layer using account-based clustering before the 90-day rolling sum is taken. Time normalization adjusts for the secular drift in the destructible coin-age inventory as the network ages.\n\nNotes. For more information on entity-adjustment and account-based metrics, read our articles here and here.\n\n\nThis is the Point-in-Time (PiT) variant of Entity-Adjusted 90D Coin Days Destroyed (eCDD-90). PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 24h
format - csv, json
jsonPossible values: timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/indicators/cdd90_account_based_age_adjusted_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. Entity-Adjusted ASOL is a variant of ASOL that discards transactions between addresses of the same entity ("in-house" transactions), so the average reflects real economic activity only and provides an improved market signal compared to its raw UTXO-based counterpart.\n\nNotes. For more information on entity-adjustment and account-based metrics, read our articles here and here.\n\n\nThis is the Point-in-Time (PiT) variant of Entity-Adjusted ASOL. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 10m, 1h, 24h
format - csv, json
jsonPossible values: timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/indicators/asol_account_based_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. Entity-Adjusted CDD is the variant of Coin Days Destroyed that counts only spent outputs whose movement crosses an entity boundary, so the print reflects real economic activity rather than in-house reshuffles.\n\nTechnical. Transactions between addresses of the same entity are discarded, providing an improved market signal compared to the raw UTXO-based counterpart.\n\nNotes. For more information on entity-adjustment and account-based metrics, read our articles here and here.\n\n\nThis is the Point-in-Time (PiT) variant of Entity-Adjusted CDD. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 10m, 1h, 24h
format - csv, json
jsonPossible values: timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/indicators/cdd_account_based_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. Entity-Adjusted Coin Years Destroyed is the 365-day rolling sum of Coin Days Destroyed (CDD), the amount of coin days destroyed over the trailing year, computed on the entity-clean spending stream.\n\nTechnical. This version is entity-adjusted, meaning that transactions within addresses controlled by the same network participant are discarded.\n\nInterpretation. CYD is indicative of long-term holder behaviour.\n\nNotes. First put forward by ARK Invest. For more information on entity-adjustment and account-based metrics, read our articles here and here.\n\n\nThis is the Point-in-Time (PiT) variant of Entity-Adjusted CYD. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 24h
format - csv, json
jsonPossible values: timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/indicators/cyd_account_based_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. Entity-Adjusted Dormancy is the variant of Average Coin Dormancy that counts only spent outputs whose movement crosses an entity boundary, so the print reflects real economic activity rather than in-house reshuffles.\n\nTechnical. Transactions between addresses of the same entity are discarded, providing an improved market signal compared to the raw UTXO-based counterpart.\n\nNotes. For more information on entity-adjustment and account-based metrics, read our articles here and here.\n\n\nThis is the Point-in-Time (PiT) variant of Entity-Adjusted Dormancy. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 10m, 1h, 24h
format - csv, json
jsonPossible values: timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/indicators/dormancy_account_based_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. Entity-Adjusted Liveliness is an improved variant of Liveliness that discards transactions between addresses of the same entity ("in-house" transactions), so the ratio accounts for real economic activity only and provides an improved market signal compared to its raw UTXO-based counterpart.\n\nNotes. For more information on entity-adjustment and account-based metrics, read our articles here and here.\n\n\nThis is the Point-in-Time (PiT) variant of Entity-Adjusted Liveliness. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 10m, 1h, 24h
format - csv, json
jsonPossible values: timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/indicators/liveliness_account_based_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. Long-Term Holder variant of Entity-Adjusted ASOL, restricting the spent-output sample to outputs attributed to long-term holders. Average Spent Output Lifespan (ASOL) is the average age, in days, of spent transaction outputs.\n\nTechnical. Transactions between addresses of the same entity ("in-house" transactions) are discarded. Long- and Short-Term Holder supply is defined with respect to the entity's averaged purchasing date, with weights given by a logistic function centered at an age of 155 days and a transition width of 10 days. Entities are clusters of addresses estimated to be controlled by the same actor, identified through advanced heuristics and Glassnode's proprietary clustering algorithms. Entity-based metrics rely on statistical and data-science methods that are refined over time. The series is therefore mutable: its established history is stable, but recent data points may revise as clustering improves. For methodology, see our article on account-based metrics.\n\nNotes. For more information, see Quantifying Bitcoin HODLer Supply and our articles on entity-adjustment and account-based metrics here and here.\n\n\nThis is the Point-in-Time (PiT) variant of Entity-Adjusted Long-Term Holder ASOL. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 10m, 1h, 24h
format - csv, json
jsonPossible values: timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/indicators/asol_lth_account_based_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. Entity-Adjusted Long-Term Holder CDD is the Long-Term Holder variant of Entity-Adjusted CDD.\n\nTechnical. Coin Days Destroyed for any given transaction is calculated by taking the number of coins in a transaction and multiplying it by the number of days it has been since those coins were last spent. Transactions between addresses of the same entity are discarded. Long- and Short-Term Holder supply is defined with respect to the entity-averaged purchasing date, with weights given by a logistic function centered at an age of 155 days and a transition width of 10 days. Entities are clusters of addresses estimated to be controlled by the same actor, identified through advanced heuristics and Glassnode's proprietary clustering algorithms. Entity-based metrics rely on statistical and data-science methods that are refined over time. The series is therefore mutable: its established history is stable, but recent data points may revise as clustering improves. For methodology, see our article on account-based metrics.\n\nNotes. For more information on entity-adjustment and account-based metrics, read our articles here and here.\n\n\nThis is the Point-in-Time (PiT) variant of Entity-Adjusted Long-Term Holder CDD. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 10m, 1h, 24h
format - csv, json
jsonPossible values: timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/indicators/cdd_lth_account_based_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. Entity-Adjusted Long-Term Holder Dormancy is the Long-Term Holder variant of Entity-Adjusted Dormancy.\n\nTechnical. Dormancy is the average number of days destroyed per coin transacted, defined as the ratio of coin days destroyed to total transfer volume. Transactions between addresses of the same entity are discarded. Long- and Short-Term Holder supply is defined with respect to the entity-averaged purchasing date, with weights given by a logistic function centered at an age of 155 days and a transition width of 10 days. Entities are clusters of addresses estimated to be controlled by the same actor, identified through advanced heuristics and Glassnode's proprietary clustering algorithms. Entity-based metrics rely on statistical and data-science methods that are refined over time. The series is therefore mutable: its established history is stable, but recent data points may revise as clustering improves. For methodology, see our article on account-based metrics.\n\nNotes. For more information on entity-adjustment and account-based metrics, read our articles here and here.\n\n\nThis is the Point-in-Time (PiT) variant of Entity-Adjusted Long-Term Holder Dormancy. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 10m, 1h, 24h
format - csv, json
jsonPossible values: timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/indicators/dormancy_lth_account_based_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. Entity-Adjusted Long-Term Holder Realized Loss is the entity-adjusted variant of Realized Loss for Long-Term Holders, denoting the total profit (in USD) of all moved coins whose price at their last movement was lower than the price at the current movement.\n\nTechnical. Long- and Short-Term Holder supply is defined with respect to the entity's averaged purchasing date with weights given by a logistic function centered at an age of 155 days and a transition width of 10 days. Volume transferred between addresses owned by the same entity cluster is excluded, so no value is realized during internal or "in-house" transfers. Entities are clusters of addresses estimated to be controlled by the same actor, identified through advanced heuristics and Glassnode's proprietary clustering algorithms. Entity-based metrics rely on statistical and data-science methods that are refined over time. The series is therefore mutable: its established history is stable, but recent data points may revise as clustering improves. For methodology, see our article on account-based metrics.\n\nNotes. For more information on entity-adjustment and account-based metrics, read our articles here and here.\n\n\nThis is the Point-in-Time (PiT) variant of Entity-Adjusted LTH Realized Loss. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 10m, 1h, 24h
format - csv, json
jsonPossible values: timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/indicators/realized_loss_lth_account_based_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. Entity-Adjusted Long-Term Holder Realized Loss to Exchanges is the entity-adjusted variant of Realized Loss for coins sent from Long-Term Holders to exchanges, where realized loss denotes the total loss (in USD) of all moved coins whose price at their last movement was higher than the price at the current movement.\n\nTechnical. Long- and Short-Term Holder supply is defined with respect to the entity's averaged purchasing date with weights given by a logistic function centered at an age of 155 days and a transition width of 10 days. Entities are clusters of addresses estimated to be controlled by the same actor, identified through advanced heuristics and Glassnode's proprietary clustering algorithms. Entity-based metrics rely on statistical and data-science methods that are refined over time. The series is therefore mutable: its established history is stable, but recent data points may revise as clustering improves. For methodology, see our article on account-based metrics. Exchange metrics are based on Glassnode's continually updated set of labeled exchange addresses, together with statistical and data-science methods that are refined over time. The series is therefore mutable: its established history is stable, but recent data points may revise as labels update. For methodology and limitations, see our article on exchange metrics and Exchange Data Transparency Notice.\n\nNotes. For more information on entity-adjustment and account-based metrics, read our articles here and here.\n\n\nThis is the Point-in-Time (PiT) variant of Entity-Adjusted LTH Realized Loss to Exchanges. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 10m, 1h, 24h
format - csv, json
jsonPossible values: exchange name - aggregated, binance, bitcoin.de, bitfinex, bitflyer, bitget, bithumb, bitmex, bitstamp, bittrex, bybit, coinbase, coincheck, coinex, coinspot, crypto.com, deribit, firi, ftx, gate.io, gemini, hashkey, hitbtc, huobi, indodax, korbit, kraken, kucoin, luno, mexc, okex, phemex, poloniex, robinhood, swissborg, upbit, uphold
timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/indicators/realized_loss_lth_to_exchanges_account_based_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. Entity-Adjusted Long-Term Holder Realized Profit is the entity-adjusted variant of Realized Profit for Long-Term Holders, denoting the total profit (in USD) of all moved coins whose price at their last movement was lower than the price at the current movement.\n\nTechnical. Long- and Short-Term Holder supply is defined with respect to the entity's averaged purchasing date with weights given by a logistic function centered at an age of 155 days and a transition width of 10 days. Volume transferred between addresses owned by the same entity cluster is excluded, so no value is realized during internal or "in-house" transfers. Entities are clusters of addresses estimated to be controlled by the same actor, identified through advanced heuristics and Glassnode's proprietary clustering algorithms. Entity-based metrics rely on statistical and data-science methods that are refined over time. The series is therefore mutable: its established history is stable, but recent data points may revise as clustering improves. For methodology, see our article on account-based metrics.\n\nNotes. For more information on entity-adjustment and account-based metrics, read our articles here and here.\n\n\nThis is the Point-in-Time (PiT) variant of Entity-Adjusted LTH Realized Profit. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 10m, 1h, 24h
format - csv, json
jsonPossible values: timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/indicators/realized_profit_lth_account_based_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. Entity-Adjusted Long-Term Holder Realized Profit to Exchanges is the entity-adjusted variant of Realized Profit restricted to coins sent from Long-Term Holders to exchange-labeled entities. Realized profit is the total profit (in USD) of all moved coins whose price at their last movement was lower than the price at the current movement. Long-Term and Short-Term Holder supply is defined with respect to the entity's averaged purchasing date with weights given by a logistic function centered at an age of 155 days and a transition width of 10 days.\n\nTechnical. Entities are clusters of addresses estimated to be controlled by the same actor, identified through advanced heuristics and Glassnode's proprietary clustering algorithms. Entity-based metrics rely on statistical and data-science methods that are refined over time. The series is therefore mutable: its established history is stable, but recent data points may revise as clustering improves. For methodology, see our article on account-based metrics. Exchange metrics are based on Glassnode's continually updated set of labeled exchange addresses, together with statistical and data-science methods that are refined over time. The series is therefore mutable: its established history is stable, but recent data points may revise as labels update. For methodology and limitations, see our article on exchange metrics and Exchange Data Transparency Notice.\n\nNotes. For more information on entity-adjustment and account-based metrics, read our articles here and here.\n\n\nThis is the Point-in-Time (PiT) variant of Entity-Adjusted LTH Realized Profit to Exchanges. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 10m, 1h, 24h
format - csv, json
jsonPossible values: exchange name - aggregated, binance, bitcoin.de, bitfinex, bitflyer, bitget, bithumb, bitmex, bitstamp, bittrex, bybit, coinbase, coincheck, coinex, coinspot, crypto.com, deribit, firi, ftx, gate.io, gemini, hashkey, hitbtc, huobi, indodax, korbit, kraken, kucoin, luno, mexc, okex, phemex, poloniex, robinhood, swissborg, upbit, uphold
timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/indicators/realized_profit_lth_to_exchanges_account_based_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. The total estimated amount of coins moved by long-term holders. Long-Term and Short-Term Holder supply is defined with respect to the entity's averaged purchasing date with weights given by a logistic function centered at an age of 155 days and a transition width of 10 days.\n\nTechnical. Volume transferred within addresses of the same entity is excluded. Entities are clusters of addresses estimated to be controlled by the same actor, identified through advanced heuristics and Glassnode's proprietary clustering algorithms. Entity-based metrics rely on statistical and data-science methods that are refined over time. The series is therefore mutable: its established history is stable, but recent data points may revise as clustering improves. For methodology, see our article on account-based metrics.\n\nNotes. For more information on entity-adjustment and account-based metrics, read our articles here and here.\n\n\nThis is the Point-in-Time (PiT) variant of Entity-Adjusted LTH Transfer Volume. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 10m, 1h, 24h
format - csv, json
jsonPossible values: currency - native, usd
timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/transactions/transfers_volume_entity_adjusted_from_lth_sum_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. The total estimated amount of coins moved by long-term holders in loss. Coins are considered to be in loss when the price at the time the coins are spent is lower than the entity's average on-chain acquisition price for its funds. Long-Term and Short-Term Holder supply is defined with respect to the entity's averaged purchasing date with weights given by a logistic function centered at an age of 155 days and a transition width of 10 days.\n\nTechnical. Volume transferred within addresses of the same entity is excluded. Entities are clusters of addresses estimated to be controlled by the same actor, identified through advanced heuristics and Glassnode's proprietary clustering algorithms. Entity-based metrics rely on statistical and data-science methods that are refined over time. The series is therefore mutable: its established history is stable, but recent data points may revise as clustering improves. For methodology, see our article on account-based metrics.\n\nNotes. For more information on entity-adjustment and account-based metrics, read our articles here and here.\n\n\nThis is the Point-in-Time (PiT) variant of Entity-Adjusted LTH Transfer Volume in Loss. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 10m, 1h, 24h
format - csv, json
jsonPossible values: currency - native, usd
timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/transactions/transfers_volume_entity_adjusted_from_lth_loss_sum_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. The total estimated amount of coins moved by long-term holders in profit. Volume transferred within addresses of the same entity is excluded. Coins are considered in profit when the price at the time the coins are spent is higher than the entity's average on-chain acquisition price for its funds.\n\nTechnical. Long- and Short-Term Holder supply is defined with respect to the entity's averaged purchasing date, with weights given by a logistic function centered at an age of 155 days and a transition width of 10 days. Entities are clusters of addresses estimated to be controlled by the same actor, identified through advanced heuristics and Glassnode's proprietary clustering algorithms. Entity-based metrics rely on statistical and data-science methods that are refined over time. The series is therefore mutable: its established history is stable, but recent data points may revise as clustering improves. For methodology, see our article on account-based metrics.\n\nNotes. For more information on entity-adjustment and account-based metrics, read our articles here and here.\n\n\nThis is the Point-in-Time (PiT) variant of Entity-Adjusted LTH Transfer Volume in Profit. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 10m, 1h, 24h
format - csv, json
jsonPossible values: currency - native, usd
timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/transactions/transfers_volume_entity_adjusted_from_lth_profit_sum_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. Entity-Adjusted LTH-NUPL is an improved variant of Long-Term Holders Net Unrealized Profit/Loss (LTH-NUPL) that discards transactions between addresses of the same entity ("in-house" transactions), so the ratio accounts for real economic activity only and provides an improved market signal compared to its raw UTXO-based counterpart.\n\nTechnical. An entity is considered a Long-Term Holder if the time since its averaged purchasing date is more than 155 days.\n\nNotes. For more information on entity-adjustment and account-based metrics, read our articles here and here.\n\n\nThis is the Point-in-Time (PiT) variant of Entity-Adjusted LTH-NUPL. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 24h
format - csv, json
jsonPossible values: timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/indicators/nupl_more_155_account_based_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. The relative amount of coins moved by long- and short-term holders in profit or loss. Coins are considered to be in profit or loss when the price at the time the coins are spent is higher or lower than the entity's average on-chain acquisition price for its funds. Long-Term and Short-Term Holder supply is defined with respect to the entity's averaged purchasing date with weights given by a logistic function centered at an age of 155 days and a transition width of 10 days.\n\nTechnical. Volume transferred within addresses of the same entity is excluded. Entities are clusters of addresses estimated to be controlled by the same actor, identified through advanced heuristics and Glassnode's proprietary clustering algorithms. Entity-based metrics rely on statistical and data-science methods that are refined over time. The series is therefore mutable: its established history is stable, but recent data points may revise as clustering improves. For methodology, see our article on account-based metrics.\n\nNotes. For more information on entity-adjustment and account-based metrics, read our articles here and here.\n\n\nThis is the Point-in-Time (PiT) variant of Entity-Adjusted LTH/STH Transfer Volume in Profit/Loss. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 10m, 1h, 24h
format - csv, json
jsonPossible values: timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/transactions/transfers_volume_entity_adjusted_from_lth_sth_profit_loss_relative_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. Entity-Adjusted MSOL is an improved variant of MSOL that discards transactions between addresses of the same entity ("in-house" transactions), so the median accounts for real economic activity only and provides an improved market signal compared to its raw UTXO-based counterpart.\n\nNotes. For more information on entity-adjustment and account-based metrics, read our articles here and here.\n\n\nThis is the Point-in-Time (PiT) variant of Entity-Adjusted MSOL. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 10m, 1h, 24h
format - csv, json
jsonPossible values: timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/indicators/msol_account_based_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. Entity-Adjusted MVRV is an improved variant of MVRV Ratio that discards transactions between addresses of the same entity ("in-house" transactions), so the ratio accounts for real economic activity only and provides an improved market signal compared to its raw UTXO-based counterpart.\n\nNotes. For more information on entity-adjustment and account-based metrics, read our articles here and here.\n\n\nThis is the Point-in-Time (PiT) variant of Entity-Adjusted MVRV. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 10m, 1h, 24h
format - csv, json
jsonPossible values: timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/indicators/mvrv_account_based_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. Entity-Adjusted NUPL is an improved variant of Net Unrealized Profit/Loss (NUPL) that discards transactions between addresses of the same entity ("in-house" transactions), so the ratio accounts for real economic activity only and provides an improved market signal compared to its raw UTXO-based counterpart.\n\nNotes. For more information on entity-adjustment and account-based metrics, read our articles here and here.\n\n\nThis is the Point-in-Time (PiT) variant of Entity-Adjusted NUPL. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 24h
format - csv, json
jsonPossible values: timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/indicators/net_unrealized_profit_loss_account_based_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. Entity-Adjusted NVT is market cap divided by entity-adjusted on-chain volume, an entity-adjusted variant of the NVT Ratio that accounts for actual economic throughput and is therefore more accurate than the unfiltered ratio.\n\n\nThis is the Point-in-Time (PiT) variant of Entity-Adjusted NVT. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 10m, 1h, 24h
format - csv, json
jsonPossible values: timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/indicators/nvt_entity_adjusted_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. Entity-Adjusted Realized Cap is a variant of Realized Cap that discards transactions between addresses of the same entity ("in-house" transactions), accounting for real economic activity only and providing an improved market signal compared to its raw UTXO-based counterpart.\n\nNotes. For more information on entity-adjustment and account-based metrics, read our articles here and here.\n\n\nThis is the Point-in-Time (PiT) variant of Entity-Adjusted Realized Cap. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 10m, 1h, 24h
format - csv, json
jsonPossible values: timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/indicators/rcap_account_based_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. Entity-Adjusted Realized Loss is the entity-adjusted variant of Realized Loss, which denotes the total profit (in USD) of all moved coins whose price at their last movement was lower than the price at the current movement.\n\nTechnical. Volume transferred between addresses owned by the same entity cluster is excluded, so no value is realized during internal or "in-house" transfers. Entities are clusters of addresses estimated to be controlled by the same actor, identified through advanced heuristics and Glassnode's proprietary clustering algorithms. Entity-based metrics rely on statistical and data-science methods that are refined over time. The series is therefore mutable: its established history is stable, but recent data points may revise as clustering improves. For methodology, see our article on account-based metrics.\n\nNotes. For more information on entity-adjustment and account-based metrics, read our articles here and here.\n\n\nThis is the Point-in-Time (PiT) variant of Entity-Adjusted Realized Loss. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 10m, 1h, 24h
format - csv, json
jsonPossible values: timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/indicators/realized_loss_account_based_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. Entity-Adjusted Realized Loss to Exchanges is the entity-adjusted variant of Realized Loss for coins sent to exchanges, where realized loss denotes the total loss (in USD) of all moved coins whose price at their last movement was higher than the price at the current movement.\n\nTechnical. Entities are clusters of addresses estimated to be controlled by the same actor, identified through advanced heuristics and Glassnode's proprietary clustering algorithms. Entity-based metrics rely on statistical and data-science methods that are refined over time. The series is therefore mutable: its established history is stable, but recent data points may revise as clustering improves. For methodology, see our article on account-based metrics. Exchange metrics are based on Glassnode's continually updated set of labeled exchange addresses, together with statistical and data-science methods that are refined over time. The series is therefore mutable: its established history is stable, but recent data points may revise as labels update. For methodology and limitations, see our article on exchange metrics and Exchange Data Transparency Notice.\n\nNotes. For more information on entity-adjustment and account-based metrics, read our articles here and here.\n\n\nThis is the Point-in-Time (PiT) variant of Entity-Adjusted Realized Loss to Exchanges. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 10m, 1h, 24h
format - csv, json
jsonPossible values: exchange name - aggregated, binance, bitcoin.de, bitfinex, bitflyer, bitget, bithumb, bitmex, bitstamp, bittrex, bybit, coinbase, coincheck, coinex, coinspot, crypto.com, deribit, firi, ftx, gate.io, gemini, hashkey, hitbtc, huobi, indodax, korbit, kraken, kucoin, luno, mexc, okex, phemex, poloniex, robinhood, swissborg, upbit, uphold
timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/indicators/realized_loss_to_exchanges_account_based_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. Entity-Adjusted variant of Realized Profit, the total USD profit of all moved coins whose price at their last movement was lower than the price at the current movement.\n\nTechnical. Volume transferred between addresses owned by the same entity cluster is excluded, so no value is realized during internal or "in-house" transfers. Entities are clusters of addresses estimated to be controlled by the same actor, identified through advanced heuristics and Glassnode's proprietary clustering algorithms. Entity-based metrics rely on statistical and data-science methods that are refined over time. The series is therefore mutable: its established history is stable, but recent data points may revise as clustering improves. For methodology, see our article on account-based metrics.\n\nNotes. For more information on entity-adjustment and account-based metrics, read our articles here and here.\n\n\nThis is the Point-in-Time (PiT) variant of Entity-Adjusted Realized Profit. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 10m, 1h, 24h
format - csv, json
jsonPossible values: timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/indicators/realized_profit_account_based_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. Entity-Adjusted Realized Profit to Exchanges is the entity-adjusted variant of Realized Profit restricted to coins sent to exchange-labeled entities. Realized profit is the total profit (in USD) of all moved coins whose price at their last movement was lower than the price at the current movement.\n\nTechnical. Entities are clusters of addresses estimated to be controlled by the same actor, identified through advanced heuristics and Glassnode's proprietary clustering algorithms. Entity-based metrics rely on statistical and data-science methods that are refined over time. The series is therefore mutable: its established history is stable, but recent data points may revise as clustering improves. For methodology, see our article on account-based metrics. Exchange metrics are based on Glassnode's continually updated set of labeled exchange addresses, together with statistical and data-science methods that are refined over time. The series is therefore mutable: its established history is stable, but recent data points may revise as labels update. For methodology and limitations, see our article on exchange metrics and Exchange Data Transparency Notice.\n\nNotes. For more information on entity-adjustment and account-based metrics, read our articles here and here.\n\n\nThis is the Point-in-Time (PiT) variant of Entity-Adjusted Realized Profit to Exchanges. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 10m, 1h, 24h
format - csv, json
jsonPossible values: exchange name - aggregated, binance, bitcoin.de, bitfinex, bitflyer, bitget, bithumb, bitmex, bitstamp, bittrex, bybit, coinbase, coincheck, coinex, coinspot, crypto.com, deribit, firi, ftx, gate.io, gemini, hashkey, hitbtc, huobi, indodax, korbit, kraken, kucoin, luno, mexc, okex, phemex, poloniex, robinhood, swissborg, upbit, uphold
timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/indicators/realized_profit_to_exchanges_account_based_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. Short-Term Holder variant of Entity-Adjusted ASOL, restricting the spent-output sample to outputs attributed to short-term holders. Average Spent Output Lifespan (ASOL) is the average age, in days, of spent transaction outputs.\n\nTechnical. Transactions between addresses of the same entity ("in-house" transactions) are discarded. Long- and Short-Term Holder supply is defined with respect to the entity's averaged purchasing date, with weights given by a logistic function centered at an age of 155 days and a transition width of 10 days. Entities are clusters of addresses estimated to be controlled by the same actor, identified through advanced heuristics and Glassnode's proprietary clustering algorithms. Entity-based metrics rely on statistical and data-science methods that are refined over time. The series is therefore mutable: its established history is stable, but recent data points may revise as clustering improves. For methodology, see our article on account-based metrics.\n\nNotes. For more information, see Quantifying Bitcoin HODLer Supply and our articles on entity-adjustment and account-based metrics here and here.\n\n\nThis is the Point-in-Time (PiT) variant of Entity-Adjusted Short-Term Holder ASOL. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 10m, 1h, 24h
format - csv, json
jsonPossible values: timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/indicators/asol_sth_account_based_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. Entity-Adjusted Short-Term Holder CDD is the Short-Term Holder variant of Entity-Adjusted CDD.\n\nTechnical. Coin Days Destroyed for any given transaction is calculated by taking the number of coins in a transaction and multiplying it by the number of days it has been since those coins were last spent. Transactions between addresses of the same entity are discarded. Long- and Short-Term Holder supply is defined with respect to the entity-averaged purchasing date, with weights given by a logistic function centered at an age of 155 days and a transition width of 10 days. Entities are clusters of addresses estimated to be controlled by the same actor, identified through advanced heuristics and Glassnode's proprietary clustering algorithms. Entity-based metrics rely on statistical and data-science methods that are refined over time. The series is therefore mutable: its established history is stable, but recent data points may revise as clustering improves. For methodology, see our article on account-based metrics.\n\nNotes. For more information on entity-adjustment and account-based metrics, read our articles here and here.\n\n\nThis is the Point-in-Time (PiT) variant of Entity-Adjusted Short-Term Holder CDD. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 10m, 1h, 24h
format - csv, json
jsonPossible values: timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/indicators/cdd_sth_account_based_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. Entity-Adjusted Short-Term Holder Dormancy is the Short-Term Holder variant of Entity-Adjusted Dormancy.\n\nTechnical. Dormancy is the average number of days destroyed per coin transacted, defined as the ratio of coin days destroyed to total transfer volume. Transactions between addresses of the same entity are discarded. Long- and Short-Term Holder supply is defined with respect to the entity-averaged purchasing date, with weights given by a logistic function centered at an age of 155 days and a transition width of 10 days. Entities are clusters of addresses estimated to be controlled by the same actor, identified through advanced heuristics and Glassnode's proprietary clustering algorithms. Entity-based metrics rely on statistical and data-science methods that are refined over time. The series is therefore mutable: its established history is stable, but recent data points may revise as clustering improves. For methodology, see our article on account-based metrics.\n\nNotes. For more information on entity-adjustment and account-based metrics, read our articles here and here.\n\n\nThis is the Point-in-Time (PiT) variant of Entity-Adjusted Short-Term Holder Dormancy. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 10m, 1h, 24h
format - csv, json
jsonPossible values: timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response
Unix timestamp
1726790400Metric value (can be number, object, or array depending on the metric)
822077Bad Request - Invalid parameters or unsupported asset
Unauthorized - Invalid or missing API key
Too Many Requests - Rate limit exceeded
GET /v1/metrics/indicators/dormancy_sth_account_based_pit?a=text HTTP/1.1
Host: api.glassnode.com
Accept: */*
[
{
"t": 1726790400,
"v": 822077
}
]Definition. Entity-Adjusted SOPR is a variant of SOPR that discards transactions between addresses of the same entity ("in-house" transactions), so the aggregate accounts for real economic activity and provides an improved market signal compared to the raw UTXO-based counterpart.\n\nInterpretation. Readings above 1 mean the average coin moved that day was sold at a profit, readings below 1 mean it was sold at a loss.\n\nNotes. For more information on entity-adjustment and account-based metrics, read our articles here and here.\n\n\nThis is the Point-in-Time (PiT) variant of Entity-Adjusted SOPR. PiT metrics are strictly append-only and their history is immutable. The historic data does not necessarily reflect the best current knowledge, but the information at the time when a data point was first computed. PiT metrics are ideal candidates for applications in model backtesting and related quantitative purposes. Read our article on PiT metrics for more information.
Your Glassnode API key
asset id - (see metadata (metadata/metric) page for more details)
since, unix timestamp
until, unix timestamp
frequency interval - 10m, 1h, 24h
format - csv, json
jsonPossible values: timestamp format - unix or humanized (RFC 3339)
unixPossible values: Successful response