# Experiment tools

> The current Lexsis A/B testing workflow and experiment automation

Canonical URL: https://fa7e86e3d553:3005/tools/experiments

> **MCP v3 routing:** The operation names on this page are retained as action-contract references. Do not call them as top-level tools. Pass the former name to `lexsis_discover`, then call the returned router and action with the documented parameters inside `args`.

The primary way to run an A/B test is through the **A/B Testing** area in the
Lexsis workspace.

Read the complete guide first:

- [A/B Testing](/guides/ab-testing)

The guide explains how to prepare pages, start routing, understand production
links, read analytics, and pause or complete an experiment.

## Automation and MCP

If your workspace exposes experiment automation through MCP, use the tools
available in your current tool catalog rather than relying on an older
experiment payload.

The product rules are the same:

- An experiment compares two or more page arms.
- One arm is the control baseline.
- Traffic allocation must be explicit.
- A page is frozen into a prepared artifact before routing starts.
- Results are based on eligible experiment exposures and attributed orders.
- A winner should not be selected from early data alone.

The dashboard remains the source of truth for experiment lifecycle state and
results. Use [A/B Testing](/guides/ab-testing) for the user-facing workflow.