> 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/2.5-a-new-economic-benchmark.md).

# 2.5 A New Economic Benchmark

**We’ve cracked the code. Your steps are now a measurable asset.** For the first time ever, we have a proven way to measure and turn your movement into real value. This is the blueprint for a fairer economy where *your* effort pays off. Backed by data from top universities and over 100,000 users worldwide, this benchmark shapes every part of the Movement Economy.

Here’s how it powers $SWEAT:

* **Rewards that match your value**: Your steps earn $SWEAT based on what movement is truly worth.
* **Community-driven decisions**: The data guides DAO votes, so you shape the future.
* **Fair deals for partners**: Businesses and insurers get clear, data-backed incentives to join.
* **Sustainable growth**: It fuels staking and token models that keep the economy strong.
* **Real-world impact**: Governments and health systems can use it to reward movement.

This benchmark isn’t only for $SWEAT, it’s a roadmap for the world to join the Movement Economy. As more people and organizations adopt $SWEAT, we’re growing users and building a new standard for value.


---

# 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/2.5-a-new-economic-benchmark.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.
