> 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/verification-bot.md). # verification bot scribes © 2026 the verification bot reads every upload and decides whether it is a complete agent that runs. ### reading every upload for each file the bot: * confirms the file type * recomputes its size and hash * extracts the values used for rarity any missing piece is recorded as missing. ### verifying * **complete**: model, runtime, personality, tools, memory and manifest are all present and every hash matches * **working**: the agent loads and answers a fixed test prompt a scribe is **verified** when both checks pass and $scribes is locked in its capsule. otherwise it is **unverified**. for a hybrid scribe, the working check calls the hosted model through scribes, and the complete check looks for a valid brain reference where the model file would be. the answer cannot be reproduced exactly, so hybrid results are labelled separately. ### transparency * the bot's code is published. * each result is recorded on solana and signed with the bot's key. * the indexer runs the same reading on scribes inscribed straight to the chain without the website. > the fixed test prompt and its pass criteria will be published with the bot's code. --- # 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/verification-bot.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.