# Website histories

Keep every retained run for a URL together and compare matching observations.

## One property per URL

The [Websites](/dashboard) page groups your runs by the normalized requested URL. Opening a property shows its latest result, the most recent comparable pair and a paginated history. Grouping covers all retained runs, not just the first page.

HTTP and HTTPS remain separate, as do different paths and query strings. Fragments are removed by the existing URL normalizer. Property keys identify URLs; they do not grant access to another account’s history.

## Run and compare

Rerun & compare immediately starts an audit of the same URL with the displayed report as its baseline. The new report opens while the audit runs. Merely opening a property or report never starts an audit.

```sh
evx vibecheck https://example.com --compare-to REPORT_ID --wait
```

Comparisons require matching targets, auditors and methodologies. A version change can make runs incomparable. Coverage changes are separate from measured check changes; neither establishes an effect on agent performance. Legacy reports remain accessible in their original form.

## Read history through the API

```sh
evx api GET /websites
evx api GET /websites/PROPERTY_KEY
```

Use the returned nextCursor unchanged to fetch the next page. Website collections and histories require account access through the API. The web interface also supports browser-owned guest history. Individual website report links remain shareable; the grouped history is private.

Delete removes an individual report’s content and its public link. Deleting the final retained run removes that property from the overview. Creating more reports does not overwrite earlier runs.