Independent MeasurementSeller: purchase results on BaseRead from the database 2026-09-29 06:11 UTC · reused for up to 5 min

vet402Sellers · What to fix firstMethodology

skim402.com: x402 purchase results on Base, as of 2026-09-26

9 Base listings. By the latest attempt at each: 3 delivered · 0 failed on the seller's side · 3 on vet402's side · 3 not tried yet. Latest attempt: 2026-09-26 18:01 UTC.

1.Your listings

skim402.com/api/v2/signal/studio-jobs/latestGET
Latest attempt
2026-09-26 18: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.005 USDC · payTo 0x63ae…cddc. Input sent: body none, query not recorded. The listing's maxTimeoutSeconds is 120; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.005 USDC · payTo 0x63ae…cddc · nonce 0xd816…c3a4 · 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 0x108d2874…de92In export.csv?days=4: the row with attempted_at 2026-09-26T18:01:53Z and resource_key skim402.com/api/v2/signal/studio-jobs/latest.Dispute this purchase Email me when this result changes
Earlier attempts
1. 2026-09-02 19:01 UTC · No record of the input vet402 sent · not sorted: vet402 unprovensettle_failed (vet402 signed a payment and got no settlement receipt back) · HTTP 402 · no tx
  What vet402 recorded
  This purchase is from before vet402 recorded the body and the query it sent on each paid request (the query on Base since 2026-09-27 23:27 UTC), so it cannot show that it sent the input the listing declares. The row is not counted against the seller.The 402 terms vet402 paid: vet402 signed: exact · 0.005 USDC · payTo 0x63ae…cddc. 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.005 USDC · payTo 0x63ae…cddc · nonce not recorded · validBefore not recorded.Answer to the paid request: HTTP 402 · Content-Type application/json; charset=utf-8 · no PAYMENT-RESPONSE recorded.Not shown for this row: vet402 has no record of the input it sent.
  Dispute this purchase
skim402.com/api/v2/signal/film-incentives/latestGET
Latest attempt
2026-09-22 06: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.005 USDC · payTo 0x63ae…cddc. Input sent: body none, query not recorded. The listing's maxTimeoutSeconds is 120; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.005 USDC · payTo 0x63ae…cddc · nonce 0x96ab…cd98 · 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 0x3b08b90b…8e13In export.csv?days=9: the row with attempted_at 2026-09-22T06:00:50Z and resource_key skim402.com/api/v2/signal/film-incentives/latest.Dispute this purchase Email me when this result changes
skim402.com/api/v2/readGET
Latest attempt
2026-09-17 18:00 UTC
Result
vet402 did not send the declared query
Whose side
vet402's side
What we saw: Before 2026-09-27 23:27 UTC, vet402 did not add the query parameters the seller's 402 declares to paid requests on Base, and this listing declares them (example values, or required names). The seller refused the request with 400 or 422.Last result about the seller: none among the attempts shown. The latest attempt failed on vet402's side; vet402 has not bought this listing again since.The 402 terms vet402 paid: vet402 signed: exact · 0.002 USDC · payTo 0x63ae…cddc. 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.002 USDC · payTo 0x63ae…cddc · nonce 0x9f06…34c0 · validBefore not recorded.Answer to the paid request: HTTP 400 · Content-Type application/json; charset=utf-8 · no PAYMENT-RESPONSE recorded.What to fix: Nothing for the seller to fix.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 query.This failure was on vet402's side, not the seller's.Recorded (L1 paid purchase): settle_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)In export.csv?days=13: the row with attempted_at 2026-09-17T18:00:59Z and resource_key skim402.com/api/v2/read.Dispute this purchase Email me when this result changes
Earlier attempts
1. 2026-09-10 07:01 UTC · vet402 did not send the declared query · 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 recorded
  Before 2026-09-27 23:27 UTC, vet402 did not add the query parameters the seller's 402 declares to paid requests on Base, and this listing declares them (example values, or required names). The seller refused the request with 400 or 422.The 402 terms vet402 paid: vet402 signed: exact · 0.002 USDC · payTo 0x63ae…cddc. 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.002 USDC · payTo 0x63ae…cddc · nonce 0x9c9e…1505 · 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 query.
  Dispute this purchase
