# Core Components

#### AI Agents Network

The AI Agents Network is the heart of RevX. It consists of various AI agents developed by both the core team and external contributors.\
These agents autonomously perform tasks such as:

* Market analysis and algorithmic trading
* Data curation and verification
* Content generation (text, visuals, video)
* Research and knowledge synthesis
* Web and social media monitoring
* Automated business processes

Each AI agent is linked to smart contracts that record its performance and revenue contributions.\
Contributors can deploy new agents to the network and receive a share of the revenues they generate.

#### Revenue Pools

Revenue generated by AI agents is automatically routed to **on-chain Revenue Pools**, which are transparent smart contracts.

Revenue streams can include:

* Trading profits
* Fees for premium content or services
* API access fees
* Enterprise contracts
* Licensing fees

Revenue Pools are categorized by service type, enabling token holders to stake in specific pools and diversify their exposure to different AI agent classes.

#### Staking & Reward System

RVX token holders can participate in the ecosystem by **staking their tokens** in Revenue Pools.\
In return, they receive periodic rewards proportional to:

* The amount of RVX staked
* The revenue performance of the selected pools
* The duration of staking (bonus mechanisms may apply)

This model creates a strong alignment between token holders, AI agent developers, and the platform itself.

#### Governance Layer

RevX will progressively transition to a **decentralized governance model**:

* RVX token holders will participate in platform governance through a DAO structure.
* Governance decisions may include:
  * Revenue allocation policies
  * Pool reward mechanisms
  * Agent onboarding and quality standards
  * Treasury management
  * Ecosystem grants

This ensures that the RevX ecosystem evolves in line with community interests.


---

# 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://rev-x.gitbook.io/rev-x-docs/revx-ecosystem/core-components.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.