The Brand API Register
One-off lookups

Brandfetch vs Context.dev

Both return a company's logos, colours and images from its domain. Brandfetch adds font names, a voice summary and webhooks; Context.dev adds fonts and styles.

Last updated 2026-11-10

Both go further than a logo: each returns logos, colours, images and company details from a domain. They differ in what else they read. Brandfetch summarises how a brand sounds; Context.dev reads how its website is styled.

BrandfetchContext.dev
JobOne-off lookupsOne-off lookups
What it gives you
LogosYesYes
ColoursYesYes
FontsPartlyYes
GuidancePartlyNo
FilesPartlyPartly
Access and cost
You sendA domain, URL, email, ticker, ISIN or crypto symbolA domain, name, work email, ticker or page URL
AuthenticationAPI key; a client ID for the Logo APIAPI key; a public client ID for Logo Link
Free tier100 brand fetches, once; 1M logo requests a month1,000 credits a month
Paid from$129 a month (Growth Starter)$20 a month (Developer)
MCP serverYesYes
Checked2026-11-102026-11-10

Choose Brandfetch if

  • You want a written summary of a brand's voice and visual style, from the Brand Context API.
  • You want webhooks when a brand you follow is updated or rebrands.
  • You want data its owners can curate: since May 2026, brands claimed by their owners aren't overwritten by re-crawls.

Choose Context.dev if

  • You need the website's type, spacing and component styles, with font files where they can be resolved (Styleguide).
  • You want a lower entry price: $20 a month for 5,000 credits, which is 500 lookups at 10 credits each. Brandfetch's first paid plan is $129 a month for 2,500.
  • You also need other web data, since Brand and Styleguide are part of a wider scraping API.

What do they have in common?

  • Both describe what a brand publishes, not the guidelines its team follows.
  • Both re-read a brand when their copy is about three months old: Brandfetch on the next request, Context.dev by default.
  • Both have an MCP server with OAuth sign-in.

Sources