Back to Readiness
Compare exact reports
Use two scan IDs. A score change is shown only when the URL, site type, and model match.
The URL, site type, or model changed. The scores cannot be compared directly.
Earlier: bestbuy.com
Sep 22, 2026 17:29 UTC · 34.83/100 · Coverage Not measured
Model 26 · legacy scope
Capture static v27
View exact report
Later: bestbuy.com
Sep 30, 2026 18:10 UTC · 59.39/100 · Coverage 80.7%
Model 27 · commerce
Capture static v27
View exact report
Changed checks
-
A2A Agent Card: error → not_applicable
-
Agent auth discovery metadata: fail → not_applicable
-
API catalog: error → not_applicable
-
auth.md exists: fail → not_applicable
-
CLI tool available: fail → not_applicable
-
Developer portal: fail → not_applicable
-
GraphQL asynchronous job pattern: error → not_applicable
-
GraphQL typed error model: error → not_applicable
-
GraphQL pagination pattern: error → not_applicable
-
GraphQL versioning and deprecation policy: error → not_applicable
-
JSON error responses: fail → not_applicable
-
OAuth authorization-server metadata: fail → not_applicable
-
Official MCP Registry listing: warning → not_applicable
-
MCP server or manifest: fail → not_applicable
-
MCP server card: fail → not_applicable
-
MCP well-known discovery: fail → not_applicable
-
NPM or PyPI SDK package: fail → not_applicable
-
OAuth protected resource metadata: error → not_applicable
-
OAuth 2.0 support: fail → not_applicable
-
Agent onboarding friction: fail → not_applicable
-
OpenAPI document is published: error → not_applicable
-
Public API documentation is linked: fail → not_applicable
-
Developer resource discoverability: error → not_applicable
-
Multi-language SDK packages: fail → not_applicable
-
Scoped permissions: fail → not_applicable
-
Universal Commerce Protocol: error → not_applicable
Capture time and missing evidence can change results. The comparison does not prove that the site change caused each result.