---
title: "What a Journey run tells you | Agent Readiness Compare"
description: "What Ora Journey records that a file-based scan does not, its published limits, and what one run cannot show, with vendor claims labelled."
canonical: https://agentreadinesscompare.com/guides/what-a-journey-run-tells-you/
site: "Agent Readiness Compare"
last_updated: 2026-11-05
date: 2026-11-04
section: "Guides"
---

# What a Journey run tells you | Agent Readiness Compare

> What Ora Journey records that a file-based scan does not, its published limits, and what one run cannot show, with vendor claims labelled.

Source: https://agentreadinesscompare.com/guides/what-a-journey-run-tells-you/
Site: Agent Readiness Compare
Last reviewed: 2026-11-05

# What a Journey run tells you that a scan cannot

Task-based testing with a real agent, read next to file-based scanning, using only what Ora publishes about it.

In short

A scan checks files, headers and pages. A Journey run sends a real agent at a domain with a task such as finding pricing and records each step, stall and outcome. It shows where an agent gets stuck, not how often. Ora caps each domain at 100 runs per rolling 24 hours.

## 1. A Journey run is a task, not a file check

Ora's Journey points a real agent at a domain with an intent such as "find pricing" and records every step, stall and outcome. A scan asks whether a file or header is present. A run asks whether an agent can finish a job. See the [glossary entry](https://agentreadinesscompare.com/glossary/journey-run/) for the term and [Ora's profile](https://agentreadinesscompare.com/tools/ora-ai/) for the product list.

| Question | Scan | Journey run |
| --- | --- | --- |
| What does it test? | Checks on files, headers and pages, across four layers. | A task that an agent attempts on the live domain. |
| What comes back? | A 0 to 100 score, a grade and a layer breakdown; deep checks finish afterwards. | A record of every step, stall and outcome. |
| What can it miss? | A dead end that only shows when an agent tries the job. | Anything the chosen task never touches. |

The Concordance of 2026-11-04 contains no Journey runs. Every score in it comes from a scan, so nothing here is a measured comparison of Journey against scanning.

## 2. The vendor claim is that a good-looking answer can hide a dead end

Ora's lab found (8 Oct 2026) that in about 99 percent of journeys that hit a dead end, the agent answered anyway from elsewhere. This is a vendor claim. This site could not re-run it, and the data does not say how many journeys it covers.

If the claim holds, the final answer alone is weak evidence. A run that ends with a plausible price may have left the site on the second step. The step record is what a team can read to see where the agent stalled and what it used instead.

## 3. The published limits shape how teams can use it

| Limit | What the source says |
| --- | --- |
| Tasks without a key | Curated tasks are listed at GET /api/journey/intents and run anonymously through POST /api/journey/runs. |
| Tasks that need a key | Free-text tasks, and POST /api/journey/domains/{host}, need a partner key. Keys are issued by email. |
| Run cap | Each domain is capped at 100 runs per rolling 24 hours and cannot run two at once. |
| Scores | is-agentic shows one journey per report as evidence outside the score, because one task cannot represent every agent. |

The cap is stated per domain, not per caller. Read plainly, anyone running Journey on your domain draws on the same 100, so a team that needs a clean batch should not assume the quota is its own.

## 4. What to do with a run, by reader type

-   **Head of web.** Use a run to show where an agent leaves your site, in steps a non-engineer can read. Do not report it as a score.
-   **Technical marketer.** Pick the curated task closest to a buying question, such as pricing, and compare the run with the scan result for the same domain.
-   **Platform engineer.** Read the first step of each run. agent-ready.dev notes that task-testing tools often hand the agent the endpoint and so skip discovery; check that a run found the site's entry points rather than being given them.

## 5. What this guide cannot tell you

-   How often a run repeats. No repeat-run data for Journey is published.
-   Which agents and models a run uses. The sources read here do not say.
-   How a run outcome relates to a scan score. No source read here gives that relationship.
-   Whether one task speaks for the rest. is-agentic's own answer is that it cannot, which is why it keeps one journey outside the score.

For how the scan side works, see [how to read an Ora score](https://agentreadinesscompare.com/guides/how-to-read-an-ora-score/). For why answer-engine results are a separate question, see [AX versus AEO](https://agentreadinesscompare.com/guides/ax-versus-aeo/).

## 6. Related

-   [Ora profile](https://agentreadinesscompare.com/tools/ora-ai/)
-   [Journey run, glossary](https://agentreadinesscompare.com/glossary/journey-run/)
-   [How to read an Ora score](https://agentreadinesscompare.com/guides/how-to-read-an-ora-score/)
-   [AX versus AEO](https://agentreadinesscompare.com/guides/ax-versus-aeo/)
-   [Scanners that test with real agents](https://agentreadinesscompare.com/scanners-that-test-with-real-agents/)

## 7. Sources

1.  Ora. [https://ora.ai/](https://ora.ai/?utm_source=agentreadinesscompare.com&utm_medium=referral&utm_campaign=guide), read 2026-11-04.
2.  Ora, llms-full.txt. [https://ora.ai/llms-full.txt](https://ora.ai/llms-full.txt?utm_source=agentreadinesscompare.com&utm_medium=referral&utm_campaign=guide), read 2026-11-04.
3.  Ora, AX is the new AEO. [https://ora.ai/blog/ax-is-the-new-aeo](https://ora.ai/blog/ax-is-the-new-aeo?utm_source=agentreadinesscompare.com&utm_medium=referral&utm_campaign=guide), read 2026-11-04.
4.  is-agentic.com. [https://is-agentic.com/](https://is-agentic.com/), read 2026-11-04.
5.  agent-ready.dev, comparison with alternatives. [https://agent-ready.dev/agent-ready-vs-alternatives](https://agent-ready.dev/agent-ready-vs-alternatives), read 2026-11-04.

Last reviewed 2026-11-05
