Color palette
Detected hex colors with an inferred role like primary, text, or background, plus how often each one appears.
POST /v1/brand
Brand identity from a domain.
Pull a site's colors, fonts, logo, and favicon with one call.
Give your agent a domain and get back structured brand data your LLM can reason over: hex colors with inferred usage, font families, the logo URL, and the favicon. Built in Rust, it reads the HTML and inline CSS directly, so no headless browser is involved.
What you get
Everything in one call.
Font families
The typefaces pulled from stylesheets and inline styles, ready to drop into a design system.
Logo and favicon
The detected logo image URL and the site's favicon, resolved from link tags or the default path.
Structured JSON
Every field comes back typed and predictable, so your agent never has to parse a screenshot or guess at CSS.
How it works
From URL to output in four steps.
01
Send a domain
POST the URL of the homepage or marketing page you want to analyze.
02
Fetch the page
We retrieve the HTML and inline CSS directly, handling JavaScript rendering and bot protection automatically when needed.
03
Extract the identity
We scan inline styles, style tags, and common CSS patterns to surface colors, fonts, the logo, and the favicon.
04
Result returned
You get back a clean JSON object with the full brand profile, typically in a single round trip.
API
One request, structured back.
POST /v1/brand
Brand: webclaw.io
Colors
#F8F9FA— Primary#212529— Secondary#6C757D— Text#101828— Text
Fonts: Geist Mono, Geist, Instrument Serif, Merchant Copy
Common questions
Frequently asked questions
How do I extract a brand's colors and fonts from a website?
Send the site's URL to POST /v1/brand and you get back a JSON object with detected hex colors, their inferred usage, font families, the logo URL, and the favicon. No design tools or manual inspection needed.
Can I get a company's logo URL from its domain?
Yes. The response includes a logo_url field resolved from the page, plus a favicon_url pulled from link tags or the default /favicon.ico path. Both come back as direct image URLs.
Does brand extraction use a headless browser?
No. Brand data is read straight from the HTML and inline CSS, so it stays fast and lightweight. It still handles JavaScript rendering and bot protection automatically when a site needs it.
What pages work best for brand extraction?
Homepages and marketing pages give the strongest results, since that's where the primary palette, type, and logo usually live. Pass the apex domain or main landing page for the cleanest profile.
Am I billed for failed requests?
No. Credits are only consumed on successful responses. A standard page is 1 credit; heavier work like JS rendering or protected-site access costs a few extra credits.
Ship an agent that actually sees the web.
One credit pool, every endpoint. Cancel anytime, or self-host the open-source core for free.