> For the complete documentation index, see [llms.txt](https://bone-headz.gitbook.io/boneheadz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bone-headz.gitbook.io/boneheadz/about-us/why-play-2-earn.md).

# Why Play 2 Earn?

![](/files/z9Sa2dgFgyZU9SkY3mw1)

We believe that the P2E ecosystem is going to be one of the largest subsects of the NFT space. NFTs started off very simple, they became profile pictures, they became utility based, they gave you access to events, channels, groups, etc. 

The market is hungry for, "a reason to buy" and, "a reason to hold." Beyond being a profile picture and having access to a community of likeminded people, our NFTs give you the opportunity to evolve, upgrade, change, and better the visual attributes of your NFT through our Tomb Raiding mechanic. 

You have a % chance to upgrade your NFT by sending it in the Tomb to find loot. If you find loot, your NFT upgrades and gains an attribute. If you lose, your NFT gets locked in the Tomb until the next season. 

The players who collect the most amount of loot at the end of each season win equal share of the prize pool. 

So you can choose to play, upgrade, and potentially win - or you can just sit back and enjoy your NFT as is.


---

# 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:

```
GET https://bone-headz.gitbook.io/boneheadz/about-us/why-play-2-earn.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.