Skip to main content
GET
Resolve brand

Query Parameters

domain
string
required
Example:

"acmecorp.com"

fresh
enum<string>

Bypass the resolution cache and refetch from the origin. When a fresh fetch fails and a stored record is returned instead, live_brand_json carries that fetch's diagnostics.

Available options:
true,
false

Response

Brand resolved successfully

canonical_id
string
required
Example:

"acmecorp.com"

canonical_domain
string
required
Example:

"acmecorp.com"

brand_name
string
required
Example:

"Acme Corp"

source
enum<string>
required

Provenance of the selected record, not relationship authorization. Deterministic precedence is hosted > brand_json > community > enriched; normal reads prefer the durable stored winner on a source tie, while fresh=true lets a successful live origin read win a tie. brand_json: the domain's own /.well-known/brand.json. hosted: registered by an owner whose control of the domain was verified. community: contributed by a member. enriched: third-party enrichment.

Available options:
hosted,
brand_json,
community,
enriched
names
object[]
keller_type
enum<string>
Available options:
master,
sub_brand,
endorsed,
independent
parent_brand
string
house_domain
string
claimed_house_domain
string

House the requested domain claims. This field never extends trust on its own; relationship_trust reports whether the reciprocal declaration is current enough to do so.

house_name
string
relationship_trust
enum<string>

How the brand-to-house relationship was established. inline: the house's own document defines the brand. mutual: both sides publish the relationship — the trust-extending edge. leaf_only: the brand claims a house whose reciprocal declaration is missing, not yet active, or too old to extend trust. house_only: a house claims the brand, which has not reciprocated. standalone: the brand claims no house. unverifiable: a claimed house could not be checked.

Available options:
inline,
mutual,
leaf_only,
house_only,
standalone,
unverifiable
relationship_verified_at
string<date-time>

When both sides of a mutual relationship were last seen agreeing. Present only for mutual, and it does not advance while the house side is unreachable, so callers can apply their own edge-aging policy.

Example:

"2026-07-28T12:00:00.000Z"

relationship_declared_at
string<date-time>

When the house declared the relationship in brand_refs[].effective_at, or the resolver's durable first observation if the publisher omitted that field. Callers can apply a declaration-age ceiling independently of relationship_verified_at.

Example:

"2026-01-29T12:00:00.000Z"

promoted_from_schema
string

Set when a pre-v3 document was promoted to a canonical v3 document for this response. Identity only — legacy relationship data is preserved opaquely, never promoted to a trust claim.

migration_warnings
object[]

Loss or ambiguity encountered while promoting a pre-v3 document. A house warning means the legacy house object was preserved only as opaque metadata and did not establish a trusted relationship.

brand_agent_url
string
brand_manifest
object
live_brand_json
object

This request's origin-validation diagnostics when fresh=true falls back to a stored registry record. Presence means the response is stored evidence, not a successful live-origin read.