> For the complete documentation index, see [llms.txt](https://docs.helixapp.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.helixapp.com/getting-started/sign-up.md).
# Sign Up
The first step in onboarding to Helix is signing up. This is very similar to what you would do on any other website, and can be done with an email address or a Web3 wallet.
Just click the  button in the top right-hand corner of the Helix app to get started.
### Via Email
When the pop-up window appears, you will see two options for signing up with email. You can choose to proceed using Google SSO or by typing your email in directly. Selecting either option will automatically create a fresh wallet address for your account without the need to download a separate browser extension.
Pick your preferred email method and click "Continue" to finish creating your account. That's it, at this point you are ready to move on to the next step: [Add Funds](/getting-started/add-funds.md)
### Via Wallet
When the pop-up window appears, you will see several options for signing up with a wallet. Helix supports 10+ wallets, including most popular providers like MetaMask, Keplr, Ledger, and Phantom.
Select your wallet of choice and sign the message granting Helix permission to connect. That's it, at this point your account has successfully been created, and you are ready to move on to the next step: [Add Funds](/getting-started/add-funds.md)
---
# 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.helixapp.com/getting-started/sign-up.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 `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.
