Independent MeasurementSeller: purchase results on BaseRead from the database 2026-09-28 05:02 UTC · reused for up to 5 min
win.oneshotagent.com
17 Base listings. By the latest purchase of each: 4 delivered · 2 failed on the seller's side · 6 on vet402's side · 5 not yet bought. Latest purchase: 2026-09-26 12:02 UTC.
1.Your listings
| Listing | Latest purchase | Result | Whose side |
|---|---|---|---|
| win.oneshotagent.com/v1/tools/local/searchPOST | 2026-09-26 12:02 UTC | delivered | — |
What we saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 202.The latest purchase delivered. An earlier purchase listed below did not.Recorded: settled · HTTP 202 · tx 0x102dead8…7a56In export.csv?days=3: the row with attempted_at 2026-09-26T12:02:04Z and resource_key win.oneshotagent.com/v1/tools/local/search.Earlier: 2026-09-15 18:01 UTC vet402's wallet was out of USDC (vet402's side) · 2026-09-09 07:00 UTC vet402 did not send the declared request body (vet402's side) | |||
| win.oneshotagent.com/v1/tools/enrich/companyPOST | 2026-09-26 00:01 UTC | delivered | — |
What we saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 202.The latest purchase delivered. An earlier purchase listed below did not.Recorded: settled · HTTP 202 · tx 0x83f78839…ff77In export.csv?days=4: the row with attempted_at 2026-09-26T00:01:24Z and resource_key win.oneshotagent.com/v1/tools/enrich/company.Earlier: 2026-09-19 18:01 UTC delivered · 2026-09-13 12:08 UTC vet402's wallet was out of USDC (vet402's side) · 2026-09-07 07:00 UTC vet402 did not send the declared request body (vet402's side) | |||
| win.oneshotagent.com/v1/tools/research/newsfeedPOST | 2026-09-24 12:02 UTC | delivered | — |
What we saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 202.Recorded: settled · HTTP 202 · tx 0x926d5f13…ea6bIn export.csv?days=5: the row with attempted_at 2026-09-24T12:02:26Z and resource_key win.oneshotagent.com/v1/tools/research/newsfeed.Earlier: 2026-09-18 00:01 UTC delivered | |||
| win.oneshotagent.com/v1/tools/linkedin/replyPOST | 2026-09-24 00:01 UTC | Took the payment, then refused the input | seller's side |
What we saw: The payment settled on-chain, and then the paid request got 400, 404, 415 or 422: the route took the payment before it checked the input, so the buyer paid for a refused request. When the seller declared a body, or a required query, that vet402 was not yet sending, the row is on vet402's side instead.What to fix: Check the input before you settle, so an invalid request is refused without taking the payment; and declare the input in the listing with example values that work as written. (a server change)Recorded: settled · HTTP 400 · tx 0xdd77a3c1…ddc5 · held as settled_4xxIn export.csv?days=6: the row with attempted_at 2026-09-24T00:01:17Z and resource_key win.oneshotagent.com/v1/tools/linkedin/reply. | |||
| win.oneshotagent.com/v1/tools/enrich/emailPOST | 2026-09-23 00:02 UTC | Took the payment, then refused the input | seller's side |
What we saw: The payment settled on-chain, and then the paid request got 400, 404, 415 or 422: the route took the payment before it checked the input, so the buyer paid for a refused request. When the seller declared a body, or a required query, that vet402 was not yet sending, the row is on vet402's side instead.What to fix: Check the input before you settle, so an invalid request is refused without taking the payment; and declare the input in the listing with example values that work as written. (a server change)Recorded: settled · HTTP 400 · tx 0x75869475…3d04 · held as settled_4xxIn export.csv?days=7: the row with attempted_at 2026-09-23T00:02:02Z and resource_key win.oneshotagent.com/v1/tools/enrich/email.Earlier: 2026-09-16 18:01 UTC vet402 did not send the declared request body (vet402's side) · 2026-09-10 07:00 UTC vet402 did not send the declared request body (vet402's side) | |||
| win.oneshotagent.com/v1/tools/research/peoplePOST | 2026-09-17 15:27 UTC | delivered | — |
What we saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 202.Recorded: settled · HTTP 202 · tx 0x5539f317…91c5In export.csv?days=12: the row with attempted_at 2026-09-17T15:27:31Z and resource_key win.oneshotagent.com/v1/tools/research/people.Earlier: 2026-09-10 12:09 UTC delivered · 2026-09-04 07:00 UTC delivered | |||
| win.oneshotagent.com/v1/tools/research/personPOST | 2026-09-16 18: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 400 · no tx · held as unsettled_4xxIn export.csv?days=13: the row with attempted_at 2026-09-16T18:01:41Z and resource_key win.oneshotagent.com/v1/tools/research/person.Earlier: 2026-09-10 07:01 UTC vet402 did not send the declared request body (vet402's side) · 2026-09-03 01:00 UTC vet402 did not send the declared request body (vet402's side) | |||
| win.oneshotagent.com/v1/tools/web-readPOST | 2026-09-16 18: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 400 · no tx · held as unsettled_4xxIn export.csv?days=13: the row with attempted_at 2026-09-16T18:01:40Z and resource_key win.oneshotagent.com/v1/tools/web-read.Earlier: 2026-09-10 01:01 UTC vet402 did not send the declared request body (vet402's side) · 2026-09-03 12:09 UTC vet402 did not send the declared request body (vet402's side) | |||
| win.oneshotagent.com/v1/tools/searchPOST | 2026-09-15 18:00 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-15T18:00:48Z and resource_key win.oneshotagent.com/v1/tools/search.Earlier: 2026-09-09 12:09 UTC vet402 did not send the declared request body (vet402's side) · 2026-09-03 01:00 UTC vet402 did not send the declared request body (vet402's side) | |||
| win.oneshotagent.com/v1/tools/enrich/profilePOST | 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:11Z and resource_key win.oneshotagent.com/v1/tools/enrich/profile.Earlier: 2026-09-08 19:01 UTC vet402 did not send the declared request body (vet402's side) · 2026-09-02 07:00 UTC vet402 did not send the declared request body (vet402's side) | |||
| win.oneshotagent.com/v1/tools/verify/emailPOST | 2026-09-15 12:07 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:07:58Z and resource_key win.oneshotagent.com/v1/tools/verify/email.Earlier: 2026-09-09 01:01 UTC vet402 did not send the declared request body (vet402's side) · 2026-09-02 07:01 UTC vet402 did not send the declared request body (vet402's side) | |||
| win.oneshotagent.com/v1/tools/email/sendPOST | 2026-09-02 01:00 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 400 · no tx · held as unsettled_4xxIn export.csv?days=28: the row with attempted_at 2026-09-02T01:00:43Z and resource_key win.oneshotagent.com/v1/tools/email/send. | |||
| win.oneshotagent.com/v1/tools/linkedin/profile-viewPOST | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| win.oneshotagent.com/v1/tools/local/resolvePOST | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| win.oneshotagent.com/v1/tools/researchPOST | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| win.oneshotagent.com/v1/tools/research/companyPOST | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| win.oneshotagent.com/v1/tools/research/socialPOST | 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.