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

# Onboarding

Creek Mainnet introduces a complete suite of gold-powered DeFi primitives on Sui.

Letting you swap stablecoins and gold, stake XAUm to mint GR and GY tokens, borrow GUSD against your collateral, redeem back into XAUm, and trade GR/GY through DeepBook integration.

This guide walks you through every action available on the Creek mainnet app.

**App Guide includes:**

* Swap — convert between USDC, GUSD, and XAUm
* Stake — split XAUm into GR + GY
* Borrow — mint GUSD against collateral
* Redeem — recombine GR + GY back into XAUm
* Trade — buy and sell GR / GY (powered by DeepBook)
* Earn — GY Holdings, earn yield from gold volatility
* Stats — track your positions and history

<figure><img src="https://2610373334-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRbg69gAKJERCD6Rn7EKa%2Fuploads%2FgPzFc3XCzWCLxvfJvqcD%2Fa794120be4133ec64b2c21678b916be1.png?alt=media&amp;token=f49cdc44-ff6c-4565-b0b5-0153f34a6676" alt=""><figcaption></figcaption></figure>

<p align="right"></p>

<p align="right"></p>


---

# 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.creek.finance/mainnet-user-guide/onboarding.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.
