> For the complete documentation index, see [llms.txt](https://docs.cryptocraftgame.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cryptocraftgame.com/genesis-land/gameplay/land-ownership/buying-land.md). # Buying Land Any Land owned by a player can be sold to any other player through the use of "Purchase Signs." A **Purchase Sign** is a special sign that will allow players to buy Land by right-clicking on the sign. This action is irreversible and will give full ownership of the Land to the new owner in exchange for $EMRD. The owner of Land can create a Purchase Sign at any time for any price. The sign can also be destroyed by the owner to cancel the purchase option. {% hint style="info" %} **Purchase Sign:** All signs will have the same format. An example of the format can be seen below. Right click to use this sign and purchase the Land.\ \ ![](/files/ocVJI8GGIt0v4G4XHuGo) {% endhint %} --- # 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.cryptocraftgame.com/genesis-land/gameplay/land-ownership/buying-land.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.