> For the complete documentation index, see [llms.txt](https://metaportal.gitbook.io/welcome/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://metaportal.gitbook.io/welcome/useful-information/faqs.md).

# FAQs

**What the heck is an infinite player?**

In the book [*Finite & Infinite Games*](https://www.amazon.co.uk/Finite-Infinite-Games-James-Carse/dp/1476731713), James Carse describes how there are two kinds of players in life: “finite players (who) play **within** boundaries and infinite players (who) play **with** boundaries.”

**How does that apply to what's happening at MetaPortal?**

The Metaverse is going to be a massive set of ever-moving boundaries. We are here to explore those alongside a community of like-minded people. That means we need some revenue to sustain us and the intrinsic curiosity to explore without needing to play games of status.

**Why focus on index products?**

Indexes are a great way for newer crypto entrants to get exposure to a theme without needing to know a lot about it. They are beginner friendly, simple and provide a steady revenue stream.

**Why is \[insert project token here] not included in MVI/GAME?**

The methodology for token selection is laid out in the [product section](/welcome/products/metaverse-index-mvi.md) here on Gitbook. In short, we use objective criteria to determine valid tokens before doing a deeper dive on those that qualify. This includes looking at token distribution, team background and factors affecting liquidity. The combination of these two stages determines what will be included.

**Do you want to invest in XYZ project?**

Sure, pitch it in the #alpha channel in [Discord](https://discord.gg/7nqfvnF8y9.) and we can take a look.

**Wen MetaPortal token?**

We have been thinking about what tools are available to us that can bring the community together and help democratise access to what we are building. There are no plans for a token currently but we exploring options that we think would work well for MetaPortal.


---

# 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://metaportal.gitbook.io/welcome/useful-information/faqs.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.