2. 2026-09-02 07:01 UTC · vet402 did not send the declared query · 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 recorded
  Before 2026-09-27 23:27 UTC, vet402 did not add the query parameters the seller's 402 declares to paid requests on Base, and this listing declares them (example values, or required names). The seller refused the request with 400 or 422.The 402 terms vet402 paid: vet402 signed: exact · 0.002 USDC · payTo 0x63ae…cddc. 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.002 USDC · payTo 0x63ae…cddc · nonce not recorded · 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 query.
  Dispute this purchase
skim402.com/api/v2/signal/ai-news/latestGET
Latest attempt
2026-09-17 15:24 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.005 USDC · payTo 0x63ae…cddc. 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.005 USDC · payTo 0x63ae…cddc · nonce 0x0bc5…032d · 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 0xfedf41e0…4dbdIn export.csv?days=13: the row with attempted_at 2026-09-17T15:24:42Z and resource_key skim402.com/api/v2/signal/ai-news/latest.Dispute this purchase Email me when this result changes
Earlier attempts
1. 2026-09-10 19:01 UTC · delivered · no failure (delivered)settled (vet402 confirmed the USDC transfer on-chain) · HTTP 200 · tx 0xbb0b7e70…8f6d
  What vet402 recorded
  Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.The 402 terms vet402 paid: vet402 signed: exact · 0.005 USDC · payTo 0x63ae…cddc. 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.005 USDC · payTo 0x63ae…cddc · nonce 0xe60f…02e6 · 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-04 12:07 UTC · delivered · no failure (delivered)settled (vet402 confirmed the USDC transfer on-chain) · HTTP 200 · tx 0xc5385580…0400
  What vet402 recorded
  Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.The 402 terms vet402 paid: vet402 signed: exact · 0.005 USDC · payTo 0x63ae…cddc. 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.005 USDC · payTo 0x63ae…cddc · nonce 0x4ef4…7101 · 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
skim402.com/api/v1/read/jsPOST
Latest attempt
2026-08-31 12:09 UTC
Result
vet402 did not send the declared request body
Whose side
vet402's side
What we saw: Before 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").Last result about the seller: none among the attempts shown. The latest attempt failed on vet402's side; vet402 has not bought this listing again since.The 402 terms vet402 paid: vet402 signed: exact · 0.005 USDC · payTo 0x63ae…cddc. Input sent: body not recorded, query not recorded. The listing's maxTimeoutSeconds is 60; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.005 USDC · payTo 0x63ae…cddc · nonce not recorded · validBefore not recorded.Answer to the paid request: HTTP 400 · Content-Type application/json; charset=utf-8 · no PAYMENT-RESPONSE recorded.What to fix: Nothing for the seller to fix.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.This failure was on vet402's side, not the seller's.Recorded (L1 paid purchase): settle_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)In export.csv?days=30: the row with attempted_at 2026-08-31T12:09:16Z and resource_key skim402.com/api/v1/read/js.Dispute this purchase Email me when this result changes
skim402.com/api/v1/readPOST
Latest attempt
2026-08-28 12:20 UTC
Result
vet402 did not send the declared request body
Whose side
vet402's side
What we saw: Before 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").Last result about the seller: none among the attempts shown. The latest attempt failed on vet402's side; vet402 has not bought this listing again since.The 402 terms vet402 paid: vet402 signed: exact · 0.002 USDC · payTo 0x63ae…cddc. Input sent: body not recorded, query not recorded. The listing's maxTimeoutSeconds is 60; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.002 USDC · payTo 0x63ae…cddc · nonce not recorded · validBefore not recorded.Answer to the paid request: HTTP 400 · Content-Type application/json; charset=utf-8 · no PAYMENT-RESPONSE recorded.What to fix: Nothing for the seller to fix.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.This failure was on vet402's side, not the seller's.Recorded (L1 paid purchase): settle_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)In export.csv?days=33: the row with attempted_at 2026-08-28T12:20:25Z and resource_key skim402.com/api/v1/read.Dispute this purchase Email me when this result changes
skim402.com/api/v2/feeds/x402/latestGET
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.Email me when this result changes
skim402.com/api/v2/read/jsGET
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.Email me when this result changes
skim402.com/api/v2/signal/entity-formations/latestGET
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.