> For the complete documentation index, see [llms.txt](https://docs.stakestone.io/stakestone/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stakestone.io/stakestone/stone-wallet/frequently-asked-questions/how-to-create-your-account.md).

# How to Create Your Account

Getting started with Stone Wallet is fast, easy, and crypto-optional. You can sign up in seconds using one of your existing social accounts.

{% stepper %}
{% step %}

### **Choose login method**

You can sign up using:

* Google
* X (Twitter)
* Telegram
* Email

No password or private keys to remember, just link your socials.
{% endstep %}

{% step %}

### **Verify and Create Your Account**

Once you choose a login method:

* We'll verify your identity with your selected platform
* If it's your first time, we'll auto-create your Stone Wallet smart account.
  {% endstep %}

{% step %}

### **Start Receiving Payments**

After logging in, you can start receiving and sending payments right away! You will get a unique Stone Wallet payment link and QR code to share with payees.
{% endstep %}
{% endstepper %}


---

# 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.stakestone.io/stakestone/stone-wallet/frequently-asked-questions/how-to-create-your-account.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.