Independent MeasurementSeller: purchase results on BaseRead from the database 2026-09-28 04:50 UTC · reused for up to 5 min
vape-x402.vapex402.workers.dev
14 Base listings. By the latest purchase of each: 8 delivered · 1 failed on the seller's side · 0 on vet402's side · 5 not yet bought. Latest purchase: 2026-09-25 12:02 UTC.
1.Your listings
| Listing | Latest purchase | Result | Whose side |
|---|---|---|---|
| vape-x402.vapex402.workers.dev/data/bridgesGET | 2026-09-25 12: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 0x1915d55d…c169In export.csv?days=4: the row with attempted_at 2026-09-25T12:02:46Z and resource_key vape-x402.vapex402.workers.dev/data/bridges.Earlier: 2026-09-19 06:01 UTC delivered | |||
| vape-x402.vapex402.workers.dev/data/dex_volumesGET | 2026-09-24 12: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 0xabe27538…64b0In export.csv?days=5: the row with attempted_at 2026-09-24T12:01:49Z and resource_key vape-x402.vapex402.workers.dev/data/dex_volumes.Earlier: 2026-09-18 06:01 UTC delivered | |||
| vape-x402.vapex402.workers.dev/scan/liquidity_checkGET | 2026-09-22 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 0x68cfdd39…7eabIn export.csv?days=7: the row with attempted_at 2026-09-22T12:08:35Z and resource_key vape-x402.vapex402.workers.dev/scan/liquidity_check. | |||
| vape-x402.vapex402.workers.dev/data/yieldsGET | 2026-09-22 06:02 UTC | delivered | — |
What we saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.The latest purchase delivered. An earlier purchase listed below did not.Recorded: settled · HTTP 200 · tx 0x23566411…2542In export.csv?days=7: the row with attempted_at 2026-09-22T06:02:27Z and resource_key vape-x402.vapex402.workers.dev/data/yields.Earlier: 2026-09-15 18:01 UTC vet402's wallet was out of USDC (vet402's side) · 2026-09-09 07:00 UTC delivered | |||
| vape-x402.vapex402.workers.dev/data/protocol_feesGET | 2026-09-19 12:08 UTC | Server error on the paid request | seller's side |
What we saw: vet402 signed the payment and the paid request got a 5xx.What to fix: Check the route's logs: the handler or its upstream failed on the paid request. (a server change)Recorded: settle_failed · HTTP 502 · no txIn export.csv?days=10: the row with attempted_at 2026-09-19T12:08:29Z and resource_key vape-x402.vapex402.workers.dev/data/protocol_fees. | |||
| vape-x402.vapex402.workers.dev/data/stablecoinsGET | 2026-09-17 18: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 0x31a37d51…66a3In export.csv?days=12: the row with attempted_at 2026-09-17T18:01:03Z and resource_key vape-x402.vapex402.workers.dev/data/stablecoins.Earlier: 2026-09-11 01:00 UTC delivered · 2026-09-04 19:00 UTC delivered | |||
| vape-x402.vapex402.workers.dev/scan/rug_pull_alertGET | 2026-09-12 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 0xf39a0d70…8c97In export.csv?days=17: the row with attempted_at 2026-09-12T18:00:21Z and resource_key vape-x402.vapex402.workers.dev/scan/rug_pull_alert.Earlier: 2026-09-06 12:07 UTC delivered | |||
| vape-x402.vapex402.workers.dev/scan/exploit_checkGET | 2026-09-11 01: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 0x52015bb0…ea7aIn export.csv?days=19: the row with attempted_at 2026-09-11T01:02:31Z and resource_key vape-x402.vapex402.workers.dev/scan/exploit_check.Earlier: 2026-09-03 01:01 UTC delivered | |||
| vape-x402.vapex402.workers.dev/scan/token_safety_checkGET | 2026-09-06 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 0x0f153419…6913In export.csv?days=23: the row with attempted_at 2026-09-06T12:07:46Z and resource_key vape-x402.vapex402.workers.dev/scan/token_safety_check. | |||
| vape-x402.vapex402.workers.dev/data/chain_feesGET | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| vape-x402.vapex402.workers.dev/data/chain_overviewGET | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| vape-x402.vapex402.workers.dev/data/chain_protocolsGET | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| vape-x402.vapex402.workers.dev/data/protocolGET | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| vape-x402.vapex402.workers.dev/data/treasuryGET | 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.