> For the complete documentation index, see [llms.txt](https://docs.chiliz.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chiliz.com/fr/apprendre/a-propos-des-stablecoins.md).

# À propos des Stablecoins

Vue d'ensemble des stablecoins sur Chiliz Chain, incluant USDT et USDC bridgés via Chainport, avec des liens vers les contrats de stablecoins supportés.

Les stablecoins sont des monnaies numériques conçues pour maintenir une valeur stable en étant ancrées (ou rattachées) à des actifs du monde réel, comme le dollar américain.

Contrairement à la plupart des cryptomonnaies, les stablecoins offrent une stabilité des prix, ce qui les rend idéaux pour les transactions, la conservation et le transfert de fonds sans variations significatives de valeur.

Les stablecoins maintiennent leur valeur grâce à des réserves de garantie, telles que des monnaies fiduciaires (par ex. USDT, USDC) ou des cryptomonnaies sur-collatéralisées. Certains reposent sur des algorithmes pour ajuster l'offre.

Consultez le tableau des stablecoins disponibles sur Chiliz Chain :

{% content-ref url="/pages/9qmvqkM4jj8ih9oTOeP6" %}
[Les stablecoins sur Chiliz Chain](/fr/apprendre/a-propos-des-stablecoins/stablecoins-sur-chiliz-chain.md)
{% endcontent-ref %}


---

# 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://docs.chiliz.com/fr/apprendre/a-propos-des-stablecoins.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.