What it is
brand.json tells agents who your brand is and how it wants to be represented: names, logos, colors, fonts, tone, visual guidelines, and the properties you own. Agents read it the same way crawlers read robots.txt: from a well-known location on your own domain.
Who hosts it
You
Recommended. Put the file at https://yourdomain/.well-known/brand.json. The builder generates it and checks it once it's live.
Your agency or platform
They host the full file; you publish a small pointer on your domain with authoritative_location.
A hosting service
AgenticAdvertising.org can host it for you. Your domain still publishes the pointer, so you stay in control.
A minimal example
{
"$schema": "https://brandjson.org/schemas/v3/brand.json",
"house": { "domain": "acme.example", "name": "Acme Corp" },
"brands": [
{
"id": "acme",
"names": [{ "en": "Acme" }],
"logos": [{ "url": "https://acme.example/logo.svg" }],
"colors": { "primary": "#1A4D8F" }
}
]
}
Schema
Validate against https://brandjson.org/schemas/v3/brand.json. The standard's agent and trust fields are moving to a separate record, trust.json, so brand.json can stay focused on identity.
Declare who can act for your brand
Publishing identity is one part of protecting your brand. The experimental trust.json standard lets you publish which agents you run and which agencies or platforms may represent you. Sellers that implement its checks can verify those permissions before accepting a request.
Learn how to publish authority and protect a brand portfolio →