> For the complete documentation index, see [llms.txt](https://despend.gitbook.io/despend/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://despend.gitbook.io/despend/welcome.md).

# Welcome

Amid the dual waves of the digital economy and consumption upgrade, the limitations of traditional e-commerce models have become increasingly apparent—centralized platforms monopolize profit distribution, consumer value is marginalized, and merchant acquisition costs continue to rise. These structural contradictions call for a fundamental transformation of the business paradigm. This is where DeSpend emerges, leveraging Web3 technology to redefine the relationship between consumption and value.

<figure><img src="/files/1Hd3D0WhuKBrfnloFxVn" alt=""><figcaption></figcaption></figure>

This is not merely a technological upgrade but a reconstruction of production relations. DeSpend breaks the traditional logic of "consumption as expenditure" and pioneers a new paradigm of "consumption as investment," transforming consumers from passive buyers into active ecosystem co-builders and benefit sharers.


---

# 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://despend.gitbook.io/despend/welcome.md?ask=<question>&goal=<endgoal>
```

`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.