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

vet402Sellers · What to fix firstMethodology

proxy.suverse.io: x402 purchase results on Base, latest attempt 2026-09-27

53 Base listings. Latest result about the seller at each listing: 11 delivered · 0 failed on the seller's side · 3 with no such result among the attempts shown · 39 not tried yet. This counts, for each listing, the newest purchase that delivered or the newest failure on the seller's side. Attempts on vet402's side, not bought, not sorted, or awaiting on-chain verification are skipped.

By the latest attempt at each listing, whatever it was: 8 delivered · 0 failed on the seller's side · 4 on vet402's side · 2 not sorted (vet402 cannot show the failure was not its own) · 39 not tried yet.

Latest attempt: 2026-09-27 00:02 UTC. This page read the ledger at 2026-09-29 06:51 UTC and reuses that read for up to 5 min.

1.Your listings

proxy.suverse.io/v1/data/fiat-exchange-ratesGET
Latest attempt
2026-09-27 00:02 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.05 USDC · payTo 0x260f…82b0. Input sent: body none, query not recorded. The listing's maxTimeoutSeconds is 60; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.05 USDC · payTo 0x260f…82b0 · nonce 0xe4b2…6311 · validBefore not recorded.Answer to the paid request: HTTP 200 · Content-Type application/json · PAYMENT-RESPONSE: success true, names a transaction.Decision API now: asking… · the full answerRecorded (L1 paid purchase): settled (vet402 confirmed the USDC transfer on-chain) · HTTP 200 · tx 0x90d4ae15…f65cIn export.csv?days=4: the row with attempted_at 2026-09-27T00:02:19Z and resource_key proxy.suverse.io/v1/data/fiat-exchange-rates.Dispute this purchase Email me when this result changes
Earlier attempts
1. 2026-09-17 00:00 UTC · delivered · no failure (delivered)settled (vet402 confirmed the USDC transfer on-chain) · HTTP 200 · tx 0xb4bc2cb0…4bc9
  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.05 USDC · payTo 0x260f…82b0. 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.05 USDC · payTo 0x260f…82b0 · nonce 0x0dac…fd9c · validBefore not recorded.Answer to the paid request: HTTP 200 · Content-Type application/json · PAYMENT-RESPONSE: success true, names a transaction.
  Dispute this purchase
proxy.suverse.io/v1/data/ethereum-gas-trackerGET
Latest attempt
2026-09-27 00:02 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.05 USDC · payTo 0x260f…82b0. Input sent: body none, query not recorded. The listing's maxTimeoutSeconds is 60; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.05 USDC · payTo 0x260f…82b0 · nonce 0x865c…6c41 · validBefore not recorded.Answer to the paid request: HTTP 200 · Content-Type application/json; charset=utf-8 · PAYMENT-RESPONSE: success true, names a transaction.Decision API now: asking… · the full answerThe 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 0x4e8c8e82…edc4In export.csv?days=4: the row with attempted_at 2026-09-27T00:02:03Z and resource_key proxy.suverse.io/v1/data/ethereum-gas-tracker.Dispute this purchase Email me when this result changes
Earlier attempts
1. 2026-09-14 06:01 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 signed: vet402 signed: exact · 0.05 USDC · payTo 0x260f…82b0. 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.05 USDC · payTo 0x260f…82b0 · nonce 0x0e56…e8ea · 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-08-30 12:07 UTC · delivered · no failure (delivered)settled (vet402 confirmed the USDC transfer on-chain) · HTTP 200 · tx 0x3d053bf9…9764
  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.05 USDC · payTo 0x260f…82b0. 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.05 USDC · payTo 0x260f…82b0 · nonce not recorded · 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-08-23 12:43 UTC · delivered · no failure (delivered)settled (vet402 confirmed the USDC transfer on-chain) · HTTP 200 · tx 0x67e0147f…2f8d
  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.05 USDC · payTo 0x260f…82b0. 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.05 USDC · payTo 0x260f…82b0 · nonce not recorded · 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
