> For the complete documentation index, see [llms.txt](https://debit.teller.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://debit.teller.org/how-debit-works/borrowing-against-a-pool.md). # Borrowing against a pool A borrower chooses a pool whose collateral token they hold and whose supply token they want to borrow. After entering a collateral amount, the app derives the borrowable amount from that pool's collateralization ratio and its LTV oracle route. In a single Deposit and Borrow transaction, the collateral is locked into the Teller escrow contract and the borrowed asset is sent to the borrower's wallet directly from the pool. Loans are over-collateralized, so the collateral value is higher than the amount borrowed, with WBTC and WETH among the common collateral assets against stablecoin or WETH liquidity. From the underlying protocol's perspective the pool itself is the lender: the pool's smart contract acts as a smart-wallet lender on an otherwise standard loan. --- # 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://debit.teller.org/how-debit-works/borrowing-against-a-pool.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.