> For the complete documentation index, see [llms.txt](https://crowdmuse.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://crowdmuse.gitbook.io/docs/user-docs/sign-in-with-wallet-or-email.md).
# Sign in with wallet or email
For buyers with a crypto wallet, simply click the Connect Wallet option when you sign in and choose from the wallet options provided.
For buyers without a crypto wallet, simply sign in using your email address directly or click on the Gmail icon for immediate email sign in. Alternatively you can also use social sign in with your Twitter account.
Our wallet and sign in integration partner, [Privy](https://privy.io/), helps make onboarding simple for buyers and users that don’t own a crypto wallet. Once a user clicks signs in with email or social, a wallet is generated to secure your digital assets when you purchase on [crowdmuse.xyz](https://crowdmuse.xyz/)
---
# 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://crowdmuse.gitbook.io/docs/user-docs/sign-in-with-wallet-or-email.md?ask=&goal=
```
`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.