> For the complete documentation index, see [llms.txt](https://docs.micro.fun/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.micro.fun/secondary-markets/nft-and-gear-markets.md). # NFT and Gear Markets Ownership of Genesis Agent NFTs and Tactical Gear is absolute and resides entirely within the player's self-custody wallet. These assets are issued on the Base Network and are fully compatible with major secondary marketplaces such as OpenSea. The NFT serves as the exclusive key to an agent’s command layer. Selling a Genesis Agent NFT transfers all accumulated levels, permanent stat upgrades, and historical combat records to the new user. This makes high-level, battle-proven agents premium assets on the secondary market. Tactical Gear acquired from Boss encounters functions as tradable equipment. Pilots seeking to optimize their builds can purchase elite gear from other players. To ensure market stability and combat integrity, any item actively equipped to an agent is considered Bound. A user must unequip an item and move it to their idle inventory before it can be listed for sale or transferred to another wallet. --- # 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.micro.fun/secondary-markets/nft-and-gear-markets.md?ask=&goal= ``` `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.