> 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/6.-partnerships-a-movement-powered-by-strategic-collaboration/6.4-sweatcoin-the-on-ramp-that-started-it-all.md).

# 6.4 Sweatcoin: The On-Ramp That Started It All

Before Sweat Wallet, there was **Sweatcoin**, the original movement validator founded in 2014 that introduced hundreds of millions of people to the value of their steps.

With over **200 million users worldwide**, Sweatcoin remains the **entry point to Sweat Wallet and the Movement Economy**, turning casual daily movement into tangible $SWEAT earnings. Its movement validation technology is the backbone of $SWEAT’s minting system—ensuring every token is rooted in real, verified physical effort.

Sweatcoin is a constant funnel of new users into Web3, helping to bridge the gap between simple movement and advanced crypto utility. For many, Sweatcoin is their first taste of a decentralized future and the first step toward full participation in the Movement Economy through Sweat Wallet.


---

# 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/6.-partnerships-a-movement-powered-by-strategic-collaboration/6.4-sweatcoin-the-on-ramp-that-started-it-all.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.