---
title: "How to share approved brand assets across AI agents | Rainbrand"
description: "Agents redraw logos and pick the wrong product photos when they can’t reach the real files. What to share, the ways to share it, and how to keep one approved set that every agent can call."
url: "https://www.rainbrand.com/blog/share-brand-assets-across-ai-agents/"
---

By [Tomas Ward](https://www.linkedin.com/in/tomasward1/)

Published 6 Nov 2026

4 min read

# How to share approved brand assets across AI agents

Agents redraw logos and pick the wrong product photos when they can’t reach the real files. What to share, the ways to share it, and how to keep one approved set that every agent can call.

## TL;DR

Keep one current, approved set of files agents can retrieve. Supply original logos, usable fonts with specimens, and clearly labelled product photos and references. Check that each agent can open and use them, and remove retired files when replacements arrive. A returned file still needs instructions for its intended use.

## Why agents get brand files wrong

Missing or ambiguous files leave room for substitutions:

| Asset | Failure to prevent |
| --- | --- |
| Logo | A generated approximation instead of original artwork |
| Font | A lookalike in an image or fallback in a layout |
| Product photo | Old packaging or invented details |
| Reference | A retired campaign mistaken for current direction |

[OpenAI documents limits](https://developers.openai.com/api/docs/guides/image-generation) in recurring brand-element consistency. Give the agent the approved file and a usage note, such as which logo goes on a dark background.

## What to share, and in what form

| Asset | Supply |
| --- | --- |
| Logos | SVG/PNG variants and when to use each |
| Fonts | Font files, licence and specimen image |
| Products | Current approved photos, labelled by product and view |
| References | Approved images with what to borrow: style, subject or setting |

Place original logos in the final layout rather than generating them. Keep drafts, rejected variants and retired files out of the working set.

Check licences before sharing: [Fontspring’s desktop licence](https://www.fontspring.com/lic/nct/desktop), for example, allows licensed users’ access on a controlled server but requires a web licence for website embedding.

[Shared guidelines](https://www.rainbrand.com/blog/give-multiple-ai-assistants-the-same-brand-guidelines/) covers the accompanying rules; [AI image references](https://www.rainbrand.com/blog/apply-brand-guidelines-to-ai-images/) covers briefing models.

## Three ways to give agents the files

| Route | Access and behaviour | Maintain |
| --- | --- | --- |
| DAM/shared-drive link | Agent must be able to open it; a folder link alone does not identify approval | Permissions and approval metadata |
| Assistant uploads | Claude/ChatGPT projects can use files; shared Claude projects need Team/Enterprise, shared ChatGPT projects work on every plan | Replace every uploaded copy after changes |
| Library queried through MCP/API | Return files selected for the task, with usage guidance | One approved collection |

DAM tools can supply more than a folder link:

- [Frontify MCP](https://help.frontify.com/en/articles/14787214-frontify-mcp) retrieves assets, fonts and colours.
- [Bynder MCP](https://api.bynder.com/page/mcp) searches assets under the signed-in user’s permissions.
- [Brandkit](https://brandkit.com/mcp) exposes draft, archived, expired and release status.

Their usefulness depends on maintained metadata, as [DAM consultant Timo Faber explains](https://digitalassetmanagementnews.org/features/is-your-dam-ready-for-agentic-operations/). Anthropic’s [custom Skills do not sync](https://platform.claude.com/docs/en/agents-and-tools/agent-skills/overview) across claude.ai, Claude Code and API surfaces.

[MCP can return images and file links](https://modelcontextprotocol.io/specification/2026-07-28/server/tools). Rainbrand uses that route; [SlideSpeak Onbrand](https://slidespeak.co/features/onbrand) provides read-only slide-focused brand assets. The [MCP survey](https://www.rainbrand.com/blog/mcp-servers-for-brand-guidelines/) compares servers.

## How Rainbrand’s Brand Library works

Rainbrand maintains guidance and assets agents use across recurring work. Its [Brand Library](https://docs.rainbrand.com/guides/manage-brand-library) holds approved logos, photos, illustrations and references, with video/audio in beta. Fonts, colours and guidance change through [brand edits](https://docs.rainbrand.com/guides/edit-brand).

| Action | What happens |
| --- | --- |
| [Add](https://docs.rainbrand.com/guides/manage-brand-library#add-assets) | Explicitly add local files, public links or generation results. [Upload local files first](https://docs.rainbrand.com/guides/upload-files); supported clients offer a picker. Uploads and results stay outside until added. |
| [Find](https://docs.rainbrand.com/api-reference/images/search-library-images) | List the Library or search images by what they show |
| [Use](https://docs.rainbrand.com/guides/request-brief) | A Brief selects relevant images, logos, fonts and specimens; stored video/audio serves other work |
| [Remove](https://docs.rainbrand.com/mcp/tools) | Take a file out of the Library so future Briefs stop selecting it; the file itself remains |

Connect [Claude](https://www.rainbrand.com/integrations/claude/), [ChatGPT](https://www.rainbrand.com/integrations/chatgpt/), [Codex](https://www.rainbrand.com/integrations/codex/) or [Cursor](https://www.rainbrand.com/integrations/cursor/), or use the [API](https://docs.rainbrand.com/getting-started/embed-into-your-product). Put a shared brand in the intended team.

The Library keeps its own copies: replace changed DAM files there too. [Brief asset links](https://docs.rainbrand.com/api-reference/briefs/get-a-brief) are stable public links anyone holding them can open, so confirm your licences permit that sharing.

For Yumbun, a London bao brand, Claude made a phone menu, printed menu decoder and counter-screen film using Rainbrand. The saved Brief included:

| File | Instruction |
| --- | --- |
| [Wordmark](https://www.rainbrand.com/examples/yumbun/brand/b4328b78-9f36-4e07-adb6-4f8cc59bbcd0.svg) | Place intact |
| [Faro Lucky Bold](https://www.rainbrand.com/examples/yumbun/fonts/faro-lucky-700.woff2) and [specimen](https://www.rainbrand.com/examples/yumbun/brief/faro-lucky-700-specimen.png) | Use for headings/buttons |
| [Chicken-bao photo](https://www.rainbrand.com/examples/yumbun/brand/d7b015b2-6ec1-4ab9-89cc-884603892394.jpg) | Photographic reference, not proof of current fillings |

![Yumbun menu decoder using the supplied wordmark and typography](https://www.rainbrand.com/examples/yumbun/outputs/tray-liner-v3.webp)

Inspect the [print PDF](https://www.rainbrand.com/examples/yumbun/outputs/tray-liner-v3.pdf). A separate photo Brief found no aubergine-bao image and returned pork, chicken and tofu references with different sets. Claude generated the missing image; the Brief left its exact background unresolved.

![The generated Yumbun aubergine-bao image, with aubergine, cucumber and spring onion in a bun on a plate against a pink and wood backdrop](https://www.rainbrand.com/examples/yumbun/outputs/aubergine-bao.webp)

The [full example](https://www.rainbrand.com/examples/yumbun/) distinguishes retrieving approved files from making a new asset. A [Brand Skill export](https://docs.rainbrand.com/guides/use-brand-skill) supplies local files for other tools; download it again after changes.

## Check that each agent can use the files

Have each agent retrieve, open and show its selection before production. For layouts, load the actual fonts and place the logo. For image models, pass references through the supported inputs.

Ask your agent

```
Show me the product images in [your brand]'s Brand Library in Rainbrand. Identify files that may be outdated and explain why. Wait for my confirmation before removing them. Then add the approved replacements I supply, with descriptions that identify the product, view and intended use.
```

## Keep the set current

- **On replacement:** add the new file and remove its predecessor; replace copies in projects and Skills.
- **On a gap:** source or make the missing asset and approve it before adding it.
- **Before publishing:** check original-logo use, product accuracy and brand fit.

Use [Rainbrand Review](https://docs.rainbrand.com/guides/request-review) on the finished work and resolve uncertain findings. [Image checking](https://www.rainbrand.com/blog/check-ai-images-against-brand-guidelines/) covers that loop.

To try Rainbrand, [connect an agent](https://docs.rainbrand.com/mcp/getting-started), add the original logo and a few approved product photos, and request a Brief for a real task.

## More in AI tools

[All 8 AI tools articles](https://www.rainbrand.com/blog/topics/ai-tools/)

- 6 Nov 2026 4 min read

    ### [How to give Claude Code and Cursor your brand, not just your design system](https://www.rainbrand.com/blog/brand-context-for-coding-agents/)

    Coding agents read your design system and instruction files, but a landing page also needs your voice, product claims, imagery and logo rules. Keep code conventions in the repo, fetch the current brand for each task, and check the page before it merges.

- 6 Nov 2026 3 min read

    ### [How to use ChatGPT for marketing and stay on brand](https://www.rainbrand.com/blog/chatgpt-for-marketing/)

    Use ChatGPT to research, draft, analyse and make campaign assets from real sources. Keep projects for campaign work, fetch current brand context through a connection, and check the deliverables before publication.

- 6 Nov 2026 3 min read

    ### [How to use Claude for marketing without losing your brand](https://www.rainbrand.com/blog/claude-for-marketing/)

    Give Claude a real marketing job, the sources behind it and current brand guidance. Use Projects, skills and connectors for their different jobs, then inspect the finished work before it goes out.

One brand, every agent.

[Connect your agents](https://docs.rainbrand.com/mcp/getting-started)