proxy.suverse.io/v1/data/suverse-net-ip-geoPOST
Latest attempt
2026-09-21 06: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.05 USDC · payTo 0x1b25…964a. 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.05 USDC · payTo 0x1b25…964a · nonce 0x5e9c…5297 · validBefore not recorded.Answer to the paid request: HTTP 200 · Content-Type application/json; charset=utf-8 · PAYMENT-RESPONSE: success true, names a transaction.Decision API now: · the full answerRecorded (L1 paid purchase): settled (vet402 confirmed the USDC transfer on-chain) · HTTP 200 · tx 0x00660ba0…4ee2In export.csv?days=10: the row with attempted_at 2026-09-21T06:01:20Z and resource_key proxy.suverse.io/v1/data/suverse-net-ip-geo.Dispute this purchase Email me when this result changes
proxy.suverse.io/v1/data/suverse-time-coordinatePOST
Latest attempt
2026-09-20 12:08 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. This page does not count the row as the seller's fault.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 signed: vet402 signed: exact · 0.05 USDC · payTo 0x2d50…dfba. 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.05 USDC · payTo 0x2d50…dfba · nonce 0x6cfa…f827 · validBefore not recorded.Answer to the paid request: HTTP 402 · Content-Type application/json; charset=utf-8 · no PAYMENT-RESPONSE recorded.What to fix: This page does not count it as the seller's fault.Not shown for this row: vet402 has no record of the input it sent.Decision API now: · the full answerRecorded (L1 paid purchase): settle_failed (vet402 signed a payment and got no settlement receipt back) · HTTP 402 · no txIn export.csv?days=10: the row with attempted_at 2026-09-20T12:08:34Z and resource_key proxy.suverse.io/v1/data/suverse-time-coordinate.Dispute this purchase Email me when this result changes
proxy.suverse.io/v1/data/ip-geolocationGET
Latest attempt
2026-09-20 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.05 USDC · payTo 0x260f…82b0. 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.05 USDC · payTo 0x260f…82b0 · nonce 0xf02c…d2a9 · validBefore not recorded.Answer to the paid request: HTTP 200 · Content-Type application/json; charset=utf-8 · PAYMENT-RESPONSE: success true, names a transaction.Decision API now: · the full answerRecorded (L1 paid purchase): settled (vet402 confirmed the USDC transfer on-chain) · HTTP 200 · tx 0xb5456fe6…dc88In export.csv?days=11: the row with attempted_at 2026-09-20T00:01:06Z and resource_key proxy.suverse.io/v1/data/ip-geolocation.Dispute this purchase Email me when this result changes
proxy.suverse.io/v1/swap/base/quotePOST
Latest attempt
2026-09-16 12:09 UTC
Result
Charged, then refused an input vet402 had not sent
Whose side
not sorted: charged, then rejected an input vet402 had not sent
What we saw: 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. This page counts the row against neither side.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.001 USDC · payTo 0x4261…3b2e. 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.001 USDC · payTo 0x4261…3b2e · nonce 0x7c56…41ff · validBefore not recorded.Answer to the paid request: HTTP 400 · Content-Type application/json; charset=utf-8 · PAYMENT-RESPONSE: success true, names a transaction.What to fix: This page does not count it as the seller's fault. Checking the input before settling avoids taking a payment for a request you refuse.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.Decision API now: · the full answerRecorded (L1 paid purchase): settled (vet402 confirmed the USDC transfer on-chain) · HTTP 400 · tx 0x052e84f6…86bd · held as settled_4xx (the payment settled, then the paid request got a 4xx)In export.csv?days=14: the row with attempted_at 2026-09-16T12:09:52Z and resource_key proxy.suverse.io/v1/swap/base/quote.Dispute this purchase Email me when this result changes
Earlier attempts
1. 2026-09-10 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 0x7947c44c…9d5c · 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. This page counts the row against neither side.The 402 terms vet402 paid: vet402 signed: exact · 0.001 USDC · payTo 0x4261…3b2e. 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.001 USDC · payTo 0x4261…3b2e · nonce 0x5233…0959 · validBefore not recorded.Answer to the paid request: HTTP 400 · Content-Type application/json; charset=utf-8 · 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. 2026-08-27 12:32 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 0x2c2f20f1…ea73 · 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. This page counts the row against neither side.The 402 terms vet402 paid: vet402 signed: exact · 0.001 USDC · payTo 0x4261…3b2e. 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.001 USDC · payTo 0x4261…3b2e · nonce not recorded · validBefore not recorded.Answer to the paid request: HTTP 400 · Content-Type application/json; charset=utf-8 · 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-21 08:32 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 0x8e4bb970…b156 · 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. This page counts the row against neither side.The 402 terms vet402 paid: vet402 signed: exact · 0.001 USDC · payTo 0x4261…3b2e. 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.001 USDC · payTo 0x4261…3b2e · nonce not recorded · validBefore not recorded.Answer to the paid request: HTTP 400 · Content-Type application/json; charset=utf-8 · 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
proxy.suverse.io/v1/proxy/reskey_1166628d/bazaar-testGET
Latest attempt
2026-09-15 12:07 UTC
Result
vet402's wallet was out of USDC
Whose side
vet402's side
What we saw: 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).Last result about the seller: delivered on 2026-09-08 19:01 UTC. The latest attempt failed on vet402's side; vet402 has not bought this listing again since.The 402 terms vet402 signed: vet402 signed: exact · 0.001 USDC · payTo 0x260f…82b0. 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.001 USDC · payTo 0x260f…82b0 · nonce 0x8985…fe4e · validBefore not recorded.Answer to the paid request: HTTP 402 · Content-Type application/json; charset=utf-8 · no PAYMENT-RESPONSE recorded.What to fix: Nothing for the seller to fix.Decision API now: · the full answerThis 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 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))In export.csv?days=15: the row with attempted_at 2026-09-15T12:07:57Z and resource_key proxy.suverse.io/v1/proxy/reskey_1166628d/bazaar-test.Dispute this purchase Email me when this result changes
Earlier attempts
1. 2026-09-08 19:01 UTC · delivered · no failure (delivered)settled (vet402 confirmed the USDC transfer on-chain) · HTTP 200 · tx 0x18f9accf…1a6f
  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.001 USDC · payTo 0x260f…82b0. 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.001 USDC · payTo 0x260f…82b0 · nonce 0x1eca…a60f · 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-08-31 12:07 UTC · delivered · no failure (delivered)settled (vet402 confirmed the USDC transfer on-chain) · HTTP 200 · tx 0x0d9d809b…0b65
  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.001 USDC · payTo 0x260f…82b0. 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.001 USDC · payTo 0x260f…82b0 · nonce not recorded · 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-08-24 23:34 UTC · delivered · no failure (delivered)settled (vet402 confirmed the USDC transfer on-chain) · HTTP 200 · tx 0x1427884b…6449
  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.001 USDC · payTo 0x260f…82b0. 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.001 USDC · payTo 0x260f…82b0 · nonce not recorded · 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-08-17 12:47 UTC · delivered · no failure (delivered)settled (vet402 confirmed the USDC transfer on-chain) · HTTP 200 · tx 0x3648ffc3…4383
  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.001 USDC · payTo 0x260f…82b0. 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.001 USDC · payTo 0x260f…82b0 · nonce not recorded · 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
