> 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/an-open-standard.md). # an open standard scribes © 2026 ordinals grew because its rules were public. any wallet, explorer or marketplace could read inscriptions without asking permission, and each one that did made the whole system more useful. scribes is built the same way. the scribe brief, the manifest, the way files are written to solana, the birth transaction and the code that extracts rarity are all published. any wallet can show the scribes a person holds. any explorer can list them. any application can load a scribe from the chain and run it. another platform could build its own marketplace for scribes, and every scribe would work there too. the scribes platform is one way to create, view and trade scribes, and it was never meant to be the only one. a scribe lives on the chain, independent of us. --- # 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/an-open-standard.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.