> For the complete documentation index, see [llms.txt](https://docs.sweep.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sweep.finance/entrance/why-sweep.md).
# Why Sweep?
The digital interaction and gaming industries are undergoing a fundamental transformation, yet most platforms continue to operate on models that extract value without distributing it. Users generate massive activity, engagement, and liquidity, but remain disconnected from the economic systems they help sustain. Even many Web3 projects fail to resolve this imbalance, often replicating traditional structures under a decentralized framework.
Sweep represents a paradigm shift by introducing a unified, transparent, and economically aligned ecosystem where interaction, financial activity, and value creation are directly connected. Rather than treating systems as isolated products designed for short-term engagement, Sweep establishes a continuously operating structure where every user action contributes to a broader economic framework.
At the core of this system lies the SWEEP token, not as a secondary utility, but as the foundation of the entire ecosystem. All interactions across the platform are powered by SWEEP, creating continuous demand driven by real usage. Unlike inflationary models that depend on artificial incentives, Sweep is built around a usage-driven deflationary mechanism that operates as a permanent system behavior.
In addition to its deflationary structure, Sweep integrates a volume-linked distribution model that aligns ecosystem activity with user incentives. A fixed portion of transaction activity is automatically allocated to a distribution pool and distributed to SWEEP holders in USDT through transparent and automated logic. As long as system activity continues, participation directly translates into measurable outcomes.
Beyond interaction systems, Sweep expands into a broader financial layer through integrated payment infrastructure and tokenized value frameworks. This enables users to not only interact within the system, but also move, utilize, and participate in value across different contexts.
Every transaction within the ecosystem contributes to the system’s core mechanisms. A fixed portion is permanently removed from circulation, while another portion is redistributed, ensuring that both scarcity and distribution are continuously driven by real activity. This structure operates without reliance on external triggers, predefined schedules, or market-dependent interventions.
This positions Sweep not only as a transformation of digital interaction models, but as a foundational economic layer within the broader Web3 landscape. A system where value is generated through real usage, scarcity is enforced through activity, and all processes are transparent and verifiable.
By combining structured interaction systems, financial infrastructure, and programmable value frameworks, Sweep establishes a model where engagement, trust, and economic sustainability coexist. It is not designed around short-term cycles, but around continuous operation and long-term scalability.
\
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.sweep.finance/entrance/why-sweep.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.