> For the complete documentation index, see [llms.txt](https://docs.kaiko.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kaiko.com/whats-new/2026/october-2026.md).

# October 2026

2026-10-06

### Funding Rate Update

The `funding_rate` field on the Derivatives Risk endpoint, `/v2/data/derivatives.v2/risk`, documented under Exchange-provided metrics, has been corrected to return the settled funding rate, the value charged at the last settlement, rather than the predicted rate for the upcoming period. The change rolled out on 2026-10-06 between `08:31Z` and `08:35Z` depending on the exchange. In hourly or coarser intervals, the `08:00Z` bucket is the first to carry the new behaviour.

The correction applies to Bybit (`bbit`), OKX (`okex`), Bitget (`bgdm`), Gate (`gtdm`), Bullish (`bull`), Deribit (`drbt`), HTX (`hbdm`) and Hyperliquid (`hldv`), where `funding_rate` was previously returning the predicted rate. Binance (`binc`), Kraken (`crfl`) and Coinbase Derivatives (`cbde`) already returned the settled rate and are unaffected.

The predicted rate remains available in `predicted_funding_rate`.

The change was made at collection, so it applies both to `/v2/data/derivatives.v2/risk` and to the Exchange-provided metrics stream.

The same work added four fields, `funding_rate_ts`, `next_funding_time`, `funding_interval` and `is_actual_funding_rate`. These are available on the Exchange-provided metrics stream.&#x20;

Data before 2026-10-06 retains the previous behaviour on the affected exchanges, with `funding_rate` carrying the predicted rate. A query spanning that timestamp will return both behaviours in the same field.


---

# 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://docs.kaiko.com/whats-new/2026/october-2026.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.
