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

# Getting Started

Learn to connect to OpenTrade and get ready to invest.

Getting started on OpenTrade is a straightforward process. Before getting started, you must first be onboarded. You can learn more about onboarding [here](/getting-started/onboarding.md). 

Our team will inform you when onboarding is complete. After onboarding, follow these steps to  connect to OpenTrade and get ready to invest. 

1. Visit the OpenTrade Web Application
2. Connect the digital asset wallet you want to whitelist. This will be the wallet you use to interact with the OpenTrade platform going forward. 
3. Read the Platform [Terms of Service](/terms-and-conditions/platform-terms-of-service.md)
4. Accept the Platform [Terms of Service](/terms-and-conditions/platform-terms-of-service.md) and approve the transaction in your wallet. 
5. After accepting the Platform Terms of Service, OpenTrade will whitelist your wallet onto one or more Vaults. 
6. OpenTrade will inform you via email when this is complete. You are now ready to invest. 


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.opentrade.io/getting-started/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 `build a script that syncs our docs to a CMS` 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.