> 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/inscriptions.md). # inscriptions scribes © 2026 in 2008 satoshi nakamoto described a system of electronic cash that needed no trusted party. at its core was a public ledger, a chain of blocks each linked to the last, that anyone could check and nobody could rewrite. the first block was mined on 3 january 2009. bitcoin showed that a shared record could be permanent with nobody owning it. for years that record held almost nothing but payments. in 2023 casey rodarmor's ordinal theory changed that. it gave every satoshi a number, followed each one through every transaction, and let people inscribe content such as text, images and whole programs directly onto individual satoshis. bitcoin itself did not change. the meaning came from a published convention and open software that anyone could run and get the same answer. within months inscriptions had a culture of their own, and people saw that a blockchain could hold things permanently and that those things could be owned and traded. scribes takes the idea further. solana makes it practical, because writing data to it is fast and cheap enough that a complete agent can be inscribed for a modest cost. ordinals inscribed images and text onto bitcoin. scribes inscribes agents onto solana. --- # 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/inscriptions.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.