> 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/for-builders/hybrid-brains.md).

# hybrid brains

scribes © 2026

a hybrid scribe inscribes everything except the model weights. where an inscribed scribe has a model file, its manifest carries a **brain reference** that names a hosted model.

### inscribed and hybrid compared

* **brain field**: `"inscribed"` or `"hybrid"`
* **model in the package**: a gguf file or a reference to an inscribed model for inscribed scribes, none for hybrid
* **where inference runs**: the visitor's browser for inscribed, the provider's servers for hybrid
* **determinism**: required for inscribed (temperature 0, fixed seed), not guaranteed for hybrid
* **provable replies**: supported for inscribed, not for hybrid
* **backup model**: not needed for inscribed, optional but recommended for hybrid

### brain reference

```
{
  "format": "scribes:v1",
  "brain": "hybrid",
  "brain_reference": {
    "provider": "anthropic",
    "model": "claude-model-id",
    "backup": { "file": "backup.gguf", "hash": "sha256:..." }
  },
  "runtime": { "file": "runtime.wasm", "hash": "sha256:..." },
  "personality": { "file": "personality.json", "hash": "sha256:..." },
  "tools": [],
  "memory": { "file": "memory.json", "hash": "sha256:..." },
  "settings": { "temperature": 0, "max_tokens": 512 }
}
```

`backup` is optional. if it is set, it points to a small open model inscribed with the scribe, which the runtime uses when the hosted model is no longer available.

### calling the model

the runtime sends the personality, memory, tools and conversation to the provider in one of three modes:

* **own key**: the visitor pays, and the key stays only in the visitor's browser and is never stored
* **credits**: the visitor pays scribes per message, and the key is kept on a scribes server and never exposed
* **holder credits**: the holder prepays, and the key is kept on a scribes server and never exposed

### rules

* **no api key may appear in any inscribed file.** the verification bot rejects any package containing something that looks like a key.
* the listing has to show **brain: hybrid**, the provider and the model, so a buyer knows what they are getting.
* each provider's terms of use govern how its models are accessed and resold. provider names and logos are not used in marketing without permission.
* conversations with a hybrid scribe go through the provider, and through scribes in the credit modes. visitors have to be told this.

> supported providers, credit pricing, request formats and the hybrid verification badge are still to be decided.


---

# 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/for-builders/hybrid-brains.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.