Skip to main content
POST
Force a synchronous brand.json crawl

Authorizations

Authorization
string
header
required

Bearer token in the Authorization header. Two token types are accepted:

  • Organization API key (sk_...) issued via the dashboard. Org-scoped, long-lived, for server-to-server use.
  • User JWT obtained via the OAuth 2.1 authorization code flow with PKCE. User-scoped, short-lived. Discover the authorization server at /.well-known/oauth-authorization-server and the protected-resource metadata at /.well-known/oauth-protected-resource/api.

Path Parameters

domain
string
required
Example:

"brand.example"

Response

Synchronous crawl result

domain
string
required
previous_source
enum<string> | null
required
Available options:
hosted,
brand_json,
community,
enriched,
stub,
null
new_source
enum<string> | null
required
Available options:
hosted,
brand_json,
community,
enriched,
stub,
null
previous_source_type
enum<string> | null
required
Available options:
brand_json,
community,
enriched,
stub,
null
new_source_type
enum<string> | null
required
Available options:
brand_json,
community,
enriched,
stub,
null
promoted
boolean
required

True when the crawl replaced lower-trust stored evidence with live brand.json evidence.

brand_json_found
boolean
required
live_variant
enum<string> | null
required
Available options:
authoritative_location,
house_redirect,
brand_agent,
house_portfolio,
brand_canonical,
null
has_manifest
boolean
required
checked_at
string<date-time>
required