Query the Google CrUX API for Core Web Vitals field data
domain: chromeuxreport.googleapis.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
POST https://chromeuxreport.googleapis.com/v1/records:queryRecord?key={API_KEY} with a JSON body specifying url or origin and optionally formFactor or metrics
Parse the record.metrics object in the response for histogramData and percentiles (p75) per metric
Note that each response reflects a rolling 28-day aggregation window of real Chrome user data — not a single day snapshot
Expect data to be approximately 2 days behind the current date; the dataset updates daily around 04:00 UTC after processing the prior day's data
To track trends over time use the CrUX History API (POST .../records:queryHistoryRecord) which returns weekly data points over a longer window
For bulk/large-scale queries use the CrUX BigQuery dataset (google.com/chrome/ux-report), which is updated monthly
Known gotchas
The CrUX API (REST endpoint) updates DAILY around 04:00 UTC with a rolling 28-day window — it is NOT a monthly snapshot; the monthly cadence applies only to the BigQuery public dataset
Data is typically 2 days behind today because the pipeline waits for a complete day of data before publishing; do not expect same-day metrics
If an origin or URL has insufficient traffic it will be absent from the dataset and the API returns a 404; there is no zero-traffic record
Give your agent this knowledge — and 15,600+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?