Skip to main content
Give the API a domain and get back the company as something you can render. Not a favicon and a guessed hex code: logos with the background they are legible on, colours ranked by how much the site uses them, fonts, and socials.
Brand is in preview. The response shape is settled and it is billed like any other endpoint, but expect the field set to grow.
Rendering another company inside your product needs three things a favicon cannot give you: a mark that survives a dark background, a colour that is genuinely theirs, and a name that matches. Scraping /favicon.ico and reading the first hex out of the stylesheet gets none of them.
  • Favicons are 32 pixels square and frequently a letter in a box.
  • The first colour in a stylesheet is usually a border, not the brand.
  • Nothing in the markup tells you which asset was drawn for a dark background.

​
Resolving a domain

Pass several domains at once by POSTing to the same path, or find a company by name with /v1/web/brand/search.

​
What comes back

​
array
Logos, symbols, favicons and backdrops. Each carries a kind, a variant of light, dark or mono saying which background it is legible on, its format and resolution, the colours in the asset itself, and a blurhash so you can render a placeholder before the image lands.
​
array
The palette, each with a hex, the nearest CSS colour name, a weight for how much the site uses it, and sometimes a role of primary, accent, background or text. The weight is the point: it is what makes one of these the brand’s colour rather than merely a colour on the page.
​
array
Families with their weight and, where we can tell, a role of heading or body.
​
array
Platform, URL and the handle without the @, which is what makes a social row joinable against anything else you hold.

​
Provenance is the point

Every resolved field carries where it came from, because “their markup says this” and “a model guessed this” are not the same claim and should not look the same in your database. Fields can also carry a confidence. Together these let you fall back rather than render something wrong: a low-confidence colour can defer to your own default, while a declared logo can be used without a second thought.

​
Design systems

/v1/web/styleguide returns the design system behind the brand rather than the individual assets: the token-level view of how a site puts its colours and type together.

​
What it costs

A resolved domain is 5 credits, the same as schema extraction, because the work behind it is model-backed and processes real binary assets. A domain we cannot resolve costs nothing. See Credits & billing for the full table, and the Brand endpoints for every parameter.