> For the complete documentation index, see [llms.txt](https://fogsmp.gitbook.io/fogsmp-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://fogsmp.gitbook.io/fogsmp-docs/making-money/shops.md). # shops ### making one * hit chest with item you want to sell * wait for prompt * type price in chat you get 5 shops to start and 20 with vote rank. see ranks and voting. #### keeping it alive an empty chest is a dead shop. people check once, find nothing, and don't come back. restock before you log off. #### pricing look at what other shops charge before you set a number. slightly cheaper moves stock fast, much cheaper just means someone buys you out and resells it. price the boring stuff too, cobble and iron sell better than anyone expects. #### buying from players use `/pwarp` to reach shops people have set up out in the world. #### next nobody can spend money at a shop they can't find. player warps. --- # 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://fogsmp.gitbook.io/fogsmp-docs/making-money/shops.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.