# Liquidation

### <mark style="color:blue;">Client</mark>

Lending and Borrowing protocols

### <mark style="color:blue;">Monitoring (optional) + Liquidation</mark>

1. **Liquidation only:** Most clients with an existing integration with an oracle, self-monitor the health factors of their assets. If a certain threshold is reached, they send an Liquidation Intent trigger to Decimal to automatically fulfil the task of their assets liquidation and paying back their lenders per the best available market rate.
2. **Monitoring + Liquidation:** In some cases, the newer protocols have requested Decimal to also undertake responsibility of monitoring multiple oracles with predefined health factor triggers. Decimal solvers undertake the task of both monitoring the assets and automatically trigger the liquidation task when the right conditions are identified.&#x20;

This saves the clients significant cost and effort of integration and monitoring oracle prices while having the flexibility to dynamically switch service providers of their choice to maximise their gains.

***

[<mark style="color:orange;">In short</mark> – focus on your core work.](#user-content-fn-1)[^1]

[^1]:


---

# Agent Instructions: 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:

```
GET https://wiki.decimal.at/use-cases/liquidation.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.