SlideSpeak Onbrand: Brand Context for Presentation Agents

Last updated: 2026-07-24

Last verified: 2026-07-24

TL;DR: SlideSpeak Onbrand exposes approved brand assets and slide layouts to Codex, Claude Code, Cursor, and other MCP clients. The goal is to let an agent fetch logos, colors, typography, imagery, and layouts before producing a deck or one-pager. It can reduce manual brand cleanup, but organizations need strict permissions, asset rights, versioning, and a final design review.

What Onbrand does

Onbrand is a brand-context service built around the Model Context Protocol. A brand manager maintains a workspace, and an approved agent can request typed assets or layout information from that workspace. SlideSpeak presents it as a way to replace brand instructions scattered across prompts and files.

The product page shows logos, palettes, type, imagery, icons, and approved slide layouts as governed resources. An agent can retrieve a specific brand or layout and use that material while building a presentation.

Why structured brand context matters

A prompt such as “make this on brand” is incomplete. It does not say which logo version is valid, how much clear space it needs, which fonts are licensed, or which layout is approved for a financial result. Structured tools can make those choices explicit and reusable.

MCP also separates retrieval from the model’s memory. A team can update a centrally governed asset instead of changing every agent prompt. That can help with brand refreshes, regional variants, and different client accounts.

Readers following agent-workflow AI News should not assume that protocol compatibility equals safe access. The organization still controls credentials, scopes, logging, and which agent is allowed to retrieve each asset.

SlideSpeak platform and pricing

SlideSpeak’s API documentation covers presentation generation and editing, branded templates, document inputs, asynchronous tasks, and webhook delivery. Its broader platform can export editable PowerPoint files, which gives a human reviewer a practical correction path.

The current application pricing page lists a free tier, Premium, Premium Plus, and custom Enterprise plans. It lists Premium at $29 per month on the monthly view, Premium Plus at $40 per month, and a custom-template add-on at $129 per template. API plans use separate credit pricing. Confirm the live account view because annual discounts and feature entitlements differ.

Where Onbrand may fit

Give a presentation agent the current approved logo and palette.
Reuse accepted title, comparison, timeline, and KPI layouts.
Separate client brands inside an agency workflow.
Update shared assets without rewriting each agent instruction.
Create a draft one-pager that remains editable by a designer.

Governance and design risks

Brand assets can be confidential or licensed for limited use. Access should be scoped by workspace, client, environment, and task. Tokens must be revocable, and logs should show which agent retrieved which asset.

Correct colors and logos do not guarantee good design. An agent can crop imagery badly, overuse a logo, create inaccessible contrast, or put a component in the wrong narrative context. A designer or trained reviewer should inspect the exported deck at presentation size.

Evaluation checklist

Create a test workspace with non-sensitive assets and two approved layouts.
Connect one MCP client with the narrowest available permissions.
Generate the same short deck with and without Onbrand context.
Compare logo use, typography, color, layout, editability, and cleanup time.
Revoke access and confirm that the client can no longer retrieve assets.

Kingy AI verdict

Onbrand addresses a real weakness in presentation agents: brand rules are often vague, stale, or inaccessible. It is worth testing where a team already has approved assets and clear ownership. Start with a limited workspace, verify revocation and logs, and keep a human design gate before distribution.