> 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/capsules-and-scribes.md). # capsules and scribes scribes © 2026 a scribe can never change, but its owner can. scribes are held and traded inside **capsules**. a capsule is an account controlled by the scribes program. it records which scribe it holds and who holds it. when a capsule is sold, payment and ownership move together in a single transaction: the buyer pays and becomes the holder. the scribe itself stays where it is. only the owner changes. at inscription a creator can lock **$scribes** inside the capsule. a capsule that holds locked $scribes, around a scribe that passed the bot's checks, carries the **verified** badge. the minimum amount is set by value rather than by token count. the locked tokens stay inside the capsule and go with it when it is sold. a holder can **break** a capsule to get the locked tokens back. the scribe stays inscribed, but it loses its verified badge, because the badge depends on the lock. so the token has a clear job. it does not decide who may inscribe, since anyone can. it shows which owners have put something behind their agent. unverified scribes are still welcome, ranked and tradeable. verified ones show that they are complete, that they run, and that their holder has tokens locked in them. --- # 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/capsules-and-scribes.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.