# Revenue Model

<figure><img src="/files/FHdOjKAgB3rmpBQuZ4He" alt=""><figcaption></figcaption></figure>

### Equinox AI is structured around sustainable, on-chain revenue loops. The platform does not rely on token speculation, venture capital, or artificial inflation. Instead, it operates on usage-based economic flows that directly fund protocol growth and reward long-term participants.

***

#### Sources of Revenue

* **Premium Access Fees**\
  Paid by users to unlock extended features, including deeper analytics, advanced tracking capabilities, and cross-chain tooling.
* **Data Licensing (B2B)**\
  API or dashboard-based access to specific on-chain/off-chain datasets for DeFi protocols, security firms, and institutional users.
* **Privacy Opt-out Fees**\
  Users can burn $ENOX to mask their visibility in social and DeFi datasets, making privacy a monetised right.
* **Custom Intelligence Modules**\
  White-labelled solutions or private dashboards for clients with unique monitoring or intelligence needs.
* **Partner Network Integrations**\
  Revenue-sharing agreements via embedded Equinox AI tools in third-party frontends and wallets.

***

#### Revenue Usage

* **Protocol Development & Maintenance**\
  Covers engineering, data ingestion, infrastructure, and updates.
* **Buyback and Burn**\
  A portion of the revenue is used to buy back $ENOX from the market and burn it permanently, reducing supply.
* **Strategic Reserve Funding**\
  Emergency and scaling allocations funded via actual revenue rather than preminted reserves.

**The model ensures Equinox AI remains self-sustaining, user-aligned, and token-integrated without relying on speculative inflows.**


---

# 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://equinoxai.gitbook.io/equinox-ai-whitepaper/token-+-model/revenue-model.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.