> For the complete documentation index, see [llms.txt](https://userguide.cryptoquant.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://userguide.cryptoquant.com/ja/nettowku/stock-to-flow-reversion.md).

# Stock to Flow Reversion

## 定義

Stock to Flow（SF）Reversion は、BTCの価格をSF比率で割った比率で定義されます。

$$
\text{SF Reversion} = \frac{\text{BTC価格 }}{\text{SF 比率}}
$$

## 解釈

SF Reversionは、市場価格とSF比率の相対的な差を測定する指標です。これまでのところ、SF比率は価格のトレンドを正しく推定しているため、価格がSF比率から逸脱した場合はベットするチャンスとなります。SF Reversion が価格と比較して高すぎる場合、市場価格はすぐに修正され、弱気の傾向を意味します。

![](/files/-Mi0sjX3XMY1iLCM1t5u)

## 使用例

#### マーケットのトップとボトムを予測する

まず、2つの変数を揃えるために、SF価格回帰の線形回帰モデルを構築します。下図のように2つの変数を1つのグラフにまとめると、SF価格回帰の偏差が明確にわかります。これらのポイントはそれぞれ強気（緑のボックス）と弱気（赤のボックス）の状態を明確に示しています。

## データへのリンク

* [CryptoQuantライブチャートでのSF Reversion](https://cryptoquant.com/overview/full/468?window=day)
* [CryptoQuant データAPI ドキュメントのSF Reversion](https://cryptoquant.com/docs#operation/getStockToFlow)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://userguide.cryptoquant.com/ja/nettowku/stock-to-flow-reversion.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
