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

# Create an Account

## **Creating Your Account**

* **Navigate to KoinBay:** Start by visiting the KoinBay website and selecting 'Register'.
* **Registration Options:** You can sign up using your email address. It’s recommended to use a well-known email provider like Gmail or Outlook to ensure you receive all necessary communications, including One Time Passwords (OTPs).
* **Age Requirement:** You must be at least 18 years old to register and use KoinBay.

#### **📧 Registering with an Email Address**

1. Click 'SignUp' on the KoinBay homepage.
2. Fill in your email, create a password, and enter a Referral ID (if you have one).
   * **Password Requirements:** Your password should have at least 8 characters, including one uppercase letter and one number.
3. Complete the security verification by entering the code sent to your email within 30 minutes. Check your Spam/Junk folder if you don’t see it, or resend the email if needed.
4. Once verified, your account is successfully created.

####

{% hint style="success" %}
For enhanced security, enable two-factor authentication (2FA) in your account settings.
{% endhint %}


---

# 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.koinbay.com/get-started/create-an-account.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.