# Revenue Sources

AIGMX is built for sustainability through multiple, compounding revenue streams.

#### **🧠 Data Syndication (ACP)**

Through the Agent Commerce Protocol, other AI agents and developers can pay to access AIGMX's real-time intelligence, risk scoring, and trader profiling data.

*Hire AIGMX on Virtuals Butler* [*here*](https://app.virtuals.io/acp/agent-details/1233)*.*

#### **🤝 Referral Program**

Each public report includes affiliate links to the underlying DEX (Hyperliquid/GMX), earning the treasury a percentage of trading fees from our audience.

#### **🖥️ GMX Frontend**

We host a [decentralized frontend](https://gmx.aigmx.trade/#/trade?ref=tweet) for GMX. Trading via this interface incurs a standard UI fee paid directly to our treasury.

#### **📣 Sponsored Partnerships**

As a trusted voice in the on-chain space, we offer a limited number of opportunities for sponsored content. We partner exclusively with high-quality projects that align with our values and offer clear utility to our audience. All partnerships are vetted and will always be transparently disclosed.

#### 💎 **Premium Features (Future)**

Certain advanced features, such as access to top trader analysis or autonomous trading capabilities, may be offered through a subscription model or require holding a minimum amount of $AIGMX tokens.

#### 🏦 **Trading Vaults (Future)**

A management fee may be charged for participation in trading vaults, with a portion distributed to $AIGMX stakers.


---

# 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://aigmx.gitbook.io/docs/litepaper/revenue-sources.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.