www.api-xpay.com
12 Base listings. By the latest purchase of each: 4 delivered · 1 failed on the seller's side · 1 on vet402's side · 6 not yet bought. Latest purchase: 2026-09-27 06:01 UTC.
Your most recent purchase failed on vet402's side. Nothing for you to fix there.
1.Your listings
| Listing | Latest purchase | Result | Whose side |
|---|---|---|---|
| www.api-xpay.com/x402/sentimentPOST | 2026-09-27 06: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=2: the row with attempted_at 2026-09-27T06:01:17Z and resource_key www.api-xpay.com/x402/sentiment. | |||
| www.api-xpay.com/x402/timeGET | 2026-09-27 00:00 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 0x8d19a354…c3ecIn export.csv?days=3: the row with attempted_at 2026-09-27T00:00:28Z and resource_key www.api-xpay.com/x402/time.Earlier: 2026-09-20 18:01 UTC The 402 asked for a different price than the listing (seller's side) · 2026-09-13 12:07 UTC The paid request was refused as invalid (seller's side) | |||
| www.api-xpay.com/x402/pingGET | 2026-09-26 00:00 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 0xdbe77dc5…c1ebIn export.csv?days=4: the row with attempted_at 2026-09-26T00:00:56Z and resource_key www.api-xpay.com/x402/ping.Earlier: 2026-09-19 18:00 UTC delivered · 2026-09-13 00:00 UTC The paid request was refused as invalid (seller's side) | |||
| www.api-xpay.com/x402/paymentGET | 2026-09-24 12: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 0x5606deff…bfbfIn export.csv?days=5: the row with attempted_at 2026-09-24T12:01:39Z and resource_key www.api-xpay.com/x402/payment.Earlier: 2026-09-18 06:00 UTC delivered | |||
| www.api-xpay.com/x402/ipGET | 2026-09-23 12: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 0x03a81123…ef22In export.csv?days=6: the row with attempted_at 2026-09-23T12:00:32Z and resource_key www.api-xpay.com/x402/ip. | |||
| www.api-xpay.com/x402/uuidGET | 2026-09-22 06:01 UTC | Server error on the paid request | seller's side |
What we saw: vet402 signed the payment and the paid request got a 5xx.What to fix: Check the route's logs: the handler or its upstream failed on the paid request. (a server change)Recorded: settle_failed · HTTP 502 · no txIn export.csv?days=7: the row with attempted_at 2026-09-22T06:01:47Z and resource_key www.api-xpay.com/x402/uuid.Earlier: 2026-09-14 12:07 UTC The paid request was refused as invalid (seller's side) | |||
| www.api-xpay.com/x402/keywordsPOST | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| www.api-xpay.com/x402/networkGET | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| www.api-xpay.com/x402/quoteGET | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| www.api-xpay.com/x402/randomGET | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| www.api-xpay.com/x402/rewritePOST | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| www.api-xpay.com/x402/statusGET | 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.