> 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-builders/capsule-program.md). # capsule program scribes © 2026 every scribe is held in a capsule, an account controlled by the scribes program. it records which scribe it holds, who the holder is, its status and any locked $scribes. ### actions * \*\*`seal_capsule`\*\*: called by the owner at birth. creates the capsule and optionally locks $scribes * \*\*`list_capsule`\*\*: called by the holder. sets a price, and nothing moves * \*\*`cancel_listing`\*\*: called by the holder. removes the price * \*\*`buy_capsule`\*\*: called by anyone. pays the holder and makes the caller the holder in one transaction, with a maximum price * \*\*`gift_capsule`\*\*: called by the holder. changes the holder with no payment * \*\*`break_capsule`\*\*: called by the holder. returns the locked $scribes to the holder and removes the verified badge ### rules * no action ever modifies the scribe. only the capsule changes. * payment and the change of holder happen together or not at all. * the badge exists only while $scribes is locked and the scribe has passed verification. * the program holds real tokens and needs an independent audit before launch. > marketplace fees, the minimum lock value and the price feed used to set it are still to be decided. --- # 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-builders/capsule-program.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.