unifont.dev valid

unifont

unifont reads font metadata from every major font CDN through one interface: Google Fonts, Bunny Fonts, Fontshare, Fontsource, Google Icons, npm and Adobe Fonts. It is an MIT-licensed JavaScript library, and unifont.dev is its project site, catalogue and public HTTP API.

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-27T10:03:58.088Z. Cached copy · Source on unifont.dev

# unifont

> unifont reads font metadata from every major font CDN through one interface: Google Fonts, Bunny Fonts, Fontshare, Fontsource, Google Icons, npm and Adobe Fonts. It is an MIT-licensed JavaScript library, and unifont.dev is its project site, catalogue and public HTTP API.

Every page on unifont.dev is also an endpoint. Ask for `text/markdown` (or append `.md` to a path) and any prose page answers in markdown. The API is described by an OpenAPI document, and there is an MCP server for agents that would rather call tools than URLs.

## When to use this

Reach for unifont.dev when the question is about a **web font that is published on a CDN**. Specifically:

- **"Does family X exist, and where can I get it?"** Search the merged catalogue of every family the providers will list: `GET /api/v1/fonts?q=<query>`. Never fuzzy, so a miss means the name is wrong.
- **"What weights, styles and subsets does family X actually publish?"** `GET /api/v1/fonts/<family>`. Returns provider metadata plus the resolved `@font-face` data, so you do not have to guess whether a weight exists before you ship CSS referencing it.
- **"Give me `@font-face` CSS for these families."** `GET /api/v1/fonts/<family>/css`, or `GET /api/v1/css?families=A,B,C` for a batch. The output is servable as-is and includes a metric-matched fallback where one can be built.
- **"Which provider should I load this family from?"** `GET /api/v1/fonts/<family>/compare` asks every credential-free provider the same question and shows where the answers differ (weights, subsets, hosts, file counts, bytes).
- **"Can this font draw this text?"** `GET /api/v1/fonts/<family>/coverage?text=…` checks the resolved `unicode-range`s, which is how you catch a family that silently cannot set Polish, Vietnamese or Greek.
- **"How heavy is this selection?"** `GET /api/v1/fonts/<family>/transfer` measures the real files with `HEAD` requests. Nothing is downloaded. `GET /api/v1/transfer?families=A,B,C` does the same for a list, all quoted against one selection.
- **"What does *this text* cost in this family?"** `GET /api/v1/fonts/<family>/budget?text=…` prices one string three ways: everything the selection publishes, only the files the text pulls through `unicode-range`, and, where the provider subsets to a glyph list, the subset. For a CJK family the three differ by orders of magnitude.
- **"Which families are variable, have an italic, or cover Greek?"** `GET /api/v1/fonts?variable=1&italic=1&subset=greek`, with `GET /api/v1/facets` for the counts.
- **"What should I put in the fallback stack?"** `GET /api/v1/fonts/<family>/fallback` returns a metric-matched `@font-face` and the descriptors it sets.
- **"Which fonts are only on npm?"** `GET /api/v1/fonts?provider=npm` lists the families this site resolves through the `npm` provider, which the font CDNs do not carry.
- **"How do I do this in my own build?"** Read the library documentation below. For a Vite or Nuxt app, the answer is usually `fontless` or
…

Related sites

Explore similar publishers →

Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.

Machine-readable: GET /v1/resolve?q=unifont.dev · GET /v1/domain/unifont.dev · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for unifont.dev:
1. POST https://agentwebmap.com/v1/sites/unifont.dev/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://unifont.dev/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/unifont.dev/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/unifont.dev).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.