agent-proxy.alchemy.com
2 Base listings. By the latest purchase of each: 1 delivered · 1 failed on the seller's side · 0 on vet402's side · 0 not yet bought. Latest purchase: 2026-09-22 12:09 UTC.
1.Your listings
| Listing | Latest purchase | Result | Whose side |
|---|---|---|---|
| agent-proxy.alchemy.com/v1/x402/86b0ec6d1d0b3dc0/swap-allowance-holder-priceGET | 2026-09-22 12:09 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)Before 2026-09-27 23:27 UTC, vet402 did not add query parameters to paid requests on Base; this listing declares optional ones.Recorded: settled · HTTP 400 · tx 0xc532110e…dcb1 · held as settled_4xxIn export.csv?days=7: the row with attempted_at 2026-09-22T12:09:00Z and resource_key agent-proxy.alchemy.com/v1/x402/86b0ec6d1d0b3dc0/swap-allowance-holder-price. | |||
| agent-proxy.alchemy.com/v1/x402/4013ed2b4f50e768/abc-test-123POST | 2026-09-17 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 0x5845e9f5…b133In export.csv?days=12: the row with attempted_at 2026-09-17T18:01:19Z and resource_key agent-proxy.alchemy.com/v1/x402/4013ed2b4f50e768/abc-test-123.Earlier: 2026-09-11 12:09 UTC delivered · 2026-08-29 12:08 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.