> 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/3.-sweat-wallet-gateway-to-the-movement-economy.md).

# 3. Sweat Wallet: Gateway to the Movement Economy

**Step into a world where your movement unlocks real value.** The Sweat Wallet is more than just an app. It’s your access point to the Movement Economy, where every move you make turns into something valuable. Think of it as a one-stop hub that turns your steps into $SWEAT, letting you earn, spend, trade, and even shape the future, all from your phone. More than a wallet; it’s a **game-changer** that blends fitness, finance, and freedom into one seamless experience.

Built for simplicity and scale, the Sweat Wallet makes Web3 feel as easy as your favorite legacy app. The backend hums with cutting-edge blockchain tech, but the front end? It’s clean, intuitive, and mobile-first. **You’ll engage with Web3 without even noticing the complexity**. Whether you’re new to crypto or a seasoned pro, the Sweat Wallet empowers you to turn every move into tangible economic power.


---

# 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/3.-sweat-wallet-gateway-to-the-movement-economy.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.
