# The FLock Platform

The FLock Platform is the infrastructure and coordination layer behind FOMO.

It provides:

* Model deployment infrastructure.
* API usage accounting.
* Launchpad mechanics.
* Revenue routing.
* Buyback and burn execution.
* Reward distribution.
* Integration with AI Arena and the broader FLock ecosystem.

In the FOMO whitepaper, the platform is described as the layer responsible for model deployment, revenue accounting, buyback logic, emission distribution, and transparent execution of tokenomic flows.

#### Platform Revenue

The FLock Platform captures value through several channels:

| Source                  | Description                                                 |
| ----------------------- | ----------------------------------------------------------- |
| Launch fee              | A one-time $FLOCK fee paid by RMA Issuers                   |
| Protocol trading fee    | A portion of internal market trades during the launch phase |
| Treasury share          | A portion of net inference revenue                          |
| Platform $MT allocation | Treasury allocation from each $MT supply                    |
| $FLOCK buyback and burn | Protocol-level value capture from inference revenue         |

This aligns the platform with actual model usage. FLock benefits when FOMO models generate demand, revenue, and sustainable token economies.

#### Platform Role in Emissions

The platform distributes daily rewards across supported $MTs according to competition-based activity.

Each $MT distributes three types of rewards:

1. Global $FLOCK emission.
2. Per-$MT $FLOCK incentive.
3. Per-$MT token incentive.

During the transition phase, emissions come from the emission gap period. Over time, the system can evolve toward a more mature emission schedule where model usage, staking alignment, and gmFLOCK commitment determine reward share more precisely.

#### FOMO and AI Arena

FOMO is the demand-side counterpart to AI Arena.

AI Arena incentivizes model creation, training, and improvement. FOMO incentivizes model deployment, distribution, and usage.

Together:

{% code overflow="wrap" %}

```
AI Arena produces intelligence.
FOMO distributes intelligence.
API usage validates demand.
Revenue and emissions route value back into the ecosystem.
```

{% endcode %}

This closes the loop between model supply and model demand.

gmFLOCK can be shared across both FOMO and AI Arena, reinforcing ecosystem-wide alignment. A participant who supports the broader FLock economy can receive benefits across multiple parts of the protocol rather than being siloed into a single model market.

#### Why This Matters for FLock

FOMO strengthens FLock in four ways.

First, it gives the ecosystem a demand-side engine. Instead of only incentivizing model production, FLock can now incentivize actual usage.

Second, it turns the API Platform into an economic layer. API usage is no longer just revenue; it becomes the signal that determines emissions, buybacks, and model-token value.

Third, it creates a new route for model commercialization. Model developers, distributors, and AI companies can launch real model assets rather than relying only on centralized API pricing.

Fourth, it makes $FLOCK more deeply embedded in the ecosystem. $FLOCK is used for launches, emissions, incentives, and buybacks, while FOMO activity creates ongoing demand and deflationary pressure for the macro token.


---

# 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://docs.flock.io/flock-tokenomics/network-participation/fomo/the-flock-platform.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.