> For the complete documentation index, see [llms.txt](https://commseed.gitbook.io/multi-universe-central-muc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://commseed.gitbook.io/multi-universe-central-muc/9.-ecosystem2.md).

# 9. Ecosystem2

&#x20;The ecosystem of MUC, centered around NFT holders, is represented by the following:

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

&#x20;By utilizing web3, NFT owners may obtain IP Tokens by integrating their NFTs with content. In this way, holders can be connected and supported through MUC.

&#x20;The following is an explanation of each flow within the ecosystem centered around NFT holders:

1. Holders hold NFTs and connect them to content through web3.
2. Supply IP Tokens to each content.
3. Holders connected through the web3 wallet can acquire IP Tokens through

   various services provided by the content.
4. Acquired IP Tokens can be swapped for MUC through the LP of MUC.


---

# 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://commseed.gitbook.io/multi-universe-central-muc/9.-ecosystem2.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.
