# Point-In-Time ## Accumulation Addresses > 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. 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\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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/addresses/accumulation_count_pit":{"get":{"summary":"Accumulation Addresses","description":"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. 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\\nThis is the Point-in-Time (PiT) variant of [Accumulation Addresses](https://studio.glassnode.com/metrics?a=BTC&m=addresses.AccumulationCount). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/addresses.AccumulationCountPit?a=BTC)\n","operationId":"addresses.AccumulationCountPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Accumulation Balance > The total amount of funds held in \[accumulation addresses]\(). Accumulation addresses are defined as addresses that have at least 2 incoming non-dust transfers and have never spent funds. 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\nThis is the Point-in-Time (PiT) variant of \[Accumulation 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/addresses/accumulation_balance_pit":{"get":{"summary":"Accumulation Balance","description":"The total amount of funds held in [accumulation addresses](https://studio.glassnode.com/metrics?a=BTC&m=addresses.AccumulationCount). Accumulation addresses are defined as addresses that have at least 2 incoming non-dust transfers and have never spent funds. 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\\nThis is the Point-in-Time (PiT) variant of [Accumulation Balance](https://studio.glassnode.com/metrics?a=BTC&m=addresses.AccumulationBalance). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/addresses.AccumulationBalancePit?a=BTC)\n","operationId":"addresses.AccumulationBalancePit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"c","in":"query","required":false,"description":"currency - NATIVE, USD","schema":{"type":"string"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Accumulation Trend Score > The Accumulation Trend Score is an indicator that reflects the relative size of entities that are actively accumulating coins on-chain in terms of their BTC holdings. The scale of the Accumulation Trend Score represents both the size of the entities balance (their participation score), and the amount of new coins they have acquired/sold over the last month (their balance change score). An Accumulation Trend Score of closer to 1 indicates that on aggregate, larger entities (or a big part of the network) are accumulating, and a value closer to 0 indicates they are distributing or not accumulating. This provides insight into the balance size of market participants, and their accumulation behavior over the last month. For more information see the metric description in \[Glassnode Academy]\( 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/indicators/accumulation_trend_score_pit":{"get":{"summary":"Accumulation Trend Score","description":"The Accumulation Trend Score is an indicator that reflects the relative size of entities that are actively accumulating coins on-chain in terms of their BTC holdings. The scale of the Accumulation Trend Score represents both the size of the entities balance (their participation score), and the amount of new coins they have acquired/sold over the last month (their balance change score). An Accumulation Trend Score of closer to 1 indicates that on aggregate, larger entities (or a big part of the network) are accumulating, and a value closer to 0 indicates they are distributing or not accumulating. This provides insight into the balance size of market participants, and their accumulation behavior over the last month. For more information see the metric description in [Glassnode Academy](https://academy.glassnode.com/indicators/accumulation-trend-score).\\n\\nThis is the Point-in-Time (PiT) variant of [Accumulation Trend Score](https://studio.glassnode.com/metrics?a=BTC&m=indicators.AccumulationTrendScore). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/indicators.AccumulationTrendScorePit?a=BTC)\n","operationId":"indicators.AccumulationTrendScorePit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Active Entities > 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. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see \[this article]\( 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/entities/active_count_pit":{"get":{"summary":"Active Entities","description":"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. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see [this article](https://insights.glassnode.com/bitcoin_holders/).\\n\\nThis is the Point-in-Time (PiT) variant of [Active Entities](https://studio.glassnode.com/metrics?a=BTC&m=entities.ActiveCount). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/entities.ActiveCountPit?a=BTC)\n","operationId":"entities.ActiveCountPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Asia Year-over-Year Supply Change > \nThis metric aims at giving an estimate for the year-over-year change in the share of the Bitcoin supply to be held/traded in Asia.\n\nGeolocation of Bitcoin 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 probabilities for each entity being located in the US, Europe, or Asia. Working hours are defined as:\n\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)\n\nAn entity\'s balance will only contribute to the supply in the respective region if the location can be determined with a high certainty. Supply held on exchanges wallets are excluded.\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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/supply/apac_1y_supply_change_pit":{"get":{"summary":"Asia Year-over-Year Supply Change","description":"\\nThis metric aims at giving an estimate for the year-over-year change in the share of the Bitcoin supply to be held/traded in Asia.\\n\\nGeolocation of Bitcoin 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 probabilities for each entity being located in the US, Europe, or Asia. Working hours are defined as:\\n\\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)\\n\\nAn entity's balance will only contribute to the supply in the respective region if the location can be determined with a high certainty. Supply held on exchanges wallets are excluded.\\n \\n\\nThis is the Point-in-Time (PiT) variant of [Asia Year-over-Year Supply Change](https://studio.glassnode.com/metrics?a=BTC&m=supply.Apac1YSupplyChange). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/supply.Apac1YSupplyChangePit?a=BTC)\n","operationId":"supply.Apac1YSupplyChangePit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Bridges Deposits By Chain > This metric measures the USD value which is deposited into bridge smart contracts on Ethereum, and is therefore flowing out of the Ethereum blockchain, and into target blockchains. Deposit Volume is computed daily by multiplying the number of tokens deposited into bridges by the latest daily price of each token.\n\nBridges are protocols that enable digital assets to be transferred from one blockchain to another. When an asset is transferred out of Ethereum, it gets deposited and locked into a bridge smart contract. When the asset is transferred back to Ethereum, it is withdrawn and released from the smart contract.\n\nThis metric only includes bridge contracts on the Ethereum side. The bridges included in this metric cover bridge deposits into both L1 and L2 blockchains, providing information on the value transferred to both L1 competitors, and L2 scaling solutions. Each bridge included in this metric 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\nThis 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/bridges/deposits_by_chain_pit":{"get":{"summary":"Bridges Deposits By Chain","description":"This metric measures the USD value which is deposited into bridge smart contracts on Ethereum, and is therefore flowing out of the Ethereum blockchain, and into target blockchains. Deposit Volume is computed daily by multiplying the number of tokens deposited into bridges by the latest daily price of each token.\\n\\nBridges are protocols that enable digital assets to be transferred from one blockchain to another. When an asset is transferred out of Ethereum, it gets deposited and locked into a bridge smart contract. When the asset is transferred back to Ethereum, it is withdrawn and released from the smart contract.\\n\\nThis metric only includes bridge contracts on the Ethereum side. The bridges included in this metric cover bridge deposits into both L1 and L2 blockchains, providing information on the value transferred to both L1 competitors, and L2 scaling solutions. Each bridge included in this metric 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\\nThis is the Point-in-Time (PiT) variant of [Bridges Deposits By Chain](https://studio.glassnode.com/metrics?a=BTC&m=bridges.DepositsByChain). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/bridges.DepositsByChainPit?a=ETH)\n","operationId":"bridges.DepositsByChainPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - ETH","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Bridges Net Flow By Chain > This metric shows the net USD value flowing into, or out of Ethereum bridge smart contracts, calculated as bridge deposits minus bridge withdrawals. It can also be considered to represent the net USD value flowing in, or out of the Ethereum blockchain via bridges. A positive value means that there is more value being deposited into bridges, which translates into a net value outflow from Ethereum. On the other hand, a negative value means that there is more USD value being withdrawn from bridges, which translates into more USD value flowing back into Ethereum.\n\nBridges are protocols that enable digital assets to be transferred from one blockchain to another. When an asset is transferred out of Ethereum, it gets deposited and locked into a bridge smart contract. When the asset is transferred back to Ethereum, it is withdrawn and released from the smart contract.\n\nThis metric only includes bridge contracts on the Ethereum side. The bridges included in this metric cover bridge deposits into both L1 and L2 blockchains, providing information on the value transferred to both L1 competitors, and L2 scaling solutions. Each bridge included in this metric 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\nThis 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/bridges/net_volume_by_chain_pit":{"get":{"summary":"Bridges Net Flow By Chain","description":"This metric shows the net USD value flowing into, or out of Ethereum bridge smart contracts, calculated as bridge deposits minus bridge withdrawals. It can also be considered to represent the net USD value flowing in, or out of the Ethereum blockchain via bridges. A positive value means that there is more value being deposited into bridges, which translates into a net value outflow from Ethereum. On the other hand, a negative value means that there is more USD value being withdrawn from bridges, which translates into more USD value flowing back into Ethereum.\\n\\nBridges are protocols that enable digital assets to be transferred from one blockchain to another. When an asset is transferred out of Ethereum, it gets deposited and locked into a bridge smart contract. When the asset is transferred back to Ethereum, it is withdrawn and released from the smart contract.\\n\\nThis metric only includes bridge contracts on the Ethereum side. The bridges included in this metric cover bridge deposits into both L1 and L2 blockchains, providing information on the value transferred to both L1 competitors, and L2 scaling solutions. Each bridge included in this metric 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\\nThis is the Point-in-Time (PiT) variant of [Bridges Net Flow By Chain](https://studio.glassnode.com/metrics?a=BTC&m=bridges.NetVolumeByChain). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/bridges.NetVolumeByChainPit?a=ETH)\n","operationId":"bridges.NetVolumeByChainPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - ETH","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Bridges Transactions (Absolute) > The number of transactions (transaction count) in the Ethereum network by contracts that allow transfer of tokens between different blockchains.\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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/transactions/transfers_count_bridges_pit":{"get":{"summary":"Bridges Transactions (Absolute)","description":"The number of transactions (transaction count) in the Ethereum network by contracts that allow transfer of tokens between different blockchains.\\n\\nThis is the Point-in-Time (PiT) variant of [Bridges Transactions (Absolute)](https://studio.glassnode.com/metrics?a=BTC&m=transactions.TransfersCountBridges). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/transactions.TransfersCountBridgesPit?a=ETH)\n","operationId":"transactions.TransfersCountBridgesPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - ETH","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Bridges Transactions (Relative) > The relative amount (share) of transactions in the Ethereum network by contracts that allow transfer of tokens between different blockchains.\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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/transactions/transfers_count_bridges_relative_pit":{"get":{"summary":"Bridges Transactions (Relative)","description":"The relative amount (share) of transactions in the Ethereum network by contracts that allow transfer of tokens between different blockchains.\\n\\nThis is the Point-in-Time (PiT) variant of [Bridges Transactions (Relative)](https://studio.glassnode.com/metrics?a=BTC&m=transactions.TransfersCountBridgesRelative). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/transactions.TransfersCountBridgesRelativePit?a=ETH)\n","operationId":"transactions.TransfersCountBridgesRelativePit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - ETH","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Bridges TVL > The Total Value Locked (TVL) in bridges measures the total USD value that is locked within the Ethereum side of bridge smart contracts. Locked tokens are not available on the Ethereum chain, but are available on the target blockchains. An increasing TVL means that value is flowing out of Ethereum and into other target blockchains, whilst a decreasing TVL means the value is flowing back into Ethereum. Bridge TVL is computed daily, by multiplying the number of tokens locked within the bridge smart contracts, by the latest daily price for each token.\n\nBridges are protocols that enable digital assets to be transferred from one blockchain to another. When an asset is transferred out of Ethereum, it gets deposited and locked into a bridge smart contract. When the asset is transferred back to Ethereum, it is withdrawn and released from the smart contract.\n\nThis metric only includes bridge contracts on the Ethereum side. The bridges included in this metric cover bridge deposits into both L1 and L2 blockchains, providing information on the value transferred to both L1 competitors, and L2 scaling solutions. Each bridge included in this metric 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\nThis 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/bridges/total_value_locked_by_chain_pit":{"get":{"summary":"Bridges TVL","description":"The Total Value Locked (TVL) in bridges measures the total USD value that is locked within the Ethereum side of bridge smart contracts. Locked tokens are not available on the Ethereum chain, but are available on the target blockchains. An increasing TVL means that value is flowing out of Ethereum and into other target blockchains, whilst a decreasing TVL means the value is flowing back into Ethereum. Bridge TVL is computed daily, by multiplying the number of tokens locked within the bridge smart contracts, by the latest daily price for each token.\\n\\nBridges are protocols that enable digital assets to be transferred from one blockchain to another. When an asset is transferred out of Ethereum, it gets deposited and locked into a bridge smart contract. When the asset is transferred back to Ethereum, it is withdrawn and released from the smart contract.\\n\\nThis metric only includes bridge contracts on the Ethereum side. The bridges included in this metric cover bridge deposits into both L1 and L2 blockchains, providing information on the value transferred to both L1 competitors, and L2 scaling solutions. Each bridge included in this metric 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\\nThis is the Point-in-Time (PiT) variant of [Bridges TVL](https://studio.glassnode.com/metrics?a=BTC&m=bridges.TotalValueLockedByChain). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/bridges.TotalValueLockedByChainPit?a=ETH)\n","operationId":"bridges.TotalValueLockedByChainPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - ETH","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Bridges TVL Relative > This metric presents the Relative Total Value Locked (TVL dominance) of each target blockchain bridge compared to the total TVL across all bridges. A rising relative TVL indicates that the target blockchain is growing in USD denominated TVL dominance compared to the others (and vice versa). Bridge TVL is computed daily, by multiplying the number of tokens locked within the bridge smart contract, by the latest daily price of each token. Relative TVL is then computed by dividing the TVL of each bridge by the total TVL across all bridges.\n\nBridges are protocols that enable digital assets to be transferred from one blockchain to another. When an asset is transferred out of Ethereum, it gets deposited and locked into a bridge smart contract. When the asset is transferred back to Ethereum, it is withdrawn and released from the smart contract.\n\nThis metric only includes bridge contracts on the Ethereum side. The bridges included in this metric cover bridge deposits into both L1 and L2 blockchains, providing information on the value transferred to both L1 competitors, and L2 scaling solutions. Each bridge included in this metric 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\nThis 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/bridges/total_value_locked_by_chain_relative_pit":{"get":{"summary":"Bridges TVL Relative","description":"This metric presents the Relative Total Value Locked (TVL dominance) of each target blockchain bridge compared to the total TVL across all bridges. A rising relative TVL indicates that the target blockchain is growing in USD denominated TVL dominance compared to the others (and vice versa). Bridge TVL is computed daily, by multiplying the number of tokens locked within the bridge smart contract, by the latest daily price of each token. Relative TVL is then computed by dividing the TVL of each bridge by the total TVL across all bridges.\\n\\nBridges are protocols that enable digital assets to be transferred from one blockchain to another. When an asset is transferred out of Ethereum, it gets deposited and locked into a bridge smart contract. When the asset is transferred back to Ethereum, it is withdrawn and released from the smart contract.\\n\\nThis metric only includes bridge contracts on the Ethereum side. The bridges included in this metric cover bridge deposits into both L1 and L2 blockchains, providing information on the value transferred to both L1 competitors, and L2 scaling solutions. Each bridge included in this metric 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\\nThis is the Point-in-Time (PiT) variant of [Bridges TVL Relative](https://studio.glassnode.com/metrics?a=BTC&m=bridges.TotalValueLockedByChainRelative). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/bridges.TotalValueLockedByChainRelativePit?a=ETH)\n","operationId":"bridges.TotalValueLockedByChainRelativePit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - ETH","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Bridges Withdrawals By Chain > This metric measures the USD value which is withdrawn from bridge smart contracts on Ethereum, and is therefore flowing into the Ethereum blockchain, and out of target blockchains. Withdrawal Volume is computed daily by multiplying the number of tokens withdrawn from bridges by the latest daily price of each token.\n\nBridges are protocols that enable digital assets to be transferred from one blockchain to another. When an asset is transferred out of Ethereum, it gets deposited and locked into a bridge smart contract. When the asset is transferred back to Ethereum, it is withdrawn and released from the smart contract.\n\nThis metric only includes bridge contracts on the Ethereum side. The bridges included in this metric cover bridge deposits into both L1 and L2 blockchains, providing information on the value transferred to both L1 competitors, and L2 scaling solutions. Each bridge included in this metric 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\nThis 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/bridges/withdrawals_by_chain_pit":{"get":{"summary":"Bridges Withdrawals By Chain","description":"This metric measures the USD value which is withdrawn from bridge smart contracts on Ethereum, and is therefore flowing into the Ethereum blockchain, and out of target blockchains. Withdrawal Volume is computed daily by multiplying the number of tokens withdrawn from bridges by the latest daily price of each token.\\n\\nBridges are protocols that enable digital assets to be transferred from one blockchain to another. When an asset is transferred out of Ethereum, it gets deposited and locked into a bridge smart contract. When the asset is transferred back to Ethereum, it is withdrawn and released from the smart contract.\\n\\nThis metric only includes bridge contracts on the Ethereum side. The bridges included in this metric cover bridge deposits into both L1 and L2 blockchains, providing information on the value transferred to both L1 competitors, and L2 scaling solutions. Each bridge included in this metric 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\\nThis is the Point-in-Time (PiT) variant of [Bridges Withdrawals By Chain](https://studio.glassnode.com/metrics?a=BTC&m=bridges.WithdrawalsByChain). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/bridges.WithdrawalsByChainPit?a=ETH)\n","operationId":"bridges.WithdrawalsByChainPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - ETH","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Coinjoin Output Count > The total count of indistinguishable outputs in coinjoin transactions. The metric is an aggregate of different coinjoin providers. Note that coinjoin metrics rely on heuristics and statistical information that change over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/transactions/transfers_from_coinjoins_count_pit":{"get":{"summary":"Coinjoin Output Count","description":"The total count of indistinguishable outputs in coinjoin transactions. The metric is an aggregate of different coinjoin providers. Note that coinjoin metrics rely on heuristics and statistical information that change over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\\n\\nThis is the Point-in-Time (PiT) variant of [Coinjoin Output Count](https://studio.glassnode.com/metrics?a=BTC&m=transactions.TransfersFromCoinjoinsCount). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/transactions.TransfersFromCoinjoinsCountPit?a=BTC)\n","operationId":"transactions.TransfersFromCoinjoinsCountPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Coinjoin Output Volume > The total amount of indistinguishable outputs in coinjoin transactions, i.e. the volume of coins mixed by different coinjoin providers. Note that coinjoin metrics rely on heuristics and statistical information that change over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/transactions/transfers_volume_from_coinjoins_sum_pit":{"get":{"summary":"Coinjoin Output Volume","description":"The total amount of indistinguishable outputs in coinjoin transactions, i.e. the volume of coins mixed by different coinjoin providers. Note that coinjoin metrics rely on heuristics and statistical information that change over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\\n\\nThis is the Point-in-Time (PiT) variant of [Coinjoin Output Volume](https://studio.glassnode.com/metrics?a=BTC&m=transactions.TransfersVolumeFromCoinjoinsSum). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/transactions.TransfersVolumeFromCoinjoinsSumPit?a=BTC)\n","operationId":"transactions.TransfersVolumeFromCoinjoinsSumPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"c","in":"query","required":false,"description":"currency - NATIVE, USD","schema":{"type":"string"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## DeFi Transactions (Absolute) > The number of transactions (transaction count) in the Ethereum network by on-chain financial instruments and protocols implemented as smart contracts, including decentralized exchanges (DEXs).\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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/transactions/transfers_count_defi_pit":{"get":{"summary":"DeFi Transactions (Absolute)","description":"The number of transactions (transaction count) in the Ethereum network by on-chain financial instruments and protocols implemented as smart contracts, including decentralized exchanges (DEXs).\\n\\nThis is the Point-in-Time (PiT) variant of [DeFi Transactions (Absolute)](https://studio.glassnode.com/metrics?a=BTC&m=transactions.TransfersCountDefi). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/transactions.TransfersCountDefiPit?a=ETH)\n","operationId":"transactions.TransfersCountDefiPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - ETH","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## DeFi Transactions (Relative) > The relative amount (share) of transactions in the Ethereum network by on-chain financial instruments and protocols implemented as smart contracts, including decentralized exchanges (DEXs).\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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/transactions/transfers_count_defi_relative_pit":{"get":{"summary":"DeFi Transactions (Relative)","description":"The relative amount (share) of transactions in the Ethereum network by on-chain financial instruments and protocols implemented as smart contracts, including decentralized exchanges (DEXs).\\n\\nThis is the Point-in-Time (PiT) variant of [DeFi Transactions (Relative)](https://studio.glassnode.com/metrics?a=BTC&m=transactions.TransfersCountDefiRelative). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/transactions.TransfersCountDefiRelativePit?a=ETH)\n","operationId":"transactions.TransfersCountDefiRelativePit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - ETH","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Depositing Addresses > The number of unique addresses that appeared as a sender in a transaction sending funds to exchanges.\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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/addresses/sending_to_exchanges_count_pit":{"get":{"summary":"Depositing Addresses","description":"The number of unique addresses that appeared as a sender in a transaction sending funds to exchanges.\\n\\nThis is the Point-in-Time (PiT) variant of [Depositing Addresses](https://studio.glassnode.com/metrics?a=BTC&m=addresses.SendingToExchangesCount). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/addresses.SendingToExchangesCountPit?a=BTC)\n","operationId":"addresses.SendingToExchangesCountPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id (see list below for more details)","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 1month, 1w, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Dormancy Flow > Dormancy Flow is the ratio of the current market capitalization and the annualized dormancy value (measured in USD). The metric can be used to time market lows and assess whether the bull market remains in relatively normal conditions. It helps confirm whether an asset is in a bullish or bearish primary trend. This metric was put forward by \[David Puell]\(). For more information please read his \[introductory article]\( 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/indicators/dormancy_flow_pit":{"get":{"summary":"Dormancy Flow","description":"Dormancy Flow is the ratio of the current market capitalization and the annualized dormancy value (measured in USD). The metric can be used to time market lows and assess whether the bull market remains in relatively normal conditions. It helps confirm whether an asset is in a bullish or bearish primary trend. This metric was put forward by [David Puell](https://twitter.com/kenoshaking). For more information please read his [introductory article](https://medium.com/@kenoshaking/bitcoin-average-dormancy-28f88ea4c2ce).\\n\\nThis is the Point-in-Time (PiT) variant of [Dormancy Flow](https://studio.glassnode.com/metrics?a=BTC&m=indicators.DormancyFlow). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/indicators.DormancyFlowPit?a=BTC)\n","operationId":"indicators.DormancyFlowPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Entities Net Growth > The net growth of unique entities in the network. This metric is 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). 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. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see \[this article]\( computation of this metric requires statistical information from several days, and is therefore only available with a lag of one week.\*\*\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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/entities/net_growth_count_pit":{"get":{"summary":"Entities Net Growth","description":"The net growth of unique entities in the network. This metric is 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). 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. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see [this article](https://insights.glassnode.com/bitcoin_holders/).\\n\\n**The computation of this metric requires statistical information from several days, and is therefore only available with a lag of one week.**\\n\\nThis is the Point-in-Time (PiT) variant of [Entities Net Growth](https://studio.glassnode.com/metrics?a=BTC&m=entities.NetGrowthCount). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/entities.NetGrowthCountPit?a=BTC)\n","operationId":"entities.NetGrowthCountPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Entities Supply Distribution > Relative distribution of the circulating supply held by entities with specific balance bands.\n\nThis 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/entities/supply_distribution_relative_pit":{"get":{"summary":"Entities Supply Distribution","description":"Relative distribution of the circulating supply held by entities with specific balance bands.\\n\\nThis is the Point-in-Time (PiT) variant of [Entities Supply Distribution](https://studio.glassnode.com/metrics?a=BTC&m=entities.SupplyDistributionRelative). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/entities.SupplyDistributionRelativePit?a=BTC)\n","operationId":"entities.SupplyDistributionRelativePit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Entity- and Supply-Adjusted CYD > Coin Years Destroyed (CYD) is defined as the 365 day rolling sum of \[Coin Days Destroyed (CDD)]\(), and shows the amount of coin days that have been destroyed over the past year. It is indicative of long-term holder behaviour. This version is entity-adjusted, meaning that transactions within addresses controlled by the same network participant are discarded (see \[this article]\() for more information), as well as supply-adjusted to account for the increasing baseline of the metric over time. This metric was first put forward by \[ARK Invest]\() and further developed by Glassnode by adjusting for the circulating supply.\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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/indicators/cyd_account_based_supply_adjusted_pit":{"get":{"summary":"Entity- and Supply-Adjusted CYD","description":"Coin Years Destroyed (CYD) is defined as the 365 day rolling sum of [Coin Days Destroyed (CDD)](https://studio.glassnode.com/metrics?a=BTC&m=indicators.Cdd), and shows the amount of coin days that have been destroyed over the past year. It is indicative of long-term holder behaviour. This version is entity-adjusted, meaning that transactions within addresses controlled by the same network participant are discarded (see [this article](https://insights.glassnode.com/account-based-metrics) for more information), as well as supply-adjusted to account for the increasing baseline of the metric over time. This metric was first put forward by [ARK Invest](https://twitter.com/ARKInvest) and further developed by Glassnode by adjusting for the circulating supply.\\n\\nThis is the Point-in-Time (PiT) variant of [Entity- and Supply-Adjusted CYD](https://studio.glassnode.com/metrics?a=BTC&m=indicators.CydAccountBasedSupplyAdjusted). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/indicators.CydAccountBasedSupplyAdjustedPit?a=BTC)\n","operationId":"indicators.CydAccountBasedSupplyAdjustedPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Entity-Adjusted 90D Coin Days Destroyed (eCDD-90) > 90D Coin Days Destroyed is the 90 day rolling sum of \[Coin Days Destroyed (CDD)]\() and shows the amount of coin days that have been destroyed over the past year. This version is entity-adjusted, meaning that transactions within addresses controlled by the same network participant are discarded (see \[this article]\() for more information), as well as age-adjusted meaning that we normalize by time in order to account for the increasing baseline as time goes by.\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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/indicators/cdd90_account_based_age_adjusted_pit":{"get":{"summary":"Entity-Adjusted 90D Coin Days Destroyed (eCDD-90)","description":"90D Coin Days Destroyed is the 90 day rolling sum of [Coin Days Destroyed (CDD)](https://studio.glassnode.com/metrics?a=BTC&m=indicators.Cdd) and shows the amount of coin days that have been destroyed over the past year. This version is entity-adjusted, meaning that transactions within addresses controlled by the same network participant are discarded (see [this article](https://insights.glassnode.com/account-based-metrics) for more information), as well as age-adjusted meaning that we normalize by time in order to account for the increasing baseline as time goes by.\\n\\nThis is the Point-in-Time (PiT) variant of [Entity-Adjusted 90D Coin Days Destroyed (eCDD-90)](https://studio.glassnode.com/metrics?a=BTC&m=indicators.Cdd90AccountBasedAgeAdjusted). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/indicators.Cdd90AccountBasedAgeAdjustedPit?a=BTC)\n","operationId":"indicators.Cdd90AccountBasedAgeAdjustedPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Entity-Adjusted ASOL > Entity-adjusted ASOL is an improved variant of \[ASOL]\() that discards transactions between addresses of the same entity (\\"in-house\\" transactions). Entity-adjusted ASOL therefore accounts for real economic activity only, and provides an improved market signal compared to its raw UTXO-based counterpart. For detailed information read this \[article]\( 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/indicators/asol_account_based_pit":{"get":{"summary":"Entity-Adjusted ASOL","description":"Entity-adjusted ASOL is an improved variant of [ASOL](https://studio.glassnode.com/metrics?a=BTC&m=indicators.Asol) that discards transactions between addresses of the same entity (\\\"in-house\\\" transactions). Entity-adjusted ASOL therefore accounts for real economic activity only, and provides an improved market signal compared to its raw UTXO-based counterpart. For detailed information read this [article](http://insights.glassnode.com/account-based-metrics).\\n\\nThis is the Point-in-Time (PiT) variant of [Entity-Adjusted ASOL](https://studio.glassnode.com/metrics?a=BTC&m=indicators.AsolAccountBased). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/indicators.AsolAccountBasedPit?a=BTC)\n","operationId":"indicators.AsolAccountBasedPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Entity-Adjusted CDD > Entity-adjusted CDD is an improved variant of \[CDD]\() that discards transactions between addresses of the same entity (\\"in-house\\" transactions). Entity-adjusted CDD therefore accounts for real economic activity only, and provides an improved market signal compared to its raw UTXO-based counterpart. For detailed information read this \[article]\( 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/indicators/cdd_account_based_pit":{"get":{"summary":"Entity-Adjusted CDD","description":"Entity-adjusted CDD is an improved variant of [CDD](https://studio.glassnode.com/metrics?a=BTC&m=indicators.Cdd) that discards transactions between addresses of the same entity (\\\"in-house\\\" transactions). Entity-adjusted CDD therefore accounts for real economic activity only, and provides an improved market signal compared to its raw UTXO-based counterpart. For detailed information read this [article](http://insights.glassnode.com/account-based-metrics).\\n\\nThis is the Point-in-Time (PiT) variant of [Entity-Adjusted CDD](https://studio.glassnode.com/metrics?a=BTC&m=indicators.CddAccountBased). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/indicators.CddAccountBasedPit?a=BTC)\n","operationId":"indicators.CddAccountBasedPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Entity-Adjusted CYD > Coin Years Destroyed (CYD) is defined as the 365 day rolling sum of \[Coin Days Destroyed (CDD)]\(), and shows the amount of coin days that have been destroyed over the past year. It is indicative of long-term holder behaviour. This version is entity-adjusted, meaning that transactions within addresses controlled by the same network participant are discarded (see \[this article]\() for more information). This metric was first put forward by \[ARK Invest]\( 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/indicators/cyd_account_based_pit":{"get":{"summary":"Entity-Adjusted CYD","description":"Coin Years Destroyed (CYD) is defined as the 365 day rolling sum of [Coin Days Destroyed (CDD)](https://studio.glassnode.com/metrics?a=BTC&m=indicators.Cdd), and shows the amount of coin days that have been destroyed over the past year. It is indicative of long-term holder behaviour. This version is entity-adjusted, meaning that transactions within addresses controlled by the same network participant are discarded (see [this article](https://insights.glassnode.com/account-based-metrics) for more information). This metric was first put forward by [ARK Invest](https://twitter.com/ARKInvest).\\n\\nThis is the Point-in-Time (PiT) variant of [Entity-Adjusted CYD](https://studio.glassnode.com/metrics?a=BTC&m=indicators.CydAccountBased). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/indicators.CydAccountBasedPit?a=BTC)\n","operationId":"indicators.CydAccountBasedPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Entity-Adjusted Dormancy > Entity-adjusted Dormancy is an improved variant of \[Average Coin Dormancy]\() that discards transactions between addresses of the same entity (\\"in-house\\" transactions). Entity-adjusted Dormancy therefore accounts for real economic activity only, and provides an improved market signal compared to its raw UTXO-based counterpart. For detailed information read this \[article]\( 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/indicators/dormancy_account_based_pit":{"get":{"summary":"Entity-Adjusted Dormancy","description":"Entity-adjusted Dormancy is an improved variant of [Average Coin Dormancy](https://studio.glassnode.com/metrics?a=BTC&m=indicators.AverageDormancy) that discards transactions between addresses of the same entity (\\\"in-house\\\" transactions). Entity-adjusted Dormancy therefore accounts for real economic activity only, and provides an improved market signal compared to its raw UTXO-based counterpart. For detailed information read this [article](http://insights.glassnode.com/account-based-metrics).\\n\\nThis is the Point-in-Time (PiT) variant of [Entity-Adjusted Dormancy](https://studio.glassnode.com/metrics?a=BTC&m=indicators.DormancyAccountBased). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/indicators.DormancyAccountBasedPit?a=BTC)\n","operationId":"indicators.DormancyAccountBasedPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Entity-Adjusted Liveliness > Entity-adjusted Liveliness is an improved variant of \[Liveliness]\() that discards transactions between addresses of the same entity (\\"in-house\\" transactions). Entity-adjusted Liveliness therefore accounts for real economic activity only, and provides an improved market signal compared to its raw UTXO-based counterpart. For detailed information read this \[article]\( 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/indicators/liveliness_account_based_pit":{"get":{"summary":"Entity-Adjusted Liveliness","description":"Entity-adjusted Liveliness is an improved variant of [Liveliness](https://studio.glassnode.com/metrics?a=BTC&m=indicators.Liveliness) that discards transactions between addresses of the same entity (\\\"in-house\\\" transactions). Entity-adjusted Liveliness therefore accounts for real economic activity only, and provides an improved market signal compared to its raw UTXO-based counterpart. For detailed information read this [article](http://insights.glassnode.com/account-based-metrics).\\n\\nThis is the Point-in-Time (PiT) variant of [Entity-Adjusted Liveliness](https://studio.glassnode.com/metrics?a=BTC&m=indicators.LivelinessAccountBased). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/indicators.LivelinessAccountBasedPit?a=BTC)\n","operationId":"indicators.LivelinessAccountBasedPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Entity-Adjusted Long-Term Holder ASOL > \[Long-Term Holder]\() variant of \[Entity-Adjusted ASOL]\(). Average Spent Output Lifespan (ASOL) is the average age (in days) of spent transaction outputs. 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.\n\nEntities 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. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see \[this article]\( 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/indicators/asol_lth_account_based_pit":{"get":{"summary":"Entity-Adjusted Long-Term Holder ASOL","description":"[Long-Term Holder](https://insights.glassnode.com/quantifying-bitcoin-hodler-supply/) variant of [Entity-Adjusted ASOL](https://studio.glassnode.com/metrics?a=BTC&m=indicators.AsolAccountBased). Average Spent Output Lifespan (ASOL) is the average age (in days) of spent transaction outputs. 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](https://insights.glassnode.com/quantifying-bitcoin-hodler-supply/) with weights given by a logistic function centered at an age of 155 days and a transition width of 10 days.\\n\\nEntities 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. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see [this article](https://insights.glassnode.com/true-bitcoin-volume/).\\n\\nThis is the Point-in-Time (PiT) variant of [Entity-Adjusted Long-Term Holder ASOL](https://studio.glassnode.com/metrics?a=BTC&m=indicators.AsolLthAccountBased). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/indicators.AsolLthAccountBasedPit?a=BTC)\n","operationId":"indicators.AsolLthAccountBasedPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Entity-Adjusted Long-Term Holder CDD > \[Long-Term Holder]\() variant of \[Entity-Adjusted CDD]\(). Coin Days Destroyed (CDD) 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 (\\"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.\n\nEntities 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. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see \[this article]\( 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/indicators/cdd_lth_account_based_pit":{"get":{"summary":"Entity-Adjusted Long-Term Holder CDD","description":"[Long-Term Holder](https://insights.glassnode.com/quantifying-bitcoin-hodler-supply/) variant of [Entity-Adjusted CDD](https://studio.glassnode.com/metrics?a=BTC&m=indicators.CddAccountBased). Coin Days Destroyed (CDD) 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 (\\\"in-house\\\" transactions) are discarded. Long- and Short-Term Holder supply is defined with respect to the [entity's averaged purchasing date](https://insights.glassnode.com/quantifying-bitcoin-hodler-supply/) with weights given by a logistic function centered at an age of 155 days and a transition width of 10 days.\\n\\nEntities 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. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see [this article](https://insights.glassnode.com/true-bitcoin-volume/).\\n\\nThis is the Point-in-Time (PiT) variant of [Entity-Adjusted Long-Term Holder CDD](https://studio.glassnode.com/metrics?a=BTC&m=indicators.CddLthAccountBased). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/indicators.CddLthAccountBasedPit?a=BTC)\n","operationId":"indicators.CddLthAccountBasedPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Entity-Adjusted Long-Term Holder Dormancy > \[Long-Term Holder]\() variant of \[Entity-Adjusted Dormancy]\(). Dormancy is the average number of days destroyed per coin transacted, and is defined as the ratio of coin days destroyed and total transfer volume. 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.\n\nEntities 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. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see \[this article]\( 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/indicators/dormancy_lth_account_based_pit":{"get":{"summary":"Entity-Adjusted Long-Term Holder Dormancy","description":"[Long-Term Holder](https://insights.glassnode.com/quantifying-bitcoin-hodler-supply/) variant of [Entity-Adjusted Dormancy](https://studio.glassnode.com/metrics?a=BTC&m=indicators.DormancyAccountBased). Dormancy is the average number of days destroyed per coin transacted, and is defined as the ratio of coin days destroyed and total transfer volume. 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](https://insights.glassnode.com/quantifying-bitcoin-hodler-supply/) with weights given by a logistic function centered at an age of 155 days and a transition width of 10 days.\\n\\nEntities 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. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see [this article](https://insights.glassnode.com/true-bitcoin-volume/).\\n\\nThis is the Point-in-Time (PiT) variant of [Entity-Adjusted Long-Term Holder Dormancy](https://studio.glassnode.com/metrics?a=BTC&m=indicators.DormancyLthAccountBased). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/indicators.DormancyLthAccountBasedPit?a=BTC)\n","operationId":"indicators.DormancyLthAccountBasedPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Entity-Adjusted LTH Realized Loss > Entity-Adjusted variant of \[Realized Loss]\() for \[Long-Term Holders]\(), 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. 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.\n\nVolume transferred between addresses owned by the same entity cluster is excluded. As such, no value is realized during internal or “in-house” transfers.\n\nEntities 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. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see \[this article]\( 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/indicators/realized_loss_lth_account_based_pit":{"get":{"summary":"Entity-Adjusted LTH Realized Loss","description":"Entity-Adjusted variant of [Realized Loss](https://studio.glassnode.com/metrics?a=BTC&m=indicators.RealizedLoss) for [Long-Term Holders](https://insights.glassnode.com/quantifying-bitcoin-hodler-supply/), 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. Long- and Short-Term Holder supply is defined with respect to the [entity's averaged purchasing date](https://insights.glassnode.com/quantifying-bitcoin-hodler-supply/) with weights given by a logistic function centered at an age of 155 days and a transition width of 10 days.\\n\\nVolume transferred between addresses owned by the same entity cluster is excluded. As such, no value is realized during internal or “in-house” transfers.\\n\\nEntities 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. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see [this article](https://insights.glassnode.com/true-bitcoin-volume).\\n\\nThis is the Point-in-Time (PiT) variant of [Entity-Adjusted LTH Realized Loss](https://studio.glassnode.com/metrics?a=BTC&m=indicators.RealizedLossLthAccountBased). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/indicators.RealizedLossLthAccountBasedPit?a=BTC)\n","operationId":"indicators.RealizedLossLthAccountBasedPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Entity-Adjusted LTH Realized Loss to Exchanges > Entity-Adjusted variant of \[Realized Loss]\() for coins that are sent from \[Long-Term Holders]\() to exchanges. 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. 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.\n\nEntities 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. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see \[this article]\( that exchange metrics are based on our labeled data of exchange addresses that we constantly keep updating, as well as data science techniques and statistical information that changes over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/indicators/realized_loss_lth_to_exchanges_account_based_pit":{"get":{"summary":"Entity-Adjusted LTH Realized Loss to Exchanges","description":"Entity-Adjusted variant of [Realized Loss](https://studio.glassnode.com/metrics?a=BTC&m=indicators.RealizedLoss) for coins that are sent from [Long-Term Holders](https://insights.glassnode.com/quantifying-bitcoin-hodler-supply/) to exchanges. 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. Long- and Short-Term Holder supply is defined with respect to the [entity's averaged purchasing date](https://insights.glassnode.com/quantifying-bitcoin-hodler-supply/) with weights given by a logistic function centered at an age of 155 days and a transition width of 10 days.\\n\\nEntities 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. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see [this article](https://insights.glassnode.com/true-bitcoin-volume).\\n\\nNote that exchange metrics are based on our labeled data of exchange addresses that we constantly keep updating, as well as data science techniques and statistical information that changes over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\\n\\nThis is the Point-in-Time (PiT) variant of [Entity-Adjusted LTH Realized Loss to Exchanges](https://studio.glassnode.com/metrics?a=BTC&m=indicators.RealizedLossLthToExchangesAccountBased). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/indicators.RealizedLossLthToExchangesAccountBasedPit?a=BTC)\n","operationId":"indicators.RealizedLossLthToExchangesAccountBasedPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Entity-Adjusted LTH Realized Profit > Entity-Adjusted variant of \[Realized Profit]\() for \[Long-Term Holders]\(), 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. 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.\n\nVolume transferred between addresses owned by the same entity cluster is excluded. As such, no value is realized during internal or “in-house” transfers.\n\nEntities 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. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see \[this article]\( 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/indicators/realized_profit_lth_account_based_pit":{"get":{"summary":"Entity-Adjusted LTH Realized Profit","description":"Entity-Adjusted variant of [Realized Profit](https://studio.glassnode.com/metrics?a=BTC&m=indicators.RealizedProfit) for [Long-Term Holders](https://insights.glassnode.com/quantifying-bitcoin-hodler-supply/), 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. Long- and Short-Term Holder supply is defined with respect to the [entity's averaged purchasing date](https://insights.glassnode.com/quantifying-bitcoin-hodler-supply/) with weights given by a logistic function centered at an age of 155 days and a transition width of 10 days.\\n\\nVolume transferred between addresses owned by the same entity cluster is excluded. As such, no value is realized during internal or “in-house” transfers.\\n\\nEntities 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. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see [this article](https://insights.glassnode.com/true-bitcoin-volume).\\n\\nThis is the Point-in-Time (PiT) variant of [Entity-Adjusted LTH Realized Profit](https://studio.glassnode.com/metrics?a=BTC&m=indicators.RealizedProfitLthAccountBased). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/indicators.RealizedProfitLthAccountBasedPit?a=BTC)\n","operationId":"indicators.RealizedProfitLthAccountBasedPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Entity-Adjusted LTH Realized Profit to Exchanges > Entity-Adjusted variant of \[Realized Profit]\() for coins that are sent from \[Long-Term Holders]\() to exchanges. Realized profit 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. 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.\n\nEntities 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. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see \[this article]\( that exchange metrics are based on our labeled data of exchange addresses that we constantly keep updating, as well as data science techniques and statistical information that changes over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/indicators/realized_profit_lth_to_exchanges_account_based_pit":{"get":{"summary":"Entity-Adjusted LTH Realized Profit to Exchanges","description":"Entity-Adjusted variant of [Realized Profit](https://studio.glassnode.com/metrics?a=BTC&m=indicators.RealizedProfit) for coins that are sent from [Long-Term Holders](https://insights.glassnode.com/quantifying-bitcoin-hodler-supply/) to exchanges. Realized profit 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. Long- and Short-Term Holder supply is defined with respect to the [entity's averaged purchasing date](https://insights.glassnode.com/quantifying-bitcoin-hodler-supply/) with weights given by a logistic function centered at an age of 155 days and a transition width of 10 days.\\n\\nEntities 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. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see [this article](https://insights.glassnode.com/true-bitcoin-volume).\\n\\nNote that exchange metrics are based on our labeled data of exchange addresses that we constantly keep updating, as well as data science techniques and statistical information that changes over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\\n\\nThis is the Point-in-Time (PiT) variant of [Entity-Adjusted LTH Realized Profit to Exchanges](https://studio.glassnode.com/metrics?a=BTC&m=indicators.RealizedProfitLthToExchangesAccountBased). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/indicators.RealizedProfitLthToExchangesAccountBasedPit?a=BTC)\n","operationId":"indicators.RealizedProfitLthToExchangesAccountBasedPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Entity-Adjusted LTH Transfer Volume > The total estimated amount of coins moved by \[long-term holders]\(). Volume transferred within addresses of the same entity is excluded. 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.\n\nEntities 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. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see \[this article]\( 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/transactions/transfers_volume_entity_adjusted_from_lth_sum_pit":{"get":{"summary":"Entity-Adjusted LTH Transfer Volume","description":"The total estimated amount of coins moved by [long-term holders](https://insights.glassnode.com/quantifying-bitcoin-hodler-supply/). Volume transferred within addresses of the same entity is excluded. Long- and Short-Term Holder supply is defined with respect to the [entity's averaged purchasing date](https://insights.glassnode.com/quantifying-bitcoin-hodler-supply/) with weights given by a logistic function centered at an age of 155 days and a transition width of 10 days.\\n\\nEntities 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. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see [this article](https://insights.glassnode.com/true-bitcoin-volume).\\n\\nThis is the Point-in-Time (PiT) variant of [Entity-Adjusted LTH Transfer Volume](https://studio.glassnode.com/metrics?a=BTC&m=transactions.TransfersVolumeEntityAdjustedFromLthSum). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/transactions.TransfersVolumeEntityAdjustedFromLthSumPit?a=BTC)\n","operationId":"transactions.TransfersVolumeEntityAdjustedFromLthSumPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"c","in":"query","required":false,"description":"currency - NATIVE, USD","schema":{"type":"string"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Entity-Adjusted LTH Transfer Volume in Loss > The total estimated amount of coins moved by \[long-term holders]\() in loss. Volume transferred within addresses of the same entity is excluded. 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- 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\nEntities 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. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see \[this article]\( 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/transactions/transfers_volume_entity_adjusted_from_lth_loss_sum_pit":{"get":{"summary":"Entity-Adjusted LTH Transfer Volume in Loss","description":"The total estimated amount of coins moved by [long-term holders](https://insights.glassnode.com/quantifying-bitcoin-hodler-supply/) in loss. Volume transferred within addresses of the same entity is excluded. 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- and Short-Term Holder supply is defined with respect to the [entity's averaged purchasing date](https://insights.glassnode.com/quantifying-bitcoin-hodler-supply/) with weights given by a logistic function centered at an age of 155 days and a transition width of 10 days.\\n\\nEntities 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. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see [this article](https://insights.glassnode.com/true-bitcoin-volume).\\n\\nThis is the Point-in-Time (PiT) variant of [Entity-Adjusted LTH Transfer Volume in Loss](https://studio.glassnode.com/metrics?a=BTC&m=transactions.TransfersVolumeEntityAdjustedFromLthLossSum). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/transactions.TransfersVolumeEntityAdjustedFromLthLossSumPit?a=BTC)\n","operationId":"transactions.TransfersVolumeEntityAdjustedFromLthLossSumPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"c","in":"query","required":false,"description":"currency - NATIVE, USD","schema":{"type":"string"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Entity-Adjusted LTH Transfer Volume in Profit > 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 to be 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. 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.\n\nEntities 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. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see \[this article]\( 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/transactions/transfers_volume_entity_adjusted_from_lth_profit_sum_pit":{"get":{"summary":"Entity-Adjusted LTH Transfer Volume in Profit","description":"The total estimated amount of coins moved by [long-term holders](https://insights.glassnode.com/quantifying-bitcoin-hodler-supply/) in profit. Volume transferred within addresses of the same entity is excluded. Coins are considered to be 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. Long- and Short-Term Holder supply is defined with respect to the [entity's averaged purchasing date](https://insights.glassnode.com/quantifying-bitcoin-hodler-supply/) with weights given by a logistic function centered at an age of 155 days and a transition width of 10 days.\\n\\nEntities 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. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see [this article](https://insights.glassnode.com/true-bitcoin-volume).\\n\\nThis is the Point-in-Time (PiT) variant of [Entity-Adjusted LTH Transfer Volume in Profit](https://studio.glassnode.com/metrics?a=BTC&m=transactions.TransfersVolumeEntityAdjustedFromLthProfitSum). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/transactions.TransfersVolumeEntityAdjustedFromLthProfitSumPit?a=BTC)\n","operationId":"transactions.TransfersVolumeEntityAdjustedFromLthProfitSumPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"c","in":"query","required":false,"description":"currency - NATIVE, USD","schema":{"type":"string"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Entity-Adjusted LTH-NUPL > 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). Entity-adjusted LTH NUPL therefore accounts for real economic activity only, and provides an improved market signal compared to its raw UTXO-based counterpart. For detailed information read this \[article]\(). An entity is considered as a Long-Term Holder if the time since its averaged purchasing date is more than 155 days.\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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/indicators/nupl_more_155_account_based_pit":{"get":{"summary":"Entity-Adjusted LTH-NUPL","description":"Entity-adjusted LTH-NUPL is an improved variant of [Long-Term Holders Net Unrealized Profit/Loss (LTH-NUPL)](https://studio.glassnode.com/metrics?a=BTC&m=indicators.NuplMore155) that discards transactions between addresses of the same entity (\\\"in-house\\\" transactions). Entity-adjusted LTH NUPL therefore accounts for real economic activity only, and provides an improved market signal compared to its raw UTXO-based counterpart. For detailed information read this [article](http://insights.glassnode.com/account-based-metrics). An entity is considered as a Long-Term Holder if the time since its averaged purchasing date is more than 155 days.\\n\\nThis is the Point-in-Time (PiT) variant of [Entity-Adjusted LTH-NUPL](https://studio.glassnode.com/metrics?a=BTC&m=indicators.NuplMore155AccountBased). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/indicators.NuplMore155AccountBasedPit?a=BTC)\n","operationId":"indicators.NuplMore155AccountBasedPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Entity-Adjusted LTH/STH Transfer Volume in Profit/Loss > The relative amount of coins moved by by \[long- and short-term holders]\() in profit/loss. Volume transferred within addresses of the same entity is excluded. Coins are considered to be in profit/loss when the price at the time the coins are spent is higher/lower than the entity\'s average on-chain acquisition price for its funds. 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.\n\nEntities 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. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see \[this article]\( 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/transactions/transfers_volume_entity_adjusted_from_lth_sth_profit_loss_relative_pit":{"get":{"summary":"Entity-Adjusted LTH/STH Transfer Volume in Profit/Loss","description":"The relative amount of coins moved by by [long- and short-term holders](https://insights.glassnode.com/quantifying-bitcoin-hodler-supply/) in profit/loss. Volume transferred within addresses of the same entity is excluded. Coins are considered to be in profit/loss when the price at the time the coins are spent is higher/lower than the entity's average on-chain acquisition price for its funds. Long- and Short-Term Holder supply is defined with respect to the [entity's averaged purchasing date](https://insights.glassnode.com/quantifying-bitcoin-hodler-supply/) with weights given by a logistic function centered at an age of 155 days and a transition width of 10 days.\\n\\nEntities 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. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see [this article](https://insights.glassnode.com/true-bitcoin-volume).\\n\\nThis is the Point-in-Time (PiT) variant of [Entity-Adjusted LTH/STH Transfer Volume in Profit/Loss](https://studio.glassnode.com/metrics?a=BTC&m=transactions.TransfersVolumeEntityAdjustedFromLthSthProfitLossRelative). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/transactions.TransfersVolumeEntityAdjustedFromLthSthProfitLossRelativePit?a=BTC)\n","operationId":"transactions.TransfersVolumeEntityAdjustedFromLthSthProfitLossRelativePit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Entity-Adjusted MSOL > Entity-adjusted MSOL is an improved variant of \[MSOL]\() that discards transactions between addresses of the same entity (\\"in-house\\" transactions). Entity-adjusted MSOL therefore accounts for real economic activity only, and provides an improved market signal compared to its raw UTXO-based counterpart. For detailed information read this \[article]\( 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/indicators/msol_account_based_pit":{"get":{"summary":"Entity-Adjusted MSOL","description":"Entity-adjusted MSOL is an improved variant of [MSOL](https://studio.glassnode.com/metrics?a=BTC&m=indicators.Msol) that discards transactions between addresses of the same entity (\\\"in-house\\\" transactions). Entity-adjusted MSOL therefore accounts for real economic activity only, and provides an improved market signal compared to its raw UTXO-based counterpart. For detailed information read this [article](http://insights.glassnode.com/account-based-metrics).\\n\\nThis is the Point-in-Time (PiT) variant of [Entity-Adjusted MSOL](https://studio.glassnode.com/metrics?a=BTC&m=indicators.MsolAccountBased). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/indicators.MsolAccountBasedPit?a=BTC)\n","operationId":"indicators.MsolAccountBasedPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Entity-Adjusted MVRV > Entity-adjusted MVRV is an improved variant of \[MVRV Ratio]\() that discards transactions between addresses of the same entity (\\"in-house\\" transactions). Entity-adjusted MVRV therefore accounts for real economic activity only, and provides an improved market signal compared to its raw UTXO-based counterpart. For detailed information read this \[article]\( 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/indicators/mvrv_account_based_pit":{"get":{"summary":"Entity-Adjusted MVRV","description":"Entity-adjusted MVRV is an improved variant of [MVRV Ratio](https://studio.glassnode.com/metrics?a=BTC&m=market.Mvrv) that discards transactions between addresses of the same entity (\\\"in-house\\\" transactions). Entity-adjusted MVRV therefore accounts for real economic activity only, and provides an improved market signal compared to its raw UTXO-based counterpart. For detailed information read this [article](http://insights.glassnode.com/account-based-metrics).\\n\\nThis is the Point-in-Time (PiT) variant of [Entity-Adjusted MVRV](https://studio.glassnode.com/metrics?a=BTC&m=indicators.MvrvAccountBased). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/indicators.MvrvAccountBasedPit?a=BTC)\n","operationId":"indicators.MvrvAccountBasedPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Entity-Adjusted NUPL > 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). Entity-adjusted NUPL therefore accounts for real economic activity only, and provides an improved market signal compared to its raw UTXO-based counterpart. For detailed information read this \[article]\( 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/indicators/net_unrealized_profit_loss_account_based_pit":{"get":{"summary":"Entity-Adjusted NUPL","description":"Entity-adjusted NUPL is an improved variant of [Net Unrealized Profit/Loss (NUPL)](https://studio.glassnode.com/metrics?a=BTC&m=indicators.NetUnrealizedProfitLoss) that discards transactions between addresses of the same entity (\\\"in-house\\\" transactions). Entity-adjusted NUPL therefore accounts for real economic activity only, and provides an improved market signal compared to its raw UTXO-based counterpart. For detailed information read this [article](http://insights.glassnode.com/account-based-metrics).\\n\\nThis is the Point-in-Time (PiT) variant of [Entity-Adjusted NUPL](https://studio.glassnode.com/metrics?a=BTC&m=indicators.NetUnrealizedProfitLossAccountBased). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/indicators.NetUnrealizedProfitLossAccountBasedPit?a=BTC)\n","operationId":"indicators.NetUnrealizedProfitLossAccountBasedPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Entity-Adjusted NVT > The Network Value to Transactions (NVT) Ratio is computed by dividing the market cap by the transferred on-chain volume measured in USD. This entity-adjusted version of the NVT Ratio uses \[entity-adjusted on-chain volume]\() and is therefore more accurate as it accounts for actual economic throughput.\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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/indicators/nvt_entity_adjusted_pit":{"get":{"summary":"Entity-Adjusted NVT","description":"The Network Value to Transactions (NVT) Ratio is computed by dividing the market cap by the transferred on-chain volume measured in USD. This entity-adjusted version of the NVT Ratio uses [entity-adjusted on-chain volume](https://studio.glassnode.com/metrics?a=BTC&category=&m=transactions.TransfersVolumeEntityAdjustedSum) and is therefore more accurate as it accounts for actual economic throughput.\\n\\nThis is the Point-in-Time (PiT) variant of [Entity-Adjusted NVT](https://studio.glassnode.com/metrics?a=BTC&m=indicators.NvtEntityAdjusted). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/indicators.NvtEntityAdjustedPit?a=BTC)\n","operationId":"indicators.NvtEntityAdjustedPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Entity-Adjusted Realized Cap > Entity-adjusted Realized Cap is an improved variant of \[Realized Cap]\() that discards transactions between addresses of the same entity (\\"in-house\\" transactions). Entity-adjusted Realized Cap therefore accounts for real economic activity only, and provides an improved market signal compared to its raw UTXO-based counterpart. For detailed information read this \[article]\( 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/indicators/rcap_account_based_pit":{"get":{"summary":"Entity-Adjusted Realized Cap","description":"Entity-adjusted Realized Cap is an improved variant of [Realized Cap](https://studio.glassnode.com/metrics?a=BTC&m=market.PriceRealizedUsd) that discards transactions between addresses of the same entity (\\\"in-house\\\" transactions). Entity-adjusted Realized Cap therefore accounts for real economic activity only, and provides an improved market signal compared to its raw UTXO-based counterpart. For detailed information read this [article](http://insights.glassnode.com/account-based-metrics).\\n\\nThis is the Point-in-Time (PiT) variant of [Entity-Adjusted Realized Cap](https://studio.glassnode.com/metrics?a=BTC&m=indicators.RcapAccountBased). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/indicators.RcapAccountBasedPit?a=BTC)\n","operationId":"indicators.RcapAccountBasedPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Entity-Adjusted Realized Loss > 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\nVolume transferred between addresses owned by the same entity cluster is excluded. As such, no value is realized during internal or “in-house” transfers.\n\nEntities 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. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see \[this article]\( 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/indicators/realized_loss_account_based_pit":{"get":{"summary":"Entity-Adjusted Realized Loss","description":"Entity-Adjusted variant of [Realized Loss](https://studio.glassnode.com/metrics?a=BTC&m=indicators.RealizedLoss), 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\\nVolume transferred between addresses owned by the same entity cluster is excluded. As such, no value is realized during internal or “in-house” transfers.\\n\\nEntities 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. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see [this article](https://insights.glassnode.com/true-bitcoin-volume).\\n\\nThis is the Point-in-Time (PiT) variant of [Entity-Adjusted Realized Loss](https://studio.glassnode.com/metrics?a=BTC&m=indicators.RealizedLossAccountBased). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/indicators.RealizedLossAccountBasedPit?a=BTC)\n","operationId":"indicators.RealizedLossAccountBasedPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Entity-Adjusted Realized Loss to Exchanges > Entity-Adjusted variant of \[Realized Loss]\() for coins that are sent to exchanges. 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\nEntities 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. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see \[this article]\( that exchange metrics are based on our labeled data of exchange addresses that we constantly keep updating, as well as data science techniques and statistical information that changes over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/indicators/realized_loss_to_exchanges_account_based_pit":{"get":{"summary":"Entity-Adjusted Realized Loss to Exchanges","description":"Entity-Adjusted variant of [Realized Loss](https://studio.glassnode.com/metrics?a=BTC&m=indicators.RealizedLoss) for coins that are sent to exchanges. 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\\nEntities 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. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see [this article](https://insights.glassnode.com/true-bitcoin-volume).\\n\\nNote that exchange metrics are based on our labeled data of exchange addresses that we constantly keep updating, as well as data science techniques and statistical information that changes over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\\n\\nThis is the Point-in-Time (PiT) variant of [Entity-Adjusted Realized Loss to Exchanges](https://studio.glassnode.com/metrics?a=BTC&m=indicators.RealizedLossToExchangesAccountBased). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/indicators.RealizedLossToExchangesAccountBasedPit?a=BTC)\n","operationId":"indicators.RealizedLossToExchangesAccountBasedPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Entity-Adjusted Realized Profit > Entity-Adjusted variant of \[Realized Profit]\(), 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\nVolume transferred between addresses owned by the same entity cluster is excluded. As such, no value is realized during internal or “in-house” transfers.\n\nEntities 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. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see \[this article]\( 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/indicators/realized_profit_account_based_pit":{"get":{"summary":"Entity-Adjusted Realized Profit","description":"Entity-Adjusted variant of [Realized Profit](https://studio.glassnode.com/metrics?a=BTC&m=indicators.RealizedProfit), 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\\nVolume transferred between addresses owned by the same entity cluster is excluded. As such, no value is realized during internal or “in-house” transfers.\\n\\nEntities 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. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see [this article](https://insights.glassnode.com/true-bitcoin-volume).\\n\\nThis is the Point-in-Time (PiT) variant of [Entity-Adjusted Realized Profit](https://studio.glassnode.com/metrics?a=BTC&m=indicators.RealizedProfitAccountBased). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/indicators.RealizedProfitAccountBasedPit?a=BTC)\n","operationId":"indicators.RealizedProfitAccountBasedPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Entity-Adjusted Realized Profit to Exchanges > Entity-Adjusted variant of \[Realized Profit]\() for coins that are sent to exchanges. Realized profit 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\nEntities 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. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see \[this article]\( that exchange metrics are based on our labeled data of exchange addresses that we constantly keep updating, as well as data science techniques and statistical information that changes over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/indicators/realized_profit_to_exchanges_account_based_pit":{"get":{"summary":"Entity-Adjusted Realized Profit to Exchanges","description":"Entity-Adjusted variant of [Realized Profit](https://studio.glassnode.com/metrics?a=BTC&m=indicators.RealizedProfit) for coins that are sent to exchanges. Realized profit 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\\nEntities 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. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see [this article](https://insights.glassnode.com/true-bitcoin-volume).\\n\\nNote that exchange metrics are based on our labeled data of exchange addresses that we constantly keep updating, as well as data science techniques and statistical information that changes over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\\n\\nThis is the Point-in-Time (PiT) variant of [Entity-Adjusted Realized Profit to Exchanges](https://studio.glassnode.com/metrics?a=BTC&m=indicators.RealizedProfitToExchangesAccountBased). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/indicators.RealizedProfitToExchangesAccountBasedPit?a=BTC)\n","operationId":"indicators.RealizedProfitToExchangesAccountBasedPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Entity-Adjusted Short-Term Holder ASOL > \[Short-Term Holder]\() variant of \[Entity-Adjusted ASOL]\(). Average Spent Output Lifespan (ASOL) is the average age (in days) of spent transaction outputs. 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.\n\nEntities 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. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see \[this article]\( 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/indicators/asol_sth_account_based_pit":{"get":{"summary":"Entity-Adjusted Short-Term Holder ASOL","description":"[Short-Term Holder](https://insights.glassnode.com/quantifying-bitcoin-hodler-supply/) variant of [Entity-Adjusted ASOL](https://studio.glassnode.com/metrics?a=BTC&m=indicators.AsolAccountBased). Average Spent Output Lifespan (ASOL) is the average age (in days) of spent transaction outputs. 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](https://insights.glassnode.com/quantifying-bitcoin-hodler-supply/) with weights given by a logistic function centered at an age of 155 days and a transition width of 10 days.\\n\\nEntities 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. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see [this article](https://insights.glassnode.com/true-bitcoin-volume/).\\n\\nThis is the Point-in-Time (PiT) variant of [Entity-Adjusted Short-Term Holder ASOL](https://studio.glassnode.com/metrics?a=BTC&m=indicators.AsolSthAccountBased). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/indicators.AsolSthAccountBasedPit?a=BTC)\n","operationId":"indicators.AsolSthAccountBasedPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Entity-Adjusted Short-Term Holder CDD > \[Short-Term Holder]\() variant of \[Entity-Adjusted CDD]\(). Coin Days Destroyed (CDD) 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 (\\"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.\n\nEntities 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. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see \[this article]\( 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/indicators/cdd_sth_account_based_pit":{"get":{"summary":"Entity-Adjusted Short-Term Holder CDD","description":"[Short-Term Holder](https://insights.glassnode.com/quantifying-bitcoin-hodler-supply/) variant of [Entity-Adjusted CDD](https://studio.glassnode.com/metrics?a=BTC&m=indicators.CddAccountBased). Coin Days Destroyed (CDD) 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 (\\\"in-house\\\" transactions) are discarded. Long- and Short-Term Holder supply is defined with respect to the [entity's averaged purchasing date](https://insights.glassnode.com/quantifying-bitcoin-hodler-supply/) with weights given by a logistic function centered at an age of 155 days and a transition width of 10 days.\\n\\nEntities 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. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see [this article](https://insights.glassnode.com/true-bitcoin-volume/).\\n\\nThis is the Point-in-Time (PiT) variant of [Entity-Adjusted Short-Term Holder CDD](https://studio.glassnode.com/metrics?a=BTC&m=indicators.CddSthAccountBased). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/indicators.CddSthAccountBasedPit?a=BTC)\n","operationId":"indicators.CddSthAccountBasedPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Entity-Adjusted Short-Term Holder Dormancy > \[Short-Term Holder]\() variant of \[Entity-Adjusted Dormancy]\(). Dormancy is the average number of days destroyed per coin transacted, and is defined as the ratio of coin days destroyed and total transfer volume. 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.\n\nEntities 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. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see \[this article]\( 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/indicators/dormancy_sth_account_based_pit":{"get":{"summary":"Entity-Adjusted Short-Term Holder Dormancy","description":"[Short-Term Holder](https://insights.glassnode.com/quantifying-bitcoin-hodler-supply/) variant of [Entity-Adjusted Dormancy](https://studio.glassnode.com/metrics?a=BTC&m=indicators.DormancyAccountBased). Dormancy is the average number of days destroyed per coin transacted, and is defined as the ratio of coin days destroyed and total transfer volume. 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](https://insights.glassnode.com/quantifying-bitcoin-hodler-supply/) with weights given by a logistic function centered at an age of 155 days and a transition width of 10 days.\\n\\nEntities 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. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see [this article](https://insights.glassnode.com/true-bitcoin-volume/).\\n\\nThis is the Point-in-Time (PiT) variant of [Entity-Adjusted Short-Term Holder Dormancy](https://studio.glassnode.com/metrics?a=BTC&m=indicators.DormancySthAccountBased). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/indicators.DormancySthAccountBasedPit?a=BTC)\n","operationId":"indicators.DormancySthAccountBasedPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Entity-Adjusted SOPR > Entity-adjusted SOPR is an improved variant of \[SOPR]\() that discards transactions between addresses of the same entity (\\"in-house\\" transactions). Entity-adjusted SOPR therefore accounts for real economic activity only, and provides an improved market signal compared to its raw UTXO-based counterpart. For detailed information read this \[article]\( 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/indicators/sopr_account_based_pit":{"get":{"summary":"Entity-Adjusted SOPR","description":"Entity-adjusted SOPR is an improved variant of [SOPR](https://studio.glassnode.com/metrics?a=BTC&m=indicators.Sopr) that discards transactions between addresses of the same entity (\\\"in-house\\\" transactions). Entity-adjusted SOPR therefore accounts for real economic activity only, and provides an improved market signal compared to its raw UTXO-based counterpart. For detailed information read this [article](http://insights.glassnode.com/account-based-metrics).\\n\\nThis is the Point-in-Time (PiT) variant of [Entity-Adjusted SOPR](https://studio.glassnode.com/metrics?a=BTC&m=indicators.SoprAccountBased). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/indicators.SoprAccountBasedPit?a=BTC)\n","operationId":"indicators.SoprAccountBasedPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Entity-Adjusted Spent Volume Age Bands (SVAB) > Spent Volume Age Bands (SVAB) is a separation of the on-chain transfer volume based on the coins\' age. Each band represents the percentage of spent volume that was previously moved within the time period denoted in the legend. This metric is entity-adjusted and discards transactions between addresses of the same entity (\\"in-house\\" transactions).\n\nEntities 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. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see \[this article]\( is the Point-in-Time (PiT) variant of \[Entity-Adjusted Spent Volume Age Bands (SVAB)]\(). 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/indicators/svab_entity_adjusted_pit":{"get":{"summary":"Entity-Adjusted Spent Volume Age Bands (SVAB)","description":"Spent Volume Age Bands (SVAB) is a separation of the on-chain transfer volume based on the coins' age. Each band represents the percentage of spent volume that was previously moved within the time period denoted in the legend. This metric is entity-adjusted and discards transactions between addresses of the same entity (\\\"in-house\\\" transactions).\\n\\nEntities 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. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see [this article](https://insights.glassnode.com/true-bitcoin-volume/).\\n\\nThis is the Point-in-Time (PiT) variant of [Entity-Adjusted Spent Volume Age Bands (SVAB)](https://studio.glassnode.com/metrics?a=BTC&m=indicators.SvabEntityAdjusted). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/indicators.SvabEntityAdjustedPit?a=BTC)\n","operationId":"indicators.SvabEntityAdjustedPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Entity-Adjusted Spent Volume Lifespan < 24h > The total transfer volume of coins younger than 24 hours. This metric is entity-adjusted and discards transactions between addresses of the same entity (\\"in-house\\" transactions).\n\nEntities 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. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see \[this article]\( is the Point-in-Time (PiT) variant of \[Entity-Adjusted Spent Volume Lifespan < 24h]\(). 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/indicators/svl_entity_adjusted_24h_pit":{"get":{"summary":"Entity-Adjusted Spent Volume Lifespan < 24h","description":"The total transfer volume of coins younger than 24 hours. This metric is entity-adjusted and discards transactions between addresses of the same entity (\\\"in-house\\\" transactions).\\n\\nEntities 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. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see [this article](https://insights.glassnode.com/true-bitcoin-volume/).\\n\\nThis is the Point-in-Time (PiT) variant of [Entity-Adjusted Spent Volume Lifespan < 24h](https://studio.glassnode.com/metrics?a=BTC&m=indicators.SvlEntityAdjusted24H). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/indicators.SvlEntityAdjusted24HPit?a=BTC)\n","operationId":"indicators.SvlEntityAdjusted24HPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"c","in":"query","required":false,"description":"currency - NATIVE, USD","schema":{"type":"string"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Entity-Adjusted Spent Volume Lifespan > 10y > The total transfer volume of coins that were last active more than 10 years ago. This metric is entity-adjusted and discards transactions between addresses of the same entity (\\"in-house\\" transactions).\n\nEntities 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. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see \[this article]\( is the Point-in-Time (PiT) variant of \[Entity-Adjusted Spent Volume Lifespan > 10y]\(). 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/indicators/svl_entity_adjusted_more_10y_pit":{"get":{"summary":"Entity-Adjusted Spent Volume Lifespan > 10y","description":"The total transfer volume of coins that were last active more than 10 years ago. This metric is entity-adjusted and discards transactions between addresses of the same entity (\\\"in-house\\\" transactions).\\n\\nEntities 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. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see [this article](https://insights.glassnode.com/true-bitcoin-volume/).\\n\\nThis is the Point-in-Time (PiT) variant of [Entity-Adjusted Spent Volume Lifespan > 10y](https://studio.glassnode.com/metrics?a=BTC&m=indicators.SvlEntityAdjustedMore10Y). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/indicators.SvlEntityAdjustedMore10YPit?a=BTC)\n","operationId":"indicators.SvlEntityAdjustedMore10YPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"c","in":"query","required":false,"description":"currency - NATIVE, USD","schema":{"type":"string"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Entity-Adjusted Spent Volume Lifespan 1d-1w > The total transfer volume of coins that were last active between 1d and 1w ago. This metric is entity-adjusted and discards transactions between addresses of the same entity (\\"in-house\\" transactions).\n\nEntities 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. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see \[this article]\( is the Point-in-Time (PiT) variant of \[Entity-Adjusted Spent Volume Lifespan 1d-1w]\(). 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/indicators/svl_entity_adjusted_1d_1w_pit":{"get":{"summary":"Entity-Adjusted Spent Volume Lifespan 1d-1w","description":"The total transfer volume of coins that were last active between 1d and 1w ago. This metric is entity-adjusted and discards transactions between addresses of the same entity (\\\"in-house\\\" transactions).\\n\\nEntities 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. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see [this article](https://insights.glassnode.com/true-bitcoin-volume/).\\n\\nThis is the Point-in-Time (PiT) variant of [Entity-Adjusted Spent Volume Lifespan 1d-1w](https://studio.glassnode.com/metrics?a=BTC&m=indicators.SvlEntityAdjusted1D1W). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/indicators.SvlEntityAdjusted1D1WPit?a=BTC)\n","operationId":"indicators.SvlEntityAdjusted1D1WPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"c","in":"query","required":false,"description":"currency - NATIVE, USD","schema":{"type":"string"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Entity-Adjusted Spent Volume Lifespan 1m-3m > The total transfer volume of coins that were last active between 1m and 3m ago. This metric is entity-adjusted and discards transactions between addresses of the same entity (\\"in-house\\" transactions).\n\nEntities 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. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see \[this article]\( is the Point-in-Time (PiT) variant of \[Entity-Adjusted Spent Volume Lifespan 1m-3m]\(). 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/indicators/svl_entity_adjusted_1m_3m_pit":{"get":{"summary":"Entity-Adjusted Spent Volume Lifespan 1m-3m","description":"The total transfer volume of coins that were last active between 1m and 3m ago. This metric is entity-adjusted and discards transactions between addresses of the same entity (\\\"in-house\\\" transactions).\\n\\nEntities 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. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see [this article](https://insights.glassnode.com/true-bitcoin-volume/).\\n\\nThis is the Point-in-Time (PiT) variant of [Entity-Adjusted Spent Volume Lifespan 1m-3m](https://studio.glassnode.com/metrics?a=BTC&m=indicators.SvlEntityAdjusted1M3M). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/indicators.SvlEntityAdjusted1M3MPit?a=BTC)\n","operationId":"indicators.SvlEntityAdjusted1M3MPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"c","in":"query","required":false,"description":"currency - NATIVE, USD","schema":{"type":"string"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Entity-Adjusted Spent Volume Lifespan 1w-1m > The total transfer volume of coins that were last active between 1w and 1m ago. This metric is entity-adjusted and discards transactions between addresses of the same entity (\\"in-house\\" transactions).\n\nEntities 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. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see \[this article]\( is the Point-in-Time (PiT) variant of \[Entity-Adjusted Spent Volume Lifespan 1w-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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/indicators/svl_entity_adjusted_1w_1m_pit":{"get":{"summary":"Entity-Adjusted Spent Volume Lifespan 1w-1m","description":"The total transfer volume of coins that were last active between 1w and 1m ago. This metric is entity-adjusted and discards transactions between addresses of the same entity (\\\"in-house\\\" transactions).\\n\\nEntities 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. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see [this article](https://insights.glassnode.com/true-bitcoin-volume/).\\n\\nThis is the Point-in-Time (PiT) variant of [Entity-Adjusted Spent Volume Lifespan 1w-1m ](https://studio.glassnode.com/metrics?a=BTC&m=indicators.SvlEntityAdjusted1W1M). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/indicators.SvlEntityAdjusted1W1MPit?a=BTC)\n","operationId":"indicators.SvlEntityAdjusted1W1MPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"c","in":"query","required":false,"description":"currency - NATIVE, USD","schema":{"type":"string"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Entity-Adjusted Spent Volume Lifespan 1y-2y > The total transfer volume of coins that were last active between 1y and 2y ago. This metric is entity-adjusted and discards transactions between addresses of the same entity (\\"in-house\\" transactions).\n\nEntities 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. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see \[this article]\( is the Point-in-Time (PiT) variant of \[Entity-Adjusted Spent Volume Lifespan 1y-2y]\(). 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/indicators/svl_entity_adjusted_1y_2y_pit":{"get":{"summary":"Entity-Adjusted Spent Volume Lifespan 1y-2y","description":"The total transfer volume of coins that were last active between 1y and 2y ago. This metric is entity-adjusted and discards transactions between addresses of the same entity (\\\"in-house\\\" transactions).\\n\\nEntities 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. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see [this article](https://insights.glassnode.com/true-bitcoin-volume/).\\n\\nThis is the Point-in-Time (PiT) variant of [Entity-Adjusted Spent Volume Lifespan 1y-2y](https://studio.glassnode.com/metrics?a=BTC&m=indicators.SvlEntityAdjusted1Y2Y). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/indicators.SvlEntityAdjusted1Y2YPit?a=BTC)\n","operationId":"indicators.SvlEntityAdjusted1Y2YPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"c","in":"query","required":false,"description":"currency - NATIVE, USD","schema":{"type":"string"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Entity-Adjusted Spent Volume Lifespan 2y-3y > The total transfer volume of coins that were last active between 2y and 3y ago. This metric is entity-adjusted and discards transactions between addresses of the same entity (\\"in-house\\" transactions).\n\nEntities 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. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see \[this article]\( is the Point-in-Time (PiT) variant of \[Entity-Adjusted Spent Volume Lifespan 2y-3y]\(). 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/indicators/svl_entity_adjusted_2y_3y_pit":{"get":{"summary":"Entity-Adjusted Spent Volume Lifespan 2y-3y","description":"The total transfer volume of coins that were last active between 2y and 3y ago. This metric is entity-adjusted and discards transactions between addresses of the same entity (\\\"in-house\\\" transactions).\\n\\nEntities 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. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see [this article](https://insights.glassnode.com/true-bitcoin-volume/).\\n\\nThis is the Point-in-Time (PiT) variant of [Entity-Adjusted Spent Volume Lifespan 2y-3y](https://studio.glassnode.com/metrics?a=BTC&m=indicators.SvlEntityAdjusted2Y3Y). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/indicators.SvlEntityAdjusted2Y3YPit?a=BTC)\n","operationId":"indicators.SvlEntityAdjusted2Y3YPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"c","in":"query","required":false,"description":"currency - NATIVE, USD","schema":{"type":"string"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Entity-Adjusted Spent Volume Lifespan 3m-6m > The total transfer volume of coins that were last active between 3m and 6m ago. This metric is entity-adjusted and discards transactions between addresses of the same entity (\\"in-house\\" transactions).\n\nEntities 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. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see \[this article]\( is the Point-in-Time (PiT) variant of \[Entity-Adjusted Spent Volume Lifespan 3m-6m]\(). 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/indicators/svl_entity_adjusted_3m_6m_pit":{"get":{"summary":"Entity-Adjusted Spent Volume Lifespan 3m-6m","description":"The total transfer volume of coins that were last active between 3m and 6m ago. This metric is entity-adjusted and discards transactions between addresses of the same entity (\\\"in-house\\\" transactions).\\n\\nEntities 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. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see [this article](https://insights.glassnode.com/true-bitcoin-volume/).\\n\\nThis is the Point-in-Time (PiT) variant of [Entity-Adjusted Spent Volume Lifespan 3m-6m](https://studio.glassnode.com/metrics?a=BTC&m=indicators.SvlEntityAdjusted3M6M). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/indicators.SvlEntityAdjusted3M6MPit?a=BTC)\n","operationId":"indicators.SvlEntityAdjusted3M6MPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"c","in":"query","required":false,"description":"currency - NATIVE, USD","schema":{"type":"string"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Entity-Adjusted Spent Volume Lifespan 3y-5y > The total transfer volume of coins that were last active between 3y and 5y ago. This metric is entity-adjusted and discards transactions between addresses of the same entity (\\"in-house\\" transactions).\n\nEntities 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. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see \[this article]\( is the Point-in-Time (PiT) variant of \[Entity-Adjusted Spent Volume Lifespan 3y-5y]\(). 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/indicators/svl_entity_adjusted_3y_5y_pit":{"get":{"summary":"Entity-Adjusted Spent Volume Lifespan 3y-5y","description":"The total transfer volume of coins that were last active between 3y and 5y ago. This metric is entity-adjusted and discards transactions between addresses of the same entity (\\\"in-house\\\" transactions).\\n\\nEntities 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. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see [this article](https://insights.glassnode.com/true-bitcoin-volume/).\\n\\nThis is the Point-in-Time (PiT) variant of [Entity-Adjusted Spent Volume Lifespan 3y-5y](https://studio.glassnode.com/metrics?a=BTC&m=indicators.SvlEntityAdjusted3Y5Y). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/indicators.SvlEntityAdjusted3Y5YPit?a=BTC)\n","operationId":"indicators.SvlEntityAdjusted3Y5YPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"c","in":"query","required":false,"description":"currency - NATIVE, USD","schema":{"type":"string"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Entity-Adjusted Spent Volume Lifespan 5y-7y > The total transfer volume of coins that were last active between 5y and 7y ago. This metric is entity-adjusted and discards transactions between addresses of the same entity (\\"in-house\\" transactions).\n\nEntities 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. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see \[this article]\( is the Point-in-Time (PiT) variant of \[Entity-Adjusted Spent Volume Lifespan 5y-7y]\(). 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/indicators/svl_entity_adjusted_5y_7y_pit":{"get":{"summary":"Entity-Adjusted Spent Volume Lifespan 5y-7y","description":"The total transfer volume of coins that were last active between 5y and 7y ago. This metric is entity-adjusted and discards transactions between addresses of the same entity (\\\"in-house\\\" transactions).\\n\\nEntities 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. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see [this article](https://insights.glassnode.com/true-bitcoin-volume/).\\n\\nThis is the Point-in-Time (PiT) variant of [Entity-Adjusted Spent Volume Lifespan 5y-7y](https://studio.glassnode.com/metrics?a=BTC&m=indicators.SvlEntityAdjusted5Y7Y). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/indicators.SvlEntityAdjusted5Y7YPit?a=BTC)\n","operationId":"indicators.SvlEntityAdjusted5Y7YPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"c","in":"query","required":false,"description":"currency - NATIVE, USD","schema":{"type":"string"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Entity-Adjusted Spent Volume Lifespan 6m-12m > The total transfer volume of coins that were last active between 6m and 12m ago. This metric is entity-adjusted and discards transactions between addresses of the same entity (\\"in-house\\" transactions).\n\nEntities 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. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see \[this article]\( is the Point-in-Time (PiT) variant of \[Entity-Adjusted Spent Volume Lifespan 6m-12m ]\(). 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/indicators/svl_entity_adjusted_6m_12m_pit":{"get":{"summary":"Entity-Adjusted Spent Volume Lifespan 6m-12m","description":"The total transfer volume of coins that were last active between 6m and 12m ago. This metric is entity-adjusted and discards transactions between addresses of the same entity (\\\"in-house\\\" transactions).\\n\\nEntities 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. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see [this article](https://insights.glassnode.com/true-bitcoin-volume/).\\n\\nThis is the Point-in-Time (PiT) variant of [Entity-Adjusted Spent Volume Lifespan 6m-12m ](https://studio.glassnode.com/metrics?a=BTC&m=indicators.SvlEntityAdjusted6M12M). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/indicators.SvlEntityAdjusted6M12MPit?a=BTC)\n","operationId":"indicators.SvlEntityAdjusted6M12MPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"c","in":"query","required":false,"description":"currency - NATIVE, USD","schema":{"type":"string"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Entity-Adjusted Spent Volume Lifespan 7y-10y > The total transfer volume of coins that were last active between 7y and 10y ago. This metric is entity-adjusted and discards transactions between addresses of the same entity (\\"in-house\\" transactions).\n\nEntities 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. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see \[this article]\( is the Point-in-Time (PiT) variant of \[Entity-Adjusted Spent Volume Lifespan 7y-10y]\(). 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/indicators/svl_entity_adjusted_7y_10y_pit":{"get":{"summary":"Entity-Adjusted Spent Volume Lifespan 7y-10y","description":"The total transfer volume of coins that were last active between 7y and 10y ago. This metric is entity-adjusted and discards transactions between addresses of the same entity (\\\"in-house\\\" transactions).\\n\\nEntities 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. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see [this article](https://insights.glassnode.com/true-bitcoin-volume/).\\n\\nThis is the Point-in-Time (PiT) variant of [Entity-Adjusted Spent Volume Lifespan 7y-10y](https://studio.glassnode.com/metrics?a=BTC&m=indicators.SvlEntityAdjusted7Y10Y). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/indicators.SvlEntityAdjusted7Y10YPit?a=BTC)\n","operationId":"indicators.SvlEntityAdjusted7Y10YPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"c","in":"query","required":false,"description":"currency - NATIVE, USD","schema":{"type":"string"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Entity-Adjusted STH Realized Loss > Entity-Adjusted variant of \[Realized Loss]\() for \[Short-Term Holders]\(), 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. 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.\n\nVolume transferred between addresses owned by the same entity cluster is excluded. As such, no value is realized during internal or “in-house” transfers.\n\nEntities 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. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see \[this article]\( is the Point-in-Time (PiT) variant of \[Entity-Adjusted STH 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/indicators/realized_loss_sth_account_based_pit":{"get":{"summary":"Entity-Adjusted STH Realized Loss","description":"Entity-Adjusted variant of [Realized Loss](https://studio.glassnode.com/metrics?a=BTC&m=indicators.RealizedLoss) for [Short-Term Holders](https://insights.glassnode.com/quantifying-bitcoin-hodler-supply/), 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. Long- and Short-Term Holder supply is defined with respect to the [entity's averaged purchasing date](https://insights.glassnode.com/quantifying-bitcoin-hodler-supply/) with weights given by a logistic function centered at an age of 155 days and a transition width of 10 days.\\n\\nVolume transferred between addresses owned by the same entity cluster is excluded. As such, no value is realized during internal or “in-house” transfers.\\n\\nEntities 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. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see [this article](https://insights.glassnode.com/true-bitcoin-volume).\\n\\nThis is the Point-in-Time (PiT) variant of [Entity-Adjusted STH Realized Loss](https://studio.glassnode.com/metrics?a=BTC&m=indicators.RealizedLossSthAccountBased). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/indicators.RealizedLossSthAccountBasedPit?a=BTC)\n","operationId":"indicators.RealizedLossSthAccountBasedPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Entity-Adjusted STH Realized Loss to Exchanges > Entity-Adjusted variant of \[Realized Loss]\() for coins that are sent from \[Short-Term Holders]\() to exchanges. 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. 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.\n\nEntities 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. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see \[this article]\( that exchange metrics are based on our labeled data of exchange addresses that we constantly keep updating, as well as data science techniques and statistical information that changes over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\n\nThis is the Point-in-Time (PiT) variant of \[Entity-Adjusted STH 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/indicators/realized_loss_sth_to_exchanges_account_based_pit":{"get":{"summary":"Entity-Adjusted STH Realized Loss to Exchanges","description":"Entity-Adjusted variant of [Realized Loss](https://studio.glassnode.com/metrics?a=BTC&m=indicators.RealizedLoss) for coins that are sent from [Short-Term Holders](https://insights.glassnode.com/quantifying-bitcoin-hodler-supply/) to exchanges. 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. Long- and Short-Term Holder supply is defined with respect to the [entity's averaged purchasing date](https://insights.glassnode.com/quantifying-bitcoin-hodler-supply/) with weights given by a logistic function centered at an age of 155 days and a transition width of 10 days.\\n\\nEntities 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. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see [this article](https://insights.glassnode.com/true-bitcoin-volume).\\n\\nNote that exchange metrics are based on our labeled data of exchange addresses that we constantly keep updating, as well as data science techniques and statistical information that changes over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\\n\\nThis is the Point-in-Time (PiT) variant of [Entity-Adjusted STH Realized Loss to Exchanges](https://studio.glassnode.com/metrics?a=BTC&m=indicators.RealizedLossSthToExchangesAccountBased). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/indicators.RealizedLossSthToExchangesAccountBasedPit?a=BTC)\n","operationId":"indicators.RealizedLossSthToExchangesAccountBasedPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Entity-Adjusted STH Realized Profit > Entity-Adjusted variant of \[Realized Profit]\() for \[Short-Term Holders]\(), 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. 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.\n\nVolume transferred between addresses owned by the same entity cluster is excluded. As such, no value is realized during internal or “in-house” transfers.\n\nEntities 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. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see \[this article]\( is the Point-in-Time (PiT) variant of \[Entity-Adjusted STH 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/indicators/realized_profit_sth_account_based_pit":{"get":{"summary":"Entity-Adjusted STH Realized Profit","description":"Entity-Adjusted variant of [Realized Profit](https://studio.glassnode.com/metrics?a=BTC&m=indicators.RealizedProfit) for [Short-Term Holders](https://insights.glassnode.com/quantifying-bitcoin-hodler-supply/), 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. Long- and Short-Term Holder supply is defined with respect to the [entity's averaged purchasing date](https://insights.glassnode.com/quantifying-bitcoin-hodler-supply/) with weights given by a logistic function centered at an age of 155 days and a transition width of 10 days.\\n\\nVolume transferred between addresses owned by the same entity cluster is excluded. As such, no value is realized during internal or “in-house” transfers.\\n\\nEntities 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. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see [this article](https://insights.glassnode.com/true-bitcoin-volume).\\n\\nThis is the Point-in-Time (PiT) variant of [Entity-Adjusted STH Realized Profit](https://studio.glassnode.com/metrics?a=BTC&m=indicators.RealizedProfitSthAccountBased). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/indicators.RealizedProfitSthAccountBasedPit?a=BTC)\n","operationId":"indicators.RealizedProfitSthAccountBasedPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Entity-Adjusted STH Realized Profit to Exchanges > Entity-Adjusted variant of \[Realized Profit]\() for coins that are sent from \[Short-Term Holders]\() to exchanges. Realized profit 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. 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.\n\nEntities 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. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see \[this article]\( that exchange metrics are based on our labeled data of exchange addresses that we constantly keep updating, as well as data science techniques and statistical information that changes over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\n\nThis is the Point-in-Time (PiT) variant of \[Entity-Adjusted STH 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/indicators/realized_profit_sth_to_exchanges_account_based_pit":{"get":{"summary":"Entity-Adjusted STH Realized Profit to Exchanges","description":"Entity-Adjusted variant of [Realized Profit](https://studio.glassnode.com/metrics?a=BTC&m=indicators.RealizedProfit) for coins that are sent from [Short-Term Holders](https://insights.glassnode.com/quantifying-bitcoin-hodler-supply/) to exchanges. Realized profit 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. Long- and Short-Term Holder supply is defined with respect to the [entity's averaged purchasing date](https://insights.glassnode.com/quantifying-bitcoin-hodler-supply/) with weights given by a logistic function centered at an age of 155 days and a transition width of 10 days.\\n\\nEntities 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. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see [this article](https://insights.glassnode.com/true-bitcoin-volume).\\n\\nNote that exchange metrics are based on our labeled data of exchange addresses that we constantly keep updating, as well as data science techniques and statistical information that changes over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\\n\\nThis is the Point-in-Time (PiT) variant of [Entity-Adjusted STH Realized Profit to Exchanges](https://studio.glassnode.com/metrics?a=BTC&m=indicators.RealizedProfitSthToExchangesAccountBased). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/indicators.RealizedProfitSthToExchangesAccountBasedPit?a=BTC)\n","operationId":"indicators.RealizedProfitSthToExchangesAccountBasedPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Entity-Adjusted STH Transfer Volume > The total estimated amount of coins moved by \[short-term holders]\(). Volume transferred within addresses of the same entity is excluded. 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.\n\nEntities 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. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see \[this article]\( is the Point-in-Time (PiT) variant of \[Entity-Adjusted STH 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/transactions/transfers_volume_entity_adjusted_from_sth_sum_pit":{"get":{"summary":"Entity-Adjusted STH Transfer Volume","description":"The total estimated amount of coins moved by [short-term holders](https://insights.glassnode.com/quantifying-bitcoin-hodler-supply/). Volume transferred within addresses of the same entity is excluded. Long- and Short-Term Holder supply is defined with respect to the [entity's averaged purchasing date](https://insights.glassnode.com/quantifying-bitcoin-hodler-supply/) with weights given by a logistic function centered at an age of 155 days and a transition width of 10 days.\\n\\nEntities 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. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see [this article](https://insights.glassnode.com/true-bitcoin-volume).\\n\\nThis is the Point-in-Time (PiT) variant of [Entity-Adjusted STH Transfer Volume](https://studio.glassnode.com/metrics?a=BTC&m=transactions.TransfersVolumeEntityAdjustedFromSthSum). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/transactions.TransfersVolumeEntityAdjustedFromSthSumPit?a=BTC)\n","operationId":"transactions.TransfersVolumeEntityAdjustedFromSthSumPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"c","in":"query","required":false,"description":"currency - NATIVE, USD","schema":{"type":"string"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Entity-Adjusted STH Transfer Volume in Loss > The total estimated amount of coins moved by \[short-term holders]\() in loss. Volume transferred within addresses of the same entity is excluded. 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- 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\nEntities 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. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see \[this article]\( is the Point-in-Time (PiT) variant of \[Entity-Adjusted STH 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/transactions/transfers_volume_entity_adjusted_from_sth_loss_sum_pit":{"get":{"summary":"Entity-Adjusted STH Transfer Volume in Loss","description":"The total estimated amount of coins moved by [short-term holders](https://insights.glassnode.com/quantifying-bitcoin-hodler-supply/) in loss. Volume transferred within addresses of the same entity is excluded. 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- and Short-Term Holder supply is defined with respect to the [entity's averaged purchasing date](https://insights.glassnode.com/quantifying-bitcoin-hodler-supply/) with weights given by a logistic function centered at an age of 155 days and a transition width of 10 days.\\n\\nEntities 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. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see [this article](https://insights.glassnode.com/true-bitcoin-volume).\\n\\nThis is the Point-in-Time (PiT) variant of [Entity-Adjusted STH Transfer Volume in Loss](https://studio.glassnode.com/metrics?a=BTC&m=transactions.TransfersVolumeEntityAdjustedFromSthLossSum). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/transactions.TransfersVolumeEntityAdjustedFromSthLossSumPit?a=BTC)\n","operationId":"transactions.TransfersVolumeEntityAdjustedFromSthLossSumPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"c","in":"query","required":false,"description":"currency - NATIVE, USD","schema":{"type":"string"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Entity-Adjusted STH Transfer Volume in Profit > The total estimated amount of coins moved by \[short-term holders]\() in profit. Volume transferred within addresses of the same entity is excluded. Coins are considered to be 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. 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.\n\nEntities 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. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see \[this article]\( is the Point-in-Time (PiT) variant of \[Entity-Adjusted STH 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/transactions/transfers_volume_entity_adjusted_from_sth_profit_sum_pit":{"get":{"summary":"Entity-Adjusted STH Transfer Volume in Profit","description":"The total estimated amount of coins moved by [short-term holders](https://insights.glassnode.com/quantifying-bitcoin-hodler-supply/) in profit. Volume transferred within addresses of the same entity is excluded. Coins are considered to be 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. Long- and Short-Term Holder supply is defined with respect to the [entity's averaged purchasing date](https://insights.glassnode.com/quantifying-bitcoin-hodler-supply/) with weights given by a logistic function centered at an age of 155 days and a transition width of 10 days.\\n\\nEntities 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. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see [this article](https://insights.glassnode.com/true-bitcoin-volume).\\n\\nThis is the Point-in-Time (PiT) variant of [Entity-Adjusted STH Transfer Volume in Profit](https://studio.glassnode.com/metrics?a=BTC&m=transactions.TransfersVolumeEntityAdjustedFromSthProfitSum). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/transactions.TransfersVolumeEntityAdjustedFromSthProfitSumPit?a=BTC)\n","operationId":"transactions.TransfersVolumeEntityAdjustedFromSthProfitSumPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"c","in":"query","required":false,"description":"currency - NATIVE, USD","schema":{"type":"string"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Entity-Adjusted STH-NUPL > Entity-adjusted STH-NUPL is an improved variant of \[Shot-Term Holders Net Unrealized Profit/Loss (STH-NUPL)]\() that discards transactions between addresses of the same entity (\\"in-house\\" transactions). Entity-adjusted STH NUPL therefore accounts for real economic activity only, and provides an improved market signal compared to its raw UTXO-based counterpart. For detailed information read this \[article]\(). An entity is considered as a Short-Term Holder if the time since its averaged purchasing date is less than 155 days.\n\nThis is the Point-in-Time (PiT) variant of \[Entity-Adjusted STH-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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/indicators/nupl_less_155_account_based_pit":{"get":{"summary":"Entity-Adjusted STH-NUPL","description":"Entity-adjusted STH-NUPL is an improved variant of [Shot-Term Holders Net Unrealized Profit/Loss (STH-NUPL)](https://studio.glassnode.com/metrics?a=BTC&m=indicators.NuplLess155) that discards transactions between addresses of the same entity (\\\"in-house\\\" transactions). Entity-adjusted STH NUPL therefore accounts for real economic activity only, and provides an improved market signal compared to its raw UTXO-based counterpart. For detailed information read this [article](http://insights.glassnode.com/account-based-metrics). An entity is considered as a Short-Term Holder if the time since its averaged purchasing date is less than 155 days.\\n\\nThis is the Point-in-Time (PiT) variant of [Entity-Adjusted STH-NUPL](https://studio.glassnode.com/metrics?a=BTC&m=indicators.NuplLess155AccountBased). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/indicators.NuplLess155AccountBasedPit?a=BTC)\n","operationId":"indicators.NuplLess155AccountBasedPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Entity-Adjusted Transaction Count > The estimated entity-adjusted number of transactions is defined as the number of transactions between different entities, i.e. the total number of transactions excluding transactions within addresses of the same entity. 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. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses.\n\nFor more information \[this article]\( is the Point-in-Time (PiT) variant of \[Entity-Adjusted Transaction 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/transactions/entity_adjusted_count_pit":{"get":{"summary":"Entity-Adjusted Transaction Count","description":"The estimated entity-adjusted number of transactions is defined as the number of transactions between different entities, i.e. the total number of transactions excluding transactions within addresses of the same entity. 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. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses.\\n\\nFor more information [this article](https://insights.glassnode.com/true-bitcoin-volume).\\n\\nThis is the Point-in-Time (PiT) variant of [Entity-Adjusted Transaction Count](https://studio.glassnode.com/metrics?a=BTC&m=transactions.EntityAdjustedCount). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/transactions.EntityAdjustedCountPit?a=BTC)\n","operationId":"transactions.EntityAdjustedCountPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Entity-Adjusted Unrealized Loss > Entity-adjusted Relative Unrealized Loss is an improved variant of \[Unrealized Loss]\() that discards transactions between addresses of the same entity (\\"in-house\\" transactions). Entity-adjusted Relative Unrealized Loss therefore accounts for real economic activity only, and provides an improved market signal compared to its raw UTXO-based counterpart. For detailed information read this \[article]\( is the Point-in-Time (PiT) variant of \[Entity-Adjusted Unrealized 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/indicators/unrealized_loss_account_based_pit":{"get":{"summary":"Entity-Adjusted Unrealized Loss","description":"Entity-adjusted Relative Unrealized Loss is an improved variant of [Unrealized Loss](https://studio.glassnode.com/metrics?a=BTC&m=indicators.UnrealizedLoss) that discards transactions between addresses of the same entity (\\\"in-house\\\" transactions). Entity-adjusted Relative Unrealized Loss therefore accounts for real economic activity only, and provides an improved market signal compared to its raw UTXO-based counterpart. For detailed information read this [article](http://insights.glassnode.com/account-based-metrics).\\n\\nThis is the Point-in-Time (PiT) variant of [Entity-Adjusted Unrealized Loss](https://studio.glassnode.com/metrics?a=BTC&m=indicators.UnrealizedLossAccountBased). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/indicators.UnrealizedLossAccountBasedPit?a=BTC)\n","operationId":"indicators.UnrealizedLossAccountBasedPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Entity-Adjusted Unrealized Profit > Entity-adjusted Relative Unrealized Profit is an improved variant of \[Unrealized Profit]\() that discards transactions between addresses of the same entity (\\"in-house\\" transactions). Entity-adjusted Relative Unrealized Proft therefore accounts for real economic activity only, and provides an improved market signal compared to its raw UTXO-based counterpart. For detailed information read this \[article]\( is the Point-in-Time (PiT) variant of \[Entity-Adjusted Unrealized 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/indicators/unrealized_profit_account_based_pit":{"get":{"summary":"Entity-Adjusted Unrealized Profit","description":"Entity-adjusted Relative Unrealized Profit is an improved variant of [Unrealized Profit](https://studio.glassnode.com/metrics?a=BTC&m=indicators.UnrealizedProfit) that discards transactions between addresses of the same entity (\\\"in-house\\\" transactions). Entity-adjusted Relative Unrealized Proft therefore accounts for real economic activity only, and provides an improved market signal compared to its raw UTXO-based counterpart. For detailed information read this [article](http://insights.glassnode.com/account-based-metrics).\\n\\nThis is the Point-in-Time (PiT) variant of [Entity-Adjusted Unrealized Profit](https://studio.glassnode.com/metrics?a=BTC&m=indicators.UnrealizedProfitAccountBased). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/indicators.UnrealizedProfitAccountBasedPit?a=BTC)\n","operationId":"indicators.UnrealizedProfitAccountBasedPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Entity-Adjusted URPD > UTXO Realized Price Distribution (URPD) shows at which prices the current set of Bitcoin UTXOs were created, i.e. each bar shows the amount of existing bitcoins that last moved within that specified price bucket. This version is entity-adjusted, meaning that for each entity the average purchasing price is used to sort its full balance into a bucket. In this calculation we discard coin movements between addresses controlled by the same entity, as such transfers do not correspond to real purchasing events and would distort the actual mean purchasing price. Further, we exclude all supply that is on exchanges, because a single averaged price for the funds of millions of users would be misleading and give rise to unwanted artifacts in the data.\n\nThis is the Point-in-Time (PiT) variant of \[Entity-Adjusted URPD]\(). 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/indicators/urpd_entity_adjusted_pit":{"get":{"summary":"Entity-Adjusted URPD","description":"UTXO Realized Price Distribution (URPD) shows at which prices the current set of Bitcoin UTXOs were created, i.e. each bar shows the amount of existing bitcoins that last moved within that specified price bucket. This version is entity-adjusted, meaning that for each entity the average purchasing price is used to sort its full balance into a bucket. In this calculation we discard coin movements between addresses controlled by the same entity, as such transfers do not correspond to real purchasing events and would distort the actual mean purchasing price. Further, we exclude all supply that is on exchanges, because a single averaged price for the funds of millions of users would be misleading and give rise to unwanted artifacts in the data.\\n\\nThis is the Point-in-Time (PiT) variant of [Entity-Adjusted URPD](https://studio.glassnode.com/metrics?a=BTC&m=indicators.UrpdEntityAdjusted). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/indicators.UrpdEntityAdjustedPit?a=BTC)\n","operationId":"indicators.UrpdEntityAdjustedPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Entity-Adjusted Volume (Mean) > The mean estimated amount of coins moved between different entities, i.e. excluding the volume transferred within addresses of the same entity. 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. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses.\n\nFor more information \[this article]\( is the Point-in-Time (PiT) variant of \[Entity-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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/transactions/transfers_volume_entity_adjusted_mean_pit":{"get":{"summary":"Entity-Adjusted Volume (Mean)","description":"The mean estimated amount of coins moved between different entities, i.e. excluding the volume transferred within addresses of the same entity. 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. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses.\\n\\nFor more information [this article](https://insights.glassnode.com/true-bitcoin-volume).\\n\\nThis is the Point-in-Time (PiT) variant of [Entity-Adjusted Volume (Mean)](https://studio.glassnode.com/metrics?a=BTC&m=transactions.TransfersVolumeEntityAdjustedMean). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/transactions.TransfersVolumeEntityAdjustedMeanPit?a=BTC)\n","operationId":"transactions.TransfersVolumeEntityAdjustedMeanPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"c","in":"query","required":false,"description":"currency - NATIVE, USD","schema":{"type":"string"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Entity-Adjusted Volume (Median) > The median estimated amount of coins moved between different entities, i.e. excluding volume transferred within addresses of the same entity. 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. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses.\n\nFor more information \[this article]\( is the Point-in-Time (PiT) variant of \[Entity-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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/transactions/transfers_volume_entity_adjusted_median_pit":{"get":{"summary":"Entity-Adjusted Volume (Median)","description":"The median estimated amount of coins moved between different entities, i.e. excluding volume transferred within addresses of the same entity. 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. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses.\\n\\nFor more information [this article](https://insights.glassnode.com/true-bitcoin-volume).\\n\\nThis is the Point-in-Time (PiT) variant of [Entity-Adjusted Volume (Median)](https://studio.glassnode.com/metrics?a=BTC&m=transactions.TransfersVolumeEntityAdjustedMedian). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/transactions.TransfersVolumeEntityAdjustedMedianPit?a=BTC)\n","operationId":"transactions.TransfersVolumeEntityAdjustedMedianPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"c","in":"query","required":false,"description":"currency - NATIVE, USD","schema":{"type":"string"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Entity-Adjusted Volume (Total) > The total estimated amount of coins moved between different entities, i.e. the total volumed transferred excluding the volume transferred within addresses of the same entity. 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. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses.\n\nFor more information \[this article]\( is the Point-in-Time (PiT) variant of \[Entity-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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/transactions/transfers_volume_entity_adjusted_sum_pit":{"get":{"summary":"Entity-Adjusted Volume (Total)","description":"The total estimated amount of coins moved between different entities, i.e. the total volumed transferred excluding the volume transferred within addresses of the same entity. 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. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses.\\n\\nFor more information [this article](https://insights.glassnode.com/true-bitcoin-volume).\\n\\nThis is the Point-in-Time (PiT) variant of [Entity-Adjusted Volume (Total)](https://studio.glassnode.com/metrics?a=BTC&m=transactions.TransfersVolumeEntityAdjustedSum). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/transactions.TransfersVolumeEntityAdjustedSumPit?a=BTC)\n","operationId":"transactions.TransfersVolumeEntityAdjustedSumPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"c","in":"query","required":false,"description":"currency - NATIVE, USD","schema":{"type":"string"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## ERC-20 Transactions (Absolute) > The number of transactions (transaction count) in the Ethereum network by transactions calling ERC20 contracts. Stablecoins contracts are excluded here.\n\nThis is the Point-in-Time (PiT) variant of \[ERC-20 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/transactions/transfers_count_erc20_pit":{"get":{"summary":"ERC-20 Transactions (Absolute)","description":"The number of transactions (transaction count) in the Ethereum network by transactions calling ERC20 contracts. Stablecoins contracts are excluded here.\\n\\nThis is the Point-in-Time (PiT) variant of [ERC-20 Transactions (Absolute)](https://studio.glassnode.com/metrics?a=BTC&m=transactions.TransfersCountErc20). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/transactions.TransfersCountErc20Pit?a=ETH)\n","operationId":"transactions.TransfersCountErc20Pit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - ETH","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## ERC-20 Transactions (Relative) > The relative amount (share) of transactions in the Ethereum network by transactions calling ERC20 contracts. Stablecoins contracts are excluded here.\n\nThis is the Point-in-Time (PiT) variant of \[ERC-20 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/transactions/transfers_count_erc20_relative_pit":{"get":{"summary":"ERC-20 Transactions (Relative)","description":"The relative amount (share) of transactions in the Ethereum network by transactions calling ERC20 contracts. Stablecoins contracts are excluded here.\\n\\nThis is the Point-in-Time (PiT) variant of [ERC-20 Transactions (Relative)](https://studio.glassnode.com/metrics?a=BTC&m=transactions.TransfersCountErc20Relative). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/transactions.TransfersCountErc20RelativePit?a=ETH)\n","operationId":"transactions.TransfersCountErc20RelativePit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - ETH","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## ETH 2.0 Total Value Staked by Provider > The total amount of ETH transferred to the ETH2 deposit contract via staking providers.\n\nThis is the Point-in-Time (PiT) variant of \[ETH 2.0 Total Value Staked by Provider]\(). 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/eth2/deposited_by_provider_volume_sum_pit":{"get":{"summary":"ETH 2.0 Total Value Staked by Provider","description":"The total amount of ETH transferred to the ETH2 deposit contract via staking providers.\\n\\nThis is the Point-in-Time (PiT) variant of [ETH 2.0 Total Value Staked by Provider](https://studio.glassnode.com/metrics?a=BTC&m=eth2.DepositedByProviderVolumeSum). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/eth2.DepositedByProviderVolumeSumPit?a=ETH)\n","operationId":"eth2.DepositedByProviderVolumeSumPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - ETH","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"c","in":"query","required":false,"description":"currency - NATIVE, USD","schema":{"type":"string"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## EU Year-over-Year Supply Change > \nThis metric aims at giving an estimate for the year-over-year change in the share of the Bitcoin supply to be held/traded in Europe.\n\nGeolocation of Bitcoin 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 probabilities for each entity being located in the US, Europe, or Asia. Working hours are defined as:\n\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)\n\nAn entity\'s balance will only contribute to the supply in the respective region if the location can be determined with a high certainty. Supply held on exchanges wallets are excluded.\n \n\nThis is the Point-in-Time (PiT) variant of \[EU 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/supply/emea_1y_supply_change_pit":{"get":{"summary":"EU Year-over-Year Supply Change","description":"\\nThis metric aims at giving an estimate for the year-over-year change in the share of the Bitcoin supply to be held/traded in Europe.\\n\\nGeolocation of Bitcoin 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 probabilities for each entity being located in the US, Europe, or Asia. Working hours are defined as:\\n\\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)\\n\\nAn entity's balance will only contribute to the supply in the respective region if the location can be determined with a high certainty. Supply held on exchanges wallets are excluded.\\n \\n\\nThis is the Point-in-Time (PiT) variant of [EU Year-over-Year Supply Change](https://studio.glassnode.com/metrics?a=BTC&m=supply.Emea1YSupplyChange). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/supply.Emea1YSupplyChangePit?a=BTC)\n","operationId":"supply.Emea1YSupplyChangePit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Exchange Balance (Percent) > The percent supply held on exchange addresses. Note that exchange metrics are based on our labeled data of exchange addresses that we constantly keep updating, as well as data science techniques and statistical information that changes over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\n\nThis is the Point-in-Time (PiT) variant of \[Exchange Balance (Percent)]\(). 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/distribution/balance_exchanges_relative_pit":{"get":{"summary":"Exchange Balance (Percent)","description":"The percent supply held on exchange addresses. Note that exchange metrics are based on our labeled data of exchange addresses that we constantly keep updating, as well as data science techniques and statistical information that changes over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\\n\\nThis is the Point-in-Time (PiT) variant of [Exchange Balance (Percent)](https://studio.glassnode.com/metrics?a=BTC&m=distribution.BalanceExchangesRelative). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/distribution.BalanceExchangesRelativePit?a=BTC)\n","operationId":"distribution.BalanceExchangesRelativePit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id (see list below for more details)","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Exchange Balance (Stacked) > The total amount of coins held on exchange addresses. Note that exchange metrics are based on our labeled data of exchange addresses that we constantly keep updating, as well as data science techniques and statistical information that changes over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\n\nThis is the Point-in-Time (PiT) variant of \[Exchange Balance (Stacked)]\(). 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/distribution/balance_exchanges_all_pit":{"get":{"summary":"Exchange Balance (Stacked)","description":"The total amount of coins held on exchange addresses. Note that exchange metrics are based on our labeled data of exchange addresses that we constantly keep updating, as well as data science techniques and statistical information that changes over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\\n\\nThis is the Point-in-Time (PiT) variant of [Exchange Balance (Stacked)](https://studio.glassnode.com/metrics?a=BTC&m=distribution.BalanceExchangesAll). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/distribution.BalanceExchangesAllPit?a=BTC)\n","operationId":"distribution.BalanceExchangesAllPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC, ETH, BNB, DOGE, TON, TRX, XRP","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"c","in":"query","required":false,"description":"currency - NATIVE, USD","schema":{"type":"string"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Exchange Balance (Total) > The total amount of coins held on exchange addresses. Note that exchange metrics are based on our labeled data of exchange addresses that we constantly keep updating, as well as data science techniques and statistical information that changes over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\n\nThis is the Point-in-Time (PiT) variant of \[Exchange Balance (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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/distribution/balance_exchanges_pit":{"get":{"summary":"Exchange Balance (Total)","description":"The total amount of coins held on exchange addresses. Note that exchange metrics are based on our labeled data of exchange addresses that we constantly keep updating, as well as data science techniques and statistical information that changes over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\\n\\nThis is the Point-in-Time (PiT) variant of [Exchange Balance (Total)](https://studio.glassnode.com/metrics?a=BTC&m=distribution.BalanceExchanges). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/distribution.BalanceExchangesPit?a=BTC)\n","operationId":"distribution.BalanceExchangesPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id (see list below for more details)","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"c","in":"query","required":false,"description":"currency - NATIVE, USD","schema":{"type":"string"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Exchange Deposits > The total count of transfers to exchange addresses, i.e. the number of on-chain deposits to exchanges. Note that exchange metrics are based on our labeled data of exchange addresses that we constantly keep updating, as well as data science techniques and statistical information that changes over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\n\nThis is the Point-in-Time (PiT) variant of \[Exchange Deposits]\(). 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/transactions/transfers_to_exchanges_count_pit":{"get":{"summary":"Exchange Deposits","description":"The total count of transfers to exchange addresses, i.e. the number of on-chain deposits to exchanges. Note that exchange metrics are based on our labeled data of exchange addresses that we constantly keep updating, as well as data science techniques and statistical information that changes over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\\n\\nThis is the Point-in-Time (PiT) variant of [Exchange Deposits](https://studio.glassnode.com/metrics?a=BTC&m=transactions.TransfersToExchangesCount). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/transactions.TransfersToExchangesCountPit?a=BTC)\n","operationId":"transactions.TransfersToExchangesCountPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id (see list below for more details)","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Exchange Fee Dominance > The Exchange Fee Dominance metric is defined as the percent amount of total fees paid in transactions related to on-chain exchange activity.\n- Deposits: Transactions that include an exchange address as the receiver of funds.\n- Withdrawals: Transactions that include an exchange address as the sender of funds.\n- In-House: Transactions that include addresses of a single exchange as both the sender and receiver of funds.\n- Inter-Exchange: Transactions that include addresses of (distinct) exchanges as both the sender and receiver of funds.\n\nIf a transaction can be categorized into multiple of these categories (e.g. a transaction that sends funds externally as well as in-house), the fees are split into percentages according to the volume transferred.\n\nThis is the Point-in-Time (PiT) variant of \[Exchange Fee 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/fees/exchanges_relative_pit":{"get":{"summary":"Exchange Fee Dominance","description":"The Exchange Fee Dominance metric is defined as the percent amount of total fees paid in transactions related to on-chain exchange activity.\\n- Deposits: Transactions that include an exchange address as the receiver of funds.\\n- Withdrawals: Transactions that include an exchange address as the sender of funds.\\n- In-House: Transactions that include addresses of a single exchange as both the sender and receiver of funds.\\n- Inter-Exchange: Transactions that include addresses of (distinct) exchanges as both the sender and receiver of funds.\\n\\nIf a transaction can be categorized into multiple of these categories (e.g. a transaction that sends funds externally as well as in-house), the fees are split into percentages according to the volume transferred.\\n\\nThis is the Point-in-Time (PiT) variant of [Exchange Fee Dominance](https://studio.glassnode.com/metrics?a=BTC&m=fees.ExchangesRelative). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/fees.ExchangesRelativePit?a=BTC)\n","operationId":"fees.ExchangesRelativePit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC, ETH","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Exchange Fees (Mean) > The mean amount of fees paid in transactions related to on-chain exchange activity. Note that the mean is computed over transfers, not transactions.\n- Deposits: Transactions that include an exchange address as the receiver of funds.\n- Withdrawals: Transactions that include an exchange address as the sender of funds.\n- In-House: Transactions that include addresses of a single exchange as both the sender and receiver of funds.\n- Inter-Exchange: Transactions that include addresses of (distinct) exchanges as both the sender and receiver of funds.\n\nIf a transaction can be categorized into multiple of these categories (e.g. a transaction that sends funds externally as well as in-house), the fees are split into percentages according to the volume transferred.\n\nThis is the Point-in-Time (PiT) variant of \[Exchange Fees (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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/fees/exchanges_mean_pit":{"get":{"summary":"Exchange Fees (Mean)","description":"The mean amount of fees paid in transactions related to on-chain exchange activity. Note that the mean is computed over transfers, not transactions.\\n- Deposits: Transactions that include an exchange address as the receiver of funds.\\n- Withdrawals: Transactions that include an exchange address as the sender of funds.\\n- In-House: Transactions that include addresses of a single exchange as both the sender and receiver of funds.\\n- Inter-Exchange: Transactions that include addresses of (distinct) exchanges as both the sender and receiver of funds.\\n\\nIf a transaction can be categorized into multiple of these categories (e.g. a transaction that sends funds externally as well as in-house), the fees are split into percentages according to the volume transferred.\\n\\nThis is the Point-in-Time (PiT) variant of [Exchange Fees (Mean)](https://studio.glassnode.com/metrics?a=BTC&m=fees.ExchangesMean). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/fees.ExchangesMeanPit?a=BTC)\n","operationId":"fees.ExchangesMeanPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC, ETH","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"c","in":"query","required":false,"description":"currency - NATIVE, USD","schema":{"type":"string"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Exchange Fees (Total) > The total amount of fees paid in transactions related to on-chain exchange activity.\n- Deposits: Transactions that include an exchange address as the receiver of funds.\n- Withdrawals: Transactions that include an exchange address as the sender of funds.\n- In-House: Transactions that include addresses of a single exchange as both the sender and receiver of funds.\n- Inter-Exchange: Transactions that include addresses of (distinct) exchanges as both the sender and receiver of funds.\n\nIf a transaction can be categorized into multiple of these categories (e.g. a transaction that sends funds externally as well as in-house), the fees are split into percentages according to the volume transferred.\n\nThis is the Point-in-Time (PiT) variant of \[Exchange Fees (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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/fees/exchanges_sum_pit":{"get":{"summary":"Exchange Fees (Total)","description":"The total amount of fees paid in transactions related to on-chain exchange activity.\\n- Deposits: Transactions that include an exchange address as the receiver of funds.\\n- Withdrawals: Transactions that include an exchange address as the sender of funds.\\n- In-House: Transactions that include addresses of a single exchange as both the sender and receiver of funds.\\n- Inter-Exchange: Transactions that include addresses of (distinct) exchanges as both the sender and receiver of funds.\\n\\nIf a transaction can be categorized into multiple of these categories (e.g. a transaction that sends funds externally as well as in-house), the fees are split into percentages according to the volume transferred.\\n\\nThis is the Point-in-Time (PiT) variant of [Exchange Fees (Total)](https://studio.glassnode.com/metrics?a=BTC&m=fees.ExchangesSum). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/fees.ExchangesSumPit?a=BTC)\n","operationId":"fees.ExchangesSumPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC, ETH","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"c","in":"query","required":false,"description":"currency - NATIVE, USD","schema":{"type":"string"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Exchange Inflow Volume (Mean) > The mean value of a transfer to exchanges addresses. Only successful transfers are counted. Note that exchange metrics are based on our labeled data of exchange addresses that we constantly keep updating, as well as data science techniques and statistical information that changes over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\n\nThis is the Point-in-Time (PiT) variant of \[Exchange Inflow 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/transactions/transfers_volume_to_exchanges_mean_pit":{"get":{"summary":"Exchange Inflow Volume (Mean)","description":"The mean value of a transfer to exchanges addresses. Only successful transfers are counted. Note that exchange metrics are based on our labeled data of exchange addresses that we constantly keep updating, as well as data science techniques and statistical information that changes over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\\n\\nThis is the Point-in-Time (PiT) variant of [Exchange Inflow Volume (Mean)](https://studio.glassnode.com/metrics?a=BTC&m=transactions.TransfersVolumeToExchangesMean). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/transactions.TransfersVolumeToExchangesMeanPit?a=BTC)\n","operationId":"transactions.TransfersVolumeToExchangesMeanPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id (see list below for more details)","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"c","in":"query","required":false,"description":"currency - NATIVE, USD","schema":{"type":"string"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Exchange Inflow Volume (Total) > The total amount of coins transferred to exchange addresses. Note that exchange metrics are based on our labeled data of exchange addresses that we constantly keep updating, as well as data science techniques and statistical information that changes over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\n\nThis is the Point-in-Time (PiT) variant of \[Exchange Inflow 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/transactions/transfers_volume_to_exchanges_sum_pit":{"get":{"summary":"Exchange Inflow Volume (Total)","description":"The total amount of coins transferred to exchange addresses. Note that exchange metrics are based on our labeled data of exchange addresses that we constantly keep updating, as well as data science techniques and statistical information that changes over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\\n\\nThis is the Point-in-Time (PiT) variant of [Exchange Inflow Volume (Total)](https://studio.glassnode.com/metrics?a=BTC&m=transactions.TransfersVolumeToExchangesSum). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/transactions.TransfersVolumeToExchangesSumPit?a=BTC)\n","operationId":"transactions.TransfersVolumeToExchangesSumPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id (see list below for more details)","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"c","in":"query","required":false,"description":"currency - NATIVE, USD","schema":{"type":"string"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Exchange Net Position Change > The 30d change of the supply held in exchange wallets.\n\nThis is the Point-in-Time (PiT) variant of \[Exchange Net Position 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/distribution/exchange_net_position_change_pit":{"get":{"summary":"Exchange Net Position Change","description":"The 30d change of the supply held in exchange wallets.\\n\\nThis is the Point-in-Time (PiT) variant of [Exchange Net Position Change](https://studio.glassnode.com/metrics?a=BTC&m=distribution.ExchangeNetPositionChange). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/distribution.ExchangeNetPositionChangePit?a=BTC)\n","operationId":"distribution.ExchangeNetPositionChangePit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id (see list below for more details)","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"c","in":"query","required":false,"description":"currency - NATIVE, USD","schema":{"type":"string"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Exchange Netflow Volume > The difference in volume flowing into exchanges and out of exchanges, i.e. the net flow of coins into/out of exchanges. Note that exchange metrics are based on our labeled data of exchange addresses that we constantly keep updating, as well as data science techniques and statistical information that changes over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\n\nThis is the Point-in-Time (PiT) variant of \[Exchange Netflow 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/transactions/transfers_volume_exchanges_net_pit":{"get":{"summary":"Exchange Netflow Volume","description":"The difference in volume flowing into exchanges and out of exchanges, i.e. the net flow of coins into/out of exchanges. Note that exchange metrics are based on our labeled data of exchange addresses that we constantly keep updating, as well as data science techniques and statistical information that changes over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\\n\\nThis is the Point-in-Time (PiT) variant of [Exchange Netflow Volume](https://studio.glassnode.com/metrics?a=BTC&m=transactions.TransfersVolumeExchangesNet). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/transactions.TransfersVolumeExchangesNetPit?a=BTC)\n","operationId":"transactions.TransfersVolumeExchangesNetPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id (see list below for more details)","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"c","in":"query","required":false,"description":"currency - NATIVE, USD","schema":{"type":"string"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Exchange Netflow Volume by Size > Breakdown of the net flow of coins into/out of exchanges by the USD value of the transactions. Note that exchange metrics are based on our labeled data of exchange addresses that we constantly keep updating, as well as data science techniques and statistical information that changes over time. Therefore these metrics are mutable - the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\n\nThis is the Point-in-Time (PiT) variant of \[Exchange Netflow Volume by Size]\(). 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/transactions/transfers_volume_exchanges_net_by_size_pit":{"get":{"summary":"Exchange Netflow Volume by Size","description":"Breakdown of the net flow of coins into/out of exchanges by the USD value of the transactions. Note that exchange metrics are based on our labeled data of exchange addresses that we constantly keep updating, as well as data science techniques and statistical information that changes over time. Therefore these metrics are mutable - the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\\n\\nThis is the Point-in-Time (PiT) variant of [Exchange Netflow Volume by Size](https://studio.glassnode.com/metrics?a=BTC&m=transactions.TransfersVolumeExchangesNetBySize). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/transactions.TransfersVolumeExchangesNetBySizePit?a=BTC)\n","operationId":"transactions.TransfersVolumeExchangesNetBySizePit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC, ETH","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"c","in":"query","required":false,"description":"currency - NATIVE, USD","schema":{"type":"string"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Exchange Outflow Volume (Mean) > The mean value of a transfer from exchanges addresses. Only successful transfers are counted. Note that exchange metrics are based on our labeled data of exchange addresses that we constantly keep updating, as well as data science techniques and statistical information that changes over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\n\nThis is the Point-in-Time (PiT) variant of \[Exchange Outflow 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/transactions/transfers_volume_from_exchanges_mean_pit":{"get":{"summary":"Exchange Outflow Volume (Mean)","description":"The mean value of a transfer from exchanges addresses. Only successful transfers are counted. Note that exchange metrics are based on our labeled data of exchange addresses that we constantly keep updating, as well as data science techniques and statistical information that changes over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\\n\\nThis is the Point-in-Time (PiT) variant of [Exchange Outflow Volume (Mean)](https://studio.glassnode.com/metrics?a=BTC&m=transactions.TransfersVolumeFromExchangesMean). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/transactions.TransfersVolumeFromExchangesMeanPit?a=BTC)\n","operationId":"transactions.TransfersVolumeFromExchangesMeanPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id (see list below for more details)","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"c","in":"query","required":false,"description":"currency - NATIVE, USD","schema":{"type":"string"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Exchange Outflow Volume (Total) > The total amount of coins transferred from exchange addresses. Note that exchange metrics are based on our labeled data of exchange addresses that we constantly keep updating, as well as data science techniques and statistical information that changes over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\n\nThis is the Point-in-Time (PiT) variant of \[Exchange Outflow 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/transactions/transfers_volume_from_exchanges_sum_pit":{"get":{"summary":"Exchange Outflow Volume (Total)","description":"The total amount of coins transferred from exchange addresses. Note that exchange metrics are based on our labeled data of exchange addresses that we constantly keep updating, as well as data science techniques and statistical information that changes over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\\n\\nThis is the Point-in-Time (PiT) variant of [Exchange Outflow Volume (Total)](https://studio.glassnode.com/metrics?a=BTC&m=transactions.TransfersVolumeFromExchangesSum). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/transactions.TransfersVolumeFromExchangesSumPit?a=BTC)\n","operationId":"transactions.TransfersVolumeFromExchangesSumPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id (see list below for more details)","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"c","in":"query","required":false,"description":"currency - NATIVE, USD","schema":{"type":"string"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Exchange Withdrawals > The total count of transfers from exchange addresses, i.e. the number of on-chain withdrawals from exchanges. Note that exchange metrics are based on our labeled data of exchange addresses that we constantly keep updating, as well as data science techniques and statistical information that changes over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\n\nThis is the Point-in-Time (PiT) variant of \[Exchange Withdrawals]\(). 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/transactions/transfers_from_exchanges_count_pit":{"get":{"summary":"Exchange Withdrawals","description":"The total count of transfers from exchange addresses, i.e. the number of on-chain withdrawals from exchanges. Note that exchange metrics are based on our labeled data of exchange addresses that we constantly keep updating, as well as data science techniques and statistical information that changes over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\\n\\nThis is the Point-in-Time (PiT) variant of [Exchange Withdrawals](https://studio.glassnode.com/metrics?a=BTC&m=transactions.TransfersFromExchangesCount). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/transactions.TransfersFromExchangesCountPit?a=BTC)\n","operationId":"transactions.TransfersFromExchangesCountPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id (see list below for more details)","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Gas Usage by Bridges (Absolute) > The amount of gas consumed by the Ethereum network by contracts that allow transfer of tokens between different blockchains.\n\nThis is the Point-in-Time (PiT) variant of \[Gas Usage by Bridges (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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/fees/gas_used_sum_bridges_pit":{"get":{"summary":"Gas Usage by Bridges (Absolute)","description":"The amount of gas consumed by the Ethereum network by contracts that allow transfer of tokens between different blockchains.\\n\\nThis is the Point-in-Time (PiT) variant of [Gas Usage by Bridges (Absolute)](https://studio.glassnode.com/metrics?a=BTC&m=fees.GasUsedSumBridges). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/fees.GasUsedSumBridgesPit?a=ETH)\n","operationId":"fees.GasUsedSumBridgesPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - ETH","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Gas Usage by Bridges (Relative) > The relative amount (share) of gas consumed by the Ethereum network by contracts that allow transfer of tokens between different blockchains.\n\nThis is the Point-in-Time (PiT) variant of \[Gas Usage by Bridges (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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/fees/gas_used_sum_bridges_relative_pit":{"get":{"summary":"Gas Usage by Bridges (Relative)","description":"The relative amount (share) of gas consumed by the Ethereum network by contracts that allow transfer of tokens between different blockchains.\\n\\nThis is the Point-in-Time (PiT) variant of [Gas Usage by Bridges (Relative)](https://studio.glassnode.com/metrics?a=BTC&m=fees.GasUsedSumBridgesRelative). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/fees.GasUsedSumBridgesRelativePit?a=ETH)\n","operationId":"fees.GasUsedSumBridgesRelativePit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - ETH","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Gas Usage by DeFi (Absolute) > The amount of gas consumed by the Ethereum network by on-chain financial instruments and protocols implemented as smart contracts, including decentralized exchanges (DEXs).\n\nThis is the Point-in-Time (PiT) variant of \[Gas Usage by DeFi (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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/fees/gas_used_sum_defi_pit":{"get":{"summary":"Gas Usage by DeFi (Absolute)","description":"The amount of gas consumed by the Ethereum network by on-chain financial instruments and protocols implemented as smart contracts, including decentralized exchanges (DEXs).\\n\\nThis is the Point-in-Time (PiT) variant of [Gas Usage by DeFi (Absolute)](https://studio.glassnode.com/metrics?a=BTC&m=fees.GasUsedSumDefi). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/fees.GasUsedSumDefiPit?a=ETH)\n","operationId":"fees.GasUsedSumDefiPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - ETH","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Gas Usage by DeFi (Relative) > The relative amount (share) of gas consumed by the Ethereum network by on-chain financial instruments and protocols implemented as smart contracts, including decentralized exchanges (DEXs).\n\nThis is the Point-in-Time (PiT) variant of \[Gas Usage by DeFi (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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/fees/gas_used_sum_defi_relative_pit":{"get":{"summary":"Gas Usage by DeFi (Relative)","description":"The relative amount (share) of gas consumed by the Ethereum network by on-chain financial instruments and protocols implemented as smart contracts, including decentralized exchanges (DEXs).\\n\\nThis is the Point-in-Time (PiT) variant of [Gas Usage by DeFi (Relative)](https://studio.glassnode.com/metrics?a=BTC&m=fees.GasUsedSumDefiRelative). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/fees.GasUsedSumDefiRelativePit?a=ETH)\n","operationId":"fees.GasUsedSumDefiRelativePit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - ETH","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Gas Usage by ERC-20 Tokens (Absolute) > The amount of gas consumed by the Ethereum network by transactions calling ERC20 contracts. Stablecoins contracts are excluded here.\n\nThis is the Point-in-Time (PiT) variant of \[Gas Usage by ERC-20 Tokens (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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/fees/gas_used_sum_erc20_pit":{"get":{"summary":"Gas Usage by ERC-20 Tokens (Absolute)","description":"The amount of gas consumed by the Ethereum network by transactions calling ERC20 contracts. Stablecoins contracts are excluded here.\\n\\nThis is the Point-in-Time (PiT) variant of [Gas Usage by ERC-20 Tokens (Absolute)](https://studio.glassnode.com/metrics?a=BTC&m=fees.GasUsedSumErc20). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/fees.GasUsedSumErc20Pit?a=ETH)\n","operationId":"fees.GasUsedSumErc20Pit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - ETH","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Gas Usage by ERC-20 Tokens (Relative) > The relative amount (share) of gas consumed by the Ethereum network by transactions calling ERC20 contracts. Stablecoins contracts are excluded here.\n\nThis is the Point-in-Time (PiT) variant of \[Gas Usage by ERC-20 Tokens (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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/fees/gas_used_sum_erc20_relative_pit":{"get":{"summary":"Gas Usage by ERC-20 Tokens (Relative)","description":"The relative amount (share) of gas consumed by the Ethereum network by transactions calling ERC20 contracts. Stablecoins contracts are excluded here.\\n\\nThis is the Point-in-Time (PiT) variant of [Gas Usage by ERC-20 Tokens (Relative)](https://studio.glassnode.com/metrics?a=BTC&m=fees.GasUsedSumErc20Relative). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/fees.GasUsedSumErc20RelativePit?a=ETH)\n","operationId":"fees.GasUsedSumErc20RelativePit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - ETH","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Gas Usage by NFTs (Absolute) > The amount of gas consumed by the Ethereum network by transactions interacting with non-fungible tokens. This category includes of both token contract standards (ERC721, ERC1155), as well as NFT marketplaces (OpenSea, Blur, LooksRare, Rarible, SuperRare) for trading those.\n\nThis is the Point-in-Time (PiT) variant of \[Gas Usage by NFTs (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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/fees/gas_used_sum_nfts_pit":{"get":{"summary":"Gas Usage by NFTs (Absolute)","description":"The amount of gas consumed by the Ethereum network by transactions interacting with non-fungible tokens. This category includes of both token contract standards (ERC721, ERC1155), as well as NFT marketplaces (OpenSea, Blur, LooksRare, Rarible, SuperRare) for trading those.\\n\\nThis is the Point-in-Time (PiT) variant of [Gas Usage by NFTs (Absolute)](https://studio.glassnode.com/metrics?a=BTC&m=fees.GasUsedSumNfts). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/fees.GasUsedSumNftsPit?a=ETH)\n","operationId":"fees.GasUsedSumNftsPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - ETH","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Gas Usage by NFTs (Relative) > The relative amount (share) of gas consumed by the Ethereum network by transactions interacting with non-fungible tokens. This category includes of both token contract standards (ERC721, ERC1155), as well as NFT marketplaces (OpenSea, Blur, LooksRare, Rarible, SuperRare) for trading those.\n\nThis is the Point-in-Time (PiT) variant of \[Gas Usage by NFTs (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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/fees/gas_used_sum_nfts_relative_pit":{"get":{"summary":"Gas Usage by NFTs (Relative)","description":"The relative amount (share) of gas consumed by the Ethereum network by transactions interacting with non-fungible tokens. This category includes of both token contract standards (ERC721, ERC1155), as well as NFT marketplaces (OpenSea, Blur, LooksRare, Rarible, SuperRare) for trading those.\\n\\nThis is the Point-in-Time (PiT) variant of [Gas Usage by NFTs (Relative)](https://studio.glassnode.com/metrics?a=BTC&m=fees.GasUsedSumNftsRelative). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/fees.GasUsedSumNftsRelativePit?a=ETH)\n","operationId":"fees.GasUsedSumNftsRelativePit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - ETH","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Gas Usage by Stablecoins (Absolute) > The amount of gas consumed by the Ethereum network by stablecoin transactions. Stablecoin are fungible tokens that have their value pegged to an off-chain asset, either by the issuer or by an algorithm. We include 150+ stablecoins in this category, with USDT, USDC, UST, BUSD, and DAI being the most prominent ones.\n\nThis is the Point-in-Time (PiT) variant of \[Gas Usage by Stablecoins (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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/fees/gas_used_sum_stablecoins_pit":{"get":{"summary":"Gas Usage by Stablecoins (Absolute)","description":"The amount of gas consumed by the Ethereum network by stablecoin transactions. Stablecoin are fungible tokens that have their value pegged to an off-chain asset, either by the issuer or by an algorithm. We include 150+ stablecoins in this category, with USDT, USDC, UST, BUSD, and DAI being the most prominent ones.\\n\\nThis is the Point-in-Time (PiT) variant of [Gas Usage by Stablecoins (Absolute)](https://studio.glassnode.com/metrics?a=BTC&m=fees.GasUsedSumStablecoins). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/fees.GasUsedSumStablecoinsPit?a=ETH)\n","operationId":"fees.GasUsedSumStablecoinsPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - ETH","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Gas Usage by Stablecoins (Relative) > The relative amount (share) of gas consumed by the Ethereum network by stablecoin transactions. Stablecoin are fungible tokens that have their value pegged to an off-chain asset, either by the issuer or by an algorithm. We include 150+ stablecoins in this category, with USDT, USDC, UST, BUSD, and DAI being the most prominent ones.\n\nThis is the Point-in-Time (PiT) variant of \[Gas Usage by Stablecoins (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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/fees/gas_used_sum_stablecoins_relative_pit":{"get":{"summary":"Gas Usage by Stablecoins (Relative)","description":"The relative amount (share) of gas consumed by the Ethereum network by stablecoin transactions. Stablecoin are fungible tokens that have their value pegged to an off-chain asset, either by the issuer or by an algorithm. We include 150+ stablecoins in this category, with USDT, USDC, UST, BUSD, and DAI being the most prominent ones.\\n\\nThis is the Point-in-Time (PiT) variant of [Gas Usage by Stablecoins (Relative)](https://studio.glassnode.com/metrics?a=BTC&m=fees.GasUsedSumStablecoinsRelative). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/fees.GasUsedSumStablecoinsRelativePit?a=ETH)\n","operationId":"fees.GasUsedSumStablecoinsRelativePit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - ETH","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Gas Usage by Transaction Type (Absolute) > The amount of gas consumed by the Ethereum network by category. Transactions are classified into the following categories:\n\n- \*Vanilla:\* Pure ETH transfers between Externally Owned Accounts (EOAs), with no contracts being called.\n\n- \*ERC20:\* All transactions calling ERC20 contracts. Contracts in the Stablecoins category are excluded here.\n\n- \*Stablecoins:\* Fungible tokens that have their value pegged to an off-chain asset, either by the issuer or by an algorithm. We include 150+ stablecoins in this category, with USDT, USDC, UST, BUSD, and DAI being the most prominent ones.\n\n- \*DeFi:\* On-chain financial instruments and protocols implemented as smart contracts, including decentralized exchanges (DEXs). We include over 90+ DeFi protocols in this category, such as Uniswap, Etherdelta, 1inch, Sushiswap, Aave, and 0x.\n\n- \*Bridges:\* Contracts allowing transfer of tokens between different blockchains. We include 50+ bridges in this category, such as Ronin, Polygon, Optimism, and Arbitrum.\n\n- \*NFTs:\* Transactions interacting with non-fungible tokens. This category includes of both token contract standards (ERC721, ERC1155), as well as NFT marketplaces (OpenSea, Blur, LooksRare, Rarible, SuperRare) for trading those.\n\n- \*MEV Bots:\* Miner Extractable Value (MEV) bots execute transactions for profit by reordering, inserting, and censoring transactions within blocks.\n\n- \*Other:\* This category includes all other transactions in the Ethereum network that are not included in categories listed above.\n\nThis is the Point-in-Time (PiT) variant of \[Gas Usage by Transaction Type (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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/fees/tx_types_breakdown_sum_pit":{"get":{"summary":"Gas Usage by Transaction Type (Absolute)","description":"The amount of gas consumed by the Ethereum network by category. Transactions are classified into the following categories:\\n\\n- *Vanilla:* Pure ETH transfers between Externally Owned Accounts (EOAs), with no contracts being called.\\n\\n- *ERC20:* All transactions calling ERC20 contracts. Contracts in the Stablecoins category are excluded here.\\n\\n- *Stablecoins:* Fungible tokens that have their value pegged to an off-chain asset, either by the issuer or by an algorithm. We include 150+ stablecoins in this category, with USDT, USDC, UST, BUSD, and DAI being the most prominent ones.\\n\\n- *DeFi:* On-chain financial instruments and protocols implemented as smart contracts, including decentralized exchanges (DEXs). We include over 90+ DeFi protocols in this category, such as Uniswap, Etherdelta, 1inch, Sushiswap, Aave, and 0x.\\n\\n- *Bridges:* Contracts allowing transfer of tokens between different blockchains. We include 50+ bridges in this category, such as Ronin, Polygon, Optimism, and Arbitrum.\\n\\n- *NFTs:* Transactions interacting with non-fungible tokens. This category includes of both token contract standards (ERC721, ERC1155), as well as NFT marketplaces (OpenSea, Blur, LooksRare, Rarible, SuperRare) for trading those.\\n\\n- *MEV Bots:* Miner Extractable Value (MEV) bots execute transactions for profit by reordering, inserting, and censoring transactions within blocks.\\n\\n- *Other:* This category includes all other transactions in the Ethereum network that are not included in categories listed above.\\n\\nThis is the Point-in-Time (PiT) variant of [Gas Usage by Transaction Type (Absolute)](https://studio.glassnode.com/metrics?a=BTC&m=fees.TxTypesBreakdownSum). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/fees.TxTypesBreakdownSumPit?a=ETH)\n","operationId":"fees.TxTypesBreakdownSumPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - ETH","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Gas Usage by Transaction Type (Relative) > The relative amount (share) of gas consumed by the Ethereum network by category. Transactions are classified into one of the following categories:\n\n- \*Vanilla:\* Pure ETH transfers between Externally Owned Accounts (EOAs), with no contracts being called.\n\n- \*ERC20:\* All transactions calling ERC20 contracts. Contracts in the Stablecoins category are excluded here.\n\n- \*Stablecoins:\* Fungible tokens that have their value pegged to an off-chain asset, either by the issuer or by an algorithm. We include 150+ stablecoins in this category, with USDT, USDC, UST, BUSD, and DAI being the most prominent ones.\n\n- \*DeFi:\* On-chain financial instruments and protocols implemented as smart contracts, including decentralized exchanges (DEXs). We include over 90+ DeFi protocols in this category, such as Uniswap, Etherdelta, 1inch, Sushiswap, Aave, and 0x.\n\n- \*Bridges:\* Contracts allowing transfer of tokens between different blockchains. We include 50+ bridges in this category, such as Ronin, Polygon, Optimism, and Arbitrum.\n\n- \*NFTs:\* Transactions interacting with non-fungible tokens. This category includes of both token contract standards (ERC721, ERC1155), as well as NFT marketplaces (OpenSea, Blur, LooksRare, Rarible, SuperRare) for trading those.\n\n- \*MEV Bots:\* Miner Extractable Value (MEV) bots execute transactions for profit by reordering, inserting, and censoring transactions within blocks.\n\n- \*Other:\* This category includes all other transactions in the Ethereum network that are not included in categories listed above.\n\nThis is the Point-in-Time (PiT) variant of \[Gas Usage by Transaction Type (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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/fees/tx_types_breakdown_relative_pit":{"get":{"summary":"Gas Usage by Transaction Type (Relative)","description":"The relative amount (share) of gas consumed by the Ethereum network by category. Transactions are classified into one of the following categories:\\n\\n- *Vanilla:* Pure ETH transfers between Externally Owned Accounts (EOAs), with no contracts being called.\\n\\n- *ERC20:* All transactions calling ERC20 contracts. Contracts in the Stablecoins category are excluded here.\\n\\n- *Stablecoins:* Fungible tokens that have their value pegged to an off-chain asset, either by the issuer or by an algorithm. We include 150+ stablecoins in this category, with USDT, USDC, UST, BUSD, and DAI being the most prominent ones.\\n\\n- *DeFi:* On-chain financial instruments and protocols implemented as smart contracts, including decentralized exchanges (DEXs). We include over 90+ DeFi protocols in this category, such as Uniswap, Etherdelta, 1inch, Sushiswap, Aave, and 0x.\\n\\n- *Bridges:* Contracts allowing transfer of tokens between different blockchains. We include 50+ bridges in this category, such as Ronin, Polygon, Optimism, and Arbitrum.\\n\\n- *NFTs:* Transactions interacting with non-fungible tokens. This category includes of both token contract standards (ERC721, ERC1155), as well as NFT marketplaces (OpenSea, Blur, LooksRare, Rarible, SuperRare) for trading those.\\n\\n- *MEV Bots:* Miner Extractable Value (MEV) bots execute transactions for profit by reordering, inserting, and censoring transactions within blocks.\\n\\n- *Other:* This category includes all other transactions in the Ethereum network that are not included in categories listed above.\\n\\nThis is the Point-in-Time (PiT) variant of [Gas Usage by Transaction Type (Relative)](https://studio.glassnode.com/metrics?a=BTC&m=fees.TxTypesBreakdownRelative). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/fees.TxTypesBreakdownRelativePit?a=ETH)\n","operationId":"fees.TxTypesBreakdownRelativePit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - ETH","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Gas Usage by Vanilla Transactions (Absolute) > The amount of gas consumed by the Ethereum network by vanilla transactions. Vanilla transactions are pure ETH transfers between Externally Owned Accounts (EOAs), with no contracts being called. Note that occasionally the value of the last datapoint can slightly change as some addresses initially transact as \\"vanilla\\" before their associated smart contract deployment is observed.\n\nThis is the Point-in-Time (PiT) variant of \[Gas Usage by Vanilla 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/fees/gas_used_sum_vanilla_pit":{"get":{"summary":"Gas Usage by Vanilla Transactions (Absolute)","description":"The amount of gas consumed by the Ethereum network by vanilla transactions. Vanilla transactions are pure ETH transfers between Externally Owned Accounts (EOAs), with no contracts being called. Note that occasionally the value of the last datapoint can slightly change as some addresses initially transact as \\\"vanilla\\\" before their associated smart contract deployment is observed.\\n\\nThis is the Point-in-Time (PiT) variant of [Gas Usage by Vanilla Transactions (Absolute)](https://studio.glassnode.com/metrics?a=BTC&m=fees.GasUsedSumVanilla). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/fees.GasUsedSumVanillaPit?a=ETH)\n","operationId":"fees.GasUsedSumVanillaPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - ETH","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Gas Usage by Vanilla Transactions (Relative) > The relative amount (share) of gas consumed by the Ethereum network by vanilla transactions. Vanilla transactions are pure ETH transfers between Externally Owned Accounts (EOAs), with no contracts being called. Note that occasionally the value of the last datapoint can slightly change as some addresses initially transact as \\"vanilla\\" before their associated smart contract deployment is observed.\n\nThis is the Point-in-Time (PiT) variant of \[Gas Usage by Vanilla 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/fees/gas_used_sum_vanilla_relative_pit":{"get":{"summary":"Gas Usage by Vanilla Transactions (Relative)","description":"The relative amount (share) of gas consumed by the Ethereum network by vanilla transactions. Vanilla transactions are pure ETH transfers between Externally Owned Accounts (EOAs), with no contracts being called. Note that occasionally the value of the last datapoint can slightly change as some addresses initially transact as \\\"vanilla\\\" before their associated smart contract deployment is observed.\\n\\nThis is the Point-in-Time (PiT) variant of [Gas Usage by Vanilla Transactions (Relative)](https://studio.glassnode.com/metrics?a=BTC&m=fees.GasUsedSumVanillaRelative). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/fees.GasUsedSumVanillaRelativePit?a=ETH)\n","operationId":"fees.GasUsedSumVanillaRelativePit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - ETH","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## German Government Balance > The German Government Balance corresponds to the amount of BTC held in addresses controlled by German authorities. The metric includes seized funds, e.g. from Movie2k that were seized by the German BKA. We constantly keep updating the set of addresses contributing to the total balance.\n\nThis is the Point-in-Time (PiT) variant of \[German 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/distribution/balance_german_government_pit":{"get":{"summary":"German Government Balance","description":"The German Government Balance corresponds to the amount of BTC held in addresses controlled by German authorities. The metric includes seized funds, e.g. from Movie2k that were seized by the German BKA. We constantly keep updating the set of addresses contributing to the total balance.\\n\\nThis is the Point-in-Time (PiT) variant of [German Government Balance](https://studio.glassnode.com/metrics?a=BTC&m=distribution.BalanceGermanGovernment). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/distribution.BalanceGermanGovernmentPit?a=BTC)\n","operationId":"distribution.BalanceGermanGovernmentPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"c","in":"query","required":false,"description":"currency - NATIVE, USD","schema":{"type":"string"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Gini Coefficient > The gini coefficient for the distribution of coins over addresses. Exchange addresses, smart contract addresses, and other special asset-specific addresses (e.g. team fund addresses) are excluded for the computation of the gini.\n\nThis is the Point-in-Time (PiT) variant of \[Gini Coefficient]\(). 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/distribution/gini_pit":{"get":{"summary":"Gini Coefficient","description":"The gini coefficient for the distribution of coins over addresses. Exchange addresses, smart contract addresses, and other special asset-specific addresses (e.g. team fund addresses) are excluded for the computation of the gini.\\n\\nThis is the Point-in-Time (PiT) variant of [Gini Coefficient](https://studio.glassnode.com/metrics?a=BTC&m=distribution.Gini). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/distribution.GiniPit?a=ETH)\n","operationId":"distribution.GiniPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - ETH","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Herfindahl Index > Originally used as a \[measure of competition]\(), we adapt the Herfindahl Index as a metric for decentralization. It measures the addresses\' shares of the current supply, and is defined as the sum of weighted address balances in the network. A large score indicates high concentration of supply, whereas a small score is an indicator for more evenly distributed funds across addresses. Exchange addresses, smart contract addresses and other special asset-specific addresses (e.g. team fund addresses) are excluded.\n\nThis is the Point-in-Time (PiT) variant of \[Herfindahl Index]\(). 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/distribution/herfindahl_pit":{"get":{"summary":"Herfindahl Index","description":"Originally used as a [measure of competition](https://en.wikipedia.org/wiki/Herfindahl–Hirschman_Index), we adapt the Herfindahl Index as a metric for decentralization. It measures the addresses' shares of the current supply, and is defined as the sum of weighted address balances in the network. A large score indicates high concentration of supply, whereas a small score is an indicator for more evenly distributed funds across addresses. Exchange addresses, smart contract addresses and other special asset-specific addresses (e.g. team fund addresses) are excluded.\\n\\nThis is the Point-in-Time (PiT) variant of [Herfindahl Index](https://studio.glassnode.com/metrics?a=BTC&m=distribution.Herfindahl). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/distribution.HerfindahlPit?a=ETH)\n","operationId":"distribution.HerfindahlPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - ETH","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Highly Liquid Supply > The total supply held by \\"highly liquid\\" entities. The liquidity of an entity is defined as the ratio of cumulative outflows and cumulative inflows over the entity\'s lifespan. An entity is considered to be illiquid / liquid / highly liquid if its liquidity \*L\* is ≲ 0.25 / 0.25 ≲ \*L\* ≲ 0.75 / 0.75 ≲ L, respectively. For more information see our \[introductory article on Bitcoin liquidity]\( is the Point-in-Time (PiT) variant of \[Highly Liquid 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/supply/highly_liquid_sum_pit":{"get":{"summary":"Highly Liquid Supply","description":"The total supply held by \\\"highly liquid\\\" entities. The liquidity of an entity is defined as the ratio of cumulative outflows and cumulative inflows over the entity's lifespan. An entity is considered to be illiquid / liquid / highly liquid if its liquidity *L* is ≲ 0.25 / 0.25 ≲ *L* ≲ 0.75 / 0.75 ≲ L, respectively. For more information see our [introductory article on Bitcoin liquidity](https://insights.glassnode.com/bitcoin-liquid-supply).\\n\\nThis is the Point-in-Time (PiT) variant of [Highly Liquid Supply](https://studio.glassnode.com/metrics?a=BTC&m=supply.HighlyLiquidSum). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/supply.HighlyLiquidSumPit?a=BTC)\n","operationId":"supply.HighlyLiquidSumPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"c","in":"query","required":false,"description":"currency - NATIVE, USD","schema":{"type":"string"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Illiquid Supply > The total supply held by illiquid entities. The liquidity of an entity is defined as the ratio of cumulative outflows and cumulative inflows over the entity\'s lifespan. An entity is considered to be illiquid / liquid / highly liquid if its liquidity \*L\* is ≲ 0.25 / 0.25 ≲ \*L\* ≲ 0.75 / 0.75 ≲ L, respectively. For more information see our \[introductory article on Bitcoin liquidity]\( is the Point-in-Time (PiT) variant of \[Illiquid 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/supply/illiquid_sum_pit":{"get":{"summary":"Illiquid Supply","description":"The total supply held by illiquid entities. The liquidity of an entity is defined as the ratio of cumulative outflows and cumulative inflows over the entity's lifespan. An entity is considered to be illiquid / liquid / highly liquid if its liquidity *L* is ≲ 0.25 / 0.25 ≲ *L* ≲ 0.75 / 0.75 ≲ L, respectively. For more information see our [introductory article on Bitcoin liquidity](https://insights.glassnode.com/bitcoin-liquid-supply).\\n\\nThis is the Point-in-Time (PiT) variant of [Illiquid Supply](https://studio.glassnode.com/metrics?a=BTC&m=supply.IlliquidSum). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/supply.IlliquidSumPit?a=BTC)\n","operationId":"supply.IlliquidSumPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"c","in":"query","required":false,"description":"currency - NATIVE, USD","schema":{"type":"string"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Illiquid Supply Change > The monthly (30d) net change of supply held by illiquid entities. For more information see our \[introductory article on Bitcoin liquidity]\( is the Point-in-Time (PiT) variant of \[Illiquid 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/supply/illiquid_change_pit":{"get":{"summary":"Illiquid Supply Change","description":"The monthly (30d) net change of supply held by illiquid entities. For more information see our [introductory article on Bitcoin liquidity](http://insights.glassnode.com/bitcoin-liquid-supply).\\n\\nThis is the Point-in-Time (PiT) variant of [Illiquid Supply Change](https://studio.glassnode.com/metrics?a=BTC&m=supply.IlliquidChange). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/supply.IlliquidChangePit?a=BTC)\n","operationId":"supply.IlliquidChangePit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## In-House Exchange Volume > The total amount of coins transferred within wallets of the same exchange. Note that exchange metrics are based on our labeled data of exchange addresses that we constantly keep updating, as well as data science techniques and statistical information that changes over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\n\nThis is the Point-in-Time (PiT) variant of \[In-House Exchange 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/transactions/transfers_volume_within_exchanges_sum_pit":{"get":{"summary":"In-House Exchange Volume","description":"The total amount of coins transferred within wallets of the same exchange. Note that exchange metrics are based on our labeled data of exchange addresses that we constantly keep updating, as well as data science techniques and statistical information that changes over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\\n\\nThis is the Point-in-Time (PiT) variant of [In-House Exchange Volume](https://studio.glassnode.com/metrics?a=BTC&m=transactions.TransfersVolumeWithinExchangesSum). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/transactions.TransfersVolumeWithinExchangesSumPit?a=BTC)\n","operationId":"transactions.TransfersVolumeWithinExchangesSumPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id (see list below for more details)","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"c","in":"query","required":false,"description":"currency - NATIVE, USD","schema":{"type":"string"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Inter-Exchange Transfers > The total count of transfers between exchanges. Note that exchange metrics are based on our labeled data of exchange addresses that we constantly keep updating, as well as data science techniques and statistical information that changes over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\n\nThis is the Point-in-Time (PiT) variant of \[Inter-Exchange Transfers]\(). 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/transactions/transfers_between_exchanges_count_pit":{"get":{"summary":"Inter-Exchange Transfers","description":"The total count of transfers between exchanges. Note that exchange metrics are based on our labeled data of exchange addresses that we constantly keep updating, as well as data science techniques and statistical information that changes over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\\n\\nThis is the Point-in-Time (PiT) variant of [Inter-Exchange Transfers](https://studio.glassnode.com/metrics?a=BTC&m=transactions.TransfersBetweenExchangesCount). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/transactions.TransfersBetweenExchangesCountPit?a=BTC)\n","operationId":"transactions.TransfersBetweenExchangesCountPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id (see list below for more details)","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"from_exchange","in":"query","required":false,"description":"from_exchange name (see **/v1/metrics/transactions/transfers_between_exchanges_count_pit/flows** for a full list)","schema":{"type":"string"},"style":"form","explode":false},{"name":"to_exchange","in":"query","required":false,"description":"to_exchange name (see **/v1/metrics/transactions/transfers_between_exchanges_count_pit/flows** for a full list)","schema":{"type":"string"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Inter-Exchange Volume > The total amount of coins transferred between exchanges. Note that exchange metrics are based on our labeled data of exchange addresses that we constantly keep updating, as well as data science techniques and statistical information that changes over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\n\nThis is the Point-in-Time (PiT) variant of \[Inter-Exchange 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/transactions/transfers_volume_between_exchanges_sum_pit":{"get":{"summary":"Inter-Exchange Volume","description":"The total amount of coins transferred between exchanges. Note that exchange metrics are based on our labeled data of exchange addresses that we constantly keep updating, as well as data science techniques and statistical information that changes over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\\n\\nThis is the Point-in-Time (PiT) variant of [Inter-Exchange Volume](https://studio.glassnode.com/metrics?a=BTC&m=transactions.TransfersVolumeBetweenExchangesSum). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/transactions.TransfersVolumeBetweenExchangesSumPit?a=BTC)\n","operationId":"transactions.TransfersVolumeBetweenExchangesSumPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id (see list below for more details)","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"c","in":"query","required":false,"description":"currency - NATIVE, USD","schema":{"type":"string"},"style":"form","explode":false},{"name":"from_exchange","in":"query","required":false,"description":"from_exchange name (see **/v1/metrics/transactions/transfers_volume_between_exchanges_sum_pit/flows** for a full list)","schema":{"type":"string"},"style":"form","explode":false},{"name":"to_exchange","in":"query","required":false,"description":"to_exchange name (see **/v1/metrics/transactions/transfers_volume_between_exchanges_sum_pit/flows** for a full list)","schema":{"type":"string"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Liquid and Illiquid Supply > The total supply held by illiquid, liquid, and highly liquid entities. The liquidity of an entity is defined as the ratio of cumulative outflows and cumulative inflows over the entity\'s lifespan. An entity is considered to be illiquid / liquid / highly liquid if its liquidity \*L\* is ≲ 0.25 / 0.25 ≲ \*L\* ≲ 0.75 / 0.75 ≲ L, respectively. For more information see our \[introductory article on Bitcoin liquidity]\( is the Point-in-Time (PiT) variant of \[Liquid and Illiquid 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/supply/liquid_illiquid_sum_pit":{"get":{"summary":"Liquid and Illiquid Supply","description":"The total supply held by illiquid, liquid, and highly liquid entities. The liquidity of an entity is defined as the ratio of cumulative outflows and cumulative inflows over the entity's lifespan. An entity is considered to be illiquid / liquid / highly liquid if its liquidity *L* is ≲ 0.25 / 0.25 ≲ *L* ≲ 0.75 / 0.75 ≲ L, respectively. For more information see our [introductory article on Bitcoin liquidity](http://insights.glassnode.com/bitcoin-liquid-supply).\\n\\nThis is the Point-in-Time (PiT) variant of [Liquid and Illiquid Supply](https://studio.glassnode.com/metrics?a=BTC&m=supply.LiquidIlliquidSum). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/supply.LiquidIlliquidSumPit?a=BTC)\n","operationId":"supply.LiquidIlliquidSumPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"c","in":"query","required":false,"description":"currency - NATIVE, USD","schema":{"type":"string"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Liquid Supply > The total supply held by \\"liquid\\" entities. The liquidity of an entity is defined as the ratio of cumulative outflows and cumulative inflows over the entity\'s lifespan. An entity is considered to be illiquid / liquid / highly liquid if its liquidity \*L\* is ≲ 0.25 / 0.25 ≲ \*L\* ≲ 0.75 / 0.75 ≲ L, respectively. For more information see our \[introductory article on Bitcoin liquidity]\( is the Point-in-Time (PiT) variant of \[Liquid 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/supply/liquid_sum_pit":{"get":{"summary":"Liquid Supply","description":"The total supply held by \\\"liquid\\\" entities. The liquidity of an entity is defined as the ratio of cumulative outflows and cumulative inflows over the entity's lifespan. An entity is considered to be illiquid / liquid / highly liquid if its liquidity *L* is ≲ 0.25 / 0.25 ≲ *L* ≲ 0.75 / 0.75 ≲ L, respectively. For more information see our [introductory article on Bitcoin liquidity](https://insights.glassnode.com/bitcoin-liquid-supply).\\n\\nThis is the Point-in-Time (PiT) variant of [Liquid Supply](https://studio.glassnode.com/metrics?a=BTC&m=supply.LiquidSum). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/supply.LiquidSumPit?a=BTC)\n","operationId":"supply.LiquidSumPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"c","in":"query","required":false,"description":"currency - NATIVE, USD","schema":{"type":"string"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Liquid Supply Change > The monthly (30d) net change of supply held by liquid and highly liquid entities. For more information see our \[introductory article on Bitcoin liquidity]\( is the Point-in-Time (PiT) variant of \[Liquid 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/supply/liquid_change_pit":{"get":{"summary":"Liquid Supply Change","description":"The monthly (30d) net change of supply held by liquid and highly liquid entities. For more information see our [introductory article on Bitcoin liquidity](http://insights.glassnode.com/bitcoin-liquid-supply).\\n\\nThis is the Point-in-Time (PiT) variant of [Liquid Supply Change](https://studio.glassnode.com/metrics?a=BTC&m=supply.LiquidChange). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/supply.LiquidChangePit?a=BTC)\n","operationId":"supply.LiquidChangePit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Long-Term Holder in Loss to Exchanges (Volume) > The total amount of coins transferred from \[long-term holders]\() in loss to exchange wallets. Only direct transfers are counted. 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- 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\nEntities 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. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see \[this article]\( that exchange metrics are based on our labeled data of exchange addresses that we constantly keep updating, as well as data science techniques and statistical information that changes over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\n\nThis is the Point-in-Time (PiT) variant of \[Long-Term Holder in Loss to Exchanges (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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/transactions/transfers_volume_lth_to_exchanges_loss_sum_pit":{"get":{"summary":"Long-Term Holder in Loss to Exchanges (Volume)","description":"The total amount of coins transferred from [long-term holders](https://insights.glassnode.com/quantifying-bitcoin-hodler-supply/) in loss to exchange wallets. Only direct transfers are counted. 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- and Short-Term Holder supply is defined with respect to the [entity's averaged purchasing date](https://insights.glassnode.com/quantifying-bitcoin-hodler-supply/) with weights given by a logistic function centered at an age of 155 days and a transition width of 10 days.\\n\\nEntities 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. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see [this article](https://insights.glassnode.com/true-bitcoin-volume/).\\n\\nNote that exchange metrics are based on our labeled data of exchange addresses that we constantly keep updating, as well as data science techniques and statistical information that changes over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\\n\\nThis is the Point-in-Time (PiT) variant of [Long-Term Holder in Loss to Exchanges (Volume)](https://studio.glassnode.com/metrics?a=BTC&m=transactions.TransfersVolumeLthToExchangesLossSum). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/transactions.TransfersVolumeLthToExchangesLossSumPit?a=BTC)\n","operationId":"transactions.TransfersVolumeLthToExchangesLossSumPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"c","in":"query","required":false,"description":"currency - NATIVE, USD","schema":{"type":"string"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Long-Term Holder in Profit to Exchanges (Volume) > The total amount of coins transferred from \[long-term holders]\() in profit to exchange wallets. Only direct transfers are counted. Coins are considered to be 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. 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.\n\nEntities 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. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see \[this article]\( that exchange metrics are based on our labeled data of exchange addresses that we constantly keep updating, as well as data science techniques and statistical information that changes over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\n\nThis is the Point-in-Time (PiT) variant of \[Long-Term Holder in Profit to Exchanges (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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/transactions/transfers_volume_lth_to_exchanges_profit_sum_pit":{"get":{"summary":"Long-Term Holder in Profit to Exchanges (Volume)","description":"The total amount of coins transferred from [long-term holders](https://insights.glassnode.com/quantifying-bitcoin-hodler-supply/) in profit to exchange wallets. Only direct transfers are counted. Coins are considered to be 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. Long- and Short-Term Holder supply is defined with respect to the [entity's averaged purchasing date](https://insights.glassnode.com/quantifying-bitcoin-hodler-supply/) with weights given by a logistic function centered at an age of 155 days and a transition width of 10 days.\\n\\nEntities 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. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see [this article](https://insights.glassnode.com/true-bitcoin-volume/).\\n\\nNote that exchange metrics are based on our labeled data of exchange addresses that we constantly keep updating, as well as data science techniques and statistical information that changes over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\\n\\nThis is the Point-in-Time (PiT) variant of [Long-Term Holder in Profit to Exchanges (Volume)](https://studio.glassnode.com/metrics?a=BTC&m=transactions.TransfersVolumeLthToExchangesProfitSum). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/transactions.TransfersVolumeLthToExchangesProfitSumPit?a=BTC)\n","operationId":"transactions.TransfersVolumeLthToExchangesProfitSumPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"c","in":"query","required":false,"description":"currency - NATIVE, USD","schema":{"type":"string"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Long-Term Holder Position Change > The monthly net position change of long term holders, i.e. the 30 day change in supply held by long term holders. 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.\n\nThis is the Point-in-Time (PiT) variant of \[Long-Term Holder Position 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/supply/lth_net_change_pit":{"get":{"summary":"Long-Term Holder Position Change","description":"The monthly net position change of long term holders, i.e. the 30 day change in supply held by long term holders. Long- and Short-Term Holder supply is defined with respect to the [entity's averaged purchasing date](https://insights.glassnode.com/quantifying-bitcoin-hodler-supply/) with weights given by a logistic function centered at an age of 155 days and a transition width of 10 days.\\n\\nThis is the Point-in-Time (PiT) variant of [Long-Term Holder Position Change](https://studio.glassnode.com/metrics?a=BTC&m=supply.LthNetChange). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/supply.LthNetChangePit?a=BTC)\n","operationId":"supply.LthNetChangePit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Long-Term Holder Supply > The total amount of circulating supply held by long term holders. 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.\n\nThis is the Point-in-Time (PiT) variant of \[Long-Term Holder 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/supply/lth_sum_pit":{"get":{"summary":"Long-Term Holder Supply","description":"The total amount of circulating supply held by long term holders. Long- and Short-Term Holder supply is defined with respect to the [entity's averaged purchasing date](https://insights.glassnode.com/quantifying-bitcoin-hodler-supply/) with weights given by a logistic function centered at an age of 155 days and a transition width of 10 days.\\n\\nThis is the Point-in-Time (PiT) variant of [Long-Term Holder Supply](https://studio.glassnode.com/metrics?a=BTC&m=supply.LthSum). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/supply.LthSumPit?a=BTC)\n","operationId":"supply.LthSumPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"c","in":"query","required":false,"description":"currency - NATIVE, USD","schema":{"type":"string"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Long-Term Holder Supply in Loss > The total amount of circulating supply that is currently at loss and held by long term holders. 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.\n\nThis is the Point-in-Time (PiT) variant of \[Long-Term Holder Supply 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/supply/lth_loss_sum_pit":{"get":{"summary":"Long-Term Holder Supply in Loss","description":"The total amount of circulating supply that is currently at loss and held by long term holders. Long- and Short-Term Holder supply is defined with respect to the [entity's averaged purchasing date](https://insights.glassnode.com/quantifying-bitcoin-hodler-supply/) with weights given by a logistic function centered at an age of 155 days and a transition width of 10 days.\\n\\nThis is the Point-in-Time (PiT) variant of [Long-Term Holder Supply in Loss](https://studio.glassnode.com/metrics?a=BTC&m=supply.LthLossSum). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/supply.LthLossSumPit?a=BTC)\n","operationId":"supply.LthLossSumPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"c","in":"query","required":false,"description":"currency - NATIVE, USD","schema":{"type":"string"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Long-Term Holder Supply in Profit > The total amount of circulating supply that is currently in profit and held by long term holders. 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.\n\nThis is the Point-in-Time (PiT) variant of \[Long-Term Holder Supply 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/supply/lth_profit_sum_pit":{"get":{"summary":"Long-Term Holder Supply in Profit","description":"The total amount of circulating supply that is currently in profit and held by long term holders. Long- and Short-Term Holder supply is defined with respect to the [entity's averaged purchasing date](https://insights.glassnode.com/quantifying-bitcoin-hodler-supply/) with weights given by a logistic function centered at an age of 155 days and a transition width of 10 days.\\n\\nThis is the Point-in-Time (PiT) variant of [Long-Term Holder Supply in Profit](https://studio.glassnode.com/metrics?a=BTC&m=supply.LthProfitSum). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/supply.LthProfitSumPit?a=BTC)\n","operationId":"supply.LthProfitSumPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"c","in":"query","required":false,"description":"currency - NATIVE, USD","schema":{"type":"string"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Long-Term Holder to Exchanges (Volume) > The total amount of coins transferred from \[long-term holders]\() to exchange wallets. Only direct transfers are counted. 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.\n\nEntities 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. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see \[this article]\( that exchange metrics are based on our labeled data of exchange addresses that we constantly keep updating, as well as data science techniques and statistical information that changes over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\n\nThis is the Point-in-Time (PiT) variant of \[Long-Term Holder to Exchanges (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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/transactions/transfers_volume_lth_to_exchanges_sum_pit":{"get":{"summary":"Long-Term Holder to Exchanges (Volume)","description":"The total amount of coins transferred from [long-term holders](https://insights.glassnode.com/quantifying-bitcoin-hodler-supply/) to exchange wallets. Only direct transfers are counted. Long- and Short-Term Holder supply is defined with respect to the [entity's averaged purchasing date](https://insights.glassnode.com/quantifying-bitcoin-hodler-supply/) with weights given by a logistic function centered at an age of 155 days and a transition width of 10 days.\\n\\nEntities 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. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see [this article](https://insights.glassnode.com/true-bitcoin-volume/).\\n\\nNote that exchange metrics are based on our labeled data of exchange addresses that we constantly keep updating, as well as data science techniques and statistical information that changes over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\\n\\nThis is the Point-in-Time (PiT) variant of [Long-Term Holder to Exchanges (Volume)](https://studio.glassnode.com/metrics?a=BTC&m=transactions.TransfersVolumeLthToExchangesSum). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/transactions.TransfersVolumeLthToExchangesSumPit?a=BTC)\n","operationId":"transactions.TransfersVolumeLthToExchangesSumPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"c","in":"query","required":false,"description":"currency - NATIVE, USD","schema":{"type":"string"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## LTH/STH Transfer Volume in Profit/Loss to Exchanges > The relative amount of coins moved by by \[long- and short-term holders]\() in profit/loss to exchanges. Only direct transfers are counted. Coins are considered to be in profit/loss when the price at the time the coins are spent is higher/lower than the entity\'s average on-chain acquisition price for its funds. 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.\n\nEntities 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. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see \[this article]\( that exchange metrics are based on our labeled data of exchange addresses that we constantly keep updating, as well as data science techniques and statistical information that changes over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\n\nThis is the Point-in-Time (PiT) variant of \[LTH/STH Transfer Volume in Profit/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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/transactions/transfers_volume_lth_sth_to_exchanges_profit_loss_relative_pit":{"get":{"summary":"LTH/STH Transfer Volume in Profit/Loss to Exchanges","description":"The relative amount of coins moved by by [long- and short-term holders](https://insights.glassnode.com/quantifying-bitcoin-hodler-supply/) in profit/loss to exchanges. Only direct transfers are counted. Coins are considered to be in profit/loss when the price at the time the coins are spent is higher/lower than the entity's average on-chain acquisition price for its funds. Long- and Short-Term Holder supply is defined with respect to the [entity's averaged purchasing date](https://insights.glassnode.com/quantifying-bitcoin-hodler-supply/) with weights given by a logistic function centered at an age of 155 days and a transition width of 10 days.\\n\\nEntities 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. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see [this article](https://insights.glassnode.com/true-bitcoin-volume/).\\n\\nNote that exchange metrics are based on our labeled data of exchange addresses that we constantly keep updating, as well as data science techniques and statistical information that changes over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\\n\\nThis is the Point-in-Time (PiT) variant of [LTH/STH Transfer Volume in Profit/Loss to Exchanges](https://studio.glassnode.com/metrics?a=BTC&m=transactions.TransfersVolumeLthSthToExchangesProfitLossRelative). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/transactions.TransfersVolumeLthSthToExchangesProfitLossRelativePit?a=BTC)\n","operationId":"transactions.TransfersVolumeLthSthToExchangesProfitLossRelativePit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Miner Balance > The total supply held in miner addresses.\n\nThis is the Point-in-Time (PiT) variant of \[Miner 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/distribution/balance_miners_sum_pit":{"get":{"summary":"Miner Balance","description":"The total supply held in miner addresses.\\n\\nThis is the Point-in-Time (PiT) variant of [Miner Balance](https://studio.glassnode.com/metrics?a=BTC&m=distribution.BalanceMinersSum). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/distribution.BalanceMinersSumPit?a=BTC)\n","operationId":"distribution.BalanceMinersSumPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"c","in":"query","required":false,"description":"currency - NATIVE, USD","schema":{"type":"string"},"style":"form","explode":false},{"name":"miner","in":"query","required":true,"description":"miner name (see **/v1/metrics/distribution/balance_miners_sum_pit/miners** for a full list)","schema":{"type":"string"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Miner Balance (Stacked) > The total supply held in miner addresses.\n\nThis is the Point-in-Time (PiT) variant of \[Miner Balance (Stacked)]\(). 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/distribution/balance_miners_all_pit":{"get":{"summary":"Miner Balance (Stacked)","description":"The total supply held in miner addresses.\\n\\nThis is the Point-in-Time (PiT) variant of [Miner Balance (Stacked)](https://studio.glassnode.com/metrics?a=BTC&m=distribution.BalanceMinersAll). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/distribution.BalanceMinersAllPit?a=BTC)\n","operationId":"distribution.BalanceMinersAllPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"c","in":"query","required":false,"description":"currency - NATIVE, USD","schema":{"type":"string"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Miner Incoming Transfers > The total number of transfers in which the receiver is a miners\' address.\n\nThis is the Point-in-Time (PiT) variant of \[Miner Incoming Transfers]\(). 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/transactions/transfers_to_miners_count_pit":{"get":{"summary":"Miner Incoming Transfers","description":"The total number of transfers in which the receiver is a miners' address.\\n\\nThis is the Point-in-Time (PiT) variant of [Miner Incoming Transfers](https://studio.glassnode.com/metrics?a=BTC&m=transactions.TransfersToMinersCount). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/transactions.TransfersToMinersCountPit?a=BTC)\n","operationId":"transactions.TransfersToMinersCountPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"miner","in":"query","required":true,"description":"miner name (see **/v1/metrics/transactions/transfers_to_miners_count_pit/miners** for a full list)","schema":{"type":"string"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Miner Inflow Volume > The total amount of coins transferred to miner addresses.\n\nThis is the Point-in-Time (PiT) variant of \[Miner Inflow 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/transactions/transfers_volume_to_miners_sum_pit":{"get":{"summary":"Miner Inflow Volume","description":"The total amount of coins transferred to miner addresses.\\n\\nThis is the Point-in-Time (PiT) variant of [Miner Inflow Volume](https://studio.glassnode.com/metrics?a=BTC&m=transactions.TransfersVolumeToMinersSum). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/transactions.TransfersVolumeToMinersSumPit?a=BTC)\n","operationId":"transactions.TransfersVolumeToMinersSumPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"c","in":"query","required":false,"description":"currency - NATIVE, USD","schema":{"type":"string"},"style":"form","explode":false},{"name":"miner","in":"query","required":true,"description":"miner name (see **/v1/metrics/transactions/transfers_volume_to_miners_sum_pit/miners** for a full list)","schema":{"type":"string"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Miner Net Position Change > The 30d change of the supply held in miner addresses.\n\nThis is the Point-in-Time (PiT) variant of \[Miner Net Position 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/distribution/balance_miners_change_pit":{"get":{"summary":"Miner Net Position Change","description":"The 30d change of the supply held in miner addresses.\\n\\nThis is the Point-in-Time (PiT) variant of [Miner Net Position Change](https://studio.glassnode.com/metrics?a=BTC&m=distribution.BalanceMinersChange). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/distribution.BalanceMinersChangePit?a=BTC)\n","operationId":"distribution.BalanceMinersChangePit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"c","in":"query","required":false,"description":"currency - NATIVE, USD","schema":{"type":"string"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Miner Netflow Volume > The difference between miner\'s inflow and outflow, i.e the net flow of coins into/out of miner addresses.\n\nThis is the Point-in-Time (PiT) variant of \[Miner Netflow 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/transactions/transfers_volume_miners_net_pit":{"get":{"summary":"Miner Netflow Volume","description":"The difference between miner's inflow and outflow, i.e the net flow of coins into/out of miner addresses.\\n\\nThis is the Point-in-Time (PiT) variant of [Miner Netflow Volume](https://studio.glassnode.com/metrics?a=BTC&m=transactions.TransfersVolumeMinersNet). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/transactions.TransfersVolumeMinersNetPit?a=BTC)\n","operationId":"transactions.TransfersVolumeMinersNetPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"c","in":"query","required":false,"description":"currency - NATIVE, USD","schema":{"type":"string"},"style":"form","explode":false},{"name":"miner","in":"query","required":true,"description":"miner name (see **/v1/metrics/transactions/transfers_volume_miners_net_pit/miners** for a full list)","schema":{"type":"string"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Miner Outflow Volume > The total amount of coins transferred from miner addresses.\n\nThis is the Point-in-Time (PiT) variant of \[Miner Outflow 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/transactions/transfers_volume_from_miners_sum_pit":{"get":{"summary":"Miner Outflow Volume","description":"The total amount of coins transferred from miner addresses.\\n\\nThis is the Point-in-Time (PiT) variant of [Miner Outflow Volume](https://studio.glassnode.com/metrics?a=BTC&m=transactions.TransfersVolumeFromMinersSum). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/transactions.TransfersVolumeFromMinersSumPit?a=BTC)\n","operationId":"transactions.TransfersVolumeFromMinersSumPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"c","in":"query","required":false,"description":"currency - NATIVE, USD","schema":{"type":"string"},"style":"form","explode":false},{"name":"miner","in":"query","required":true,"description":"miner name (see **/v1/metrics/transactions/transfers_volume_from_miners_sum_pit/miners** for a full list)","schema":{"type":"string"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Miner Outgoing Transfers > The total number of transfers in which the sender is a miners\' address.\n\nThis is the Point-in-Time (PiT) variant of \[Miner Outgoing Transfers]\(). 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/transactions/transfers_from_miners_count_pit":{"get":{"summary":"Miner Outgoing Transfers","description":"The total number of transfers in which the sender is a miners' address.\\n\\nThis is the Point-in-Time (PiT) variant of [Miner Outgoing Transfers](https://studio.glassnode.com/metrics?a=BTC&m=transactions.TransfersFromMinersCount). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/transactions.TransfersFromMinersCountPit?a=BTC)\n","operationId":"transactions.TransfersFromMinersCountPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"miner","in":"query","required":true,"description":"miner name (see **/v1/metrics/transactions/transfers_from_miners_count_pit/miners** for a full list)","schema":{"type":"string"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Miner Revenue (Block Rewards) > The total amount of newly minted coins, i.e. block rewards.\n\nThis is the Point-in-Time (PiT) variant of \[Miner Revenue (Block Rewards)]\(). 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/mining/volume_mined_sum_pit":{"get":{"summary":"Miner Revenue (Block Rewards)","description":"The total amount of newly minted coins, i.e. block rewards.\\n\\nThis is the Point-in-Time (PiT) variant of [Miner Revenue (Block Rewards)](https://studio.glassnode.com/metrics?a=BTC&m=mining.VolumeMinedSum). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/mining.VolumeMinedSumPit?a=BTC)\n","operationId":"mining.VolumeMinedSumPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"c","in":"query","required":false,"description":"currency - NATIVE, USD","schema":{"type":"string"},"style":"form","explode":false},{"name":"miner","in":"query","required":true,"description":"miner name (see **/v1/metrics/mining/volume_mined_sum_pit/miners** for a full list)","schema":{"type":"string"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Miner Revenue (Total) > The total miner revenue, i.e. fees plus newly minted coins.\n\nThis is the Point-in-Time (PiT) variant of \[Miner Revenue (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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/mining/revenue_sum_pit":{"get":{"summary":"Miner Revenue (Total)","description":"The total miner revenue, i.e. fees plus newly minted coins.\\n\\nThis is the Point-in-Time (PiT) variant of [Miner Revenue (Total)](https://studio.glassnode.com/metrics?a=BTC&m=mining.RevenueSum). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/mining.RevenueSumPit?a=BTC)\n","operationId":"mining.RevenueSumPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"c","in":"query","required":false,"description":"currency - NATIVE, USD","schema":{"type":"string"},"style":"form","explode":false},{"name":"miner","in":"query","required":true,"description":"miner name (see **/v1/metrics/mining/revenue_sum_pit/miners** for a full list)","schema":{"type":"string"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Miners to Exchanges > The total amount of coins transferred from miners to exchange wallets. Only direct transfers are counted. Note that exchange metrics are based on our labeled data of exchange addresses that we constantly keep updating, as well as data science techniques and statistical information that changes over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\n\nThis is the Point-in-Time (PiT) variant of \[Miners 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/transactions/transfers_volume_miners_to_exchanges_pit":{"get":{"summary":"Miners to Exchanges","description":"The total amount of coins transferred from miners to exchange wallets. Only direct transfers are counted. Note that exchange metrics are based on our labeled data of exchange addresses that we constantly keep updating, as well as data science techniques and statistical information that changes over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\\n\\nThis is the Point-in-Time (PiT) variant of [Miners to Exchanges](https://studio.glassnode.com/metrics?a=BTC&m=transactions.TransfersVolumeMinersToExchanges). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/transactions.TransfersVolumeMinersToExchangesPit?a=BTC)\n","operationId":"transactions.TransfersVolumeMinersToExchangesPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"c","in":"query","required":false,"description":"currency - NATIVE, USD","schema":{"type":"string"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Miners to Exchanges (Stacked) > The total amount of coins transferred from miners to exchange wallets. Only direct transfers are counted. Note that exchange metrics are based on our labeled data of exchange addresses that we constantly keep updating, as well as data science techniques and statistical information that changes over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\n\nThis is the Point-in-Time (PiT) variant of \[Miners to Exchanges (Stacked)]\(). 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/transactions/transfers_volume_miners_to_exchanges_all_pit":{"get":{"summary":"Miners to Exchanges (Stacked)","description":"The total amount of coins transferred from miners to exchange wallets. Only direct transfers are counted. Note that exchange metrics are based on our labeled data of exchange addresses that we constantly keep updating, as well as data science techniques and statistical information that changes over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\\n\\nThis is the Point-in-Time (PiT) variant of [Miners to Exchanges (Stacked)](https://studio.glassnode.com/metrics?a=BTC&m=transactions.TransfersVolumeMinersToExchangesAll). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/transactions.TransfersVolumeMinersToExchangesAllPit?a=BTC)\n","operationId":"transactions.TransfersVolumeMinersToExchangesAllPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"c","in":"query","required":false,"description":"currency - NATIVE, USD","schema":{"type":"string"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Mt. Gox Balance > The Mt. Gox Trustee Balance corresponds to the amount of BTC held in addresses controlled by Nobuaki Kobayashi, the trustee overseeing the Mt. Gox civil rehabilitation proceedings.\n\nThis is the Point-in-Time (PiT) variant of \[Mt. Gox 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/distribution/balance_mtgox_trustee_pit":{"get":{"summary":"Mt. Gox Balance","description":"The Mt. Gox Trustee Balance corresponds to the amount of BTC held in addresses controlled by Nobuaki Kobayashi, the trustee overseeing the Mt. Gox civil rehabilitation proceedings.\\n\\nThis is the Point-in-Time (PiT) variant of [Mt. Gox Balance](https://studio.glassnode.com/metrics?a=BTC&m=distribution.BalanceMtgoxTrustee). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/distribution.BalanceMtgoxTrusteePit?a=BTC)\n","operationId":"distribution.BalanceMtgoxTrusteePit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"c","in":"query","required":false,"description":"currency - NATIVE, USD","schema":{"type":"string"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## New Entities > The number of unique entities that appeared for the first time in a transaction of the native coin in the network. 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. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see \[this article]\( computation of this metric requires statistical information from several days, and is therefore only available with a lag of one week.\*\*\n\nThis is the Point-in-Time (PiT) variant of \[New 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/entities/new_count_pit":{"get":{"summary":"New Entities","description":"The number of unique entities that appeared for the first time in a transaction of the native coin in the network. 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. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see [this article](https://insights.glassnode.com/bitcoin_holders/).\\n\\n**The computation of this metric requires statistical information from several days, and is therefore only available with a lag of one week.**\\n\\nThis is the Point-in-Time (PiT) variant of [New Entities](https://studio.glassnode.com/metrics?a=BTC&m=entities.NewCount). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/entities.NewCountPit?a=BTC)\n","operationId":"entities.NewCountPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## NFTs Transactions (Absolute) > The number of transactions (transaction count) in the Ethereum network by transactions interacting with non-fungible tokens. This category includes of both token contract standards (ERC721, ERC1155), as well as NFT marketplaces (OpenSea, Blur, LooksRare, Rarible, SuperRare) for trading those.\n\nThis is the Point-in-Time (PiT) variant of \[NFTs 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/transactions/transfers_count_nfts_pit":{"get":{"summary":"NFTs Transactions (Absolute)","description":"The number of transactions (transaction count) in the Ethereum network by transactions interacting with non-fungible tokens. This category includes of both token contract standards (ERC721, ERC1155), as well as NFT marketplaces (OpenSea, Blur, LooksRare, Rarible, SuperRare) for trading those.\\n\\nThis is the Point-in-Time (PiT) variant of [NFTs Transactions (Absolute)](https://studio.glassnode.com/metrics?a=BTC&m=transactions.TransfersCountNfts). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/transactions.TransfersCountNftsPit?a=ETH)\n","operationId":"transactions.TransfersCountNftsPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - ETH","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## NFTs Transactions (Relative) > The relative amount (share) of transactions in the Ethereum network by transactions interacting with non-fungible tokens. This category includes of both token contract standards (ERC721, ERC1155), as well as NFT marketplaces (OpenSea, Blur, LooksRare, Rarible, SuperRare) for trading those.\n\nThis is the Point-in-Time (PiT) variant of \[NFTs 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/transactions/transfers_count_nfts_relative_pit":{"get":{"summary":"NFTs Transactions (Relative)","description":"The relative amount (share) of transactions in the Ethereum network by transactions interacting with non-fungible tokens. This category includes of both token contract standards (ERC721, ERC1155), as well as NFT marketplaces (OpenSea, Blur, LooksRare, Rarible, SuperRare) for trading those.\\n\\nThis is the Point-in-Time (PiT) variant of [NFTs Transactions (Relative)](https://studio.glassnode.com/metrics?a=BTC&m=transactions.TransfersCountNftsRelative). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/transactions.TransfersCountNftsRelativePit?a=ETH)\n","operationId":"transactions.TransfersCountNftsRelativePit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - ETH","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Number of Whales > The number of unique entities holding at least 1k coins.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. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see \[this article]\( is the Point-in-Time (PiT) variant of \[Number of Whales]\(). 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/entities/min_1k_count_pit":{"get":{"summary":"Number of Whales","description":"The number of unique entities holding at least 1k coins.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. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see [this article](https://insights.glassnode.com/bitcoin_holders/).\\n\\nThis is the Point-in-Time (PiT) variant of [Number of Whales](https://studio.glassnode.com/metrics?a=BTC&m=entities.Min1KCount). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/entities.Min1KCountPit?a=BTC)\n","operationId":"entities.Min1KCountPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## OTC Desks Holdings > The total amount of coins held on OTC desk addresses. This data is based on three different OTC desks. Note that OTC metrics are based on our labeled data that we constantly keep updating, as well as data science techniques and statistical information that changes over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\n\nThis is the Point-in-Time (PiT) variant of \[OTC Desks Holdings]\(). 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/distribution/balance_otc_desks_pit":{"get":{"summary":"OTC Desks Holdings","description":"The total amount of coins held on OTC desk addresses. This data is based on three different OTC desks. Note that OTC metrics are based on our labeled data that we constantly keep updating, as well as data science techniques and statistical information that changes over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\\n\\nThis is the Point-in-Time (PiT) variant of [OTC Desks Holdings](https://studio.glassnode.com/metrics?a=BTC&m=distribution.BalanceOtcDesks). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/distribution.BalanceOtcDesksPit?a=BTC)\n","operationId":"distribution.BalanceOtcDesksPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"c","in":"query","required":false,"description":"currency - NATIVE, USD","schema":{"type":"string"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## OTC Desks Incoming Transactions > The total count of transfers to OTC desk addresses. This data is based on three different OTC desks. Note that OTC metrics are based on our labeled data that we constantly keep updating, as well as data science techniques and statistical information that changes over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\n\nThis is the Point-in-Time (PiT) variant of \[OTC Desks Incoming Transactions]\(). 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/transactions/transfers_to_otc_desks_count_pit":{"get":{"summary":"OTC Desks Incoming Transactions","description":"The total count of transfers to OTC desk addresses. This data is based on three different OTC desks. Note that OTC metrics are based on our labeled data that we constantly keep updating, as well as data science techniques and statistical information that changes over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\\n\\nThis is the Point-in-Time (PiT) variant of [OTC Desks Incoming Transactions](https://studio.glassnode.com/metrics?a=BTC&m=transactions.TransfersToOtcDesksCount). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/transactions.TransfersToOtcDesksCountPit?a=BTC)\n","operationId":"transactions.TransfersToOtcDesksCountPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## OTC Desks Inflows > The total amount of coins transferred to OTC desk addresses. This data is based on three different OTC desks. Note that OTC metrics are based on our labeled data that we constantly keep updating, as well as data science techniques and statistical information that changes over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\n\nThis is the Point-in-Time (PiT) variant of \[OTC Desks Inflows]\(). 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/transactions/transfers_volume_to_otc_desks_sum_pit":{"get":{"summary":"OTC Desks Inflows","description":"The total amount of coins transferred to OTC desk addresses. This data is based on three different OTC desks. Note that OTC metrics are based on our labeled data that we constantly keep updating, as well as data science techniques and statistical information that changes over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\\n\\nThis is the Point-in-Time (PiT) variant of [OTC Desks Inflows](https://studio.glassnode.com/metrics?a=BTC&m=transactions.TransfersVolumeToOtcDesksSum). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/transactions.TransfersVolumeToOtcDesksSumPit?a=BTC)\n","operationId":"transactions.TransfersVolumeToOtcDesksSumPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"c","in":"query","required":false,"description":"currency - NATIVE, USD","schema":{"type":"string"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## OTC Desks Outflows > The total amount of coins transferred from OTC desk addresses. This data is based on three different OTC desks. Note that OTC metrics are based on our labeled data that we constantly keep updating, as well as data science techniques and statistical information that changes over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\n\nThis is the Point-in-Time (PiT) variant of \[OTC Desks Outflows]\(). 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/transactions/transfers_volume_from_otc_desks_sum_pit":{"get":{"summary":"OTC Desks Outflows","description":"The total amount of coins transferred from OTC desk addresses. This data is based on three different OTC desks. Note that OTC metrics are based on our labeled data that we constantly keep updating, as well as data science techniques and statistical information that changes over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\\n\\nThis is the Point-in-Time (PiT) variant of [OTC Desks Outflows](https://studio.glassnode.com/metrics?a=BTC&m=transactions.TransfersVolumeFromOtcDesksSum). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/transactions.TransfersVolumeFromOtcDesksSumPit?a=BTC)\n","operationId":"transactions.TransfersVolumeFromOtcDesksSumPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"c","in":"query","required":false,"description":"currency - NATIVE, USD","schema":{"type":"string"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## OTC Desks Outgoing Transactions > The total count of transfers from OTC desk addresses. This data is based on three different OTC desks. Note that OTC metrics are based on our labeled data that we constantly keep updating, as well as data science techniques and statistical information that changes over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\n\nThis is the Point-in-Time (PiT) variant of \[OTC Desks Outgoing Transactions]\(). 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/transactions/transfers_from_otc_desks_count_pit":{"get":{"summary":"OTC Desks Outgoing Transactions","description":"The total count of transfers from OTC desk addresses. This data is based on three different OTC desks. Note that OTC metrics are based on our labeled data that we constantly keep updating, as well as data science techniques and statistical information that changes over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\\n\\nThis is the Point-in-Time (PiT) variant of [OTC Desks Outgoing Transactions](https://studio.glassnode.com/metrics?a=BTC&m=transactions.TransfersFromOtcDesksCount). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/transactions.TransfersFromOtcDesksCountPit?a=BTC)\n","operationId":"transactions.TransfersFromOtcDesksCountPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Percent Entities in Profit > The percentage of entities in the network that are currently in profit, e.g. the entities whose funds where on average bought at prices lower than the current price. \\"Buy price\\" is here defined as the price at the time coins were transferred into addresses controlled by the entity. 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. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information this \[article]\( is the Point-in-Time (PiT) variant of \[Percent Entities 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/entities/profit_relative_pit":{"get":{"summary":"Percent Entities in Profit","description":"The percentage of entities in the network that are currently in profit, e.g. the entities whose funds where on average bought at prices lower than the current price. \\\"Buy price\\\" is here defined as the price at the time coins were transferred into addresses controlled by the entity. 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. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information this [article](https://insights.glassnode.com/bitcoin_holders/).\\n\\nThis is the Point-in-Time (PiT) variant of [Percent Entities in Profit](https://studio.glassnode.com/metrics?a=BTC&m=entities.ProfitRelative). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/entities.ProfitRelativePit?a=BTC)\n","operationId":"entities.ProfitRelativePit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Receiving Entities > The number of unique entities that were active as a 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. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see \[this article]\( is the Point-in-Time (PiT) variant of \[Receiving 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/entities/receiving_count_pit":{"get":{"summary":"Receiving Entities","description":"The number of unique entities that were active as a 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. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see [this article](https://insights.glassnode.com/bitcoin_holders/).\\n\\nThis is the Point-in-Time (PiT) variant of [Receiving Entities](https://studio.glassnode.com/metrics?a=BTC&m=entities.ReceivingCount). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/entities.ReceivingCountPit?a=BTC)\n","operationId":"entities.ReceivingCountPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Relative Long/Short-Term Holder Supply > The relative amount of circulating supply of held by long- and short-term holders in profit/loss. 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.\n\nThis is the Point-in-Time (PiT) variant of \[Relative Long/Short-Term Holder 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/supply/lth_sth_profit_loss_relative_pit":{"get":{"summary":"Relative Long/Short-Term Holder Supply","description":"The relative amount of circulating supply of held by long- and short-term holders in profit/loss. Long- and Short-Term Holder supply is defined with respect to the [entity's averaged purchasing date](https://insights.glassnode.com/quantifying-bitcoin-hodler-supply/) with weights given by a logistic function centered at an age of 155 days and a transition width of 10 days.\\n\\nThis is the Point-in-Time (PiT) variant of [Relative Long/Short-Term Holder Supply](https://studio.glassnode.com/metrics?a=BTC&m=supply.LthSthProfitLossRelative). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/supply.LthSthProfitLossRelativePit?a=BTC)\n","operationId":"supply.LthSthProfitLossRelativePit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Relative LTH/STH Realized Profit/Loss > Relative distribution of the total profit and loss (USD value) of all coins moved by \[long- and short-term holders]\(). 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.\n\nVolume transferred between addresses owned by the same entity cluster is excluded. As such, no value is realized during internal or “in-house” transfers.\n\nEntities 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. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see \[this article]\( is the Point-in-Time (PiT) variant of \[Relative LTH/STH Realized 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/indicators/realized_profit_loss_lth_sth_relative_pit":{"get":{"summary":"Relative LTH/STH Realized Profit/Loss","description":"Relative distribution of the total profit and loss (USD value) of all coins moved by [long- and short-term holders](https://insights.glassnode.com/quantifying-bitcoin-hodler-supply/). Long- and Short-Term Holder supply is defined with respect to the [entity's averaged purchasing date](https://insights.glassnode.com/quantifying-bitcoin-hodler-supply/) with weights given by a logistic function centered at an age of 155 days and a transition width of 10 days.\\n\\nVolume transferred between addresses owned by the same entity cluster is excluded. As such, no value is realized during internal or “in-house” transfers.\\n\\nEntities 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. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see [this article](https://insights.glassnode.com/true-bitcoin-volume).\\n\\nThis is the Point-in-Time (PiT) variant of [Relative LTH/STH Realized Profit/Loss](https://studio.glassnode.com/metrics?a=BTC&m=indicators.RealizedProfitLossLthSthRelative). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/indicators.RealizedProfitLossLthSthRelativePit?a=BTC)\n","operationId":"indicators.RealizedProfitLossLthSthRelativePit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Relative LTH/STH Realized Profit/Loss to Exchanges > Relative distribution of the total profit and loss (USD value) of all coins moved by \[long- and short-term holders]\() to exchanges. Realized profit/loss denotes the total profit/loss (in USD) of all moved coins whose price at their last movement was lower/higher than the price at the current movement. 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.\n\nEntities 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. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see \[this article]\( that exchange metrics are based on our labeled data of exchange addresses that we constantly keep updating, as well as data science techniques and statistical information that changes over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\n\nThis is the Point-in-Time (PiT) variant of \[Relative LTH/STH Realized Profit/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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/indicators/realized_profit_loss_lth_sth_to_exchanges_relative_pit":{"get":{"summary":"Relative LTH/STH Realized Profit/Loss to Exchanges","description":"Relative distribution of the total profit and loss (USD value) of all coins moved by [long- and short-term holders](https://insights.glassnode.com/quantifying-bitcoin-hodler-supply/) to exchanges. Realized profit/loss denotes the total profit/loss (in USD) of all moved coins whose price at their last movement was lower/higher than the price at the current movement. Long- and Short-Term Holder supply is defined with respect to the [entity's averaged purchasing date](https://insights.glassnode.com/quantifying-bitcoin-hodler-supply/) with weights given by a logistic function centered at an age of 155 days and a transition width of 10 days.\\n\\nEntities 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. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see [this article](https://insights.glassnode.com/true-bitcoin-volume).\\n\\nNote that exchange metrics are based on our labeled data of exchange addresses that we constantly keep updating, as well as data science techniques and statistical information that changes over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\\n\\nThis is the Point-in-Time (PiT) variant of [Relative LTH/STH Realized Profit/Loss to Exchanges](https://studio.glassnode.com/metrics?a=BTC&m=indicators.RealizedProfitLossLthSthToExchangesRelative). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/indicators.RealizedProfitLossLthSthToExchangesRelativePit?a=BTC)\n","operationId":"indicators.RealizedProfitLossLthSthToExchangesRelativePit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Relative Transfer Volume by Size (Entity-Adjusted) > Entity-adjusted relative on-chain volume breakdown by the USD value of the transfers.\n\nThis is the Point-in-Time (PiT) variant of \[Relative Transfer Volume by Size (Entity-Adjusted)]\(). 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/transactions/transfers_volume_by_size_entity_adjusted_relative_pit":{"get":{"summary":"Relative Transfer Volume by Size (Entity-Adjusted)","description":"Entity-adjusted relative on-chain volume breakdown by the USD value of the transfers.\\n\\nThis is the Point-in-Time (PiT) variant of [Relative Transfer Volume by Size (Entity-Adjusted)](https://studio.glassnode.com/metrics?a=BTC&m=transactions.TransfersVolumeBySizeEntityAdjustedRelative). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/transactions.TransfersVolumeBySizeEntityAdjustedRelativePit?a=BTC)\n","operationId":"transactions.TransfersVolumeBySizeEntityAdjustedRelativePit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Sending Entities > The number of unique entities that were active as a sender. 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. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see \[this article]\( is the Point-in-Time (PiT) variant of \[Sending 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/entities/sending_count_pit":{"get":{"summary":"Sending Entities","description":"The number of unique entities that were active as a sender. 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. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see [this article](https://insights.glassnode.com/bitcoin_holders/).\\n\\nThis is the Point-in-Time (PiT) variant of [Sending Entities](https://studio.glassnode.com/metrics?a=BTC&m=entities.SendingCount). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/entities.SendingCountPit?a=BTC)\n","operationId":"entities.SendingCountPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Short-Term Holder in Loss to Exchanges (Volume) > The total amount of coins transferred from \[short-term holders]\() in loss to exchange wallets. Only direct transfers are counted. 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- 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\nEntities 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. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see \[this article]\( that exchange metrics are based on our labeled data of exchange addresses that we constantly keep updating, as well as data science techniques and statistical information that changes over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\n\nThis is the Point-in-Time (PiT) variant of \[Short-Term Holder in Loss to Exchanges (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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/transactions/transfers_volume_sth_to_exchanges_loss_sum_pit":{"get":{"summary":"Short-Term Holder in Loss to Exchanges (Volume)","description":"The total amount of coins transferred from [short-term holders](https://insights.glassnode.com/quantifying-bitcoin-hodler-supply/) in loss to exchange wallets. Only direct transfers are counted. 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- and Short-Term Holder supply is defined with respect to the [entity's averaged purchasing date](https://insights.glassnode.com/quantifying-bitcoin-hodler-supply/) with weights given by a logistic function centered at an age of 155 days and a transition width of 10 days.\\n\\nEntities 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. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see [this article](https://insights.glassnode.com/true-bitcoin-volume/).\\n\\nNote that exchange metrics are based on our labeled data of exchange addresses that we constantly keep updating, as well as data science techniques and statistical information that changes over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\\n\\nThis is the Point-in-Time (PiT) variant of [Short-Term Holder in Loss to Exchanges (Volume)](https://studio.glassnode.com/metrics?a=BTC&m=transactions.TransfersVolumeSthToExchangesLossSum). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/transactions.TransfersVolumeSthToExchangesLossSumPit?a=BTC)\n","operationId":"transactions.TransfersVolumeSthToExchangesLossSumPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"c","in":"query","required":false,"description":"currency - NATIVE, USD","schema":{"type":"string"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Short-Term Holder in Profit to Exchanges (Volume) > The total amount of coins transferred from \[short-term holders]\() in profit to exchange wallets. Only direct transfers are counted. Coins are considered to be 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. 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.\n\nEntities 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. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see \[this article]\( that exchange metrics are based on our labeled data of exchange addresses that we constantly keep updating, as well as data science techniques and statistical information that changes over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\n\nThis is the Point-in-Time (PiT) variant of \[Short-Term Holder in Profit to Exchanges (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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/transactions/transfers_volume_sth_to_exchanges_profit_sum_pit":{"get":{"summary":"Short-Term Holder in Profit to Exchanges (Volume)","description":"The total amount of coins transferred from [short-term holders](https://insights.glassnode.com/quantifying-bitcoin-hodler-supply/) in profit to exchange wallets. Only direct transfers are counted. Coins are considered to be 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. Long- and Short-Term Holder supply is defined with respect to the [entity's averaged purchasing date](https://insights.glassnode.com/quantifying-bitcoin-hodler-supply/) with weights given by a logistic function centered at an age of 155 days and a transition width of 10 days.\\n\\nEntities 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. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see [this article](https://insights.glassnode.com/true-bitcoin-volume/).\\n\\nNote that exchange metrics are based on our labeled data of exchange addresses that we constantly keep updating, as well as data science techniques and statistical information that changes over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\\n\\nThis is the Point-in-Time (PiT) variant of [Short-Term Holder in Profit to Exchanges (Volume)](https://studio.glassnode.com/metrics?a=BTC&m=transactions.TransfersVolumeSthToExchangesProfitSum). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/transactions.TransfersVolumeSthToExchangesProfitSumPit?a=BTC)\n","operationId":"transactions.TransfersVolumeSthToExchangesProfitSumPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"c","in":"query","required":false,"description":"currency - NATIVE, USD","schema":{"type":"string"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Short-Term Holder Profit/Loss Ratio > The ratio of the \[Short-Term Holder Supply in Profit]\() and the \[Short-Term Holder Supply in Loss]\(). Similar to SOPR, it detects local bottoms in bull markets and local tops in bear markets. This metric was first put forward by \[ARK Invest]\( is the Point-in-Time (PiT) variant of \[Short-Term Holder Profit/Loss Ratio]\(). 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/supply/sth_profit_loss_ratio_pit":{"get":{"summary":"Short-Term Holder Profit/Loss Ratio","description":"The ratio of the [Short-Term Holder Supply in Profit](https://studio.glassnode.com/metrics?a=BTC&category=&m=supply.SthProfitSum) and the [Short-Term Holder Supply in Loss](https://studio.glassnode.com/metrics?a=BTC&category=&m=supply.SthLossSum). Similar to SOPR, it detects local bottoms in bull markets and local tops in bear markets. This metric was first put forward by [ARK Invest](https://twitter.com/ARKInvest).\\n\\nThis is the Point-in-Time (PiT) variant of [Short-Term Holder Profit/Loss Ratio](https://studio.glassnode.com/metrics?a=BTC&m=supply.SthProfitLossRatio). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/supply.SthProfitLossRatioPit?a=BTC)\n","operationId":"supply.SthProfitLossRatioPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Short-Term Holder Supply > The total amount of circulating supply held by short term holders. 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.\n\nThis is the Point-in-Time (PiT) variant of \[Short-Term Holder 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/supply/sth_sum_pit":{"get":{"summary":"Short-Term Holder Supply","description":"The total amount of circulating supply held by short term holders. Long- and Short-Term Holder supply is defined with respect to the [entity's averaged purchasing date](https://insights.glassnode.com/quantifying-bitcoin-hodler-supply/) with weights given by a logistic function centered at an age of 155 days and a transition width of 10 days.\\n\\nThis is the Point-in-Time (PiT) variant of [Short-Term Holder Supply](https://studio.glassnode.com/metrics?a=BTC&m=supply.SthSum). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/supply.SthSumPit?a=BTC)\n","operationId":"supply.SthSumPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"c","in":"query","required":false,"description":"currency - NATIVE, USD","schema":{"type":"string"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Short-Term Holder Supply in Loss > The total amount of circulating supply that is currently at loss and held by short term holders. 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.\n\nThis is the Point-in-Time (PiT) variant of \[Short-Term Holder Supply 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/supply/sth_loss_sum_pit":{"get":{"summary":"Short-Term Holder Supply in Loss","description":"The total amount of circulating supply that is currently at loss and held by short term holders. Long- and Short-Term Holder supply is defined with respect to the [entity's averaged purchasing date](https://insights.glassnode.com/quantifying-bitcoin-hodler-supply/) with weights given by a logistic function centered at an age of 155 days and a transition width of 10 days.\\n\\nThis is the Point-in-Time (PiT) variant of [Short-Term Holder Supply in Loss](https://studio.glassnode.com/metrics?a=BTC&m=supply.SthLossSum). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/supply.SthLossSumPit?a=BTC)\n","operationId":"supply.SthLossSumPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"c","in":"query","required":false,"description":"currency - NATIVE, USD","schema":{"type":"string"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Short-Term Holder Supply in Profit > The total amount of circulating supply that is currently in profit and held by short term holders. 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.\n\nThis is the Point-in-Time (PiT) variant of \[Short-Term Holder Supply 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/supply/sth_profit_sum_pit":{"get":{"summary":"Short-Term Holder Supply in Profit","description":"The total amount of circulating supply that is currently in profit and held by short term holders. Long- and Short-Term Holder supply is defined with respect to the [entity's averaged purchasing date](https://insights.glassnode.com/quantifying-bitcoin-hodler-supply/) with weights given by a logistic function centered at an age of 155 days and a transition width of 10 days.\\n\\nThis is the Point-in-Time (PiT) variant of [Short-Term Holder Supply in Profit](https://studio.glassnode.com/metrics?a=BTC&m=supply.SthProfitSum). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/supply.SthProfitSumPit?a=BTC)\n","operationId":"supply.SthProfitSumPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"c","in":"query","required":false,"description":"currency - NATIVE, USD","schema":{"type":"string"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Short-Term Holder to Exchanges (Volume) > The total amount of coins transferred from \[short-term holders]\() to exchange wallets. Only direct transfers are counted. 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.\n\nEntities 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. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see \[this article]\( that exchange metrics are based on our labeled data of exchange addresses that we constantly keep updating, as well as data science techniques and statistical information that changes over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\n\nThis is the Point-in-Time (PiT) variant of \[Short-Term Holder to Exchanges (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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/transactions/transfers_volume_sth_to_exchanges_sum_pit":{"get":{"summary":"Short-Term Holder to Exchanges (Volume)","description":"The total amount of coins transferred from [short-term holders](https://insights.glassnode.com/quantifying-bitcoin-hodler-supply/) to exchange wallets. Only direct transfers are counted. Long- and Short-Term Holder supply is defined with respect to the [entity's averaged purchasing date](https://insights.glassnode.com/quantifying-bitcoin-hodler-supply/) with weights given by a logistic function centered at an age of 155 days and a transition width of 10 days.\\n\\nEntities 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. Note that entity–based metrics are based on data science techniques and statistical information that changes over time and are therefore mutable – the data is stable, but most recent data points are subject to slight fluctuations as time progresses. For more information see [this article](https://insights.glassnode.com/true-bitcoin-volume/).\\n\\nNote that exchange metrics are based on our labeled data of exchange addresses that we constantly keep updating, as well as data science techniques and statistical information that changes over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\\n\\nThis is the Point-in-Time (PiT) variant of [Short-Term Holder to Exchanges (Volume)](https://studio.glassnode.com/metrics?a=BTC&m=transactions.TransfersVolumeSthToExchangesSum). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/transactions.TransfersVolumeSthToExchangesSumPit?a=BTC)\n","operationId":"transactions.TransfersVolumeSthToExchangesSumPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"c","in":"query","required":false,"description":"currency - NATIVE, USD","schema":{"type":"string"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Stablecoins Transactions (Absolute) > The number of transactions (transaction count) in the Ethereum network by stablecoin transactions. Stablecoin are fungible tokens that have their value pegged to an off-chain asset, either by the issuer or by an algorithm. We include 150+ stablecoins in this category, with USDT, USDC, UST, BUSD, and DAI being the most prominent ones.\n\nThis is the Point-in-Time (PiT) variant of \[Stablecoins 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/transactions/transfers_count_stablecoins_pit":{"get":{"summary":"Stablecoins Transactions (Absolute)","description":"The number of transactions (transaction count) in the Ethereum network by stablecoin transactions. Stablecoin are fungible tokens that have their value pegged to an off-chain asset, either by the issuer or by an algorithm. We include 150+ stablecoins in this category, with USDT, USDC, UST, BUSD, and DAI being the most prominent ones.\\n\\nThis is the Point-in-Time (PiT) variant of [Stablecoins Transactions (Absolute)](https://studio.glassnode.com/metrics?a=BTC&m=transactions.TransfersCountStablecoins). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/transactions.TransfersCountStablecoinsPit?a=ETH)\n","operationId":"transactions.TransfersCountStablecoinsPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - ETH","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Stablecoins Transactions (Relative) > The relative amount (share) of transactions in the Ethereum network by stablecoin transactions. Stablecoin are fungible tokens that have their value pegged to an off-chain asset, either by the issuer or by an algorithm. We include 150+ stablecoins in this category, with USDT, USDC, UST, BUSD, and DAI being the most prominent ones.\n\nThis is the Point-in-Time (PiT) variant of \[Stablecoins 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/transactions/transfers_count_stablecoins_relative_pit":{"get":{"summary":"Stablecoins Transactions (Relative)","description":"The relative amount (share) of transactions in the Ethereum network by stablecoin transactions. Stablecoin are fungible tokens that have their value pegged to an off-chain asset, either by the issuer or by an algorithm. We include 150+ stablecoins in this category, with USDT, USDC, UST, BUSD, and DAI being the most prominent ones.\\n\\nThis is the Point-in-Time (PiT) variant of [Stablecoins Transactions (Relative)](https://studio.glassnode.com/metrics?a=BTC&m=transactions.TransfersCountStablecoinsRelative). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/transactions.TransfersCountStablecoinsRelativePit?a=ETH)\n","operationId":"transactions.TransfersCountStablecoinsRelativePit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - ETH","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Supply Held by Entities with Balance < 0.001 > The total circulating supply held by entities with balance lower than 0.001 coins.\n\nThis is the Point-in-Time (PiT) variant of \[Supply Held by Entities with Balance < 0.001]\(). 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/entities/supply_balance_less_0001_pit":{"get":{"summary":"Supply Held by Entities with Balance < 0.001","description":"The total circulating supply held by entities with balance lower than 0.001 coins.\\n\\nThis is the Point-in-Time (PiT) variant of [Supply Held by Entities with Balance < 0.001](https://studio.glassnode.com/metrics?a=BTC&m=entities.SupplyBalanceLess0001). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/entities.SupplyBalanceLess0001Pit?a=BTC)\n","operationId":"entities.SupplyBalanceLess0001Pit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"c","in":"query","required":false,"description":"currency - NATIVE, USD","schema":{"type":"string"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Supply Held by Entities with Balance > 100k > The total circulating supply held by entities with balance of at least 100,000 coins.\n\nThis is the Point-in-Time (PiT) variant of \[Supply Held by Entities 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/entities/supply_balance_more_100k_pit":{"get":{"summary":"Supply Held by Entities with Balance > 100k","description":"The total circulating supply held by entities with balance of at least 100,000 coins.\\n\\nThis is the Point-in-Time (PiT) variant of [Supply Held by Entities with Balance > 100k](https://studio.glassnode.com/metrics?a=BTC&m=entities.SupplyBalanceMore100K). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/entities.SupplyBalanceMore100KPit?a=BTC)\n","operationId":"entities.SupplyBalanceMore100KPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"c","in":"query","required":false,"description":"currency - NATIVE, USD","schema":{"type":"string"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Supply Held by Entities with Balance 0.001 - 0.01 > The total circulating supply held by entities with balance between 0.001 and 0.01 coins.\n\nThis is the Point-in-Time (PiT) variant of \[Supply Held by Entities with Balance 0.001 - 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/entities/supply_balance_0001_001_pit":{"get":{"summary":"Supply Held by Entities with Balance 0.001 - 0.01","description":"The total circulating supply held by entities with balance between 0.001 and 0.01 coins.\\n\\nThis is the Point-in-Time (PiT) variant of [Supply Held by Entities with Balance 0.001 - 0.01](https://studio.glassnode.com/metrics?a=BTC&m=entities.SupplyBalance0001001). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/entities.SupplyBalance0001001Pit?a=BTC)\n","operationId":"entities.SupplyBalance0001001Pit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"c","in":"query","required":false,"description":"currency - NATIVE, USD","schema":{"type":"string"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Supply Held by Entities with Balance 0.01 - 0.1 > The total circulating supply held by entities with balance between 0.01 and 0.1 coins.\n\nThis is the Point-in-Time (PiT) variant of \[Supply Held by Entities with Balance 0.01 - 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/entities/supply_balance_001_01_pit":{"get":{"summary":"Supply Held by Entities with Balance 0.01 - 0.1","description":"The total circulating supply held by entities with balance between 0.01 and 0.1 coins.\\n\\nThis is the Point-in-Time (PiT) variant of [Supply Held by Entities with Balance 0.01 - 0.1](https://studio.glassnode.com/metrics?a=BTC&m=entities.SupplyBalance00101). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/entities.SupplyBalance00101Pit?a=BTC)\n","operationId":"entities.SupplyBalance00101Pit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"c","in":"query","required":false,"description":"currency - NATIVE, USD","schema":{"type":"string"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Supply Held by Entities with Balance 0.1 - 1 > The total circulating supply held by entities with balance between 0.1 and 1 coins.\n\nThis is the Point-in-Time (PiT) variant of \[Supply Held by Entities with Balance 0.1 - 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/entities/supply_balance_01_1_pit":{"get":{"summary":"Supply Held by Entities with Balance 0.1 - 1","description":"The total circulating supply held by entities with balance between 0.1 and 1 coins.\\n\\nThis is the Point-in-Time (PiT) variant of [Supply Held by Entities with Balance 0.1 - 1](https://studio.glassnode.com/metrics?a=BTC&m=entities.SupplyBalance011). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/entities.SupplyBalance011Pit?a=BTC)\n","operationId":"entities.SupplyBalance011Pit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"c","in":"query","required":false,"description":"currency - NATIVE, USD","schema":{"type":"string"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Supply Held by Entities with Balance 1 - 10 > The total circulating supply held by entities with balance between 1 and 10 coins.\n\nThis is the Point-in-Time (PiT) variant of \[Supply Held by Entities with Balance 1 - 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/entities/supply_balance_1_10_pit":{"get":{"summary":"Supply Held by Entities with Balance 1 - 10","description":"The total circulating supply held by entities with balance between 1 and 10 coins.\\n\\nThis is the Point-in-Time (PiT) variant of [Supply Held by Entities with Balance 1 - 10](https://studio.glassnode.com/metrics?a=BTC&m=entities.SupplyBalance110). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/entities.SupplyBalance110Pit?a=BTC)\n","operationId":"entities.SupplyBalance110Pit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"c","in":"query","required":false,"description":"currency - NATIVE, USD","schema":{"type":"string"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Supply Held by Entities with Balance 10 - 100 > The total circulating supply held by entities with balance between 10 and 100 coins.\n\nThis is the Point-in-Time (PiT) variant of \[Supply Held by Entities with Balance 10 - 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/entities/supply_balance_10_100_pit":{"get":{"summary":"Supply Held by Entities with Balance 10 - 100","description":"The total circulating supply held by entities with balance between 10 and 100 coins.\\n\\nThis is the Point-in-Time (PiT) variant of [Supply Held by Entities with Balance 10 - 100](https://studio.glassnode.com/metrics?a=BTC&m=entities.SupplyBalance10100). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/entities.SupplyBalance10100Pit?a=BTC)\n","operationId":"entities.SupplyBalance10100Pit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"c","in":"query","required":false,"description":"currency - NATIVE, USD","schema":{"type":"string"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Supply Held by Entities with Balance 100 - 1k > The total circulating supply held by entities with balance between 100 and 1,000 coins.\n\nThis is the Point-in-Time (PiT) variant of \[Supply Held by Entities with Balance 100 - 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/entities/supply_balance_100_1k_pit":{"get":{"summary":"Supply Held by Entities with Balance 100 - 1k","description":"The total circulating supply held by entities with balance between 100 and 1,000 coins.\\n\\nThis is the Point-in-Time (PiT) variant of [Supply Held by Entities with Balance 100 - 1k](https://studio.glassnode.com/metrics?a=BTC&m=entities.SupplyBalance1001K). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/entities.SupplyBalance1001KPit?a=BTC)\n","operationId":"entities.SupplyBalance1001KPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"c","in":"query","required":false,"description":"currency - NATIVE, USD","schema":{"type":"string"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Supply Held by Entities with Balance 10k - 100k > The total circulating supply held by entities with balance between 10,000 and 100,000 coins.\n\nThis is the Point-in-Time (PiT) variant of \[Supply Held by Entities with Balance 10k - 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/entities/supply_balance_10k_100k_pit":{"get":{"summary":"Supply Held by Entities with Balance 10k - 100k","description":"The total circulating supply held by entities with balance between 10,000 and 100,000 coins.\\n\\nThis is the Point-in-Time (PiT) variant of [Supply Held by Entities with Balance 10k - 100k](https://studio.glassnode.com/metrics?a=BTC&m=entities.SupplyBalance10K100K). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/entities.SupplyBalance10K100KPit?a=BTC)\n","operationId":"entities.SupplyBalance10K100KPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"c","in":"query","required":false,"description":"currency - NATIVE, USD","schema":{"type":"string"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Supply Held by Entities with Balance 1k - 10k > The total circulating supply held by entities with balance between 1,000 and 10,000 coins.\n\nThis is the Point-in-Time (PiT) variant of \[Supply Held by Entities with Balance 1k - 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/entities/supply_balance_1k_10k_pit":{"get":{"summary":"Supply Held by Entities with Balance 1k - 10k","description":"The total circulating supply held by entities with balance between 1,000 and 10,000 coins.\\n\\nThis is the Point-in-Time (PiT) variant of [Supply Held by Entities with Balance 1k - 10k](https://studio.glassnode.com/metrics?a=BTC&m=entities.SupplyBalance1K10K). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/entities.SupplyBalance1K10KPit?a=BTC)\n","operationId":"entities.SupplyBalance1K10KPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"c","in":"query","required":false,"description":"currency - NATIVE, USD","schema":{"type":"string"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Supply in Smart Contracts > The percent of total supply of the token that is held in smart contracts.\n\nThis is the Point-in-Time (PiT) variant of \[Supply in Smart 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/distribution/supply_contracts_pit":{"get":{"summary":"Supply in Smart Contracts","description":"The percent of total supply of the token that is held in smart contracts.\\n\\nThis is the Point-in-Time (PiT) variant of [Supply in Smart Contracts](https://studio.glassnode.com/metrics?a=BTC&m=distribution.SupplyContracts). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/distribution.SupplyContractsPit?a=ETH)\n","operationId":"distribution.SupplyContractsPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - ETH","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Supply of Top 1% Addresses > The percentage of supply held by the top 1% addresses. Exchange addresses, smart contract addresses, and other special asset-specific addresses (e.g. team fund addresses) are excluded.\n\nThis is the Point-in-Time (PiT) variant of \[Supply of Top 1% 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/distribution/balance_1pct_holders_pit":{"get":{"summary":"Supply of Top 1% Addresses","description":"The percentage of supply held by the top 1% addresses. Exchange addresses, smart contract addresses, and other special asset-specific addresses (e.g. team fund addresses) are excluded.\\n\\nThis is the Point-in-Time (PiT) variant of [Supply of Top 1% Addresses](https://studio.glassnode.com/metrics?a=BTC&m=distribution.Balance1PctHolders). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/distribution.Balance1PctHoldersPit?a=ETH)\n","operationId":"distribution.Balance1PctHoldersPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - ETH","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Total Transfer Volume by Size (Entity-Adjusted) > Entity-adjusted on-chain volume breakdown by the USD value of the transfers.\n\nThis is the Point-in-Time (PiT) variant of \[Total Transfer Volume by Size (Entity-Adjusted)]\(). 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/transactions/transfers_volume_by_size_entity_adjusted_sum_pit":{"get":{"summary":"Total Transfer Volume by Size (Entity-Adjusted)","description":"Entity-adjusted on-chain volume breakdown by the USD value of the transfers.\\n\\nThis is the Point-in-Time (PiT) variant of [Total Transfer Volume by Size (Entity-Adjusted)](https://studio.glassnode.com/metrics?a=BTC&m=transactions.TransfersVolumeBySizeEntityAdjustedSum). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/transactions.TransfersVolumeBySizeEntityAdjustedSumPit?a=BTC)\n","operationId":"transactions.TransfersVolumeBySizeEntityAdjustedSumPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Transaction Type Breakdown (Absolute) > The number of transactions (transaction count) in the Ethereum network by category. Transactions are classified into the following categories:\n\n- \*Vanilla:\* Pure ETH transfers between Externally Owned Accounts (EOAs), with no contracts being called.\n\n- \*ERC20:\* All transactions calling ERC20 contracts. Contracts in the Stablecoins category are excluded here.\n\n- \*Stablecoins:\* Fungible tokens that have their value pegged to an off-chain asset, either by the issuer or by an algorithm. We include 150+ stablecoins in this category, with USDT, USDC, UST, BUSD, and DAI being the most prominent ones.\n\n- \*DeFi:\* On-chain financial instruments and protocols implemented as smart contracts, including decentralized exchanges (DEXs). We include over 90+ DeFi protocols in this category, such as Uniswap, Etherdelta, 1inch, Sushiswap, Aave, and 0x.\n\n- \*Bridges:\* Contracts allowing transfer of tokens between different blockchains. We include 50+ bridges in this category, such as Ronin, Polygon, Optimism, and Arbitrum.\n\n- \*NFTs:\* Transactions interacting with non-fungible tokens. This category includes of both token contract standards (ERC721, ERC1155), as well as NFT marketplaces (OpenSea, Blur, LooksRare, Rarible, SuperRare) for trading those.\n\n- \*MEV Bots:\* Miner Extractable Value (MEV) bots execute transactions for profit by reordering, inserting, and censoring transactions within blocks.\n\n- \*Other:\* This category includes all other transactions in the Ethereum network that are not included in categories listed above.\n\nThis is the Point-in-Time (PiT) variant of \[Transaction Type Breakdown (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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/transactions/tx_types_breakdown_count_pit":{"get":{"summary":"Transaction Type Breakdown (Absolute)","description":"The number of transactions (transaction count) in the Ethereum network by category. Transactions are classified into the following categories:\\n\\n- *Vanilla:* Pure ETH transfers between Externally Owned Accounts (EOAs), with no contracts being called.\\n\\n- *ERC20:* All transactions calling ERC20 contracts. Contracts in the Stablecoins category are excluded here.\\n\\n- *Stablecoins:* Fungible tokens that have their value pegged to an off-chain asset, either by the issuer or by an algorithm. We include 150+ stablecoins in this category, with USDT, USDC, UST, BUSD, and DAI being the most prominent ones.\\n\\n- *DeFi:* On-chain financial instruments and protocols implemented as smart contracts, including decentralized exchanges (DEXs). We include over 90+ DeFi protocols in this category, such as Uniswap, Etherdelta, 1inch, Sushiswap, Aave, and 0x.\\n\\n- *Bridges:* Contracts allowing transfer of tokens between different blockchains. We include 50+ bridges in this category, such as Ronin, Polygon, Optimism, and Arbitrum.\\n\\n- *NFTs:* Transactions interacting with non-fungible tokens. This category includes of both token contract standards (ERC721, ERC1155), as well as NFT marketplaces (OpenSea, Blur, LooksRare, Rarible, SuperRare) for trading those.\\n\\n- *MEV Bots:* Miner Extractable Value (MEV) bots execute transactions for profit by reordering, inserting, and censoring transactions within blocks.\\n\\n- *Other:* This category includes all other transactions in the Ethereum network that are not included in categories listed above.\\n\\nThis is the Point-in-Time (PiT) variant of [Transaction Type Breakdown (Absolute)](https://studio.glassnode.com/metrics?a=BTC&m=transactions.TxTypesBreakdownCount). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/transactions.TxTypesBreakdownCountPit?a=ETH)\n","operationId":"transactions.TxTypesBreakdownCountPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - ETH","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Transaction Type Breakdown (Relative) > The relative amount (share) of transactions in the Ethereum network by category. Transactions are classified into one of the following categories:\n\n- \*Vanilla:\* Pure ETH transfers between Externally Owned Accounts (EOAs), with no contracts being called.\n\n- \*ERC20:\* All transactions calling ERC20 contracts. Contracts in the Stablecoins category are excluded here.\n\n- \*Stablecoins:\* Fungible tokens that have their value pegged to an off-chain asset, either by the issuer or by an algorithm. We include 150+ stablecoins in this category, with USDT, USDC, UST, BUSD, and DAI being the most prominent ones.\n\n- \*DeFi:\* On-chain financial instruments and protocols implemented as smart contracts, including decentralized exchanges (DEXs). We include over 90+ DeFi protocols in this category, such as Uniswap, Etherdelta, 1inch, Sushiswap, Aave, and 0x.\n\n- \*Bridges:\* Contracts allowing transfer of tokens between different blockchains. We include 50+ bridges in this category, such as Ronin, Polygon, Optimism, and Arbitrum.\n\n- \*NFTs:\* Transactions interacting with non-fungible tokens. This category includes of both token contract standards (ERC721, ERC1155), as well as NFT marketplaces (OpenSea, Blur, LooksRare, Rarible, SuperRare) for trading those.\n\n- \*MEV Bots:\* Miner Extractable Value (MEV) bots execute transactions for profit by reordering, inserting, and censoring transactions within blocks.\n\n- \*Other:\* This category includes all other transactions in the Ethereum network that are not included in categories listed above.\n\nThis is the Point-in-Time (PiT) variant of \[Transaction Type Breakdown (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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/transactions/tx_types_breakdown_relative_pit":{"get":{"summary":"Transaction Type Breakdown (Relative)","description":"The relative amount (share) of transactions in the Ethereum network by category. Transactions are classified into one of the following categories:\\n\\n- *Vanilla:* Pure ETH transfers between Externally Owned Accounts (EOAs), with no contracts being called.\\n\\n- *ERC20:* All transactions calling ERC20 contracts. Contracts in the Stablecoins category are excluded here.\\n\\n- *Stablecoins:* Fungible tokens that have their value pegged to an off-chain asset, either by the issuer or by an algorithm. We include 150+ stablecoins in this category, with USDT, USDC, UST, BUSD, and DAI being the most prominent ones.\\n\\n- *DeFi:* On-chain financial instruments and protocols implemented as smart contracts, including decentralized exchanges (DEXs). We include over 90+ DeFi protocols in this category, such as Uniswap, Etherdelta, 1inch, Sushiswap, Aave, and 0x.\\n\\n- *Bridges:* Contracts allowing transfer of tokens between different blockchains. We include 50+ bridges in this category, such as Ronin, Polygon, Optimism, and Arbitrum.\\n\\n- *NFTs:* Transactions interacting with non-fungible tokens. This category includes of both token contract standards (ERC721, ERC1155), as well as NFT marketplaces (OpenSea, Blur, LooksRare, Rarible, SuperRare) for trading those.\\n\\n- *MEV Bots:* Miner Extractable Value (MEV) bots execute transactions for profit by reordering, inserting, and censoring transactions within blocks.\\n\\n- *Other:* This category includes all other transactions in the Ethereum network that are not included in categories listed above.\\n\\nThis is the Point-in-Time (PiT) variant of [Transaction Type Breakdown (Relative)](https://studio.glassnode.com/metrics?a=BTC&m=transactions.TxTypesBreakdownRelative). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/transactions.TxTypesBreakdownRelativePit?a=ETH)\n","operationId":"transactions.TxTypesBreakdownRelativePit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - ETH","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## US Government Balance > The US Government Balance corresponds to the amount of BTC held in addresses controlled by US authorities. The metric includes seized funds, e.g. from the 2016 Bitfinex Hack or the 2012 Silk Road Hack. We constantly keep updating the set of addresses contributing to the total balance.\n\nThis is the Point-in-Time (PiT) variant of \[US 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/distribution/balance_us_government_pit":{"get":{"summary":"US Government Balance","description":"The US Government Balance corresponds to the amount of BTC held in addresses controlled by US authorities. The metric includes seized funds, e.g. from the 2016 Bitfinex Hack or the 2012 Silk Road Hack. We constantly keep updating the set of addresses contributing to the total balance.\\n\\nThis is the Point-in-Time (PiT) variant of [US Government Balance](https://studio.glassnode.com/metrics?a=BTC&m=distribution.BalanceUsGovernment). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/distribution.BalanceUsGovernmentPit?a=BTC)\n","operationId":"distribution.BalanceUsGovernmentPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"c","in":"query","required":false,"description":"currency - NATIVE, USD","schema":{"type":"string"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## US Year-over-Year Supply Change > \nThis metric aims at giving an estimate for the year-over-year change in the share of the Bitcoin supply to be held/traded in the US.\n\nGeolocation of Bitcoin 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 probabilities for each entity being located in the US, Europe, or Asia. Working hours are defined as:\n\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)\n\nAn entity\'s balance will only contribute to the supply in the respective region if the location can be determined with a high certainty. Supply held on exchanges wallets are excluded.\n \n\nThis is the Point-in-Time (PiT) variant of \[US 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/supply/amer_1y_supply_change_pit":{"get":{"summary":"US Year-over-Year Supply Change","description":"\\nThis metric aims at giving an estimate for the year-over-year change in the share of the Bitcoin supply to be held/traded in the US.\\n\\nGeolocation of Bitcoin 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 probabilities for each entity being located in the US, Europe, or Asia. Working hours are defined as:\\n\\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)\\n\\nAn entity's balance will only contribute to the supply in the respective region if the location can be determined with a high certainty. Supply held on exchanges wallets are excluded.\\n \\n\\nThis is the Point-in-Time (PiT) variant of [US Year-over-Year Supply Change](https://studio.glassnode.com/metrics?a=BTC&m=supply.Amer1YSupplyChange). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/supply.Amer1YSupplyChangePit?a=BTC)\n","operationId":"supply.Amer1YSupplyChangePit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Vanilla Transactions (Absolute) > The amount of gas consumed by the Ethereum network by vanilla transactions. Vanilla transactions are pure ETH transfers between Externally Owned Accounts (EOAs), with no contracts being called.\n If at least one of the EOAs participating in the transaction (the receiver, the sender, or both) belongs to an exchange, the amount will be represented in the exchange cohort.\n Note that occasionally the value of the last datapoint can slightly change as some addresses initially transact as \\"vanilla\\" before their associated smart contract deployment is observed.\n\nThis is the Point-in-Time (PiT) variant of \[Vanilla 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/transactions/transfers_count_vanilla_pit":{"get":{"summary":"Vanilla Transactions (Absolute)","description":"The amount of gas consumed by the Ethereum network by vanilla transactions. Vanilla transactions are pure ETH transfers between Externally Owned Accounts (EOAs), with no contracts being called.\\n If at least one of the EOAs participating in the transaction (the receiver, the sender, or both) belongs to an exchange, the amount will be represented in the exchange cohort.\\n Note that occasionally the value of the last datapoint can slightly change as some addresses initially transact as \\\"vanilla\\\" before their associated smart contract deployment is observed.\\n\\nThis is the Point-in-Time (PiT) variant of [Vanilla Transactions (Absolute)](https://studio.glassnode.com/metrics?a=BTC&m=transactions.TransfersCountVanilla). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/transactions.TransfersCountVanillaPit?a=ETH)\n","operationId":"transactions.TransfersCountVanillaPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - ETH","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Vanilla Transactions (Relative) > The relative amount (share) of gas consumed by the Ethereum network by vanilla transactions. Vanilla transactions are pure ETH transfers between Externally Owned Accounts (EOAs), with no contracts being called.\n If at least one of the EOAs participating in the transaction (the receiver, the sender, or both) belongs to an exchange, the amount will be represented in the exchange cohort.\n Note that occasionally the value of the last datapoint can slightly change as some addresses initially transact as \\"vanilla\\" before their associated smart contract deployment is observed.\n\nThis is the Point-in-Time (PiT) variant of \[Vanilla 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/transactions/transfers_count_vanilla_relative_pit":{"get":{"summary":"Vanilla Transactions (Relative)","description":"The relative amount (share) of gas consumed by the Ethereum network by vanilla transactions. Vanilla transactions are pure ETH transfers between Externally Owned Accounts (EOAs), with no contracts being called.\\n If at least one of the EOAs participating in the transaction (the receiver, the sender, or both) belongs to an exchange, the amount will be represented in the exchange cohort.\\n Note that occasionally the value of the last datapoint can slightly change as some addresses initially transact as \\\"vanilla\\\" before their associated smart contract deployment is observed.\\n\\nThis is the Point-in-Time (PiT) variant of [Vanilla Transactions (Relative)](https://studio.glassnode.com/metrics?a=BTC&m=transactions.TransfersCountVanillaRelative). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/transactions.TransfersCountVanillaRelativePit?a=ETH)\n","operationId":"transactions.TransfersCountVanillaRelativePit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - ETH","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Wrapped BTC (WBTC) Balance > Wrapped Bitcoin (WBTC) is the first ERC20 token backed 1:1 with Bitcoin and designed to act as representation of Bitcoin on the Ethereum blockchain. The WBTC supply listed here corresponds to the amount of Bitcoin held by BitGo, the custodian responsible for minting new WBTC ERC20 tokens and guaranteeing backing of new ERC20 tokens by actual BTC.\n\nThis is the Point-in-Time (PiT) variant of \[Wrapped BTC (WBTC) 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/distribution/balance_wbtc_pit":{"get":{"summary":"Wrapped BTC (WBTC) Balance","description":"Wrapped Bitcoin (WBTC) is the first ERC20 token backed 1:1 with Bitcoin and designed to act as representation of Bitcoin on the Ethereum blockchain. The WBTC supply listed here corresponds to the amount of Bitcoin held by BitGo, the custodian responsible for minting new WBTC ERC20 tokens and guaranteeing backing of new ERC20 tokens by actual BTC.\\n\\nThis is the Point-in-Time (PiT) variant of [Wrapped BTC (WBTC) Balance](https://studio.glassnode.com/metrics?a=BTC&m=distribution.BalanceWbtc). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/distribution.BalanceWbtcPit?a=BTC)\n","operationId":"distribution.BalanceWbtcPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"c","in":"query","required":false,"description":"currency - NATIVE, USD","schema":{"type":"string"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Whale Deposits to Exchanges (Counts) > The total count of transfers from whales to exchange addresses. Whales are defined as network entities (cluster of addresses) that hold at least 1,000 BTC. Note that exchange metrics are based on our labeled data of exchange addresses that we constantly keep updating, as well as data science techniques and statistical information that changes over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\n\nThis is the Point-in-Time (PiT) variant of \[Whale Deposits to Exchanges (Counts)]\(). 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/transactions/transfers_whales_to_exchanges_count_pit":{"get":{"summary":"Whale Deposits to Exchanges (Counts)","description":"The total count of transfers from whales to exchange addresses. Whales are defined as network entities (cluster of addresses) that hold at least 1,000 BTC. Note that exchange metrics are based on our labeled data of exchange addresses that we constantly keep updating, as well as data science techniques and statistical information that changes over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\\n\\nThis is the Point-in-Time (PiT) variant of [Whale Deposits to Exchanges (Counts)](https://studio.glassnode.com/metrics?a=BTC&m=transactions.TransfersWhalesToExchangesCount). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/transactions.TransfersWhalesToExchangesCountPit?a=BTC)\n","operationId":"transactions.TransfersWhalesToExchangesCountPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Whale Deposits to Exchanges (Volume) > The total amount of coins transferred from whales to exchange wallets. Only direct transfers are counted. Whales are defined as network entities (cluster of addresses) that hold at least 1,000 BTC. Note that exchange metrics are based on our labeled data of exchange addresses that we constantly keep updating, as well as data science techniques and statistical information that changes over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\n\nThis is the Point-in-Time (PiT) variant of \[Whale Deposits to Exchanges (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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/transactions/transfers_volume_whales_to_exchanges_sum_pit":{"get":{"summary":"Whale Deposits to Exchanges (Volume)","description":"The total amount of coins transferred from whales to exchange wallets. Only direct transfers are counted. Whales are defined as network entities (cluster of addresses) that hold at least 1,000 BTC. Note that exchange metrics are based on our labeled data of exchange addresses that we constantly keep updating, as well as data science techniques and statistical information that changes over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\\n\\nThis is the Point-in-Time (PiT) variant of [Whale Deposits to Exchanges (Volume)](https://studio.glassnode.com/metrics?a=BTC&m=transactions.TransfersVolumeWhalesToExchangesSum). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/transactions.TransfersVolumeWhalesToExchangesSumPit?a=BTC)\n","operationId":"transactions.TransfersVolumeWhalesToExchangesSumPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"c","in":"query","required":false,"description":"currency - NATIVE, USD","schema":{"type":"string"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Whale Withdrawals from Exchanges (Counts) > The total count of transfers from exchange addresses to whales. Whales are defined as network entities (cluster of addresses) that hold at least 1,000 BTC. Note that exchange metrics are based on our labeled data of exchange addresses that we constantly keep updating, as well as data science techniques and statistical information that changes over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\n\nThis is the Point-in-Time (PiT) variant of \[Whale Withdrawals from Exchanges (Counts)]\(). 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/transactions/transfers_exchanges_to_whales_count_pit":{"get":{"summary":"Whale Withdrawals from Exchanges (Counts)","description":"The total count of transfers from exchange addresses to whales. Whales are defined as network entities (cluster of addresses) that hold at least 1,000 BTC. Note that exchange metrics are based on our labeled data of exchange addresses that we constantly keep updating, as well as data science techniques and statistical information that changes over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\\n\\nThis is the Point-in-Time (PiT) variant of [Whale Withdrawals from Exchanges (Counts)](https://studio.glassnode.com/metrics?a=BTC&m=transactions.TransfersExchangesToWhalesCount). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/transactions.TransfersExchangesToWhalesCountPit?a=BTC)\n","operationId":"transactions.TransfersExchangesToWhalesCountPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Whale Withdrawals from Exchanges (Volume) > The total amount of coins transferred from exchange wallets to whale entities. Only direct transfers are counted. Whales are defined as network entities (cluster of addresses) that hold at least 1,000 BTC. Note that exchange metrics are based on our labeled data of exchange addresses that we constantly keep updating, as well as data science techniques and statistical information that changes over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\n\nThis is the Point-in-Time (PiT) variant of \[Whale Withdrawals from Exchanges (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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/transactions/transfers_volume_exchanges_to_whales_sum_pit":{"get":{"summary":"Whale Withdrawals from Exchanges (Volume)","description":"The total amount of coins transferred from exchange wallets to whale entities. Only direct transfers are counted. Whales are defined as network entities (cluster of addresses) that hold at least 1,000 BTC. Note that exchange metrics are based on our labeled data of exchange addresses that we constantly keep updating, as well as data science techniques and statistical information that changes over time. Therefore these metrics are mutable – the data is stable, but especially most recent data points are subject to slight fluctuations as time progresses.\\n\\nThis is the Point-in-Time (PiT) variant of [Whale Withdrawals from Exchanges (Volume)](https://studio.glassnode.com/metrics?a=BTC&m=transactions.TransfersVolumeExchangesToWhalesSum). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/transactions.TransfersVolumeExchangesToWhalesSumPit?a=BTC)\n","operationId":"transactions.TransfersVolumeExchangesToWhalesSumPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id - BTC","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"c","in":"query","required":false,"description":"currency - NATIVE, USD","schema":{"type":"string"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ``` ## Withdrawing Addresses > The number of unique addresses that appeared as a receiver in a transaction receiving funds from an exchanges.\n\nThis is the Point-in-Time (PiT) variant of \[Withdrawing 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.\ > \ > \[View in Studio]\()
```json {"openapi":"3.0.3","info":{"title":"Glassnode API - Point-In-Time","version":"1.0.0"},"servers":[{"url":"https://api.glassnode.com","description":"Production API server"}],"security":[{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"ApiKeyAuth":{"type":"apiKey","in":"query","name":"api_key","description":"Your Glassnode API key"}},"schemas":{"TimeSeriesResponse":{"type":"array","items":{"$ref":"#/components/schemas/TimeSeriesDataPoint"}},"TimeSeriesDataPoint":{"type":"object","properties":{"t":{"type":"integer","format":"int64","description":"Unix timestamp"},"v":{"oneOf":[{"type":"number"},{"type":"object"},{"type":"array"}],"description":"Metric value (can be number, object, or array depending on the metric)"},"o":{"type":"object","description":"Object containing multiple metric values (when applicable)","additionalProperties":true}}},"ErrorResponse":{"type":"object","properties":{"error":{"type":"string"}}}}},"paths":{"/v1/metrics/addresses/receiving_from_exchanges_count_pit":{"get":{"summary":"Withdrawing Addresses","description":"The number of unique addresses that appeared as a receiver in a transaction receiving funds from an exchanges.\\n\\nThis is the Point-in-Time (PiT) variant of [Withdrawing Addresses](https://studio.glassnode.com/metrics?a=BTC&m=addresses.ReceivingFromExchangesCount). 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](https://insights.glassnode.com/introducing-point-in-time-data/) for more information.\n\n[View in Studio](https://studio.glassnode.com/charts/addresses.ReceivingFromExchangesCountPit?a=BTC)\n","operationId":"addresses.ReceivingFromExchangesCountPit","parameters":[{"name":"a","in":"query","required":true,"description":"asset id (see list below for more details)","schema":{"type":"string"},"style":"form","explode":false},{"name":"s","in":"query","required":false,"description":"since, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"u","in":"query","required":false,"description":"until, unix timestamp","schema":{"type":"integer"},"style":"form","explode":false},{"name":"i","in":"query","required":false,"description":"frequency interval - 10m, 1h, 1month, 1w, 24h","schema":{"type":"string"},"style":"form","explode":false},{"name":"f","in":"query","required":false,"description":"format - csv, json","schema":{"type":"string","enum":["csv","json"],"default":"json"},"style":"form","explode":false},{"name":"timestamp_format","in":"query","required":false,"description":"timestamp format - unix or humanized (RFC 3339)","schema":{"type":"string","enum":["unix","humanized"],"default":"unix"},"style":"form","explode":false}],"responses":{"200":{"description":"Successful response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TimeSeriesResponse"}}}},"400":{"description":"Bad Request - Invalid parameters or unsupported asset","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"401":{"description":"Unauthorized - Invalid or missing API key","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}},"429":{"description":"Too Many Requests - Rate limit exceeded","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResponse"}}}}}}}}} ```