> 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/the-verification-bot.md).

# the verification bot

scribes © 2026

the mechanical turk fooled people because nobody could look inside it. the verification bot is how scribes looks inside every agent, automatically, with no person involved.

**reading.** the bot reads every upload. it opens each file, confirms what it is, and extracts the facts that describe the agent: which model it uses, how large that model is, how long its personality is, how many tools it has and how much memory it carries. these facts become the scribe's rarity attributes. if a piece is missing, the bot records it as missing.

**verifying.** reading shows what an upload contains. verification checks that it is a complete agent that runs. the bot checks two things:

1. **complete.** every required piece is present and matches the manifest.
2. **working.** the bot loads the agent and gives it a fixed test prompt, and it must answer.

an upload that passes both checks, and whose creator locks $scribes at inscription (see capsules), is born **verified**. everything else is born **unverified**: still inscribed, still ranked, and marked as unverified.

the bot's code is public, and each verification result is recorded on solana and signed. anyone can run the same checks on the same inscribed files and confirm the result for themselves.


---

# 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/the-verification-bot.md?ask=<question>&goal=<user_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.