Chrome UX Report API

Name: Chrome UX Report API API
Brand: Chrome UX Report API
Availability: InStock

✓ Official Vendor SpecAnalyticsWeb AnalyticsapiKey2 EndpointsREST

For Agents

Query Chrome real-user performance data and Core Web Vitals (LCP, INP, CLS) for any public origin or URL with no instrumentation required.

Quickstart

Get started with Chrome UX Report API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"get core web vitals for an origin"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Chrome UX Report API API.

Query the latest 28-day Core Web Vitals for any public origin

Query historical six-month time series of Core Web Vitals at the URL or origin level

Filter results by form factor — phone, tablet, desktop

Retrieve metric distributions across good, needs improvement, and poor buckets

GET STARTED

Start building with Chrome UX Report API API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Chrome UX Report API API for, with concrete tasks.

★ Core Web Vitals Dashboard

Performance engineers ingest CrUX queryRecord results into a dashboard that shows LCP, INP, and CLS distributions for owned origins, broken down by form factor. The data is real-user field data — no synthetic or RUM instrumentation required — which makes it the canonical source for Google's Search ranking signal. Most teams refresh weekly because the dataset is calendar-aligned.

POST /v1/records:queryRecord with origin=https://example.com and metrics=["largest_contentful_paint","interaction_to_next_paint","cumulative_layout_shift"] and return p75 values.

Historical Trend Analysis

Engineering managers track week-by-week regression and improvement of Core Web Vitals using queryHistoryRecord, which returns a six-month rolling time series. This shows whether shipped optimisations actually moved field metrics rather than only synthetic ones. The same call also surfaces form-factor splits so teams can isolate mobile-only regressions.

POST /v1/records:queryHistoryRecord with url=https://example.com/checkout and metric=largest_contentful_paint and return the six monthly p75 values.

Competitor Benchmarking

Product teams query CrUX for competitor origins to benchmark their real-user performance. Because CrUX is public for any origin meeting the eligibility threshold, no special access is required. This is widely used in retail and media verticals to scope optimisation roadmaps against the market.

POST /v1/records:queryRecord for origin https://competitor.com formFactor=PHONE and return whether all three Core Web Vitals pass.

AI Agent Performance Reporter via Jentic

An AI agent through Jentic runs an on-demand performance check — fetching the latest CrUX data for a list of owned origins, summarising which fail Core Web Vitals thresholds, and recommending where to invest. Jentic isolates the API key so the agent never sees the raw key value.

Through Jentic, search chromeuxreport_query_record, load schema, and execute it for origin https://example.com formFactor=PHONE and return p75 LCP.

Key Endpoints

2 endpoints — the chrome ux report (crux) api exposes aggregated, anonymised real-user performance data collected from chrome users for any sufficiently popular public origin or page url.

METHOD

PATH

DESCRIPTION

POST

/v1/records:queryRecord

Query the latest 28-day CrUX record for an origin or URL

POST

/v1/records:queryHistoryRecord

Query rolling six-month CrUX history for an origin or URL

POST

/v1/records:queryRecord

Query the latest 28-day CrUX record for an origin or URL

POST

/v1/records:queryHistoryRecord

Query rolling six-month CrUX history for an origin or URL

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Google Cloud API keys are stored encrypted in the Jentic vault (MAXsystem). Agents call CrUX with scoped access — the raw API key string never enters the agent's context.

Intent-based discovery

Agents search Jentic by intent (e.g. 'get core web vitals for origin') and Jentic returns the records.queryRecord operation with its parameter schema, including form factor enums.

Time to first call

Direct integration: 0.5-1 day for project setup, API key creation, and request signing. Through Jentic: under 30 minutes — search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

PageSpeed Insights API

Combines lab Lighthouse audits with CrUX field data for a single URL.

Use PageSpeed Insights when you also want lab diagnostics; use CrUX directly when you only need field metrics.

Complementary

Google Search Console API

Reports search performance and indexing status for owned properties.

Use Search Console for search clicks and indexing; use CrUX for real-user performance metrics.

Alternative

Google Analytics Data API

Reports first-party site analytics rather than aggregated Chrome field data.

Choose Analytics Data for first-party event metrics; choose CrUX for browser-collected Core Web Vitals at the origin or URL level.

FAQs

Specific to using Chrome UX Report API API through Jentic.

What authentication does the Chrome UX Report API use?

It uses a Google Cloud API key passed as the key query parameter. No OAuth is required since CrUX data is aggregated and public. Through Jentic, the API key is stored encrypted in the Jentic vault and the agent calls CrUX without ever holding the raw key string.

Can I query Core Web Vitals for any URL?

Only for URLs and origins that meet the CrUX eligibility threshold — enough Chrome real-user samples in the 28-day window. POST /v1/records:queryRecord with either the origin or url field; if the URL has insufficient data the API returns 404 and you should fall back to the origin-level query.

What are the rate limits for the Chrome UX Report API?

Google enforces a default of 150 queries per minute per project on CrUX. Higher quota can be requested via the Google Cloud console. The dataset itself updates daily, so caching responses for several hours is the standard pattern.

How do I pull six months of LCP history through Jentic?

Use the Jentic search query "chrome ux report history record" to discover the records.queryHistoryRecord operation, load its schema, and execute it with the origin or url and metric=largest_contentful_paint. Run pip install jentic to get started.

Does CrUX cover non-Chrome browsers?

No. The dataset is collected only from opted-in Chrome users on devices that meet the criteria. Use a separate RUM provider if you need data from Safari, Firefox, or Edge users.

Is the Chrome UX Report API free?

Yes, the API is free within the default project quota. The underlying CrUX dataset is also published as a free public BigQuery dataset for callers who need bulk historical analysis.