enclave402.com
11 Base listings. By the latest purchase of each: 5 delivered · 0 failed on the seller's side · 1 on vet402's side · 5 not yet bought. Latest purchase: 2026-09-25 18:00 UTC.
1.Your listings
| Listing | Latest purchase | Result | Whose side |
|---|---|---|---|
| enclave402.com/api/compute/searchPOST | 2026-09-25 18:00 UTC | delivered | — |
What we saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.Recorded: settled · HTTP 200 · tx 0xcfe10995…a010In export.csv?days=4: the row with attempted_at 2026-09-25T18:00:52Z and resource_key enclave402.com/api/compute/search. | |||
| enclave402.com/api/census/verdictGET | 2026-09-24 06:01 UTC | delivered | — |
What we saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.Recorded: settled · HTTP 200 · tx 0x1535ecf3…d6a8In export.csv?days=5: the row with attempted_at 2026-09-24T06:01:11Z and resource_key enclave402.com/api/census/verdict. | |||
| enclave402.com/api/census/exportGET | 2026-09-22 06:01 UTC | vet402's own limits | vet402's side |
What we saw: vet402 did not pay: the price was over its per-purchase ceiling, its budget for the day was used up, its operator halted spending, or the 402 named vet402's own receiving address.What to fix: Nothing for the seller to fix.This failure was on vet402's side, not the seller's.Recorded: over_cap · HTTP — · no txIn export.csv?days=7: the row with attempted_at 2026-09-22T06:01:15Z and resource_key enclave402.com/api/census/export. | |||
| enclave402.com/api/agent/attestPOST | 2026-09-19 12:07 UTC | delivered | — |
What we saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.Recorded: settled · HTTP 200 · tx 0x4b06e2d8…3bb2In export.csv?days=10: the row with attempted_at 2026-09-19T12:07:55Z and resource_key enclave402.com/api/agent/attest. | |||
| enclave402.com/api/storage/pinPOST | 2026-09-19 06:02 UTC | delivered | — |
What we saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.Recorded: settled · HTTP 200 · tx 0xd73c2c09…507cIn export.csv?days=10: the row with attempted_at 2026-09-19T06:02:04Z and resource_key enclave402.com/api/storage/pin. | |||
| enclave402.com/api/market/signalGET | 2026-09-18 12:08 UTC | delivered | — |
What we saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.Recorded: settled · HTTP 200 · tx 0x6ae197a0…3af7In export.csv?days=11: the row with attempted_at 2026-09-18T12:08:09Z and resource_key enclave402.com/api/market/signal. | |||
| enclave402.com/api/compute/encodePOST | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| enclave402.com/api/compute/hashPOST | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| enclave402.com/api/compute/inferPOST | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| enclave402.com/api/market/verdictGET | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| enclave402.com/api/seller/vetGET | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
2.How to read this
Each listing shows its latest purchase on Base and up to four earlier ones. Whose side says where the failure came from: the seller's answer or listing, or vet402 itself. A row held (held_reason in the export) is not counted against the seller in the delivered numbers, because vet402 cannot rule out that its request was the problem. 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.