> ## Documentation Index > Fetch the complete documentation index at: https://developers.haia.finance/llms.txt > Use this file to discover all available pages before exploring further. # Quickstart > See your first Operation Receipt in under a minute. ## See a Receipt with zero setup No install needed โ€” replay a bundled fixture run through the real assembler: ```sh theme={null} npx @usehaia/trace-cli sample x402-payment ``` `sample` runs the same deterministic `(events, template) โ†’ receipt` core a live run uses; the only difference is that the events come from a bundled fixture instead of a recorder. The fixture holds three operations, so one command shows the whole model โ€” a **FULL** receipt, a **PARTIAL** one with an explained gap, and one carrying an observed fault: ```text theme={null} ๐Ÿงพ x402-payment ยท op-2 ยท PARTIAL โœ” intent confirmed โœ” payment confirmed โœ” settlement confirmed โœ– paid_action not confirmed required โœ– business_record not confirmed optional missing paid_action โ€” settlement confirmed, but the paid action's result was not observed operation not complete ``` That gap โ€” `settlement โœ“` but `paid_action โœ—` โ€” is the product: a bank statement, a block explorer, and a server log each say "payment went through"; only the Receipt says "โ€ฆbut you never got what you paid for." ## Install the CLI ```sh npm theme={null} npm install -g @usehaia/trace-cli ``` ```sh npx theme={null} npx @usehaia/trace-cli ``` Both expose the `haia-trace` command. Requires **Node โ‰ฅ 20**. ## Assemble receipts from a run Once you have a run of recorded events at `.trace/events/.ndjson`, build one Receipt per operation: ```sh theme={null} haia-trace build # build the latest run in .trace/events/ haia-trace build --json # machine-readable output, for an agent to read ``` Every command, flag, and the `.trace/` layout. ## Next steps The model behind the verdict: stages, evidence, missing, exceptions. Record the x402 lifecycle from your own app.