> For the complete documentation index, see [llms.txt](https://docs.flock.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flock.io/flock-tokenomics/network-participation/fomo/real-model-asset-rma-issuers.md).

# Real Model Asset (RMA) Issuers

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

RMA Issuers are the participants who launch model-backed token economies through FOMO. In earlier drafts, this role is also referred to as the **Model Token Owner (MTO)**. They act like franchise operators for AI inference: they select a model, configure its deployment, launch its $MT, and help drive adoption.

#### What RMA Issuers Do

An RMA Issuer initiates a Real Model Offering by configuring:

| Parameter               | Description                                                             |
| ----------------------- | ----------------------------------------------------------------------- |
| Model architecture      | The model to be deployed, such as Qwen, Llama, or a domain-specific SLM |
| Hosting tier            | The compute setup and cost structure                                    |
| Minimum inference price | The economic floor for serving the model                                |
| Fundraise bounds        | Minimum and maximum raise targets                                       |
| Launch parameters       | Token sale, bonding curve, and initial liquidity setup                  |

After configuration, the issuer launches the $MT fundraising process. If successful, the model becomes available through the FLock API Platform.

#### Why RMA Issuers Launch on FOMO

RMA Issuers launch on FOMO because it gives them a way to monetize model distribution directly.

Instead of only charging API fees, an issuer can benefit from multiple economic channels:

| Incentive          | Description                                                     |
| ------------------ | --------------------------------------------------------------- |
| Creator fee        | A portion of internal market trading fees during launch         |
| $MT allocation     | A vested allocation of the model’s token                        |
| Net revenue yield  | A share of net inference revenue                                |
| Emission bonus     | A share of model-level $FLOCK emissions                         |
| Token appreciation | Upside from increased model usage and $MT buyback/burn pressure |

This makes the RMA Issuer more than a passive model uploader. They become the economic operator of a model franchise.

#### RMA Issuer Incentive Alignment

RMA Issuers are rewarded when their model is actually used.

A successful issuer should therefore focus on:

* Selecting models with real demand.
* Setting competitive inference pricing.
* Driving API usage through distribution and partnerships.
* Supporting the $MT community.
* Maintaining long-term model quality and reliability.

The issuer’s upside depends on model traction, not just launch speculation. This is what makes FOMO closer to a real model asset market than a generic token launchpad.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.flock.io/flock-tokenomics/network-participation/fomo/real-model-asset-rma-issuers.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.