Independent MeasurementSeller: purchase results on BaseRead from the database 2026-09-28 03:14 UTC · reused for up to 5 min
api.stocktrends.com
19 Base listings. By the latest purchase of each: 8 delivered · 0 failed on the seller's side · 9 on vet402's side · 2 not yet bought. Latest purchase: 2026-09-26 12:01 UTC.
1.Your listings
| Listing | Latest purchase | Result | Whose side |
|---|---|---|---|
| api.stocktrends.com/v1/breadth/sector/latestGET | 2026-09-26 12:01 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 0x7a4104e7…af4eIn export.csv?days=3: the row with attempted_at 2026-09-26T12:01:41Z and resource_key api.stocktrends.com/v1/breadth/sector/latest.Earlier: 2026-09-14 06:00 UTC vet402's wallet was out of USDC (vet402's side) · 2026-09-04 19:02 UTC delivered | |||
| api.stocktrends.com/v1/prices/latestGET | 2026-09-26 12:01 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=3: the row with attempted_at 2026-09-26T12:01:39Z and resource_key api.stocktrends.com/v1/prices/latest.Earlier: 2026-09-19 12:07 UTC vet402 did not send the declared query (vet402's side) | |||
| api.stocktrends.com/v1/stim/latestGET | 2026-09-20 18:00 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=9: the row with attempted_at 2026-09-20T18:00:40Z and resource_key api.stocktrends.com/v1/stim/latest.Earlier: 2026-09-14 06:00 UTC vet402 did not send the declared query (vet402's side) · 2026-09-08 01:00 UTC vet402 did not send the declared query (vet402's side) | |||
| api.stocktrends.com/v1/indicators/latestGET | 2026-09-14 06:00 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=15: the row with attempted_at 2026-09-14T06:00:41Z and resource_key api.stocktrends.com/v1/indicators/latest.Earlier: 2026-09-08 01:00 UTC vet402 did not send the declared query (vet402's side) | |||
| api.stocktrends.com/v1/prices/historyGET | 2026-09-10 01:00 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=20: the row with attempted_at 2026-09-10T01:00:08Z and resource_key api.stocktrends.com/v1/prices/history. | |||
| api.stocktrends.com/v1/portfolio/evaluatePOST | 2026-09-08 12:09 UTC | vet402 did not send the declared request body | vet402's side |
What we saw: Before 2026-09-16 23:25 UTC, vet402 sent an empty JSON body on paid POST requests, even when the listing declares a body. The seller refused it with 400 or 422, before or after the payment settled.What to fix: Nothing for the seller to fix.This failure was on vet402's side, not the seller's.Recorded: settle_failed · HTTP 422 · no tx · held as unsettled_4xxIn export.csv?days=21: the row with attempted_at 2026-09-08T12:09:40Z and resource_key api.stocktrends.com/v1/portfolio/evaluate. | |||
| api.stocktrends.com/v1/portfolio/comparePOST | 2026-09-08 07:02 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:02:29Z and resource_key api.stocktrends.com/v1/portfolio/compare. | |||
| api.stocktrends.com/v1/portfolio/constructPOST | 2026-09-08 07: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 0x12d67d99…c771In export.csv?days=21: the row with attempted_at 2026-09-08T07:02:29Z and resource_key api.stocktrends.com/v1/portfolio/construct. | |||
| api.stocktrends.com/v1/decision/evaluate-symbolPOST | 2026-09-08 01:01 UTC | vet402 did not send the declared request body | vet402's side |
What we saw: Before 2026-09-16 23:25 UTC, vet402 sent an empty JSON body on paid POST requests, even when the listing declares a body. The seller refused it with 400 or 422, before or after the payment settled.What to fix: Nothing for the seller to fix.This failure was on vet402's side, not the seller's.Recorded: settle_failed · HTTP 422 · no tx · held as unsettled_4xxIn export.csv?days=22: the row with attempted_at 2026-09-08T01:01:54Z and resource_key api.stocktrends.com/v1/decision/evaluate-symbol. | |||
| api.stocktrends.com/v1/market/regime/forecastGET | 2026-09-08 01: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 0xbf2cbaf0…ab64In export.csv?days=22: the row with attempted_at 2026-09-08T01:01:54Z and resource_key api.stocktrends.com/v1/market/regime/forecast. | |||
| api.stocktrends.com/v1/indicators/historyGET | 2026-09-08 01:00 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=22: the row with attempted_at 2026-09-08T01:00:32Z and resource_key api.stocktrends.com/v1/indicators/history. | |||
| api.stocktrends.com/v1/selections/published/latestGET | 2026-09-08 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 0xd5e53734…b4abIn export.csv?days=22: the row with attempted_at 2026-09-08T01:00:30Z and resource_key api.stocktrends.com/v1/selections/published/latest. | |||
| api.stocktrends.com/v1/stim/historyGET | 2026-09-08 01:00 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=22: the row with attempted_at 2026-09-08T01:00:30Z and resource_key api.stocktrends.com/v1/stim/history. | |||
| api.stocktrends.com/v1/selections/latestGET | 2026-09-06 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 0x21d78323…2da5In export.csv?days=23: the row with attempted_at 2026-09-06T07:00:39Z and resource_key api.stocktrends.com/v1/selections/latest. | |||
| api.stocktrends.com/v1/leadership/summary/latestGET | 2026-09-05 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 0x40bec1c8…d4c9In export.csv?days=25: the row with attempted_at 2026-09-05T01:00:57Z and resource_key api.stocktrends.com/v1/leadership/summary/latest. | |||
| api.stocktrends.com/v1/breadth/sector/historyGET | 2026-09-04 19: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 0x998d2b8f…9353In export.csv?days=25: the row with attempted_at 2026-09-04T19:02:29Z and resource_key api.stocktrends.com/v1/breadth/sector/history. | |||
| api.stocktrends.com/v1/market/regime/latestGET | 2026-09-04 19: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 0x44c3a3cc…a5ffIn export.csv?days=25: the row with attempted_at 2026-09-04T19:02:28Z and resource_key api.stocktrends.com/v1/market/regime/latest. | |||
| api.stocktrends.com/v1/agent/screener/topGET | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| api.stocktrends.com/v1/leadership/rotation/historyGET | 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.