> For the complete documentation index, see [llms.txt](https://docs.nansen.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nansen.ai/api/changelog/29-10-2026-perp-screener-annualized-funding.md).

# 29-10-2026: Perp Screener Returns the Annualized Funding Rate

`POST /api/v1/perp-screener` returned `funding` as the latest hourly Hyperliquid funding rate, while the Nansen app shows the same rate annualized. For BTC, `funding` was `0.0000125` (0.00125% per hour) where the app shows 10.95%.

The endpoint now returns the annualized rate, and you can filter and sort on it.

| Where                         | Deprecated (hourly) | New (annualized)                  |
| ----------------------------- | ------------------- | --------------------------------- |
| Response, every `trader_type` | `funding`           | `funding_rate_annualized`         |
| Request filter                | `filters.funding`   | `filters.funding_rate_annualized` |
| Sort field                    | `funding`           | `funding_rate_annualized`         |

`funding_rate_annualized` is the hourly rate x 24 x 365, as a decimal: `0.1095` means 10.95% per year. The sign is unchanged. **Positive means longs pay shorts, negative means shorts pay longs.**

Sorting by `funding_rate_annualized` gives the same order as sorting by `funding`. A `funding_rate_annualized` filter uses the annualized scale, for example `{"min": 0.1}` for rates of at least 10% per year. A request that sends both `filters.funding` and `filters.funding_rate_annualized` returns HTTP 422. A request that sends `filters.funding` gets a `Warning: 299` response header.

The deprecated response field, filter and sort value keep working, with the hourly scale, until they are removed. Removal will not happen before January 27, 2027. Switch to `funding_rate_annualized` before then. Credit costs are unchanged.


---

# 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.nansen.ai/api/changelog/29-10-2026-perp-screener-annualized-funding.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.
