readiness.sh
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: readiness.sh

Sep 30, 2026 19:00 UTC · 86.63/100 · Coverage 95.7%

Model 27 · content

Capture static v28

View exact report

Later: readiness.sh

Sep 30, 2026 19:02 UTC · 71.11/100 · Coverage 93.8%

Model 27 · api

Capture static v28

View exact report

Changed checks

  • API catalog: not_applicable → error
  • REST typed error model: not_applicable → pass
  • API schema complexity: not_applicable → fail
  • REST versioning and deprecation policy: not_applicable → warning
  • REST asynchronous job pattern: not_applicable → fail
  • auth.md exists: not_applicable → pass
  • auth.md structure: not_applicable → fail
  • REST batch endpoint: not_applicable → fail
  • CLI tool available: not_applicable → fail
  • Developer portal: not_applicable → pass
  • Function calling compatibility: not_applicable → fail
  • Idempotency-Key support: not_applicable → pass
  • JSON error responses: not_applicable → fail
  • NPM or PyPI SDK package: not_applicable → fail
  • Agent onboarding friction: not_applicable → pass
  • OpenAPI document is published: not_applicable → pass
  • REST pagination pattern: not_applicable → fail
  • Pricing information is accessible: not_applicable → fail
  • Public API documentation is linked: not_applicable → pass
  • Public API endpoint responds: not_applicable → pass
  • Developer resource discoverability: not_applicable → error
  • REST response schema coverage: not_applicable → warning
  • Multi-language SDK packages: not_applicable → fail

Capture time and missing evidence can change results. The comparison does not prove that the site change caused each result.