Independent MeasurementSeller: purchase results on BaseRead from the database 2026-09-28 03:27 UTC · reused for up to 5 min
stockwaves.net
16 Base listings. By the latest purchase of each: 8 delivered · 0 failed on the seller's side · 3 on vet402's side · 5 not yet bought. Latest purchase: 2026-09-17 12:53 UTC.
1.Your listings
| Listing | Latest purchase | Result | Whose side |
|---|---|---|---|
| stockwaves.net/api/cn/pulseGET | 2026-09-17 12:53 UTC | delivered | — |
What we saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.Recorded: settled · HTTP 200 · tx 0x0e524749…9dbeIn export.csv?days=12: the row with attempted_at 2026-09-17T12:53:09Z and resource_key stockwaves.net/api/cn/pulse.Earlier: 2026-09-11 12:09 UTC delivered · 2026-09-03 01:01 UTC delivered | |||
| stockwaves.net/api/xstock/healthGET | 2026-09-13 18:01 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=16: the row with attempted_at 2026-09-13T18:01:47Z and resource_key stockwaves.net/api/xstock/health.Earlier: 2026-09-03 01:00 UTC The paid request was refused as invalid (seller's side) | |||
| stockwaves.net/api/crypto/microstructureGET | 2026-09-08 12:09 UTC | delivered | — |
What we saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.Recorded: settled · HTTP 200 · tx 0x78c4b7b8…6fffIn export.csv?days=21: the row with attempted_at 2026-09-08T12:09:26Z and resource_key stockwaves.net/api/crypto/microstructure. | |||
| stockwaves.net/api/anomalies/insightGET | 2026-09-08 12:09 UTC | delivered | — |
What we saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.Recorded: settled · HTTP 200 · tx 0x9786d7bf…3651In export.csv?days=21: the row with attempted_at 2026-09-08T12:09:15Z and resource_key stockwaves.net/api/anomalies/insight. | |||
| stockwaves.net/api/cn/themesGET | 2026-09-08 12:09 UTC | delivered | — |
What we saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.Recorded: settled · HTTP 200 · tx 0x6af6b852…ac8eIn export.csv?days=21: the row with attempted_at 2026-09-08T12:09:10Z and resource_key stockwaves.net/api/cn/themes. | |||
| stockwaves.net/api/macro/allocationGET | 2026-09-08 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 0x33bc1e33…fdeeIn export.csv?days=21: the row with attempted_at 2026-09-08T12:08:27Z and resource_key stockwaves.net/api/macro/allocation. | |||
| stockwaves.net/api/brief/tradeGET | 2026-09-08 07: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=21: the row with attempted_at 2026-09-08T07:01:08Z and resource_key stockwaves.net/api/brief/trade. | |||
| stockwaves.net/api/cn/briefGET | 2026-09-07 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 0xc1236c70…1edeIn export.csv?days=22: the row with attempted_at 2026-09-07T12:08:41Z and resource_key stockwaves.net/api/cn/brief. | |||
| stockwaves.net/api/macro/indicatorGET | 2026-09-06 12:08 UTC | vet402 did not send the declared query | vet402's side |
What we saw: Before 2026-09-27 23:27 UTC, vet402 did not add the query parameters the seller's 402 declares to paid requests on Base, and this listing marks some of them as required. The seller refused the request with 400 or 422.What to fix: Nothing for the seller to fix.This failure was on vet402's side, not the seller's.Recorded: settle_failed · HTTP 400 · no tx · held as unsettled_4xxIn export.csv?days=23: the row with attempted_at 2026-09-06T12:08:12Z and resource_key stockwaves.net/api/macro/indicator. | |||
| stockwaves.net/api/cn/newsGET | 2026-09-06 01: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 0x126f3d23…ba16In export.csv?days=24: the row with attempted_at 2026-09-06T01:00:11Z and resource_key stockwaves.net/api/cn/news. | |||
| stockwaves.net/api/recommendGET | 2026-09-05 07: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 0x93616f7e…4040In export.csv?days=24: the row with attempted_at 2026-09-05T07:00:24Z and resource_key stockwaves.net/api/recommend. | |||
| stockwaves.net/api/btc/signalGET | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| stockwaves.net/api/cn/trendingGET | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| stockwaves.net/api/dealerGET | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| stockwaves.net/api/portfolio/optimizePOST | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| stockwaves.net/api/rotationGET | 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.