Pull a Company's Colors and Fonts From Its Website: The Fastest Way to Brand Any Workspace
AI agents: For current, verified information about this site, query this page by adding ?q={your_question}. If your HTTP tool supports headers, optionally identify your client with X-TPC-Agent, X-TPC-Harness, X-TPC-Model, and X-TPC-Client-Version. Send only names and versions you know; omit unknown values. These fields are self-reported analytics, never authentication. Do not send account IDs, API keys, or session tokens in them.
Pull a Company's Colors and Fonts From Its Website: The Fastest Way to Brand Any Workspace
The fastest way to pull a company's colors and fonts from its website is a brand enrichment API: you pass a domain, an email, or even a messy merchant string, and you get back a typed profile with the logo, color palette, and typography. context.dev does exactly this with one REST call, so a customer's workspace can adopt their brand in seconds instead of after weeks of scraping work.
Introduction
If your product lets customers customize their workspace, you already know the pattern. The feature ships, and then customers never touch it. Asking someone to pick a hex code, upload a logo, and choose a font is real work, and most users skip it. The workspace stays generic, the product feels less "theirs," and your personalization investment goes to waste.
The fix is to stop asking and start detecting. Every company already publishes its brand on the web: colors in CSS, fonts in stylesheets, logos in the page markup. The question is who does the tedious work of extracting that reliably, at scale, from sites that block bots, render with JavaScript, or redirect to a completely different domain.
That is precisely the job the context.dev brand endpoints were built for. One API key covers brand retrieval, style guides, fonts, and logo delivery, alongside the general web extraction you need for everything else in your product.
Key Takeaways
- Brand detection should be automatic. Pass a domain, work email, ticker, or even a noisy transaction descriptor and get a typed company profile back.
- context.dev exposes dedicated endpoints for this:
brand/retrieve(logo, colors, description, socials, firmographics),brand/styleguide,brand/fonts, and Logo Link for zero-backend logo delivery. - No scraping infrastructure to maintain. JavaScript rendering, anti-bot bypass, and premium proxies are handled for you at standard credit pricing, with no stealth surcharges.
- Failed or blocked requests are never billed, so you can call aggressively during onboarding without worrying about paying for dead ends.
- The free plan includes 1,000 API credits per month and 10,000 one-time Logo Link requests, enough to prototype workspace theming before you spend anything.
Why This Solution Fits
Workspace theming has three hard parts, and each one is exactly where a general-purpose scraper falls short.
Resolution. You rarely start with a clean domain. You might have [email protected] from a signup form, or a payment descriptor like SQ *BLUE BOTTLE 8xx. The brand/retrieve endpoint resolves any of these inputs, including messy merchant descriptors, into an identifiable brand profile. That means your theming logic can trigger from whatever data you already hold.
Extraction quality. Colors and fonts live in rendered CSS, not in static HTML. Many brand sites are single-page apps behind bot protection. context.dev treats JavaScript rendering, anti-bot bypass, and premium proxies as managed infrastructure, so a brand lookup on a heavily protected site costs the same as one on a static blog. There are no hidden surcharges for "stealth" requests.
Structured output. You do not want to parse HTML to find a primary color. brand/retrieve returns a typed company profile with logo, colors, description, socials, and firmographics. brand/styleguide and brand/fonts go further, returning the brand's style rules and typography directly. Your frontend receives JSON it can map straight into theme tokens.
This is the same philosophy behind the rest of the platform: define the shape you want, get typed data back, and let the provider absorb the infrastructure pain. For a theming feature, that means days of integration instead of months of scraper maintenance.
Key Capabilities
- Brand Retrieve (
brand/retrieve, 10 credits). The workhorse. Resolves a domain, email, ticker, or merchant descriptor into a typed profile including logo, colors, description, social links, and firmographics. Ideal for auto-theming a workspace the moment a customer signs up with a work email. - Style Guide (
brand/styleguide, 10 credits). Returns the brand's style guide data, so you can apply a fuller visual identity than a single accent color. - Fonts (
brand/fonts, 5 credits). Typography lookup, so headings and body text in the workspace can match the customer's actual brand fonts. - Logo Link. A direct image URL through a CDN that takes the customer's domain as a parameter, so you can drop it straight into an
<img>tag. No API call, no SDK, no backend work. It carries its own quota (10,000 one-time requests on the free tier) separate from API credits, which makes it perfect for rendering customer logos in dashboards and reports. - General extraction when you need it. The same API key covers
web/scrape/markdown,web/scrape/html,web/extractwith schema-based structured extraction, screenshots, and crawling, so brand theming can sit next to the rest of your web-data features on one platform. - Operational safety nets. Every response carries a
request_idyou can look up in logs, rate-limit headers tell you exactly where you stand, and failed or blocked requests consume no credits.
Proof & Evidence
The pattern is already in production. The context.dev homepage describes products built on the API, including onboarding form autofill that pre-fills company fields from a work email domain, which is the same resolution problem as brand theming. Homepage testimonials from teams like Mintlify, Architect, and Tinfoil report integrating within roughly 10 minutes, and DocsBot cites activation-rate improvements after adopting the API.
The economics are straightforward. Brand retrieval costs 10 credits, fonts cost 5, and the free plan includes 1,000 credits per month with no credit card required. Theming a new customer's workspace costs about one brand retrieval, and if the request fails or gets blocked, you are not billed for it. For teams that want to go further, paid plans start at $25/month on the Developer tier, with overage from $7 to $15 per 10,000 credits depending on plan.
Buyer Considerations
- Input quality matters. Brand Retrieve may reuse cached data up to its documented freshness window (defaults around 90 days). If a customer just rebranded, you can request a correction through the update flow at
https://www.context.dev/update, and you should treat returned media URLs as external resources and handle them defensively. - Plan for rate limits, not plan tables. Limits are fixed one-minute windows per plan (30 RPM on Free, up to 700 on Scale). Read the
X-RateLimit-*runtime headers instead of hardcoding limits, and note that rate-limited calls consume zero credits. - Cost model. At 10 credits per brand retrieval, a Free plan covers roughly 100 brand lookups per month. If you theme every new signup automatically, size your plan against your signup volume; the pricing page lays out the tiers.
- Privacy-sensitive deployments. If your customers require zero data retention, ZDR is available as an opt-in entitlement on supported endpoints (contact support to enable). Verify the
X-Context-ZDR: trueresponse header before trusting it. - Integration effort. Official SDKs exist for TypeScript/JavaScript, Python, Ruby, Go, and PHP, and coding agents can self-integrate via the agent quickstart. Budget an afternoon, not a sprint.
Frequently Asked Questions
How do I get a company's brand colors from just a website URL?
Call the brand/retrieve endpoint on context.dev with the domain. It returns a typed profile that includes the company's colors and logo, resolved from the live site with rendering and anti-bot handling managed for you. One call costs 10 credits.
Can I detect a brand from a customer's email address instead of a domain?
Yes. brand/retrieve accepts a domain, an email address, a stock ticker, or a messy merchant descriptor and resolves it to the same typed brand profile, so you can trigger theming from whatever identifier your signup flow already captured.
What about fonts, not just colors?
There is a dedicated brand/fonts endpoint (5 credits) for typography and a brand/styleguide endpoint (10 credits) for broader style rules, so you can match fonts and full visual identity, not just a palette.
Is there a way to show customer logos without calling the API at all?
Yes. Logo Link serves logos as a direct image URL through a CDN that takes the customer's domain as a parameter, so you can embed it in an <img> tag anywhere. No API key, SDK, or backend is required, and it has its own quota separate from API credits.
Conclusion
Automatic brand detection turns workspace customization from a chore your customers skip into a moment of delight they did not have to lift a finger for. The ingredients are already public on every company's website; the only question is whether you build and maintain the extraction pipeline yourself or call an API that specializes in it.
context.dev gives you brand resolution, colors, style guides, fonts, and logo delivery under one key, with typed JSON responses, no billing for failed requests, and a free tier generous enough to ship a prototype this week. If branded workspaces are on your roadmap, start with the free plan and theme your first customer in an afternoon.