> 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/verifying-a-scribe-yourself.md). # verifying a scribe yourself scribes © 2026 you never have to take our word for anything. every claim about a scribe can be checked. ### its birth every scribe page links its birth transaction. open it in any solana explorer and you will see the block it landed in, the wallet that signed it and the time. none of these can be changed. ### its files every file in a scribe has a fingerprint (its hash) recorded in the manifest. the loader checks each piece against its fingerprint every time the scribe is opened. if a single byte were different, the scribe would refuse to load. ### its rarity rarity attributes are read from the inscribed files by open code. you can run that code against the chain yourself and get the same attributes and percentages. ### its verification each verification result is recorded on solana and signed. the bot's code is public, so you can rerun the same checks on the same files and confirm the result. ### its replies this only applies to scribes with an inscribed brain. hybrid scribes call hosted models, which do not promise identical answers, so their replies cannot be proven this way. a scribe with an inscribed brain runs with fixed settings, so the same question always gets the same answer. when someone shares a reply from a scribe, you can ask the same question yourself and check the answer word for word. we call that a **provable reply**. --- # 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/verifying-a-scribe-yourself.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.