> For the complete documentation index, see [llms.txt](https://docs.useglade.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.useglade.org/guides-for-the-app/sign-up.md).

# Signing up

Opening a Glade account takes a few minutes and assumes no prior knowledge of crypto. You won't be asked to write down a recovery phrase or buy a hardware wallet. Even so, the account is genuinely self-custodied: the keys belong to you, packaged in a way that works for ordinary people.

***

## Before you start

Have these ready:

| Item                            | Notes                                                                         |
| ------------------------------- | ----------------------------------------------------------------------------- |
| A device that supports passkeys | Face ID, Touch ID and Windows Hello all work, as does a hardware security key |
| An email address                | This becomes your sign-in and contact address                                 |
| Government-issued ID            | Needed for identity verification                                              |

***

## Setting up your account

### Step 1: Create your login

Type in your email, then make a passkey on the device you're using. Glade derives your keypair from that passkey. The result is cryptographic self-custody with nothing to memorize and nothing to store on paper.

### Step 2: Confirm who you are

Identity checks happen at account opening because Glade operates inside the GENIUS Act framework. That arrangement keeps your activity hidden from the public while still meeting legal accountability requirements. The verification provider will request two things:

* A clear picture of an ID issued by your government
* A liveness check (a brief selfie video)

Basic verification comes with standard limits. If you need more room, enhanced verification raises those limits in exchange for additional documents. It's available on Personal and Business accounts alike.

### Step 3: Pick your name

Choose a handle, such as `@yourname.glade`. It's how other people find and pay you, so no one needs to copy your raw EVM address. The rules for choosing one are in [Glade names](/guides-for-the-app/glade-names.md).

### Step 4: Add money

Move USDG in from an exchange or another wallet. Where it's supported in your region, a linked bank transfer is another option. Gas is paid in ETH, but Glade keeps a small ETH balance topped up on your behalf, so you never have to buy or manage it.

***

## What happens on-chain when you sign up

A few real pieces of infrastructure are created for you behind the scenes:

1. **A smart account on Robinhood Chain.** Its address is derived from your passkey.
2. **A confidential USDG token account** inside Glade's contracts. This is the piece that makes encrypted transfers possible.
3. **An off-chain profile record** tying your handle to your public key. It exists purely for lookups and display.

At this point your account has no balance and no transaction history. Privacy is the default from day one, so the very first transfer you make is encrypted, exactly like every one after it. There's no setting to switch on.

***

## Which account type you get

New accounts are Personal by default. If you're signing up for a company, select Business during signup instead; it adds shared access and higher limits. For a side-by-side look at Personal, Business and Agent accounts, see [Account kinds](/start-here/account-kinds.md).

***

## Next steps

* [Send and receive](/guides-for-the-app/send-and-receive.md)
* [Glade names](/guides-for-the-app/glade-names.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 by asking a question.

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

```
GET https://docs.useglade.org/guides-for-the-app/sign-up.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.