context_id; each group is folded
through the assembler independently. Every assembled receipt is written to
.trace/receipts/<context_id>.json.
Usage
Arguments and options
Run-level events that carry no
context_id (chain confirmations, capture
attestations) belong to no single operation, so they’re reported separately as
unassigned rather than attributed or dropped.
JSON output for agents
--json prints the full Receipt objects — the
machine-readable basis an agent reads (completeness, missing) to decide
whether to continue a chain of spending.
Producing a run file
build needs a .trace/events/*.ndjson run file. Today you can point it at any
NDJSON file whose lines match the Event
Contract — the CLI ships a working example fixture.
Automatic capture from a live x402 app —
@usehaia/trace-x402
writing normalized events into .trace/events so trace(...) feeds build
end-to-end — is on the roadmap.