Skip to main content
The brand.json file provides a standardized way for brands to claim their identity and establish discoverable brand information. It supports four mutually exclusive variants to accommodate different use cases.
brand.json is the canonical source of brand identity data. The brand object defined here (logos, colors, tone, tagline) is the single brand definition used across AdCP. Tasks reference brands by domain and brand_id — the system resolves full identity from brand.json or the registry.

File location

Brands host the brand.json file at:
Following RFC 8615 well-known URI conventions.

Variants

The brand.json file supports four mutually exclusive variants:

1. Authoritative Location Redirect

Points to a hosted brand.json at another URL:
Use this when:
  • Brand.json is hosted centrally (e.g., by a service provider)
  • CDN distribution is needed
  • Managed brand services

2. House Redirect

Points to the house domain that contains the full brand portfolio:
Optional fields:
  • region: ISO 3166-1 alpha-2 country code (e.g., “CN”)
  • note: Explanation text
Use this when:
  • Brand domain is owned by a larger house
  • Regional/localized domains point to main house
  • Legacy domains redirect to canonical

3. Brand Agent

Designates an MCP agent that provides brand information:
Optional fields:
  • contact: Contact information
When a brand has an agent, the agent is the authoritative source for brand identity data.

4. House Portfolio

Contains the full brand hierarchy with all brands and properties:

House definition

The house object represents the corporate entity:

Brand definition

Each brand in the brands array:

Names Array

Names are localized with language codes:
Multiple entries per language are allowed (for aliases).

Keller Types

Brand architecture classifications from marketing theory:

Visual guidelines

The visual_guidelines object provides structured rules that generative creative systems can use to produce on-brand assets consistently. These are brand constants — they don’t change campaign to campaign.
Visual guidelines complement the basic identity fields (colors, fonts, logos). Colors define what the brand palette is; visual guidelines define how to use it. Fonts define font families; visual guidelines define the type scale.

Photography

Controls how brand photography should look when selected or generated:

Graphic style

Defines the visual language for brand graphics and illustrations:
Style types: flat_illustration, geometric, gradient_mesh, editorial_collage, hand_drawn, minimal_line_art, 3d_render, isometric, photographic_composite.

Shapes

Brand shapes used as part of visual identity:

Iconography

Icon style system and usage rules:

Composition

Layout rules for overlays, textures, and backgrounds:
Texture styles: none, subtle_grain, noise, paper, fabric, concrete. Intensity: low, medium, high. Background types: solid_color, gradient, blurred_photo, image, video, pattern, transparent.

Graphic elements

Reusable decorative or structural visual elements that are part of the brand identity — torn paper edges, watermarks, dividers, background patterns:

Motion

Motion and animation rules for video, animated display, and interactive formats:

Logo placement

Logo placement and clear space rules for automated creative production:

Colorways

Named color pairings that define how colors work together. Allows a creative brief to reference “use my primary colorway” without specifying every color:

Type scale

Typography scale defining sizes and weights for different text roles:
The font field references font roles defined in the brand’s fonts object ("primary", "secondary"), or can specify a font family name directly. When sizes are in pixels, use base_width to indicate the reference canvas these sizes were designed for. Generative systems should scale proportionally for other canvas sizes — a 48px heading designed for 1080px width would scale to 14px on a 320px mobile leaderboard.

Asset libraries

References to managed asset libraries (icon sets, illustration systems, image collections). URLs are for human access — a brand portal, press kit, or DAM landing page that a person can open in a browser.
The color_guide provides generative systems with the color palettes used in the library — useful for producing on-brand illustrations or icons without accessing the library itself.

Restrictions

Visual prohibitions and guardrails — the visual equivalent of tone.donts. These tell generative systems what to avoid:

Property definition

Properties are digital touchpoints owned by brands:

Property Types

Matches AdCP property-type enum:
  • website
  • mobile_app
  • ctv_app
  • desktop_app
  • dooh
  • podcast
  • radio
  • streaming_audio

Resolution algorithm

To resolve a domain to a canonical brand:
  1. Fetch https://{domain}/.well-known/brand.json
  2. Check variant:
    • authoritative_location: Fetch from that URL, continue from step 2
    • house (string): Fetch from house domain, continue from step 2
    • brand_agent: Return agent URL (agent provides brand info)
    • house (object) + brands: Search for domain in properties
  3. For house portfolio, find the brand whose properties contain the query domain
  4. Return canonical brand information
Maximum redirect depth: 3 hops.

Complete examples

Small Business

Enterprise with Agent

Multi-Brand Portfolio

Talent Agency with Rights

A talent agency managing athlete brands with licensable rights:
The rights_agent field tells crawlers what’s licensable without any MCP calls — available uses, rights type, and countries. Buyer agents can search the registry for “Dutch athletes available for voice licensing” and find matches from the indexed brand.json data.

Regional Domain Redirect

On nike.cn/.well-known/brand.json:

Caching

Recommended cache TTLs:
  • Canonical files: 24 hours
  • Redirect files: 24 hours
  • Failed lookups: 1 hour

Best practices

  1. Start simple: Begin with minimal brand.json and add complexity as needed
  2. Use redirects for subsidiaries: Point brand domains to house domain
  3. List all properties: Include regional domains, apps, and legacy domains
  4. Keep names current: Include localized names and common aliases
  5. Visual guidelines are optional: Add them when you need generative systems to produce on-brand assets consistently. Start with colorways and restrictions — they have the highest immediate impact.
  6. Keep portfolios lean: For house portfolios with many brands, include visual guidelines only on brands that need them. Full visual guidelines on every brand in a large portfolio increases file size significantly.