The Brand API Register

Rainbrand vs Context.dev

Context.dev reads a company's look from its website, including styles and font files. Rainbrand builds a brand from site, guides and files, and checks the work.

Last updated 2026-11-10

Both go beyond a logo. Context.dev reads what a company's website shows: logos, colours, images, typography, spacing and component styles, with font files where it can resolve them. Rainbrand builds a brand from the website and from the guide, files and direction you add, then keeps it as you edit it.

RainbrandContext.dev
JobAgentic brand workOne-off lookups
What it gives you
LogosYesYes
ColoursYesYes
FontsYesYes
GuidanceYesNo
FilesYesPartly
Access and cost
You sendYour sources for a brand, then a taskA domain, name, work email, ticker or page URL
AuthenticationAPI key, or OAuth for connected accountsAPI key; a public client ID for Logo Link
Free tier1,000 credits and one new brand, once1,000 credits a month
Paid from$20 a month (Plus)$20 a month (Developer)
MCP serverYesYes
Checked2026-11-102026-11-10

Choose Context.dev if

  • You need any company's look without that company doing anything, for example to theme a design tool to a customer's website.
  • You want spacing and component styles from the site.
  • You want a low entry price, $20 a month, or other web data from the same API.

Choose Rainbrand if

  • You need the rules behind the styles: voice, claims, what to avoid. Context.dev returns no voice or usage rules, and its docs say to review the values before using them as a design system.
  • You want changes you approve, not the next re-read of the website, to decide what agents use.
  • You want each piece of work checked against the brand.

Sources