agents.driftflight.com: x402 purchase results on Base, as of 2026-09-21

1 Base listing. By the latest attempt at each: 0 delivered · 0 failed on the seller's side · 0 on vet402's side · 1 not sorted (vet402 cannot show the failure was not its own) · 0 not tried yet. Latest attempt: 2026-09-21 18:01 UTC.

1.Your listings

1. agents.driftflight.com/v1/images/generatePOST

   Latest attempt

   2026-09-21 18:01 UTC

   Result

   Payment settled, then the request was refused

   Whose side

   not sorted (held)

   What we saw: The payment settled on-chain, and then the paid request got another 4xx (for example 401, 403, 405 or 429). vet402 holds this row (held_reason settled_4xx), so it is not counted against the seller.Last result about the seller: none among the attempts shown. The latest attempt is not sorted; vet402 has not bought this listing again since.The 402 terms vet402 paid: vet402 signed: exact · 0.06 USDC · payTo 0x00ac…6d21. Input sent: body declared, query not recorded. The listing's maxTimeoutSeconds is 300; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.06 USDC · payTo 0x00ac…6d21 · nonce 0x22a4…aaaf · validBefore not recorded.Answer to the paid request: HTTP 409 · Content-Type application/json; charset=utf-8 · no PAYMENT-RESPONSE recorded.What to fix: Nothing is counted against the seller. If the paid request should have been served, let the x402 payment be enough for it.Recorded (L1 paid purchase): settled (vet402 confirmed the USDC transfer on-chain) · HTTP 409 · tx 0x3e7bd234…8de6 · held as settled_4xx (the payment settled, then the paid request got a 4xx)In export.csv?days=9: the row with attempted_at 2026-09-21T18:01:38Z and resource_key agents.driftflight.com/v1/images/generate.Dispute this purchaseEmail me when this result changes

   Earlier attempts

   1. 2026-09-15 12:08 UTC · vet402's wallet was out of USDC · vet402's sidesettle_failed (vet402 signed a payment and got no settlement receipt back) · HTTP 402 · no tx · held as payer_unfunded (a 402 or 5xx while vet402's Base wallet was out of USDC (2026-09-13 to 2026-09-15))
      What vet402 recorded

      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).The 402 terms vet402 paid: vet402 signed: exact · 0.06 USDC · payTo 0x00ac…6d21. Input sent: body not recorded, query not recorded. The listing's maxTimeoutSeconds is 300; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.06 USDC · payTo 0x00ac…6d21 · nonce 0x4f1d…f236 · validBefore not recorded.Answer to the paid request: HTTP 402 · Content-Type application/json; charset=utf-8 · no PAYMENT-RESPONSE recorded.
      Dispute this purchase
   2. 2026-09-09 01:01 UTC · Charged, then refused an input vet402 had not sent · not sorted: charged, then rejected an input vet402 had not sentsettled (vet402 confirmed the USDC transfer on-chain) · HTTP 400 · tx 0x2c04bfe8…857e · held as settled_4xx (the payment settled, then the paid request got a 4xx)
      What vet402 recorded

      The payment settled on-chain, and then the paid request got 400, 415 or 422. At the time vet402 did not send the input this listing declares: the request body before 2026-09-16 23:25 UTC, or on Base the query before 2026-09-27 23:27 UTC. Both facts stand: the seller took the payment, and the request lacked the declared input. The row is not counted against either side.The 402 terms vet402 paid: vet402 signed: exact · 0.06 USDC · payTo 0x00ac…6d21. Input sent: body not recorded, query not recorded. The listing's maxTimeoutSeconds is 300; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.06 USDC · payTo 0x00ac…6d21 · nonce 0x098e…a39d · validBefore not recorded.Answer to the paid request: HTTP 400 · Content-Type application/json · PAYMENT-RESPONSE: success true, names a transaction.In export.csv this row's held_reason is settled_4xx (the payment settled, then the paid request got a 4xx). This page names the cause the row shows: charged, then refused an input vet402 had not sent.
      Dispute this purchase
   3. 2026-08-28 12:18 UTC · Charged, then refused an input vet402 had not sent · not sorted: charged, then rejected an input vet402 had not sentsettled (vet402 confirmed the USDC transfer on-chain) · HTTP 400 · tx 0xdba765bf…4085 · held as settled_4xx (the payment settled, then the paid request got a 4xx)
      What vet402 recorded

      The payment settled on-chain, and then the paid request got 400, 415 or 422. At the time vet402 did not send the input this listing declares: the request body before 2026-09-16 23:25 UTC, or on Base the query before 2026-09-27 23:27 UTC. Both facts stand: the seller took the payment, and the request lacked the declared input. The row is not counted against either side.The 402 terms vet402 paid: vet402 signed: exact · 0.06 USDC · payTo 0x00ac…6d21. Input sent: body not recorded, query not recorded. The listing's maxTimeoutSeconds is 300; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.06 USDC · payTo 0x00ac…6d21 · nonce not recorded · validBefore not recorded.Answer to the paid request: HTTP 400 · Content-Type application/json · PAYMENT-RESPONSE: success true, names a transaction.In export.csv this row's held_reason is settled_4xx (the payment settled, then the paid request got a 4xx). This page names the cause the row shows: charged, then refused an input vet402 had not sent.
      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.