Independent MeasurementSeller: purchase results on BaseRead from the database 2026-09-28 05:02 UTC · reused for up to 5 min
api.eucompliance.tools
13 Base listings. By the latest purchase of each: 1 delivered · 1 failed on the seller's side · 7 on vet402's side · 4 not yet bought. Latest purchase: 2026-09-22 12:08 UTC.
1.Your listings
| Listing | Latest purchase | Result | Whose side |
|---|---|---|---|
| api.eucompliance.tools/x402/priceGET | 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 0x8d989e05…1403In export.csv?days=7: the row with attempted_at 2026-09-22T12:08:00Z and resource_key api.eucompliance.tools/x402/price. | |||
| api.eucompliance.tools/x402/coinGET | 2026-09-14 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=15: the row with attempted_at 2026-09-14T18:01:18Z and resource_key api.eucompliance.tools/x402/coin.Earlier: 2026-09-06 12:07 UTC delivered | |||
| api.eucompliance.tools/x402/funding-qrGET | 2026-09-13 06: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=16: the row with attempted_at 2026-09-13T06:00:15Z and resource_key api.eucompliance.tools/x402/funding-qr. | |||
| api.eucompliance.tools/x402/ai-disclosurePOST | 2026-09-08 01:02 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=22: the row with attempted_at 2026-09-08T01:02:01Z and resource_key api.eucompliance.tools/x402/ai-disclosure. | |||
| api.eucompliance.tools/x402/chatPOST | 2026-09-05 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=25: the row with attempted_at 2026-09-05T01:00:52Z and resource_key api.eucompliance.tools/x402/chat. | |||
| api.eucompliance.tools/x402/readGET | 2026-09-04 19: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=25: the row with attempted_at 2026-09-04T19:01:57Z and resource_key api.eucompliance.tools/x402/read. | |||
| api.eucompliance.tools/x402/companyGET | 2026-09-04 09:25 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=25: the row with attempted_at 2026-09-04T09:25:29Z and resource_key api.eucompliance.tools/x402/company. | |||
| api.eucompliance.tools/x402/commoditiesGET | 2026-09-04 01:00 UTC | No answer to the paid request | seller's side |
What we saw: vet402 signed the payment and the paid request got no HTTP answer in time (timeout, 408 or a closed connection).What to fix: Make the paid route answer within a few seconds; look for slow upstream calls or cold starts. (a server change)Recorded: settled · HTTP — · tx 0xdcfd6aad…bb2eIn export.csv?days=26: the row with attempted_at 2026-09-04T01:00:45Z and resource_key api.eucompliance.tools/x402/commodities. | |||
| api.eucompliance.tools/x402/historyGET | 2026-09-04 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=26: the row with attempted_at 2026-09-04T01:00:15Z and resource_key api.eucompliance.tools/x402/history. | |||
| api.eucompliance.tools/x402/chat-plusPOST | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| api.eucompliance.tools/x402/marketGET | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| api.eucompliance.tools/x402/perpsGET | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| api.eucompliance.tools/x402/socialGET | 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.