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

# Documentation

- [Technical Overview](https://docs.ursa.finance/ursa/documentation/technical-overview.md): Delve into the depths of the protocol and how it functions.
- [Supply](https://docs.ursa.finance/ursa/documentation/technical-overview/supply.md): In order to earn interest on a position, you must supply it.
- [Collateral ](https://docs.ursa.finance/ursa/documentation/technical-overview/collateral.md): In order to borrow assets, you must first collateralize your supplied position.
- [Borrow](https://docs.ursa.finance/ursa/documentation/technical-overview/borrow.md): Making and managing debt positions.
- [Interest](https://docs.ursa.finance/ursa/documentation/technical-overview/interest.md): Jump Rate Interest Model Overview
- [Reserves](https://docs.ursa.finance/ursa/documentation/technical-overview/reserves.md): A portion of all interest paid is directed to Ursa's reserves.
- [Liquidation](https://docs.ursa.finance/ursa/documentation/technical-overview/liquidation.md): Liquidations occur when borrow balances exceeds the amount allowed by the collateral factor.
- [Staking](https://docs.ursa.finance/ursa/documentation/technical-overview/staking.md): Ursa's Staking module
- [Emission Gauge Voting](https://docs.ursa.finance/ursa/documentation/technical-overview/staking/emission-gauge-voting.md): Weekly emissions voting for the URSA wars!
- [Proof of Liquidity](https://docs.ursa.finance/ursa/documentation/technical-overview/proof-of-liquidity.md): An overview of the Ursa Proof of Liquidity Flywheel.
- [Contracts](https://docs.ursa.finance/ursa/documentation/contracts.md): An in-depth view of Ursa's open-sourced Contracts.
- [Lens](https://docs.ursa.finance/ursa/documentation/contracts/lens.md): Ursa's lens into the blockchain.
- [Comptroller](https://docs.ursa.finance/ursa/documentation/contracts/comptroller.md): The risk management layer of the protocol.
- [Events](https://docs.ursa.finance/ursa/documentation/contracts/comptroller/events.md): The protocol's Comptroller emitted events.
- [Error Reporting](https://docs.ursa.finance/ursa/documentation/contracts/comptroller/error-reporting.md): The protocol's Comptroller error reporting.
- [Oracles](https://docs.ursa.finance/ursa/documentation/contracts/oracles.md): How the protocol uses oracles to accurately price assets
- [Interest Rate Models](https://docs.ursa.finance/ursa/documentation/contracts/interest-rate-models.md): Interest rates fluctuate based on borrowing utilization.
- [lTokens](https://docs.ursa.finance/ursa/documentation/contracts/ltokens.md): An overview of lToken contracts and associated methods
- [Market and Account State](https://docs.ursa.finance/ursa/documentation/contracts/ltokens/market-and-account-state.md)
- [Events](https://docs.ursa.finance/ursa/documentation/contracts/ltokens/events.md): The protocol's lToken emitted events.
- [Error Reporting](https://docs.ursa.finance/ursa/documentation/contracts/ltokens/error-reporting.md): The protocol's lToken error reporting.


---

# 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.ursa.finance/ursa/documentation.md?ask=<question>&goal=<endgoal>
```

`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.