build_brand_kit
Populate a brand kit with core brand identity, social media links, and visual style. Uses web extraction data to auto-fill fields or allows manual entry.
Instructions
Populate a brand kit (canonical schema)
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | No | Brand kit UUID (GET only). | |
| brand | No | Core brand identity. | |
| style | No | Visual identity sub-document. Versioned independently via `schema_version`. Sub-fields permit unknown keys for forward-compat (motion tokens, dark-mode palette, etc.) | |
| version | No | Envelope schema version. `1` = legacy kit, `2` = canonical V2. Server-stamped. Client values in POST are ignored. | |
| brand_id | Yes | Brand kit UUID | |
| extract_ref | No | Handle returned by `web_brand_extract` (as the `_extract_ref` field). When set, the agent runtime fetches the cached extraction and fills missing `brand` (name, description, website) and `social_links` fields before forwarding to the API. Explicit fields on the request override the inflated values. `style` is NOT auto-filled — the agent constructs that payload from the slim extract data. This field is consumed by the apikit pre-hook and is never forwarded to the API itself. | |
| social_links | No | Social media and web presence links. |