proxy.suverse.io/v1/data/smart-money-netflowPOST
Latest attempt
2026-09-14 12:08 UTC
Result
vet402's wallet was out of USDC
Whose side
vet402's side
What we saw: 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).Last result about the seller: delivered on 2026-08-30 12:07 UTC. The latest attempt failed on vet402's side; vet402 has not bought this listing again since.The 402 terms vet402 signed: vet402 signed: exact · 0.1 USDC · payTo 0x260f…82b0. 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.1 USDC · payTo 0x260f…82b0 · nonce 0x9b02…1944 · validBefore not recorded.Answer to the paid request: HTTP 402 · Content-Type application/json; charset=utf-8 · no PAYMENT-RESPONSE recorded.What to fix: Nothing for the seller to fix.Decision API now: · the full answerThis 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 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))In export.csv?days=16: the row with attempted_at 2026-09-14T12:08:24Z and resource_key proxy.suverse.io/v1/data/smart-money-netflow.Dispute this purchase Email me when this result changes
Earlier attempts
1. 2026-08-30 12:07 UTC · delivered · no failure (delivered)settled (vet402 confirmed the USDC transfer on-chain) · HTTP 200 · tx 0xea6b3dcc…c833
  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.1 USDC · payTo 0x260f…82b0. 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.1 USDC · payTo 0x260f…82b0 · nonce not recorded · 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-08-23 12:42 UTC · delivered · no failure (delivered)settled (vet402 confirmed the USDC transfer on-chain) · HTTP 200 · tx 0x24c9ecc1…2ebd
  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.1 USDC · payTo 0x260f…82b0. 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.1 USDC · payTo 0x260f…82b0 · nonce not recorded · 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
