canonical: https://jentic.com/apis/googleapis.com/webfonts

# Google Web Fonts Developer API

The Google Web Fonts Developer API exposes the catalogue of font families served by Google Fonts so that applications can programmatically discover available typefaces, variants, subsets, and category metadata. The API is read-only and returns the same font index that powers the Google Fonts directory, including version, last-modified date, files per variant, and supported scripts. It is most useful for building font pickers, design tools, and CMS integrations that need an up-to-date list of free, open-source web fonts.

## For AI agents

List Google Fonts metadata so an agent can pick a font family, variant, and subset, and resolve direct file URLs for embedding. Read-only catalogue access only.

## Scope

Does not handle font hosting, font file generation, custom font uploads, or licensing transactions - use for read-only catalogue lookups against the Google Fonts directory only.

## Capabilities

- List every Google Fonts family with variants, subsets, and category labels
- Filter the catalogue by sort order such as alpha, date, popularity, style, or trending
- Resolve direct font file URLs for each variant and format (TTF, WOFF2)
- Detect new and updated families using the lastModified timestamp on each entry
- Build font picker UIs that surface only families supporting a chosen subset like latin-ext or cyrillic

## Use cases

### Font picker for a design tool

Power a typeface chooser inside a website builder, slide editor, or design app by pulling the live Google Fonts catalogue at build or runtime. The API returns family name, category, variants, and subsets so the UI can group fonts and preview only the variants the user has installed. Because the response is read-only and cacheable, a daily refresh is sufficient for most products.

Example prompt: Fetch the full webfonts list sorted by popularity, filter to families with the latin subset and a regular 400 variant, and return the top 20 family names with their preview URLs.

### Self-hosting Google Fonts

Generate a self-hosted font bundle for privacy, performance, or compliance reasons by reading the catalogue, selecting families and subsets, and downloading the WOFF2 files referenced in each variant. Teams use this to build CSS bundles that meet GDPR requirements or to ship fonts with offline desktop apps. The lastModified field makes it possible to detect when an upstream family has been updated and re-bundle only what changed.

Example prompt: List all variants of Inter and Roboto for the latin subset, download each WOFF2 file URL, and emit a CSS @font-face block referencing the local files.

### CMS theme font catalogue

Keep a content management system or design system in sync with the latest Google Fonts directory by polling the webfonts endpoint and updating the available font dropdown for editors. The capability list (variants, subsets, category) maps directly to the controls editors expect in a theme settings panel. Update frequency can be daily or weekly because the upstream catalogue changes slowly.

Example prompt: Pull the webfonts catalogue, group families by category (sans-serif, serif, display, handwriting, monospace), and write the result to the theme configuration file used by the CMS editor.

### Agent-driven font selection through Jentic

Let an AI design assistant choose an appropriate Google Font for a brief by calling Web Fonts through Jentic. The agent searches with a phrase like 'list google fonts for body copy', loads the operation schema, and executes it with the desired sort order and subset. Jentic returns a structured response the agent can rank against tone, readability, and language coverage requirements before presenting options to the user.

Example prompt: Use Jentic to call the Google webfonts list operation with sort=popularity and subset=latin, then return the top five sans-serif families suitable for long-form body copy.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /v1/webfonts | List all Google Fonts families with variants, subsets, and file URLs |

## Key resources

- **webfonts** — The single catalogue resource. Listing it returns every Google Fonts family with its variants, subsets, category, files, and last-modified date.

## Why Jentic

- **Setup:** Wiring the Web Fonts Developer API by hand means provisioning a Google Cloud API key, appending it correctly, and matching query parameters like sort, subset, and capability against the webfonts.googleapis.com host. Through Jentic you install once, import the Web Fonts Developer API from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** The Web Fonts Developer API exposes a single read-only catalogue lookup, so you limit the agent to the operations it needs, such as listing the Google Fonts directory. You choose the operations it may call, so nothing beyond that lookup is available unless you add it.
- **Credential handling:** Your Google Cloud API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'list available Google fonts', and Jentic returns the GET /v1/webfonts operation with its query parameters so the agent calls the right endpoint without browsing Google's reference docs.

## Related APIs

- **Google Drive API** — Store generated font bundles or CSS files alongside other design assets
- **YouTube Data API** — Different read-only Google content catalogue serving creator metadata rather than typography
- **Google Calendar API** — Sibling Google API commonly used alongside webfonts in design-tool stacks

## FAQ

### What authentication does the Web Fonts Developer API use?

The Web Fonts Developer API is authenticated with a Google Cloud API key passed as the key query parameter. There is no OAuth flow because the catalogue is public and read-only. Through Jentic the API key is stored in the encrypted vault and injected at execution time so it never enters the agent's context.

### Can I download the actual font files from this API?

The API itself does not stream font binaries; the GET /v1/webfonts response includes a files object that maps each variant to a direct URL on fonts.gstatic.com. An agent or client follows those URLs over plain HTTPS to fetch the TTF or WOFF2 files.

### What are the rate limits for the Web Fonts Developer API?

Google does not publish a per-project quota specifically for webfonts; it falls under the standard Google APIs usage limits which are configurable in the Cloud Console under APIs and Services. Because the catalogue changes slowly, most integrations cache the response for hours or days rather than calling on every request.

### How do I list popular sans-serif fonts through Jentic?

Search Jentic with the query process a list of google fonts, load the schema for the GET /v1/webfonts operation, and execute it with sort=popularity. Filter the response to entries where category equals sans-serif. The full flow is search, load, execute against the single webfonts list endpoint.

### Is the Web Fonts Developer API free to use?

Yes. The Web Fonts Developer API is free; you only need a Google Cloud project and an API key. The fonts themselves are licensed under open-source licences listed in the Google Fonts directory and can be self-hosted at no cost.

### Can I limit what my agent is allowed to do with the Web Fonts Developer API?

Yes. Because Jentic One runs self-hosted on your own infrastructure, you decide which operations your agent may call, and your own rules govern the credentials it can use. The Web Fonts Developer API exposes only a single read-only catalogue lookup, the GET /v1/webfonts operation that lists Google Fonts families with their variants and subsets, so you can grant your agent that one listing call and nothing else. Any operation you do not explicitly allow stays unavailable to the agent.