> For the complete documentation index, see [llms.txt](https://beatking.gitbook.io/beatking-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://beatking.gitbook.io/beatking-docs/rewards/minting.md). # Minting New devices come from the MAKE-A-RIG Machine. Play, save up gems, mint. ## Price A mint costs gems plus **0.1 SOL**. In the Seeker app you can pay **500 SKR** instead of the SOL, 26% less. The gem price is dynamic: it moves with the economy. The machine shows today's price. You earn gems by playing. A better run on a better device earns more. See [What a run gives](/beatking-docs/rewards/rewards.md). ## What comes out Almost every mint gives a device with a random rarity. Most are common, many are uncommon, some are rare, a few are epic or legendary. Now and then a mint gives a studio pass instead. A device keeps its rarity for good. A rarer device plays more songs, scores more and earns more gems, so a good one can pay for your next mints. ## After you mint Keep what you mint, or sell it to other players. See [Items and trading](/beatking-docs/rewards/trading.md). You can't sell anything back to BEATKING. ## Payment stuck? Paid and got nothing? Email **** with your wallet address. We'll look and sort it out. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://beatking.gitbook.io/beatking-docs/rewards/minting.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.