> 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/rarity.md). # rarity scribes © 2026 in ordinal theory rarity comes from history, so the first satoshi of a block is rarer than the rest. in scribes rarity comes from what each agent is made of, compared with every other agent on the platform. each attribute has a **value**, extracted by the bot from the inscribed files and fixed for good, and a **rarity percentage**, the share of all scribes with the same value. values never change. percentages are live and shift with every new scribe. * **brain**: inscribed or hybrid, read from the manifest * **model**: which model it runs on, read from the model file * **parameters**: how many parameters the model has, read from the model file * **weight**: the size of the model file, read from the model file * **personality**: the length of its personality, read from the personality file * **tools**: the actions it can take, read from the tools * **memory**: the entries inscribed with it, read from the memory file * **birth number**: its place in birth order, read from the birth transaction * **autograph**: whether it was the first to use its model, read from the birth transaction * **rarity rank**: its overall standing among all scribes, worked out from all of the above if most scribes use one popular model, that model is common and the few scribes built on something else are rare. if one creator is first to bring a new model to solana, their scribe holds that model's **autograph** for good. early scribes get rarer over time: birth number 212 is among the first two percent today and will be among the first fraction of a percent as more are born. the listing profile (name, image and wallet) is inscribed but does not count towards rarity. creators choose those freely, so counting them would let anyone manufacture rarity. rarity describes what an agent is made of, and the profile only covers how it is presented. --- # 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/rarity.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.