cloud.trycorpus.ai: x402 purchase results on Base

29 Base listings. By the latest attempt at each: 0 delivered · 0 failed on the seller's side · 0 on vet402's side · 29 not tried yet.

1.Your listings

→ 0 more columns

2.How to read this

Each listing shows its latest attempt on Base and up to four earlier ones. A row where vet402 signed a payment and sent the paid request is an L1 result (“Recorded (L1 paid purchase)”); a row where vet402 did not sign is marked “not bought” and is not an L1 result. The listing's record page also shows the L0 state (“Published state”), which checks that an unpaid request gets a valid 402, so a listing can pass L0 and still fail here. Whose side puts a failure on the seller's side when the row shows vet402 was not at fault: it signed on the listing's terms, its wallet held the price, it sent the declared input, and the seller answered explicitly or had its declared time. A row that cannot show all of that is “not sorted”, and so is a held row (held_reason in the export) and a failure where no payment was taken (“no charge”). “The 402 terms vet402 paid” shows what the row recorded; the maxTimeoutSeconds on it is the listing's value today. The transaction link opens the settlement on Basescan. Listings removed from the Bazaar, and listings whose catalog network is not Base, are not on this page. The fix-first page groups the same results across sellers (methodology).

3.Think a row is wrong?

Open the listing's record (the link in the first column) and use “Dispute this record” there. Say which purchase and what you saw instead. The row is not deleted on dispute; a correction is published with the same weight.