Skip to main content
vet402
Independent MeasurementSeller: purchase results on BaseRead from the database 2026-09-29 06:12 UTC · reused for up to 5 min
vet402Sellers · What to fix firstMethodology

api.xfuel.app: x402 purchase results on Base, as of 2026-09-28

1 Base listing. By the latest attempt at each: 1 delivered · 0 failed on the seller's side · 0 on vet402's side · 0 not tried yet. Latest attempt: 2026-09-28 00:01 UTC.

1.Your listings

  1. api.xfuel.app/v1/chat/completionsPOST
    Latest attempt
    2026-09-28 00:01 UTC
    Result
    delivered
    Whose side
    no failure (delivered)
    What we saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.The 402 terms vet402 paid: vet402 signed: exact · 0.002 USDC · payTo 0x23f7…7334. Input sent: body declared, query empty. The listing's maxTimeoutSeconds is 120; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.002 USDC · payTo 0x23f7…7334 · nonce 0xe033…4cc8 · validBefore not recorded.Answer to the paid request: HTTP 200 · Content-Type application/json; charset=utf-8 · PAYMENT-RESPONSE: success true, names a transaction.The latest purchase delivered. An earlier attempt listed below did not.Recorded (L1 paid purchase): settled (vet402 confirmed the USDC transfer on-chain) · HTTP 200 · tx 0xa9947f31…524dIn export.csv?days=3: the row with attempted_at 2026-09-28T00:01:36Z and resource_key api.xfuel.app/v1/chat/completions.Dispute this purchaseEmail me when this result changes
    Earlier attempts
    1. 2026-09-21 18:01 UTC · delivered · no failure (delivered)settled (vet402 confirmed the USDC transfer on-chain) · HTTP 200 · tx 0x102d4115…f1d5
      What vet402 recordedPaid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.The 402 terms vet402 paid: vet402 signed: exact · 0.002 USDC · payTo 0x23f7…7334. Input sent: body declared, query not recorded. The listing's maxTimeoutSeconds is 120; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.002 USDC · payTo 0x23f7…7334 · nonce 0x611d…1120 · validBefore not recorded.Answer to the paid request: HTTP 200 · Content-Type application/json; charset=utf-8 · no PAYMENT-RESPONSE recorded.
      Dispute this purchase
    2. 2026-09-15 12:08 UTC · vet402's wallet held less USDC than the price · vet402's sidesettle_failed (vet402 signed a payment and got no settlement receipt back) · HTTP 400 · no tx · held as unsettled_4xx (the paid request got a 4xx with no settlement receipt and no transaction)
      What vet402 recordedWhen vet402 signed, its payer wallet held less USDC than the price, by the wallet's balance rebuilt from its own USDC transfers on-chain. The payment had nothing behind it, so the failure is on vet402's side.The 402 terms vet402 paid: vet402 signed: exact · 0.002 USDC · payTo 0x23f7…7334. Input sent: body not recorded, query not recorded. The listing's maxTimeoutSeconds is 120; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.002 USDC · payTo 0x23f7…7334 · nonce 0xd5fc…a93f · validBefore not recorded.Answer to the paid request: HTTP 400 · Content-Type application/json; charset=utf-8 · no PAYMENT-RESPONSE recorded.In export.csv this row's held_reason is unsettled_4xx (the paid request got a 4xx with no settlement receipt and no transaction). This page names the cause the row shows: vet402's wallet held less USDC than the price.
      Dispute this purchase
    3. 2026-09-09 01:01 UTC · vet402 did not send the declared request body · vet402's sidesettle_failed (vet402 signed a payment and got no settlement receipt back) · HTTP 400 · no tx · held as unsettled_4xx (the paid request got a 4xx with no settlement receipt and no transaction)
      What vet402 recordedBefore 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, 415 or 422, and the payment did not settle (a payment that settled is under "Charged, then refused an input vet402 had not sent").The 402 terms vet402 paid: vet402 signed: exact · 0.002 USDC · payTo 0x23f7…7334. Input sent: body not recorded, query not recorded. The listing's maxTimeoutSeconds is 120; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.002 USDC · payTo 0x23f7…7334 · nonce 0x3f05…c0fc · validBefore not recorded.Answer to the paid request: HTTP 400 · Content-Type application/json; charset=utf-8 · no PAYMENT-RESPONSE recorded.In export.csv this row's held_reason is unsettled_4xx (the paid request got a 4xx with no settlement receipt and no transaction). This page names the cause the row shows: vet402 did not send the declared request body.
      Dispute this purchase
    4. 2026-09-02 19:00 UTC · Not bought: the 402's amount was not the listing's price · not bought: vet402 did not payprice_mismatch (the 402's amount differed from the listing's price, so nothing was paid) · HTTP — · no tx
      What vet402 recordedvet402 pays the price the listing declares. The amount in the 402 was a different number, so vet402 did not sign.The 402 vet402 saw: The 402 offered: exact · eip155:8453 · amount 2000 · asset 0x8335…2913 · payTo 0x23f7…7334 · maxTimeoutSeconds 120; exact · solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp · amount 2000 · asset EPjFWd…Dt1v · payTo 58Qo8Q…JCx6 · maxTimeoutSeconds 120. At the time, the listing declared price 0.01 · payTo 0x23f7…7334.
      Dispute this purchase

2.How to read this

Each listing shows its latest attempt on Base and up to four earlier ones. A row where vet402 signed a payment and sent the paid request is an L1 result (“Recorded (L1 paid purchase)”); a row where vet402 did not sign is marked “not bought” and is not an L1 result. The listing's record page also shows the L0 state (“Published state”), which checks that an unpaid request gets a valid 402, so a listing can pass L0 and still fail here. Whose side puts a failure on the seller's side when the row shows vet402 was not at fault: it signed on the listing's terms, its wallet held the price, it sent the declared input, and the seller answered explicitly or had its declared time. Even then, one such failure is “not sorted: one failure so far”: a failure goes on the seller's side only when the same listing has one on two different days (UTC), and those rows are marked “under re-check” while we re-check them. A row that cannot show all of that is “not sorted”, and so is a held row (held_reason in the export), a failure where no payment was taken (“no charge”), and a payment that settled before the seller refused an input vet402 had not sent. “Signed payment” and “Answer to the paid request” show what the row recorded, and nothing else: the answer's body and header values are not published. The maxTimeoutSeconds on a row is the listing's value today; a declared price or address on a not-bought row is the value recorded at the time of the attempt. 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?

Use “Dispute this purchase” on the row: it opens Dispute this record on the listing's record page with the purchase time filled in. Say what you saw instead. The row is not deleted on dispute; a correction is published with the same weight.