> For the complete documentation index, see [llms.txt](https://vaultbook.gauntlet.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://vaultbook.gauntlet.xyz/fr/vaults/morpho-vaults/vault-curation-considerations-a-deeper-dive/market-rate.md).

# Taux du marché

Les rendements d’emprunt et de fourniture devraient s’aligner sur les taux du marché afin de retenir les fournisseurs et les emprunteurs :

* Les APY de fourniture et d’emprunt des stablecoins ne devraient pas différer de plus de 1 à 3 % des taux des stablecoins sur d’autres protocoles DeFi.
* Les rendements de staking du WETH (actuellement autour de 4 %) devraient constituer une borne supérieure pour les taux d’emprunt du WETH en utilisant des garanties wstETH (LRT/LSTs).

Les marchés Morpho sont des marchés à garantie unique / de fourniture unique (par opposition aux marchés mixtes), ce qui augmente l’efficacité du capital. Les taux peuvent être ciblés pour être supérieurs à la fois pour l’emprunt (plus bas) et pour la fourniture (plus élevés). Garantir des taux d’emprunt et de fourniture compétitifs aide à retenir les emprunteurs, facilitant un rendement durable pour les fournisseurs dans le vault.


---

# 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://vaultbook.gauntlet.xyz/fr/vaults/morpho-vaults/vault-curation-considerations-a-deeper-dive/market-rate.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.