> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cryptoquant.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Bitcoin Metcalfe's Price
> Bitcoin price valuation based on Metcalfe's model following the formula A*Active addresses^ 2. Each band represents a different value of A (3, 2, 1, 0.5, 0.25, 0.1 and 0.04)
## What it measures
Fair value modeled from Metcalfe's Law as A × active addresses², where the coefficient A is calibrated from the historical relationship between market cap and active addresses² (i.e. A ≈ market cap ÷ active addresses²). Different A-coefficients produce a family of upper/lower valuation bands.
## How to interpret it
Central Metcalfe Price = network-activity-based fair value. Higher A bands (3x, 2x) = upper valuation limits historically acting as resistance in bull markets. Lower A bands (0.5, 0.25, 0.1, 0.04) = lower support/fair value range. Bands themselves move with network activity levels.
## Key thresholds
Red band (higher A): price resistance in bull markets, short-term rally targets; A=2x band: key support/resistance (\~\$91K in Nov 2025); Blue band (lower A): lower fair value support; Price between red and blue bands since Feb 2024 = "fair value range"
## How to use it
Assess whether price is fundamentally supported by user activity. Price above red band = overvalued vs. network usage. Price bouncing off blue band = fundamental support. Watch bands shift downward when network activity (e.g. OP\_RETURN, transactions) declines.
## OpenAPI
````yaml openapi/v2.json GET /community/bitcoin-metcalfe-price
openapi: 3.0.0
info:
version: 2.0.0-beta
title: CryptoQuant Data API v2
description: >-
The CryptoQuant Data API v2 serves curated, research-grade indicators built
on the v1 conventions — the `status`/`result` response envelope, Bearer
token authentication, and the `window`/`from`/`to` time parameters. Each
metric ships with an interpretation guide covering what it measures, key
thresholds, and how to combine it with other metrics.
termsOfService: https://cryptoquant.com/terms-of-service
contact:
name: API Support
email: contact@cryptoquant.com
servers:
- url: https://api.cryptoquant.com/v2
description: Default server
security: []
tags:
- name: Community-built Indicators
paths:
/community/bitcoin-metcalfe-price:
get:
tags:
- Community-built Indicators
summary: Bitcoin Metcalfe's Price
description: >-
Bitcoin price valuation based on Metcalfe's model followin gthe formula
A*Active addresses^ 2. Each band represents a different value of A (3,
2, 1, 0.5, 0.25, 0.1 and 0.04)
operationId: V2getBitcoinMetcalfePrice
parameters:
- name: window
in: query
required: false
description: Time interval for aggregation.
schema:
type: string
default: day
example: day
- name: from
in: query
required: false
description: >-
Starting time, formatted as YYYYMMDDTHHMMSS (UTC). If `window=day`,
YYYYMMDD is also accepted.
schema:
type: string
- name: to
in: query
required: false
description: >-
Ending time, formatted as YYYYMMDDTHHMMSS (UTC). If `window=day`,
YYYYMMDD is also accepted.
schema:
type: string
- name: limit
in: query
required: false
description: Maximum number of data rows to return. Ranges from 1 to 10,000.
schema:
type: integer
default: 100
minimum: 1
maximum: 10000
responses:
'200':
description: Bitcoin price valuation
content:
application/json:
schema:
type: object
required:
- status
- result
properties:
status:
$ref: '#/components/schemas/Status'
result:
type: object
properties:
window:
type: string
data:
type: array
items:
type: object
properties:
datetime:
type: string
description: >-
The datetime, formatted as YYYY-MM-DD HH:MM:SS
(UTC).
example: '2026-06-14 00:00:00'
active_addresses_squared_price_365ma:
type: number
example: 23036.88
active_addresses_squared_50_price_365ma:
type: number
example: 11518.44
active_addresses_squared_25_price_365ma:
type: number
example: 5759.22
active_addresses_squared_10_price_365ma:
type: number
example: 2303.69
active_addresses_squared_3x_price_365ma:
type: number
example: 69110.65
active_addresses_squared_2x_price_365ma:
type: number
example: 46073.77
security:
- AccessToken: []
x-codeSamples:
- lang: Shell
source: >-
curl -X GET
"https://api.cryptoquant.com/v2/community/bitcoin-metcalfe-price?window=day"
\
-H "Authorization: Bearer "
- lang: JavaScript
source: >-
fetch("https://api.cryptoquant.com/v2/community/bitcoin-metcalfe-price?window=day",
{ headers: { "Authorization": "Bearer "} })
.then(response => response.json())
.then(data => console.log(data))
- lang: NodeJS
source: |-
require('axios')
.get("https://api.cryptoquant.com/v2/community/bitcoin-metcalfe-price?window=day", { headers: { Authorization: 'Bearer ' } })
.then(response => console.log(response))
- lang: Ruby
source: >-
require 'net/http'
uri =
URI("https://api.cryptoquant.com/v2/community/bitcoin-metcalfe-price?window=day")
req = Net::HTTP::Get.new(uri)
req["Authorization"] = "Bearer "
res = Net::HTTP.start(uri.hostname, uri.port, use_ssl: true) {
|http| http.request(req) }
puts res.body
- lang: Python
source: >-
import requests
headers = {'Authorization': 'Bearer '}
url =
"https://api.cryptoquant.com/v2/community/bitcoin-metcalfe-price?window=day"
print(requests.get(url, headers=headers).json())
components:
schemas:
Status:
type: object
description: >-
Returned with every response; indicates whether the request was
successful.
example:
code: 200
message: success
required:
- code
- message
properties:
code:
type: integer
format: int32
description: HTTP status code.
example: 200
message:
type: string
description: Text description of the error or success.
example: success
securitySchemes:
AccessToken:
type: http
scheme: bearer
bearerFormat: JWT
x-default: Bearer
description: >-
For each API request, include the `Authorization` HTTP header with
`Bearer `.
````