Schema
- Request:
get-brand-identity-request.json - Response:
get-brand-identity-response.json
Response time
Typically under 2 seconds for identity data. Authorized responses with large asset collections may take longer.Public by default
Brand identity is public data. Any agent can callget_brand_identity without a linked account and receive the brand’s core identity: house, names, description, industries, and basic logos. This is the same data available in brand.json — get_brand_identity provides it via MCP for agents that prefer a structured call over fetching and parsing the file.
The registry enforces this: every brand indexed from brand.json is publicly discoverable. You can always find out what house a brand belongs to, what it’s called, and what it does.
Authorized callers (linked via sync_accounts) get deeper data on top of the public baseline.
Account linking is a one-time setup: a buyer agent calls sync_accounts on the brand agent, providing its brand reference. After that, the buyer’s get_brand_identity requests are recognized as authorized.
If a request includes
fields that require authorization the caller does not have, those fields are silently omitted. The response includes available_fields listing what sections exist but were not returned, so the caller knows what they would gain by linking their account.
Quick start
Parameters
Request
Valid
fields values: description, industries, keller_type, logos, colors, fonts, visual_guidelines, tone, tagline, voice_synthesis, assets, rights, collections (experimental)
Recommended use_case values:
use_case is advisory — it tailors content within returned sections but does not override fields.
Response
The response mirrors the brand.json brand definition, extended with dynamic data the agent controls:People behind collections
A collection’stalent[].brand_ref points at a person’s brand identity. The collection carries the channel facts; the person’s details come from their brand or rights agent through this task. The person’s picture is in logos, which is always public. brand.json’s avatar is not exposed here: it is a synthesis configuration (provider, avatar_id, settings), not a profile picture. collections (experimental, brand.collection_links) links back from the person to their channels, so a buyer can go from person to channel to product selector. A collection’s brand_ref is the publisher’s claim; buyers SHOULD treat it as confirmed only when the person’s collections lists the same {publisher_domain, collection_id} back. Displaying the person’s picture from logos is not a likeness license; likeness use in ads goes through get_rights and acquire_rights. Brand agents that return collections list brand.collection_links in experimental_features:
Use cases
- DAM: Returns high-res assets, current campaign guidelines, seasonal creative toolkits
- Enterprise brand agent: Returns approved copy, brand voice guidelines, current taglines
- Rights management agent: Returns talent identity — tone, voice synthesis, photos, rights availability
Next steps
get_rights
Search for licensable rights with pricing.
acquire_rights
Acquire rights with contractual clearance.