> ## Documentation Index
> Fetch the complete documentation index at: https://docs.atomicagi.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Agent Experience (AX)

> See whether an agent can complete a task on your site and turn recorded obstacles into fixes

![AX audit overview with journey performance trends and audit history](https://mintcdn.com/atomicai/o1UXF9Kjn6xUC_RX/images/data/technical/app-technical-ax-audit.png?fit=max\&auto=format\&n=o1UXF9Kjn6xUC_RX\&q=85\&s=15e10c13b15024179eed1c690b26131a)

Open **Technical → Agent Experience (AX)** to review a recorded agent journey alongside site-readiness checks. These screenshots use illustrative local data.

## Access and starting a run

AX requires **Team Max or a higher plan** and access to Technical. Starting a run also requires write permission. A visible navigation item does not mean the current plan can run audits.

From the history page, choose **Run new audit**, select **Agent and model**, and choose a **Journey prompt** task. Review the prompt for the project domain before choosing **Run audit**. The report opens while the run progresses. Start another run from the history page; individual reports do not have a run command.

![Run AX audit dialog with an agent and model selection and journey prompt](https://mintcdn.com/atomicai/o1UXF9Kjn6xUC_RX/images/data/technical/app-technical-ax-audit-setup.png?fit=max\&auto=format\&n=o1UXF9Kjn6xUC_RX\&q=85\&s=e00ab98ef7148671ed8d2f1744aa008b)

## Read the overview and history

The overview shows the latest completed journey. Trends compare runs with the same prompt and model; changing either changes the comparison. Use the history row's status, prompt, model, steps, and duration to choose a comparable run.

* **Answer from site:** whether the answer used site evidence.
* **Answer efficiency:** how efficiently the agent gathered the evidence for its answer.
* **Followed site links:** whether navigation followed the site's links.
* **Steps and Duration:** the amount of work and time recorded for the journey.

Inside a report, **Site agent-readiness** provides technical readiness evidence separate from the journey outcome.

A successful run does not guarantee every task or agent will succeed. Check the recorded answer and trace before assigning fixes. Pending checks and incomplete provider analysis are not confirmed failures.

## Agent answer tab

![AX report showing site agent-readiness, the Agent answer tab and priority fixes](https://mintcdn.com/atomicai/o1UXF9Kjn6xUC_RX/images/data/technical/app-technical-ax-audit-answer.png?fit=max\&auto=format\&n=o1UXF9Kjn6xUC_RX\&q=85\&s=91322f83bc39893a51b93bea57bd3f85)

This is the default report tab. Compare the answer with the saved prompt and model. Inspect the recorded journey and discovered URLs to find where the agent succeeded, took a detour, or stopped. Use replay controls when a recorded trajectory is available.

If no answer or trajectory was supplied, treat that as missing evidence. Do not infer a completed task from site-readiness scores alone.

## All checks tab

Use **All checks** to investigate the technical conditions behind a journey. Expand a finding to read its observed evidence and recommended action. Work through **Priority fixes**, then rerun the same task and model after the site changes.

### By layer tab

![AX check layers grouped by technical area](https://mintcdn.com/atomicai/o1UXF9Kjn6xUC_RX/images/data/technical/app-technical-ax-audit-layers.png?fit=max\&auto=format\&n=o1UXF9Kjn6xUC_RX\&q=85\&s=a94aeac2b505c70ace394d82cf9c4f22)

Read checks by technical area to find clusters of related problems. An optional signal and a required access check do not carry the same meaning.

### By status tab

![AX checks grouped by pass, warning, failure and pending status](https://mintcdn.com/atomicai/o1UXF9Kjn6xUC_RX/images/data/technical/app-technical-ax-audit-status.png?fit=max\&auto=format\&n=o1UXF9Kjn6xUC_RX\&q=85\&s=be9651d847c2d6f10ecc0eacd3353b78)

Separate failed and partial checks from pending, error, and not-applicable results. An error means the check lacks a reliable result; it is not proof that the site failed it.

### Methodology tab

![AX methodology describing score rubrics and report provenance](https://mintcdn.com/atomicai/o1UXF9Kjn6xUC_RX/images/data/technical/app-technical-ax-audit-methodology.png?fit=max\&auto=format\&n=o1UXF9Kjn6xUC_RX\&q=85\&s=9b35a921a8320121e03640c92296f98d)

Review the provider rubrics and report provenance before comparing scores. Different rubrics use different checks and weights. Use the captured target and timestamps to understand the scope of the evidence.

## Where to go next

* [Technical overview](https://docs.atomicagi.com/data/technical/overview.md)
* [LLM audit](https://docs.atomicagi.com/data/technical/llm-audit.md)
* [Crawler logs](https://docs.atomicagi.com/data/crawler-logs/overview.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.