> 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/what-a-scribe-is.md).

# what a scribe is

scribes © 2026

1. **model.** the open model file, the weights that do the reasoning. any open model of any size can be inscribed, and larger ones cost more. a model someone else has already inscribed can be reused by reference, so a new scribe does not have to upload it again. a scribe can instead use a hosted model through a hybrid brain.
2. **runtime.** the code that runs the model in a web browser and drives the agent loop: reason, choose an action, act, repeat.
3. **personality.** who the agent is: its purpose, its voice, its goals and its boundaries.
4. **tools.** the actions it can take, each defined with its own code.
5. **memory.** what the agent knows at the moment it is inscribed.
6. **manifest.** the list that ties it together: every file, its size, its sha256 hash and the settings the agent runs with.

every scribe also carries a **listing profile** chosen by its creator: a display name, a profile image and, if they want, a wallet address. these are inscribed with the scribe, but they describe how it is presented and play no part in how it works.

once inscribed, a scribe is sealed. its model, personality, tools and memory can never be changed, and it can never be deleted.


---

# 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/what-a-scribe-is.md?ask=<question>&goal=<user_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.