proxy.suverse.io/v1/data/dex-trending-poolsPOST
Latest attempt
2026-09-14 00:00 UTC
Result
vet402's wallet was out of USDC
Whose side
vet402's side
What we saw: 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).Last result about the seller: delivered on 2026-08-31 12:08 UTC. The latest attempt failed on vet402's side; vet402 has not bought this listing again since.The 402 terms vet402 signed: vet402 signed: exact · 0.1 USDC · payTo 0xe903…b751. 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.1 USDC · payTo 0xe903…b751 · nonce 0xc2b3…9365 · validBefore not recorded.Answer to the paid request: HTTP 402 · Content-Type application/json; charset=utf-8 · no PAYMENT-RESPONSE recorded.What to fix: Nothing for the seller to fix.Decision API now: · the full answerThis 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 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))In export.csv?days=17: the row with attempted_at 2026-09-14T00:00:53Z and resource_key proxy.suverse.io/v1/data/dex-trending-pools.Dispute this purchase Email me when this result changes
Earlier attempts
1. 2026-08-31 12:08 UTC · delivered · no failure (delivered)settled (vet402 confirmed the USDC transfer on-chain) · HTTP 200 · tx 0xf51294fb…bdbd
  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.1 USDC · payTo 0xe903…b751. 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.1 USDC · payTo 0xe903…b751 · nonce not recorded · 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-08-24 23:34 UTC · delivered · no failure (delivered)settled (vet402 confirmed the USDC transfer on-chain) · HTTP 200 · tx 0x6c771d1c…1160
  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.1 USDC · payTo 0xe903…b751. 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.1 USDC · payTo 0xe903…b751 · nonce not recorded · 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
