> For the complete documentation index, see [llms.txt](https://gitbook-docs.coinmetrics.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gitbook-docs.coinmetrics.io/tutorials-and-examples/tutorials/obtaining-predicted-funding-rates-for-futures.md).

# Obtaining Predicted Funding Rates for Futures

{% embed url="<https://github.com/coinmetrics/demo/blob/master/Predicted_Market_Funding_Rates.ipynb>" %}

### Instructions

The notebook linked above shows how to obtain predicted funding rates for futures. While the *actual* funding rates don't change very frequently, the *predicted* funding rate is calculated every minute or so and therefore can be a leading indicator for funding rate changes.

The notebook also compares two plotting libraries: matplotlib and plotly express.

The notebook was published for [Google Colab](https://colab.research.google.com/). If you want to use it in Colab, the easiest way is to open Colab and load the notebook from the Github URL (pasted into the open dialog). This method does not require cloning the repo first.

If you prefer to use the notebook with Jupyter, all you need to change is the way in which the API key is retrieved.


---

# 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://gitbook-docs.coinmetrics.io/tutorials-and-examples/tutorials/obtaining-predicted-funding-rates-for-futures.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.
