> 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/2.-the-movement-economy.md).

# 2. The Movement Economy

#### The Movement Economy isn’t only a distant idea. It’s a seismic shift in how value is created.&#x20;

Imagine a world where every step you take not only drives your health but fuels a global economy, turning daily activity into real, financial opportunity. That’s what we’re building with $SWEAT. This is more than rewarding exercise, it’s redefining movement as wealth you can hold, accessible to anyone, anywhere.

We’re flipping the script on a global crisis: 1.8 billion people trapped in inactivity, draining economies with billions in losses. The Movement Economy takes a global challenge and transforms it into a multi-trillion-dollar opportunity, one step at a time. Your steps are your stake in a revolution. With 20 million people already stepping in, this isn’t a distant dream—it’s a living, breathing reality reshaping lives right now.


---

# 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/2.-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.
