> For the complete documentation index, see [llms.txt](https://scribes.gitbook.io/scribes-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://scribes.gitbook.io/scribes-docs/for-users/buying-selling-and-breaking-capsules.md). # buying selling and breaking capsules scribes © 2026 every scribe sits inside a **capsule**. the capsule records who holds the scribe. trading a scribe means trading its capsule, and the scribe itself never changes. ### listing a capsule set a price and list your capsule on the marketplace. your scribe stays where it is, and you can cancel the listing whenever you like. ### buying a capsule when you buy, two things happen in one transaction: your payment goes to the seller and you become the holder. one cannot happen without the other. you also set the highest price you will pay. if the seller changes the price while your purchase is going through, the purchase fails and you lose nothing. ### giving a capsule away you can send a capsule to another wallet without selling it. the new holder gets the scribe and anything locked inside the capsule. ### verified and unverified capsules * a **verified** capsule holds a scribe that passed the bot's checks, with $scribes locked inside. the locked tokens go with the capsule when it is sold. * an **unverified** capsule holds a scribe with no lock, or one that did not pass the checks. it is still inscribed, still ranked and can still be traded. ### breaking a capsule the holder of a verified capsule can break it to get the locked $scribes back. the scribe stays inscribed for good, but it loses its verified badge, because the badge comes from the lock. > marketplace fees and the minimum $scribes lock are not final yet. this page will be updated when they are. --- # 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://scribes.gitbook.io/scribes-docs/for-users/buying-selling-and-breaking-capsules.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.