Skip to content
UxerProof

Public Circuits

Prove the journey before asking a customer to take it

A Public Circuit follows an unauthenticated goal across the pages anyone can reach, recording what the browser observed separately from what the AI User inferred.

Run your first CircuitView a sample report
Availability: The safe fixture runner is verified. External customer execution remains disabled until the production worker, storage and provider readiness gates pass.

What this proves

  • Journey completion

    See whether a visitor can move from entry page to the declared outcome within the approved step and time budgets.

  • Evidence at the point of friction

    Tie routes, visible labels, timing, screenshots and accessibility checks to the exact step that caused hesitation or failure.

  • Mobile and keyboard states

    Run the same declared journey with bounded device and input profiles instead of judging only a desktop screenshot.

  • Responsible target control

    Require workspace authority, an exact verified origin and an approved Test Contract before a Run can enter the queue.

The workflow

Bounded from target to evidence

  1. 01

    Create a Project and add its HTTPS Environment.

  2. 02

    Prove domain control with the exact DNS TXT token UxerProof issues.

  3. 03

    Choose an AI User, define the outcome and approve the bounded Test Contract.

  4. 04

    Run, review the Evidence Timeline and classify the resulting Findings.