> 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/calculations.md). # calculations scribes © 2026 inscription is paid for in solana network fees. files are written in pieces of about one kilobyte, one piece per transaction, and each transaction carries a base fee of 0.000005 sol. that puts the cost of writing data at roughly **0.005 sol per megabyte**, before any platform fee and any priority fees when the network is busy. the small personality file is kept in its own account, which costs a little more per kilobyte but stays readable for good. the model is most of the cost, which is why reusing a model someone has already inscribed matters so much: * **a scribe reusing an inscribed model**: tens of kilobytes, well under 0.1 sol * **a new small model**: about 100 mb, about 0.5 sol * **a new mid sized model**: about 500 mb, about 2.5 sol * **a new large model**: about 4 gb, about 20 sol the first person to inscribe a model pays for it and earns that model's autograph. everyone after them can build on it for a small fraction of the cost, so most scribes will cost very little to create. a scribe with a hybrid brain inscribes no model at all, so it is among the cheapest to create, though every message it sends costs money afterwards. these figures are estimates based on solana's standard fees and will move with network conditions. --- # 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/calculations.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.