Brand Automation

Automated Brand Kits

Generate brand kits on demand with logos, colors, typography, component tokens, CSS variables and Tailwind theme exports.

Logos Colors Typography CSS

Generate a brand kit Read docs

01 Logo and backdrop discovery

02 Colors and typography preview

03 CSS variables and theme export

04 Client presentation workflow

How it works

From input to useful output in three steps

POST /v1/workflows/brand-kit

Collect

Find brand assets

Retrieve logos, colors, fonts and above-the-fold visual cues from the public site.

GET /v1/brand/retrieve

Tokenize

Turn visual cues into tokens

Build color, typography, spacing, button and card tokens for reusable layouts.

GET /v1/web/styleguide

Package

Create the kit

Return a structured payload that can feed reports, website builders or presentation templates.

POST /v1/workflows/brand-kit

Example workflow

Domain to practical brand kit

Agency needs

A starter brand kit before building a landing page or report.

MediaHarvester extracts

Logo candidates, backdrop images, semantic colors, fonts, buttons, cards and CSS variables.

Team receives

A reviewable kit that designers and developers can refine instead of creating from scratch.

{
  "domain": "clientbrand.com",
  "includeStyleguide": true
}

Built for

Teams that can use this immediately

Agencies

Challenge: Brand discovery takes too long.

Solution: Generate a first-pass kit from a domain.

Impact: Design review starts faster.

Website builders

Challenge: New sites start visually generic.

Solution: Apply extracted tokens to templates.

Impact: Generated pages feel less boilerplate.

Client reporting

Challenge: Reports rarely look like the client.

Solution: Theme deliverables with brand assets.

Impact: Output feels custom with less manual work.

Implementation FAQ

Questions teams ask before building Automated Brand Kits

12 answers

What does Automated Brand Kits help me build?

It turns Brand kit API for agencies, website builders and proposal tools. into a repeatable workflow. The first practical outcome is logo and backdrop discovery.

Which API should I call first?

Start with POST /v1/workflows/brand-kit. The workflow section shows the supporting endpoints to add when you need more context, evidence or visual assets.

What input do I need from my user?

The smallest useful input is shown in the example workflow: A starter brand kit before building a landing page or report. Ask only for the domain, URL, email, ticker or descriptor that the selected endpoint actually needs.

What should I store from the response?

Store the normalized result together with source URLs, confidence or access state, and the time it was fetched. This keeps later refreshes and human review explainable.

Can I use this from a backend, CLI or AI agent?

Yes. The REST endpoint, TypeScript and Python SDKs, CLI and MCP tools use the same local API contract. No-code templates are available for business workflows.

How do I keep the result current?

Use maxAgeMs where the endpoint supports it, or schedule the relevant crawl or workflow. Refresh facts that can change and cache stable assets such as logos more aggressively.

What happens when the website blocks access?

The API reports blocked, verification_required, login_required, robots_disallowed or permission_required instead of treating an empty page as a successful result.

How should I handle missing fields?

Keep the UI usable with optional fields, sensible placeholders and manual overrides. A missing logo, address or classification should not prevent the rest of the workflow from completing.

Who is this workflow designed for?

The examples focus on agencies, website builders, client reporting, but the API response is general enough to use in custom applications.

Can I review the result before publishing it?

Yes. Show extracted values, source URLs and generated visual previews in an approval step before changing customer-facing content or records.

Is batch processing supported?

Use the batch, crawl or workflow endpoint shown for the capability when available. For smaller integrations, process a controlled list and record individual failures rather than failing the whole job.

How do I try the complete example locally?

Open the linked playground from this page or call POST /v1/workflows/brand-kit at http://127.0.0.1:8013 with X-API-Key: mh-localhost-dev-key. The example payload on this page is ready to adapt.

Related use cases

Explore adjacent workflows

Power LLMs with Web Context Give AI agents real-time website context with clean markdown, crawl results, screenshots, brand data and structured extraction. Reduce Onboarding Friction Personalize onboarding automatically with company logos, colors, fonts, styleguides, descriptions and industry classification. Enrich Company Profiles Build richer CRM, directory and marketplace profiles with logos, descriptions, socials, colors, addresses and industry data. Stock Ticker Enrichment Resolve public-company tickers and ISINs into company websites, logos, brand profiles and stock metadata. Logo Link API Serve company logos through a spreadsheet-friendly public Logo Link endpoint with monogram fallback. Power Generative AI Enhance AI generation with real-time brand context, product facts, pricing pages, images and styleguide tokens.