> For the complete documentation index, see [llms.txt](https://docs.synfutures.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.synfutures.com/rwa-trading/getting-started.md).

# Getting Started

Follow the simple steps below to get started:

1. **Connect your wallet** to SynFutures.
2. **Go to RWA Trading** from the SynFutures navigation menu.
3. **Deposit USDC** into your RWA trading account/web3 wallet, and receive [**mUSD**](/rwa-trading/faq.md#what-is-musd).
4. **Choose a tokenized stock** from the available RWA markets.
5. **Place your order.** For a market order, enter the amount you want to buy or sell and confirm. For a limit order, enter both the amount and the price at which you want the order to execute.
6. **Receive your tokens.** Once filled, your tokenized stocks will appear in your SynFutures portfolio.
7. **To sell**, place a sell order for your tokenized stock. Once the order is filled, you will receive USDC back in your wallet.


---

# 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.synfutures.com/rwa-trading/getting-started.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.