Skip to main content

​
Overview

The Audit Scores API returns the AI-visibility scores Scrunch computes from its most recent site audit: retrievability (can an AI crawler reach and parse the page) and citability (once reached, is the page worth quoting). These are the same numbers the Site Optimization header shows in the dashboard. Two endpoints cover two questions: how is the site doing overall, and which pages are holding it back.

​
Endpoints

Both require a bearer token with the query scope. See Authentication.

​
Example request

​
Reading the fields

Two things are easy to misread.
A null site score is not an error. GET /audit-scores/site returns null when the brand has no finished audit yet — a new brand, or one whose first crawl is still running. Treat it as “not scored yet” rather than “scored zero”, and check for it before charting.
The page list is ordered by url, not by score. That is deliberate: a stable order is what makes limit/offset paging safe across requests, because a score that changes mid-page would otherwise shuffle rows between pages and cause you to skip or repeat one. Sort client-side if you want the worst pages first. limit accepts up to 1000. Page through the whole brand with offset; each page carries its url, its scores, and generated_at for when it was last scored.