> 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.1-movement-economy-a-global-value-shift-in-motion.md).

# 5.1 Movement Economy: A Global Value Shift in Motion

At the core of the Movement Economy lies a simple, universal truth: **everyone moves**. Movement is one of the most natural human behaviors: borderless, inclusive, and habitual, making it the ideal gateway into a new form of economic participation.

By converting movement into $SWEAT, the ecosystem turns effort into ownership. What used to be a personal health benefit now becomes an asset. One that users can spend, stake, govern, or trade. This shift is unlocking a powerful behavioral economy, where activity becomes currency, and participation becomes empowerment.

With over **20 million users already onboarded in Sweat Wallet**, the Movement Economy is proving that this is not a niche, it’s a paradigm shift. As more people recognize the value of their movement, and as new use cases, features, and partners are added, the potential to onboard **hundreds of millions more** becomes inevitable.


---

# 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.1-movement-economy-a-global-value-shift-in-motion.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.
