Font {API}

Detect the fonts any website uses, from just a domain.

Get font families, weights, styles, sources (Google Fonts, Adobe, self-hosted), and usage context. Perfect for branded dashboards, white-labeled templates, and design tooling.

No credit card required
View Documentation
Daydream logo
Kovai logo
Passionfroot logo
Orange logo
SendX logo
Klarna logo
Super.com logo
Daydream logo
Kovai logo
Passionfroot logo
Orange logo
SendX logo
Klarna logo
Super.com logo
Daydream logo
Kovai logo
Passionfroot logo
Orange logo
SendX logo
Klarna logo
Super.com logo
Daydream logo
Kovai logo
Passionfroot logo
Orange logo
SendX logo
Klarna logo
Super.com logo

What You Get

Each API call returns structured font data from the target website.

Font families

Primary and fallback fonts with full stack

Weights & styles

Bold, Regular, Light, and more

Font sources

Google Fonts, Adobe, self-hosted identified

Similar alternatives

For protected custom fonts

How It Works

We analyze stylesheets and web font imports to accurately detect typography.

— step 01

Pass a domain

Like airbnb.com or any company website

— step 02

We scan stylesheets

CSS files, inline styles, @font-face, and web font imports

— step 03

Fonts categorized

By role: primary, secondary, fallback

— step 04

JSON returned

Structured typography data ready for use

API Response

Extracted typography for context.dev

GET /v1/styleguide?domain=context.dev
{
  "status": "ok",
  "domain": "context.dev",
  "styleguide": {
    "typography": {
      "p": { "fontFamily": "Inter, sans-serif", "fontSize": "14px" },
      "headings": {
        "h1": { "fontFamily": "Courier New, monospace", "fontSize": "36px" },
        "h2": { "fontFamily": "Inter, sans-serif", "fontSize": "24px" }
      }
    }
  },
  "code": 200
}

Frequently asked questions

Common questions about the Context.dev Font API.

Am I billed for failed requests?
No. You are not billed for failed requests or requests where we are blocked (rarely happens). Credits are only consumed on successful responses.
How does the Font API detect fonts on a website?
The API renders the page in a headless browser, then walks the computed style tree to read the actual fontFamily applied to headings, body, and UI elements. It also parses @font-face declarations, link tags to Google Fonts / Adobe Fonts, and @import rules — so the response reflects what users really see, not just what is declared in the source CSS.
What font information does the API return?
Each response includes the primary font family for body text and headings, fallback stacks, weight and style variants in use, the source (Google Fonts, Adobe Fonts, self-hosted, or system font), and usage context (heading vs paragraph). The output is structured JSON ready to drop into a design tool or branded template.
Can the API identify what font a website uses?
Yes — Context.dev is the programmatic equivalent of "Inspect → fontFamily" for any domain on the public web. Pass a URL, get back the heading and body font names. We resolve the rendered font, not just the first item in the CSS stack.
What happens with custom or proprietary fonts?
When a brand uses a licensed custom font that isn't publicly distributable, the API returns the font name plus a publicly available alternative (similar style and metrics) so you can still render branded UI without breaching the original license.
Does the Font API work for Google Fonts and Adobe Fonts?
Yes. Google Fonts, Adobe Fonts (Typekit), Bunny Fonts, and self-hosted webfont CDNs are all detected. The "source" field in the response tells you exactly where the font is loaded from so you can replicate the embed.
Is the Font API free?
Yes — the free tier covers thousands of monthly font lookups. A single API key also unlocks Logo, Colors, Styleguide, and the rest of the Context.dev brand-data suite.

Ship an agent that actually knows things.

Free tier, 10-minute integration, and the same API powering agents at Mintlify, daily.dev, and Propane. No credit card to start.