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

---
title: The Compute sandbox
description: >-
  Try one resettable Compute example with synthetic inputs, a mock quote and
  sample results. Nothing runs, nothing is charged, and every artifact is
  labeled synthetic.
route: /docs/compute/sandbox
page_id: docs-compute-sandbox
page_type: hubIndex
content_layer: guided documentation
surface_profile: guided_docs
audience: People evaluating Compute before opening an account
voice: D
reader_question: What can I try in the Compute sandbox before anything real happens?
primary_action: Walk through a sandbox job
source_locale: en-US
source_status: APPROVED
source_version: docs-compute-sandbox-en-us-2026-09-05-v1
last_updated: '2026-09-05'
robots: index
claim_registry_pinned: true
claim_registry_resync: "npm run governed:tsx -- scripts/build-compute-public-claim-registry.ts --write"
---

## One example, no live effects

The sandbox is a single resettable example of the whole Compute lifecycle. You read a quote, approve it, watch a job change state, and open a result bundle. Nothing real runs. Nothing is charged. No account and no credentials are created, and nothing is written to any system of yours.

## Every artifact says it is synthetic

Provenance is explicit on each piece. Inputs come from a synthetic location rather than one of your sources. The quote is a mock quote and carries no signing authority. The result bundle and its receipt are labeled samples, so a sandbox artifact can never be mistaken for evidence about live work.

## This is not the contributor sample

People who help power the Lithi Agent Network have a separate sample experience of their own. It is a different thing, and it belongs to them. None of it touches your account, your inputs or your results.

## Reset it whenever you like

A sandbox is disposable by design. Reset it for a clean run, or open the same guided scenario again. There is nothing to clean up afterward and nothing to cancel.

## Where to go next

- [Walk through a sandbox job](/docs/compute/sandbox/quickstart) — open the guided scenario, read a mock quote, run a small synthetic set, and inspect every row.
- [Read the fixture catalog](/docs/compute/sandbox/scenarios) — the eight synthetic outcomes the sandbox can show you, and what each teaches you to spot in live work.
- [Reset and isolation rules](/docs/compute/sandbox/reset-and-isolation) — how reset and expiry work, what never persists, and why production identifiers are refused.
- [Move to live work](/docs/compute/sandbox/live-transition) — the fresh account, fresh quote and explicit approval that real work needs.