> 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.3-rungp-movement-on-the-global-stage.md). # 6.3 RunGP: Movement on the Global Stage SWEAT is a founding partner of the **Global Running League (GRL), also known as RunGP**, a new era of high-profile running events set to launch on **Formula 1 racetracks in 2025**. RunGP, with four time Olympic gold medalist and running legend Mo Farah as its Ambassador, is a convergence of elite competition, mass participation, and blockchain rewards. Runners earn $SWEAT based on performance. Fans engage and earn through real-time interaction. Leaderboards, live data, and gamified engagement connect sports with token incentives, turning RunGP into a showcase of what the Movement Economy looks like in action, at global scale. With access to SWEAT’s user base and a broadcast-ready format, RunGP will bring the Movement Economy to millions more, fusing **physical activity with digital 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/6.-partnerships-a-movement-powered-by-strategic-collaboration/6.3-rungp-movement-on-the-global-stage.md?ask=&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.