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

vet402Sellers · What to fix firstMethodology

onchainpulse.theaslangroupllc.com: x402 purchase results on Base, as of 2026-09-18

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

1.Your listings

onchainpulse.theaslangroupllc.com/api/rh-launchesGET
Latest attempt
2026-09-18 12:07 UTC
Result
No record of the input vet402 sent
Whose side
not sorted: vet402 unproven
What we saw: 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.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.01 USDC · payTo 0x50ab…12fc. Input sent: body not recorded, query not recorded. The listing's maxTimeoutSeconds is 604900; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.01 USDC · payTo 0x50ab…12fc · nonce 0x6f65…7fb6 · validBefore not recorded.Answer to the paid request: HTTP 500 · Content-Type application/json; charset=utf-8 · no PAYMENT-RESPONSE recorded.What to fix: Nothing is counted against the seller.Not shown for this row: vet402 has no record of the input it sent.Recorded (L1 paid purchase): settled (vet402 confirmed the USDC transfer on-chain) · HTTP 500 · tx 0xddf217da…880bIn export.csv?days=12: the row with attempted_at 2026-09-18T12:07:55Z and resource_key onchainpulse.theaslangroupllc.com/api/rh-launches.Dispute this purchase Email me when this result changes
Earlier attempts
1. 2026-09-12 06:00 UTC · No record of the input vet402 sent · not sorted: vet402 unprovensettled (vet402 confirmed the USDC transfer on-chain) · HTTP 500 · tx 0xe23bc448…3e6b
  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.01 USDC · payTo 0x50ab…12fc. Input sent: body not recorded, query not recorded. The listing's maxTimeoutSeconds is 604900; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.01 USDC · payTo 0x50ab…12fc · nonce 0x7092…76bc · validBefore not recorded.Answer to the paid request: HTTP 500 · 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
onchainpulse.theaslangroupllc.com/api/evmtokenGET
Latest attempt
2026-09-17 15:23 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.015 USDC · payTo 0x50ab…12fc. Input sent: body not recorded, query not recorded. The listing's maxTimeoutSeconds is 604900; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.015 USDC · payTo 0x50ab…12fc · nonce 0x1930…acf9 · 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-17T15:23:58Z and resource_key onchainpulse.theaslangroupllc.com/api/evmtoken.Dispute this purchase Email me when this result changes
Earlier attempts
1. 2026-09-10 12:09 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.015 USDC · payTo 0x50ab…12fc. Input sent: body not recorded, query not recorded. The listing's maxTimeoutSeconds is 604900; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.015 USDC · payTo 0x50ab…12fc · nonce 0x3c3a…250a · 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 12:09 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.015 USDC · payTo 0x50ab…12fc. Input sent: body not recorded, query not recorded. The listing's maxTimeoutSeconds is 604900; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.015 USDC · payTo 0x50ab…12fc · 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
onchainpulse.theaslangroupllc.com/api/memecoinGET
Latest attempt
2026-09-14 06:00 UTC
Result
vet402's wallet held less USDC than the price
Whose side
vet402's side
What we saw: When 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.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.015 USDC · payTo 0x50ab…12fc. Input sent: body not recorded, query not recorded. The listing's maxTimeoutSeconds is 604900; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.015 USDC · payTo 0x50ab…12fc · nonce 0x51d3…8033 · 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's wallet held less USDC than the price.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=16: the row with attempted_at 2026-09-14T06:00:52Z and resource_key onchainpulse.theaslangroupllc.com/api/memecoin.Dispute this purchase Email me when this result changes
Earlier attempts
1. 2026-09-05 12:08 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.015 USDC · payTo 0x50ab…12fc. Input sent: body not recorded, query not recorded. The listing's maxTimeoutSeconds is 604900; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.015 USDC · payTo 0x50ab…12fc · nonce 0x0c2a…fd88 · 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
onchainpulse.theaslangroupllc.com/api/etf-flowsGET
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.Email me when this result changes
onchainpulse.theaslangroupllc.com/api/facet/honeypotGET
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.Email me when this result changes
onchainpulse.theaslangroupllc.com/api/facet/liquidityGET
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.Email me when this result changes
onchainpulse.theaslangroupllc.com/api/glossaryGET
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.Email me when this result changes
onchainpulse.theaslangroupllc.com/api/legislationGET
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.Email me when this result changes
onchainpulse.theaslangroupllc.com/api/token-safetyGET
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.