> For the complete documentation index, see [llms.txt](https://guide.dem.exchange/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.dem.exchange/earn/nitron-lend-and-borrow/walkthroughs/mint-usdusc.md).
# Mint $USC
Introducing **Carbon stablecoin $USC**, the decentralised native stablecoin for the Cosmos Ecosystem! You can mint $USC right here on Nitron based on the amount of collateral you hold.
{% hint style="info" %}
Learn more about Mint [here](https://guide.carbon.network/features/money-market/functionalities-of-money-market/mint).
{% endhint %}
**Step 1:** Launch Demex, click “Earn” in the navigation menu and click “Nitron” under the dropdown bar.
The Nitron page opens up as shown below.
**Step 2:** Under the “Mint” window, you can view all the assets that you can mint at any given time. Currently, the only asset you can mint is the Carbon stablecoin ($USC)
**Step 3:** Click on the “Mint” button, which opens up to this window as shown below.
**Step 4:** Enter the desired amount of $USC that you wish to mint. The maximum amount that you can mint is limited to the amount of collateral you hold.
The window displays your new mint amount and new health factor on your input.
**Step 5:** Click the “Mint” button.
Congratulations! You have successfully minted $USC, Carbon Stablecoin.
---
# 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://guide.dem.exchange/earn/nitron-lend-and-borrow/walkthroughs/mint-usdusc.md?ask=&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.
.png?alt=media&token=69dccf44-34e5-46a4-964f-4c266fb60840)
.png?alt=media&token=dc944595-cb22-4245-9c83-7b8f50bb102f)
.png?alt=media&token=227b107e-b49a-4720-8a1c-219f01fb0fd8)
