---
title: Going live / validation
description: The three-stage validation pipeline — pre-validation, Google sandbox, and production — and how it relates to going live.
---

**Validation** runs the checks Sarvex requires before agent checkout turns on, tracking conformance through three stages: **pre-validation**, **Google sandbox**, and **production**. Run pre-validation from Path or the Validation screen; each check reports pass, fail, or warn, with what to fix.

- **Pre-validation** is the only stage you trigger yourself. It runs the reconciled UCP spec's checks — request signing, negotiation, catalog lookups, checkout — directly against your endpoints, the same checks that run automatically at Path's Verified stage. Every run is pinned to a target spec version, so "conformant" doesn't shift underneath you later. The Validation screen keeps a full run history and lists open failures with what to fix.
- **Google sandbox** and **production** track your store's status in Google's own review process for its agent surfaces, shown here for visibility — Google gates these, not Sarvex.

Going live — reaching **Active** on Path — doesn't wait on the Google sandbox or production stages; it depends only on your endpoints passing conformance. Once every check passes, agent checkout is live — there's no separate activation switch.

Common things that hold pre-validation up:

- Products missing fields agents need — check each product's readiness state under **Store**
- The connector not currently paired or reachable
- Recent sync issues flagged under **Health**