coingecko.use.x402atlas.com
6 Base listings. By the latest purchase of each: 5 delivered · 0 failed on the seller's side · 1 on vet402's side · 0 not yet bought. Latest purchase: 2026-09-16 18:01 UTC.
1.Your listings
| Listing | Latest purchase | Result | Whose side |
|---|---|---|---|
| coingecko.use.x402atlas.com/trendingGET | 2026-09-16 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 0x3c68edd0…1505In export.csv?days=13: the row with attempted_at 2026-09-16T18:01:16Z and resource_key coingecko.use.x402atlas.com/trending.Earlier: 2026-09-10 01:01 UTC delivered · 2026-08-30 12:07 UTC delivered · 2026-08-23 12:42 UTC delivered · 2026-08-14 10:09 UTC delivered | |||
| coingecko.use.x402atlas.com/priceGET | 2026-09-15 12:08 UTC | vet402's wallet was out of USDC | vet402's side |
What we saw: Between 2026-09-13 00:00 and 2026-09-15 23:49 UTC, vet402's Base payer wallet had run out of USDC. The seller refused a payment that had nothing behind it (402 or 5xx).What to fix: Nothing for the seller to fix.This failure was on vet402's side, not the seller's.Recorded: settle_failed · HTTP 402 · no tx · held as payer_unfundedIn export.csv?days=14: the row with attempted_at 2026-09-15T12:08:36Z and resource_key coingecko.use.x402atlas.com/price.Earlier: 2026-09-09 01:01 UTC delivered · 2026-08-27 12:31 UTC delivered · 2026-08-20 12:55 UTC delivered · 2026-08-14 09:56 UTC delivered | |||
| coingecko.use.x402atlas.com/ohlcGET | 2026-09-10 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 0x1c6ac1a6…e494In export.csv?days=19: the row with attempted_at 2026-09-10T12:08:17Z and resource_key coingecko.use.x402atlas.com/ohlc.Earlier: 2026-08-28 12:18 UTC delivered · 2026-08-20 12:56 UTC delivered · 2026-08-14 10:03 UTC delivered | |||
| coingecko.use.x402atlas.com/marketsGET | 2026-09-10 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 0x41a213ea…d399In export.csv?days=20: the row with attempted_at 2026-09-10T01:02:12Z and resource_key coingecko.use.x402atlas.com/markets.Earlier: 2026-08-27 12:32 UTC delivered · 2026-08-20 12:55 UTC delivered · 2026-08-14 09:55 UTC delivered | |||
| coingecko.use.x402atlas.com/historyGET | 2026-08-23 12:44 UTC | delivered | — |
What we saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.Recorded: settled · HTTP 200 · tx 0x7464a105…a0f4In export.csv?days=37: the row with attempted_at 2026-08-23T12:44:52Z and resource_key coingecko.use.x402atlas.com/history.Earlier: 2026-08-14 10:07 UTC delivered | |||
| coingecko.use.x402atlas.com/coinGET | 2026-08-23 12:44 UTC | delivered | — |
What we saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.Recorded: settled · HTTP 200 · tx 0x90569ee6…1e7dIn export.csv?days=37: the row with attempted_at 2026-08-23T12:44:17Z and resource_key coingecko.use.x402atlas.com/coin.Earlier: 2026-08-14 10:07 UTC delivered | |||
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.