The Brand Object

Context.dev Styleguide

The request and response of Context.dev's Styleguide for linear.app: color roles, type per heading, spacing, button and card styles, and font files.

Request
GET https://api.context.dev/v1/web/styleguide
Context
Observed: read from the public website of the company
Auth
Authentication is a bearer API key in the Authorization header. source, read 11 November 2026
Plans
As of 11 November 2026, Context.dev has a Free plan at $0 a month, and its cheapest paid plan, Developer, is $20 a month. Prefetching is not available on the Free plan. source, read 11 November 2026
Over MCP
Not published. The MCP setup page names no Styleguide tool. The Composio integration page lists CONTEXT_DEV_GET_WEBSITE_STYLEGUIDE as a Composio tool. source, read 11 November 2026
Sample
linear.app, requested 11 November 2026

One GET with a domain returns the styles of the Linear website. The response has three color roles, the font and size of each heading level and of body text, spacing steps and shadows. It also has the styles of buttons and cards, and download links for every font that the CSS names. Of the responses on this site, it gives the most detail about how the site looks. It says nothing about what the brand is.

The request

curl "https://api.context.dev/v1/web/styleguide?domain=linear.app" \
  -H "Authorization: Bearer $CONTEXT_DEV_API_KEY"

To read one page, send directUrl instead of domain. colorScheme=dark emulates dark mode, and Context.dev caches light and dark results separately. maxAgeMs works as on the Brand endpoint, with a default of 90 days.

The response

GET /v1/web/styleguide?domain=linear.appContext.dev Styleguide
{
"styleguide": {
"mode": "dark",1The Linear site is dark, so these are dark-mode colors.
"colors": { "accent": "#7170ff", "background": "#08090a", "text": "#f7f8f8" },
"typography": {
"headings": {
"h1": { "fontFamily": "Inter Variable", "fontSize": "72px", … },2Firecrawl read the h1 as 64px.
…
}
},
"elementSpacing": { "xs": "8px", "sm": "20px", "md": "30px", … },
"components": { "button": { "primary": { "backgroundColor": "#e5e5e6", … } } },
"fontLinks": {
"Berkeley Mono": { "type": "custom", "files": { … } },3Commercial. On media.brand.dev.
"Roboto": { "type": "google", … }4A name from the fallback list, not a brand font.
}
},
"cache_metadata": { "status": "hit", "age_ms": 239242548 }5A cached copy, about 66 hours old.
}

The full response, with every heading level and component, is in /data.json under responses.context-dev-styleguide.

What is not in it?

  • Logos, images and descriptions are not in it. For these, call the Brand endpoint.
  • The fonts that belong to the brand are not marked. The response has all seven fonts in the CSS, and five of them are fallbacks.
  • Rules are not in it. The Context.dev docs say that extracted values need review "for contrast, responsive typography and interactive states" before you use them as a design system.

Empty and failed responses

Context.dev documents these statuses: 400 (for example WEBSITE_BLOCKED or WEBSITE_NOT_FOUND), 401, 402 USAGE_EXCEEDED, 403 ACCESS_POLICY_DENIED, 408 REQUEST_TIMEOUT, 429 and 500. As on the Brand endpoint, Context.dev does not charge for validation, authentication, permission, timeout, rate-limit and server errors.

Plans

The Styleguide has the same plans as the Brand endpoint. As of 11 November 2026, Context.dev has a Free plan, and its paid plans start with Developer at $20 a month. See Context.dev's pricing page. The Context.dev docs name no Model Context Protocol (MCP) tool for the Styleguide.

Before you ship the fonts

The Context.dev docs say to make sure that you have the license for a font before you ship its files. Inter is open source. Berkeley Mono is sold by its foundry.

Last updated 11 November 2026