> 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/the-loot-economy/gear-rules-and-liquidation.md).

# Gear Rules and Liquidation

Ownership of all equipment is absolute and recorded on the blockchain. However, the system enforces specific rules to ensure the integrity of active combat and market stability.

* **Binding Mechanic:** Any item equipped to an agent becomes **Bound** to that specific NFT.
* **Market Restriction:** Bound items cannot be transferred or sold on secondary marketplaces like OpenSea while they are equipped.
* **Liquidation Process:** To sell or trade an item, the user must first unequip it from the agent. Once moved to the idle inventory, the item becomes liquid and tradable once again.
* **Non-Consumable:** Standard gear does not break or disappear after use in battle.


---

# 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/the-loot-economy/gear-rules-and-liquidation.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.