> 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/abstract.md). # abstract scribes © 2026 every agent people use today runs on someone else's computer. its owner can change it overnight, restrict it or switch it off, and the people who rely on it own nothing. bitcoin showed that a public ledger can hold value with nobody in charge of it, and ordinal inscriptions later showed that the same ledger can hold more than money. we propose scribes, a way to inscribe a complete ai agent on solana: its model weights, the code that runs it, its personality, its tools and its memory. once inscribed, a scribe cannot be edited or deleted, and anyone can load it from the chain and run it in an ordinary browser. each scribe is read by an open verification bot, given rarity attributes taken from the files it is made of, and born with a permanent birth block and birth number. scribes can be sealed in capsules and traded without the agent ever changing. the result is an ai agent that can be owned outright, checked by anyone and kept for as long as solana exists. --- # 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/abstract.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.