Agent Journey Lab

Start a $199 pilot

Product

An operator-led testing service. Not a software product.

A person runs each test and reads each record. There is no dashboard, no account, no API, and no signup. You receive the work by email.

Public research stops before form entry. An authorized test uses your written scope.

Start a $199 pilotRead the method

Our test sessions declare AgentJourneyLab/0.1. Site owners can stop a public test: read the research boundary or write to research@agentjourneylab.com.

What it is

What it is

  • The delivery model

    An operator scopes the work with you in writing, runs the test, and sends the record by email.

  • The run

    One declared journey, one completion criterion, and named agent families.

  • The record

    One dated document for each run, with each checkpoint and the exact stop.

What a run is

What a run is

A run has a declared goal, a named agent family, a checkpoint list, a control journey, and a completion criterion that you give before the run.

Control rule · fixture values

Internal fixture record — not a customer result.

Control journey

  • ✓ reached Entry
  • ✓ reached List
  • ✓ reached Availability
  • ✓ reached Details
  • ✓ reached Confirmation

Agent attempt

  • ✓ reached Entry
  • ✓ reached List
  • ✓ reached Availability
  • ✓ reached Details
  • ✗ stopped Confirmation
Two lanes, fixture values only. A control journey that a human path can finish shows that the stop is in the agent attempt, not in the test.

What you receive

What you receive

A screenshot of the example record page on this site. It shows the header field table of one run: record ID AJL-FIXTURE-CAL-002, the journey ID, the goal, the target, the attempt count, the configuration, the runner and build identity, the environment fields, and the control journey result.
The header of a finished record, photographed from our own example page. Every value in it comes from the calibration fixture in this repository, so it shows the field shape of a record and no customer work.

Record fields · fixture values

Internal fixture record — not a customer result.

Record fields
GoalThe declared journey, in your words.
Named agentThe agent family that made the attempt.
TimestampThe start of the run.
CheckpointsEach checkpoint and its state, reached or stopped.
Final stateThe place where the run stopped, and the observation that decided it.
Likely fix ownerThe team that holds the change: content, front end, platform, or policy.
Self-checkThe steps that let your team repeat the stop in less than one minute.
Change since last runWhat moved since the last dated record for the same journey.
This figure shows the field list of a record. Every value in a real record comes from a run. No value here does.

The pilot also includes one month of weekly monitoring and up to two retests after you fix an issue.

Not this

What it is not

  • No dashboard and no account.
  • No signup and no checkout.
  • No API and no integration.
  • No certificate, badge, or seal.
  • No readiness score and no grade.
  • No load test and no security test.

Fit

Who this pilot suits

A good fit

  • You sell or book through a public web journey.
  • You can name one journey that earns money.
  • You can authorize a test on the domain.
  • You want evidence that your team can repeat.

Not a fit

  • You want a certificate, a score, or a badge.
  • Your journey sits behind a private login that you cannot open for a test.
  • You want us to publish a comparison of other companies.
  • You want load testing or a security test.

Questions

Common questions

What do I get for $199?

You get three baseline attempts with the primary configuration and one attempt with the secondary configuration. You also get one dated evidence record, four dated weekly monitoring records across one month, and up to two retests after a fix.

Is this a software product?

No. This is an operator-led service. We do the work and we send you the record by email. There is no dashboard and no account.

Do you need access to my systems?

No. We use the public journey. If the scope needs a test account, you supply it and you set the limits in writing.

How do I pay?

We send payment instructions with the written scope. You pay before the test starts. This site holds no payment page and no form.

Do you publish my results?

No. Results stay private. We ask for written permission before we use any part of your results in public.

Can I stop the monthly renewal?

Yes. The renewal is optional. Tell us by email and the monitoring stops at the end of the paid month.

Which AI agents do you use?

We name the agent families in the written scope, and the record names the family that made each attempt. A record covers only the agents and the dates that it names.

How do you decide that a journey is complete?

You give the completion criterion before the run. It is the page state that means success, for example a basket with the correct total.

Does a stop prove that my site is at fault?

No. We report what the run observed. We also run a control journey and more than one attempt, and we name a likely fix owner.

Do you enter data in a form?

Not in public research. We stop before the first form field. We enter data only inside a written scope that you approve.

Do you use real customer data?

No. We use our own synthetic data. We use no real customer record, no health data, and no payment card.

Can you test more than one site?

Yes, after a pilot. We scope a multi-site program with you. Read the multi-site page for the workflow and the procurement facts.

Is the software enterprise-ready?

No. We deliver this service by hand today. The security page lists the controls that are deployed and the work that is still open.

What happens to my results?

We store each record outside the public website and we send it to you. The privacy page states what we hold and for how long.

Next step

Start with one journey.

Send the site and the journey. We reply with a written scope, the boundary, and payment instructions.

Start a $199 pilotRead the pilot scope