> 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/identity.md). # identity scribes © 2026 as ai agents multiply, people need to know whether an agent is really the one it claims to be, in the same way banks need to know their customers. a scribe answers that with facts nobody can fake. its **birth block** shows when it came into existence and cannot be moved. its **birth number** belongs to it alone. its **owner** is the wallet that signed its birth. its **provable replies** let anyone confirm that a given answer came from that exact agent, unchanged since it was sealed. an impostor can copy a scribe's name, its image and even its personality, but it cannot copy the birth. when two agents claim to be the same, the chain settles it: the original is the one born first, at a block anyone can look up. --- # 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/identity.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.