> ## 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. # Realized Net Profit and Loss > The net realized profit or loss of Bitcoin sellers in USD and BTC in daily, monthly and yearly windows. ## What it measures Total USD or BTC value of profit or loss realized by all Bitcoin holders on a given day, 30-day and 365-day rolling window. ## How to interpret it Single large loss days are not automatic bottom signals. Watch for patterns: cumulative monthly losses vs. prior bear market levels is more reliable than single-day readings. Declining profit peaks forming lower highs = bull-to-bear transition. BTC-denominated = best for structural cycle analysis across time. USD-denominated = best for measuring real-world economic impact. Rising annual profits = bull market in full force. Declining annual profit peaks = cycle top has passed. Monthly data provides near-term confirmation of profit-taking or capitulation cycles. Compare monthly readings in BTC terms against prior bear market capitulation benchmarks, not just USD figures. ## Key thresholds $5.4B single-day loss (Feb 5, 2026) = largest since Mar 2023, but insufficient for structural bottom; $9B single-day profit (Jul 2025) = local peak; Monthly BTC losses >1.1M BTC = historical capitulation level; 0.3M BTC (Feb 2026) = far below capitulation level BTC terms: 4.4M BTC annual net profit (Oct 2025) = cycle peak at \$126K ATH; +2.5M BTC (Jan 2026) = –43% from peak in 3 months, comparable to Mar 2022 (start of prior bear); Declining annual profit peaks forming lower highs = definitive bull-to-bear signal. Monthly data: 0.53M BTC (Jul 2025) = near-ATH monthly profits; +0.26M BTC (Oct 2025) = 50% below July, early momentum warning; 0.3M BTC monthly losses (Feb 2026) = far below 1.1M BTC capitulation level of 2022 ## How to use it Watch for patterns over weeks. Rising daily losses with declining price = capitulation approaching. Rising daily profits with declining trend = distribution phase ending. Successive lower profit peaks = bear market transition signal. The annual trend is the most reliable cycle signal. When annual profits begin forming lower peaks and are below its 30-day moving average, even as prices remain near highs, the cycle top has likely passed. 30-day data: Use alongside daily and annual figures for multi-timeframe confirmation. Monthly BTC-denominated losses approaching 1.1M BTC = structural capitulation approaching. ## OpenAPI ````yaml openapi/v2.json GET /community/bitcoin-realized-profit-loss 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-realized-profit-loss: get: tags: - Community-built Indicators summary: Realized Net Profit and Loss description: >- The net realized profit or loss of Bitcoin sellers in USD and BTC in daily, monthly and yearly windows. operationId: V2getBitcoinRealizedProfitLoss 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 spending behavior 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' positive_net_realized_profit: type: number example: 37514484.39 negative_net_realized_profit: type: number example: 0 yearly_realized_net_profit_btc: type: number example: 713808.98 yearly_realized_net_profit_usd: type: number example: 115843247516.25 monthly_realized_net_profit_btc: type: number example: -230680.73 monthly_realized_net_profit_usd: type: number example: -15584313788.43 security: - AccessToken: [] x-codeSamples: - lang: Shell source: >- curl -X GET "https://api.cryptoquant.com/v2/community/bitcoin-realized-profit-loss?window=day" \ -H "Authorization: Bearer " - lang: JavaScript source: >- fetch("https://api.cryptoquant.com/v2/community/bitcoin-realized-profit-loss?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-realized-profit-loss?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-realized-profit-loss?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-realized-profit-loss?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 `. ````