> For the complete documentation index, see [llms.txt](https://whitepaper.swe.at/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.swe.at/usdsweat-whitepaper/5.-growth-opportunity/5.2-onboarding-simplicity-designed-for-scale.md).

# 5.2 Onboarding: Simplicity Designed for Scale

Unlike most Web3 projects that require technical know-how and upfront capital, the Movement Economy invites anyone to join, instantly. Download the Sweat Wallet, start walking, earn and engage.

With social logins, intuitive UX, and Web2-like simplicity, onboarding feels familiar, even as users start earning token-backed assets and engaging in decentralized features. No complicated wallets, no seed phrases, no friction—just movement and reward.

**This is not only how SWEAT reached tens of millions of users, it’s why the model can scale to hundreds of millions more.**


---

# 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://whitepaper.swe.at/usdsweat-whitepaper/5.-growth-opportunity/5.2-onboarding-simplicity-designed-for-scale.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.
