> For the complete documentation index, see [llms.txt](https://docs.proliquid.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.proliquid.xyz/settings/funding.md).

# Funding

Settings for the screener application tab

<figure><img src="https://1571380119-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfwUo1o7rINODRyyILQE1%2Fuploads%2FJPLio9ccf5j7Wo74jcMv%2Fimage.png?alt=media&amp;token=5fb89396-fa57-4ec3-9969-730c219567eb" alt="Funding settings for selecting exchanges used in max-arb calculations."><figcaption><p>Funding settings for selecting exchanges used in max-arb calculations.</p></figcaption></figure>

Funding settings choose which of Hyperliquid, RISEx, Binance, Bybit, and OKX are considered when Proliquid calculates funding arbitrage opportunities.

The [Funding](/features/funding-rates-and-perp-opportunities.md) tab uses this selection to calculate `max arb`, including where to long, where to short, and the estimated daily / annualized opportunity from current rates.

Only select exchanges you can actually trade. If an exchange is enabled here but you cannot execute there, the max-arb output may show opportunities that are not practical for you.

Review this setting when you add or remove exchange accounts, change your strategy, or want to focus only on venues with enough liquidity for your size.


---

# 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.proliquid.xyz/settings/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.
