> 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/zh/market-data/zi-jin-fei-lv.md).

# 资金费率

资金费率是交易者为了使永续期货合约的价格接近指数价格，而定期支付的费用。

## Definition

Funding rates are periodic payments to long or short traders based on the difference between the perpetual contract market and the spot price. Funding rates make the perpetual futures contract price close to the index price. All cryptocurrency derivatives exchanges use funding rates for perpetual contracts. Funding rates in the given period and exchange. The standard unit is a percentage.

## Interpretation

Funding rates represent traders' sentiments of which position they bet on in the perpetual swaps market. Positive funding rates imply that many traders are bullish and long traders pay funding to short traders. Negative funding rates imply many traders are bearish and short traders pay funding to long traders.

## Link to Our Data

* [Funding Rates in CryptoQuant Live Chart](https://cryptoquant.com/overview?search=Funding+rates)
* [Funding Rates in CryptoQuant Data API docs](https://cryptoquant.com/docs#operation/getFundingRates)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://userguide.cryptoquant.com/zh/market-data/zi-jin-fei-lv.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.