> For the complete documentation index, see [llms.txt](https://monkey-gun.gitbook.io/monkeygun/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://monkey-gun.gitbook.io/monkeygun/concepts/brand-and-packs.md).

# Brand and style packs

Colors, type, motion, sound and captions, per call or locked on a channel.

Pass `brand` on any call that makes a video. Everything is optional; unset fields fall back to the source page's colors, then to the account's brand kit, then to the defaults.

```json
"brand": {
  "pack": "bold",
  "accent": "#C7F24C", "ground": "#0B0C0F", "ink": "#F4EFE6",
  "displayFont": "DM Sans", "bodyFont": "DM Sans",
  "watermark": "yourexchange.com",
  "logo": "libraries/u/<scope>/files/<assetId>.png",
  "disclaimer": "Not financial advice. Data as of render time.",
  "captionStyle": "karaoke",
  "sfx": true
}
```

## Style packs

A pack sets fonts, motion per scene type, grade, music mood and the sound-design profile in one word.

| Pack        | Look                                   | Motion                                       | Music                           | Sound design                                |
| ----------- | -------------------------------------- | -------------------------------------------- | ------------------------------- | ------------------------------------------- |
| `classic`   | Clean sans, default                    | Kinetic titles, count-up data, slide visuals | Modern electronic, 104 bpm      | Whoosh cuts, impact on stats, medium volume |
| `editorial` | Serif, warm, slower                    | Slides, typewriter quotes                    | Warm piano and strings, 88 bpm  | Quiet, riser on open                        |
| `bold`      | Condensed uppercase, hot accent        | Kinetic everything, fast                     | Driving electronic, 128 bpm     | Loud, impact on open and CTA                |
| `cinematic` | Letterbox on wide frames, filmic grade | Slow push-ins, zoom                          | Dark underscore, drones, 92 bpm | Riser on open, tick on CTA                  |

## Captions

`captionStyle: "karaoke"` shows one to three words at a time with the keyword lit (default). `"bar"` shows the phrase in a pill. `captions: false` on the call turns them off.

## Watermark and logo

`watermark` is text bottom-right. An empty string removes it. `logo` replaces it with an image from your library (upload it first, then use the path returned in the library listing).

## Locking brand on a channel or show

Set `brand` and `cta` on a channel (`update_channel`) and every video made with that `channelId` inherits them when the call sends no `brand` of its own. A show's `brandLock` goes further: it is merged over whatever the call sends, so a locked show is always an ad for its owner. If you want per-call brand on a channel with a lock, omit `showId`, or omit `channelId` entirely.

{% hint style="info" %}
Passing `channelId` also applies the channel's locked `frame` (header and footer) if one is set. To render with your own brand and no frame, do not pass `channelId`.
{% endhint %}


---

# 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://monkey-gun.gitbook.io/monkeygun/concepts/brand-and-packs.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.