> For the complete documentation index, see [llms.txt](https://broke-ceo.gitbook.io/broke-ceo-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://broke-ceo.gitbook.io/broke-ceo-docs/nft-ecosystem.md).

# NFT Ecosystem

## The BROKE CEO NFT

<figure><img src="https://3912587727-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaCkwEOotyUZP6FOZ4a0Y%2Fuploads%2FmdKjqMliPVO4OPTmpMN0%2Fbaner%20ceo%20whitepaper.png?alt=media&amp;token=e6346701-51ef-46ba-bc53-baf54c50b49f" alt=""><figcaption></figcaption></figure>

The first planned NFT collection is the **BROKE CEO NFT**.

It represents the beginning of the collectible side of the BROKE CEO universe and is planned after the $CBROKE launch and BROKE Store stage.

## BROKE → RICH

<figure><img src="https://3912587727-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaCkwEOotyUZP6FOZ4a0Y%2Fuploads%2FwDLnM9Y6IhvfSuX5LdOO%2Fbaner%20rich%20whitepaper.png?alt=media&amp;token=a9f062ff-fcbf-49a6-89e1-f17dd23277d7" alt=""><figcaption></figcaption></figure>

The next planned evolution is:

**BROKE → RICH**

Eligible BROKE NFTs may be designed to evolve into RICH through future mechanics.

Potential mechanics may include NFT upgrades, $CBROKE use, burns, treasury interactions, or other requirements.

Exact eligibility and mechanics will be announced before implementation.

## BOX Collection

<figure><img src="https://3912587727-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaCkwEOotyUZP6FOZ4a0Y%2Fuploads%2F1VWWq1CtZ9Iz5zxwpmHx%2FNFT%20BOX.png?alt=media&amp;token=81c7197c-744e-4e3d-9b48-5c27abc9a2fd" alt="" width="188"><figcaption></figcaption></figure>

The BOX is planned as the next bridge in the ecosystem.

The Box Collection may contain assets, items, components, access elements, or other collectibles that can later connect to the Company stage.

Potential categories may include:

* Company assets
* Business items
* Vehicles
* Properties
* Tools
* Special assets
* Access items

Exact contents and mechanics remain TBA.

## COMPANY NFT

<figure><img src="https://3912587727-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaCkwEOotyUZP6FOZ4a0Y%2Fuploads%2Fys1lW6n5TFnzBNGOU9Kv%2FNFT%20COMPANY.png?alt=media&amp;token=726bb92d-26d3-4c6e-bd28-3d58d197b108" alt="" width="375"><figcaption></figcaption></figure>

The Company NFT Collection is planned as a major ecosystem milestone.

Eligible Box assets may connect or integrate with the Company stage, creating a more connected BROKE CEO universe.

## The progression

**BROKE → RICH → BOX → COMPANY**


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://broke-ceo.gitbook.io/broke-ceo-docs/nft-ecosystem.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.