# Revenue Share

At Flo, we believe in building **sustainable value** for both our users and our token holders. That’s why we’ve implemented a dual-reward system designed to **share platform revenue** directly with the community.

## &#x20;AI Tools Revenue

All Flo AI tools—including the drag-and-drop app builder and coding assistant—operate on a **$FLO token-based credit system**.

* 💰 **50% of all $FLO tokens spent** on AI tool usage is distributed back to **$FLO holders** as real revenue share.
* 🔥 The remaining **50% is burned**, reducing total supply and increasing scarcity over time.

## &#x20;Marketplace Revenue

The Flo Web3 Marketplace supports **multiple payment options** (ETH, USDC, $FLO, etc.) for maximum flexibility.

* 💰 **50% of marketplace revenue**—regardless of payment token—is distributed to **$FLO holders**.
* 🔁 The other **50% is used to buy back $FLO from the open market and burn it**, creating constant token demand and deflationary pressure.

***

#### Why This Matters

* Creates **real utility and consistent demand** for $FLO
* Rewards holders with **passive income** as usage scales
* Strengthens tokenomics with a **deflationary model**
* Aligns long-term growth with community incentives

The more builders use Flo—and the more jobs completed on our marketplace—the more value flows directly back to the community.

> **Hold $FLO. Power the ecosystem. Earn from the network.**


---

# 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://floai.gitbook.io/flo-ai/roadmap-and-tokenomics/revenue-share.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.
