Getting Started

Evidence packages

One record packaged for a dispute forum or escrow arbiter: every file hashed, redactions declared, limits stated, checkable without trusting Labs.

An evidence package is one Labs record turned into a folder a dispute forum, an escrow arbiter or the other party can examine without trusting Labs. Schema lmx.evidence/1. It is built only from the public evidence record, so anyone holding the record can rebuild the same files.

package layout

summary.json              machine-readable summary; every claim points at a file
SUMMARY.md                one page for a person
record.json               the lmx.record/1 bundle, unchanged (drop it into /verify)
promise/listing.json      advertised listing and payment requirements
promise/terms.txt         seller terms, when captured
call/request.json         exact request, credential headers removed at capture
call/response-headers.json
call/response-body.raw    exact response bytes, when Labs holds them
call/response-body.parsed.json
call/payment.json         network, asset, amount, tx, explorer link
test/case-file.json       the case, written before the call
redactions.json           what was removed, when, and why
manifest.json             SHA-256 and size of every file above
signature.json            Ed25519 signature over manifest.json, when signed

What a forum gets

Needed	In the package
Stable ID and version	`record_id` (the grade hash) and `schema`
Capture times	Request sent, response received, case committed
The promise and terms	Listing, payment requirements, terms with a captured / not captured status
Request, response, payment	Separate files, each hashed; the tx links to Basescan
Why each verdict	Each level (delivered, matches listing, correct) names its method, expected answer, its source, and the files it rests on
Redactions	Declared in redactions.json, with when and why

Redactions and originals

Credential headers (authorization, cookies, API keys, tokens, secrets and the x402 payment signature) are dropped at capture, before anything is hashed or stored. Labs doesn't keep them, so there is no unredacted original of those values; the payment they authorized is proven by the on-chain transaction. Nothing else is removed. Labs keeps the original observation, grade, case file and raw response bytes, named by hash and never edited.

Two modes

test_finding: Labs' own paid test call. It shows how the endpoint answered this input at this time. It is not a copy of a buyer's call. dispute_replay (reserved): Labs replays a disputed request on demand and links the buyer's transaction. Not offered yet.

Check a package

Hash each file in manifest.json, drop record.json into /verify, and if the package is signed, check the signature against the key Labs publishes. A changed file, a summary that disagrees with the record, or a forged manifest each fail.

A package is evidence, not a ruling. Labs doesn't arbitrate or hold funds; the forum decides what it means. To request one, write to support@lmxlabs.app.

Dispute evidence

How a check works

Every check is a real paid call from a Labs wallet, graded against an expected answer written down before the call runs.

Continue