# The Revenue

With the launch of the $AVED Token, all of our early community members will have an opportunity to benefit from the adoption of Web3 and their relationship with dCommunity. &#x20;

As we connect legacy business and brands with the parallel economy, the new commerce models will allow for users to monetize their time, attention and data.  This will be built into our revenue models.

Some areas where dCommunity has a clear path to monetization:

### dCommunity

* Onboarding and Wallet Services
* White-Label upsells to our increasing client base
* Open and Bespoke Marketing Services
* NFT and Tokenization Services
* Data and Cross Promotion Services

### AvenueD

* Gamified Marketing Platform
* Advertising and Marketing Revenues
* Open and Bespoke Metaverse Services
* Rewards Program Fees
* Token Revenues
* Transaction Fees

The model is writing itself and the adoption of these technologies does the heavy lifting of market creation for us.  dCommunity will lift up it's users, participants and investors by capturing a piece of the value which is #disintermediated by the emerging system - and distributing it to our ecosystem partners.  Incentive meets execution!

<figure><img src="/files/ni6cqwNrrwsiBzqwGbIq" alt=""><figcaption><p>A different kind of opportunity:  The kind only found in the adoption of a disruptive technology.</p></figcaption></figure>


---

# Agent Instructions: 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:

```
GET https://dcommunity.gitbook.io/dcommunity-where-main-street-meets-metaverse/the-revenue.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