proxy.suverse.io/v1/data/weather-forecast-nycGET
Latest attempt
2026-09-06 01: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.05 USDC · payTo 0x260f…82b0. 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.05 USDC · payTo 0x260f…82b0 · nonce 0x2cc4…d656 · validBefore not recorded.Answer to the paid request: HTTP 200 · Content-Type application/json; charset=utf-8 · PAYMENT-RESPONSE: success true, names a transaction.Decision API now: · the full answerRecorded (L1 paid purchase): settled (vet402 confirmed the USDC transfer on-chain) · HTTP 200 · tx 0x29f2ab7a…711fIn export.csv?days=25: the row with attempted_at 2026-09-06T01:01:03Z and resource_key proxy.suverse.io/v1/data/weather-forecast-nyc.Dispute this purchase Email me when this result changes
proxy.suverse.io/v1/data/suverse-wiki-randomPOST
Latest attempt
2026-09-02 00:03 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.06 USDC · payTo 0x7d7c…0a73. 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.06 USDC · payTo 0x7d7c…0a73 · nonce not recorded · validBefore not recorded.Answer to the paid request: HTTP 200 · Content-Type application/json; charset=utf-8 · PAYMENT-RESPONSE: success true, names a transaction.Decision API now: · the full answerRecorded (L1 paid purchase): settled (vet402 confirmed the USDC transfer on-chain) · HTTP 200 · tx 0x557b59e1…e68eIn export.csv?days=29: the row with attempted_at 2026-09-02T00:03:44Z and resource_key proxy.suverse.io/v1/data/suverse-wiki-random.Dispute this purchase Email me when this result changes
proxy.suverse.io/v1/data/smart-money-top-walletsPOST
Latest attempt
2026-08-29 12:09 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.05 USDC · payTo 0xe903…b751. 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.05 USDC · payTo 0xe903…b751 · nonce not recorded · validBefore not recorded.Answer to the paid request: HTTP 200 · Content-Type application/json; charset=utf-8 · PAYMENT-RESPONSE: success true, names a transaction.Decision API now: · the full answerRecorded (L1 paid purchase): settled (vet402 confirmed the USDC transfer on-chain) · HTTP 200 · tx 0x0645807c…ec3cIn export.csv?days=32: the row with attempted_at 2026-08-29T12:09:16Z and resource_key proxy.suverse.io/v1/data/smart-money-top-wallets.Dispute this purchase Email me when this result changes
proxy.suverse.io/v1/data/crypto-market-pulsePOST
Latest attempt
2026-08-26 12:35 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.1 USDC · payTo 0x260f…82b0. 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.1 USDC · payTo 0x260f…82b0 · nonce not recorded · validBefore not recorded.Answer to the paid request: HTTP 200 · Content-Type application/json; charset=utf-8 · PAYMENT-RESPONSE: success true, names a transaction.Decision API now: · the full answerRecorded (L1 paid purchase): settled (vet402 confirmed the USDC transfer on-chain) · HTTP 200 · tx 0xf75911b4…b89bIn export.csv?days=35: the row with attempted_at 2026-08-26T12:35:28Z and resource_key proxy.suverse.io/v1/data/crypto-market-pulse.Dispute this purchase Email me when this result changes
proxy.suverse.io/v1/data/suverse-perp-open-interestPOST
Latest attempt
2026-08-25 12:53 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 signed: vet402 signed: exact · 0.1 USDC · payTo 0x260f…82b0. 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.1 USDC · payTo 0x260f…82b0 · nonce not recorded · validBefore not recorded.Answer to the paid request: HTTP 422 · 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.Decision API now: · the full answerThis 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 422 · no tx · held as unsettled_4xx (the paid request got a 4xx with no settlement receipt and no transaction)In export.csv?days=36: the row with attempted_at 2026-08-25T12:53:16Z and resource_key proxy.suverse.io/v1/data/suverse-perp-open-interest.Dispute this purchase Email me when this result changes
proxy.suverse.io/v1/data/bitcoin-block-infoPOST
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.Email me when this result changes
proxy.suverse.io/v1/data/polymarket-eventsPOST
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.Email me when this result changes
proxy.suverse.io/v1/data/polymarket-midpoint-pricePOST
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.Email me when this result changes
proxy.suverse.io/v1/data/polymarket-new-marketsPOST
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.Email me when this result changes
proxy.suverse.io/v1/data/polymarket-position-holdersPOST
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.Email me when this result changes
proxy.suverse.io/v1/data/polymarket-tagsPOST
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.Email me when this result changes
proxy.suverse.io/v1/data/suverse-anime-jikan-character-detailPOST
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.Email me when this result changes
proxy.suverse.io/v1/data/suverse-anime-topPOST
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.Email me when this result changes
proxy.suverse.io/v1/data/suverse-artic-artist-rosterPOST
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.Email me when this result changes
proxy.suverse.io/v1/data/suverse-chesscom-player-statsPOST
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.Email me when this result changes
proxy.suverse.io/v1/data/suverse-demographics-fcc-blockPOST
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.Email me when this result changes
proxy.suverse.io/v1/data/suverse-federal-agenciesPOST
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.Email me when this result changes
proxy.suverse.io/v1/data/suverse-gov-fdic-financialsPOST
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.Email me when this result changes
proxy.suverse.io/v1/data/suverse-gov-fdic-institutionsPOST
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.Email me when this result changes
proxy.suverse.io/v1/data/suverse-macro-cpi-inflationPOST
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.Email me when this result changes
proxy.suverse.io/v1/data/suverse-meal-by-categoryPOST
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.Email me when this result changes
proxy.suverse.io/v1/data/suverse-met-searchPOST
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.Email me when this result changes
proxy.suverse.io/v1/data/suverse-mlb-standingsPOST
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.Email me when this result changes
proxy.suverse.io/v1/data/suverse-net-client-ipPOST
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.Email me when this result changes
proxy.suverse.io/v1/data/suverse-ocean-station-infoPOST
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.Email me when this result changes
proxy.suverse.io/v1/data/suverse-openlibrary-subjectPOST
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.Email me when this result changes
proxy.suverse.io/v1/data/suverse-pokemon-type-matchupPOST
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.Email me when this result changes
proxy.suverse.io/v1/data/suverse-pypi-packagePOST
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.Email me when this result changes
proxy.suverse.io/v1/data/suverse-quakes-by-regionPOST
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.Email me when this result changes
proxy.suverse.io/v1/data/suverse-rel-quran-surahPOST
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.Email me when this result changes
proxy.suverse.io/v1/data/suverse-reverse-geocodePOST
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.Email me when this result changes
proxy.suverse.io/v1/data/suverse-rxnorm-rxcuiPOST
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.Email me when this result changes
proxy.suverse.io/v1/data/suverse-sec-tickersPOST
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.Email me when this result changes
proxy.suverse.io/v1/data/suverse-space-iss-orbitPOST
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.Email me when this result changes
proxy.suverse.io/v1/data/suverse-sports-next-eventsPOST
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.Email me when this result changes
proxy.suverse.io/v1/data/suverse-stablecoin-supplyPOST
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.Email me when this result changes
proxy.suverse.io/v1/data/suverse-swpc-solar-wind-magPOST
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.Email me when this result changes
proxy.suverse.io/v1/data/suverse-time-by-ipPOST
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.Email me when this result changes
proxy.suverse.io/v1/data/suverse-treasury-savings-bondsPOST
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.Email me when this result changes
proxy.suverse.io/v1/data/suverse-trivia-question-bankPOST
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.Email me when this result changes
proxy.suverse.io/v1/data/suverse-trivia-quiz-questionsPOST
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. “Decision API now” is what the decision API (GET /api/v1/resources/{id}/decision?role=payer, no key) answers for the listing when you open this page; your browser asks it for the first 2 listings, and for the others when you ask. It is cautious for the payer: it leaves out the attempts that show vet402's fault, are held, or took no payment, and counts the rest, so it can say WARN or BLOCK for a listing whose failures this page leaves not sorted (API reference). 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.