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

api.exa.ai: x402 purchase results on Base, as of 2026-09-29

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

1.Your listings

  1. api.exa.ai/searchPOST
    Latest attempt
    2026-09-29 00:00 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.007 USDC · payTo 0x6d6e…9192. Input sent: body declared, query empty. The listing's maxTimeoutSeconds is 60; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.007 USDC · payTo 0x6d6e…9192 · nonce 0x28fe…5de1 · validBefore not recorded.Answer to the paid request: HTTP 200 · Content-Type application/json; charset=utf-8 · PAYMENT-RESPONSE: success true, names a transaction.Recorded (L1 paid purchase): settled (vet402 confirmed the USDC transfer on-chain) · HTTP 200 · tx 0xcfd31f4d…3028In export.csv?days=2: the row with attempted_at 2026-09-29T00:00:33Z and resource_key api.exa.ai/search.Dispute this purchaseEmail me when this result changes
    Earlier attempts
    1. 2026-09-27 12:01 UTC · delivered · no failure (delivered)settled (vet402 confirmed the USDC transfer on-chain) · HTTP 200 · tx 0xee6dc7aa…752a
      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.007 USDC · payTo 0x6d6e…9192. Input sent: body declared, query not recorded. The listing's maxTimeoutSeconds is 60; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.007 USDC · payTo 0x6d6e…9192 · nonce 0x5ce8…86e8 · validBefore not recorded.Answer to the paid request: HTTP 200 · Content-Type application/json; charset=utf-8 · PAYMENT-RESPONSE: success true, names a transaction.
      Dispute this purchase
    2. 2026-09-26 06:01 UTC · delivered · no failure (delivered)settled (vet402 confirmed the USDC transfer on-chain) · HTTP 200 · tx 0x97a14859…c70d
      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.007 USDC · payTo 0x6d6e…9192. Input sent: body declared, query not recorded. The listing's maxTimeoutSeconds is 60; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.007 USDC · payTo 0x6d6e…9192 · nonce 0x7def…a5ff · validBefore not recorded.Answer to the paid request: HTTP 200 · Content-Type application/json; charset=utf-8 · PAYMENT-RESPONSE: success true, names a transaction.
      Dispute this purchase
    3. 2026-09-25 00:02 UTC · delivered · no failure (delivered)settled (vet402 confirmed the USDC transfer on-chain) · HTTP 200 · tx 0x620dbd40…fdcd
      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.007 USDC · payTo 0x6d6e…9192. Input sent: body declared, query not recorded. The listing's maxTimeoutSeconds is 60; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.007 USDC · payTo 0x6d6e…9192 · nonce 0x8299…ff8d · validBefore not recorded.Answer to the paid request: HTTP 200 · Content-Type application/json; charset=utf-8 · PAYMENT-RESPONSE: success true, names a transaction.
      Dispute this purchase
    4. 2026-09-23 18:01 UTC · delivered · no failure (delivered)settled (vet402 confirmed the USDC transfer on-chain) · HTTP 200 · tx 0xd4aa59e5…7d7b
      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.007 USDC · payTo 0x6d6e…9192. Input sent: body declared, query not recorded. The listing's maxTimeoutSeconds is 60; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.007 USDC · payTo 0x6d6e…9192 · nonce 0xc37d…b5f4 · validBefore not recorded.Answer to the paid request: HTTP 200 · Content-Type application/json; charset=utf-8 · PAYMENT-RESPONSE: success true, names a transaction.
      Dispute this purchase
  2. api.exa.ai/contentsPOST
    Latest attempt
    not tried yet
    Result
    —
    Whose side
    —
    vet402 has not tried to buy this listing yet.Email me when this result changes

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.