api.robotsshop.io/v0/spookfiles/search

1.Catalog declaration

→ 0 more columns

2.Probe history

→ 0 more columns

3.L1 — real purchases

1 of 1 paid attempts settled with a receipt, and 1 of those also returned a 2xx response (delivered). Each settled row carries its on-chain transaction hash — the receipt is the evidence. A settled row reads as nonce-bound when the on-chain re-read also matched the one-time signature nonce we generated for that purchase, and amount + payee when it matched amount, payee, asset and chain with no nonce on record — the binding shipped on 2026-09-04, so earlier rows carry the weaker evidence and keep their label rather than being demoted (methodology). settled is the transfer we confirmed on-chain; delivered is the response arriving. A settled row whose paid request answered 5xx counts as settled and not as delivered — definitions.

→ 0 more columns

[![vet402 receipt](https://vet402.com/api/badge/endpoint/d27bf4d4-d378-4627-b03c-4636b95dda96.svg)](https://vet402.com/observatory/e/d27bf4d4-d378-4627-b03c-4636b95dda96)

4.Catalog listing events

No listing changes observed.

unverified is not a failure; a fail is published only after two consecutive failing probes. Definitions: methodology.

5.Dispute this record

Think a measurement above is wrong? Say which probe or purchase and what you observed instead. One person reads it and replies. The record is never deleted on dispute: if it was wrong, the correction is published with the same weight; if it was right, it stands. Operators who control the receiving address can also sign a dispute via POST /api/v1/observatory/disputes (API reference), which re-measures through the normal publication gate.