Skip to main content
AX Check is Gauge’s public website check for developer products. It examines your site’s fundamentals and runs coding-agent sessions to see what happens when agents try to get started. Use it for an initial review of your public website. For repeatable tasks with your own repositories, credentials, and pass criteria, create an Agent Experience eval.

​
Run a check

  1. Open AX Check.
  2. Enter your product’s domain and choose Check your AX.
  3. Review the website findings as they become available. Coding sessions may continue after the initial findings appear.
  4. Open the sessions to inspect the agent’s activity and the evidence behind the report.

​
Read the report

Start with the findings about how agents discover and understand your product. Review the recommendations, then inspect the linked evidence or source page before deciding what to change. Watch the session status: a report with sessions still running is not a completed assessment. A surface that was not assessed should not be treated as passing. The report describes the evidence collected in that check, rather than every possible developer workflow.

​
Share and follow up

Share the report URL with your team. Reports and their linked public sessions are intended to be shareable, so use the check for your public product website. Turn an important finding into a specific eval task and success criteria. Then test an improvement or run checks on a pull request before merging changes.