> For the complete documentation index, see [llms.txt](https://docs.infinitypools.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.infinitypools.finance/protocol-overview/mechanism-details/rate-router.md). # Rate Router InfinityPools traders that interact with the team provided website or API will have access to an off-chain component called the rate router that sources liquidity for trades in a “peer to pool” manner. This router eliminates almost all liquidity fragmentation, gives traders the best available interest rates for their trades and [replenishes their position](/protocol-overview/mechanism-details/loan-maturity.md#replenishing-process). The rate router makes liquidity fragmentation a non issue thanks to the following protocol features: 1. Liquidity ranges that enable higher levels of leverage (eg. 1000x) can also be used for all levels of leverage below it (1-999x leverage). 2. Traders can combine separate liquidity ranges to create a given leverage multiple. For example, if the market price of ETH is 1000 USDC and a trader is looking to go 10x long, they can borrow liquidity centered at 900 USDC or they can borrow liquidity centered at 850 USDC and some centered at 950 USDC in the right proportions. All of this is abstracted away when using the rate router. When a trader places an order with a given leverage multiple, it searches and combines different liquidity ranges on the trader’s behalf to give them the best interest rates possible. You can think of it a bit like Uniswap’s price router but for InfinityPools interest rates. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.infinitypools.finance/protocol-overview/mechanism-details/rate-router.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.