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

answerpool.io: x402 purchase results on Base, as of 2026-09-29

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

Rows marked census or retest were bought to give this seller a row of its own, or to buy again after a failure on vet402's side.

1.Your listings

  1. answerpool.io/v1/sec/xbrl/sharesGET
    Latest attempt
    2026-09-29 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.02 USDC · payTo 0xb3ba…ed8c. Input sent: body none, query declared. The listing's maxTimeoutSeconds is 300; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.02 USDC · payTo 0xb3ba…ed8c · nonce 0xfe32…d014 · validBefore not recorded.Answer to the paid request: HTTP 200 · Content-Type application/json · 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 0xc01bfe85…95c5 · bought by the retestIn export.csv?days=2: the row with attempted_at 2026-09-29T00:01:34Z and resource_key answerpool.io/v1/sec/xbrl/shares.Dispute this purchaseEmail me when this result changes
    Earlier attempts
    1. 2026-09-21 00:01 UTC · vet402 did not send the declared query · vet402's sidesettle_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)
      What vet402 recordedBefore 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.02 USDC · payTo 0xb3ba…ed8c. Input sent: body none, query not recorded. The listing's maxTimeoutSeconds is 300; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.02 USDC · payTo 0xb3ba…ed8c · nonce 0xbca4…4ad1 · validBefore not recorded.Answer to the paid request: HTTP 422 · Content-Type application/json · 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. answerpool.io/v1/sec/13f/managerGET
    Latest attempt
    2026-09-17 12:08 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.02 USDC · payTo 0xb3ba…ed8c. 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.02 USDC · payTo 0xb3ba…ed8c · nonce 0x4458…d3af · validBefore not recorded.Answer to the paid request: HTTP 422 · Content-Type application/json · 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 422 · 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-17T12:08:36Z and resource_key answerpool.io/v1/sec/13f/manager.Dispute this purchaseEmail me when this result changes
  3. answerpool.io/v1/sec/xbrl/financialsGET
    Latest attempt
    2026-09-16 00:02 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.02 USDC · payTo 0xb3ba…ed8c. 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.02 USDC · payTo 0xb3ba…ed8c · nonce 0x3f30…2ea6 · validBefore not recorded.Answer to the paid request: HTTP 422 · Content-Type application/json · 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 422 · no tx · held as unsettled_4xx (the paid request got a 4xx with no settlement receipt and no transaction)In export.csv?days=15: the row with attempted_at 2026-09-16T00:02:17Z and resource_key answerpool.io/v1/sec/xbrl/financials.Dispute this purchaseEmail me when this result changes
    Earlier attempts
    1. 2026-09-04 07:02 UTC · vet402 did not send the declared query · vet402's sidesettle_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)
      What vet402 recordedBefore 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.02 USDC · payTo 0xb3ba…ed8c. 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.02 USDC · payTo 0xb3ba…ed8c · nonce not recorded · validBefore not recorded.Answer to the paid request: HTTP 422 · Content-Type application/json · 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
  4. answerpool.io/v1/sec/companyGET
    Latest attempt
    2026-09-14 18:01 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: 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.02 USDC · payTo 0xb3ba…ed8c. 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.02 USDC · payTo 0xb3ba…ed8c · nonce 0xf83a…cd7b · validBefore not recorded.Answer to the paid request: HTTP 402 · Content-Type application/json · no PAYMENT-RESPONSE recorded.What to fix: Nothing for the seller to fix.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 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-14T18:01:26Z and resource_key answerpool.io/v1/sec/company.Dispute this purchaseEmail me when this result changes
    Earlier attempts
    1. 2026-09-04 19:01 UTC · vet402 did not send the declared query · vet402's sidesettle_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)
      What vet402 recordedBefore 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.02 USDC · payTo 0xb3ba…ed8c. 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.02 USDC · payTo 0xb3ba…ed8c · nonce 0xcfcd…f836 · validBefore not recorded.Answer to the paid request: HTTP 422 · Content-Type application/json · 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
  5. answerpool.io/v1/sec/xbrl/frameGET
    Latest attempt
    2026-09-13 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: 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.05 USDC · payTo 0xb3ba…ed8c. 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.05 USDC · payTo 0xb3ba…ed8c · nonce 0x05ca…b78e · validBefore not recorded.Answer to the paid request: HTTP 402 · Content-Type application/json · no PAYMENT-RESPONSE recorded.What to fix: Nothing for the seller to fix.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 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-13T12:08:55Z and resource_key answerpool.io/v1/sec/xbrl/frame.Dispute this purchaseEmail me when this result changes
    Earlier attempts
    1. 2026-09-04 07:02 UTC · vet402 did not send the declared query · vet402's sidesettle_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)
      What vet402 recordedBefore 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.05 USDC · payTo 0xb3ba…ed8c. 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.05 USDC · payTo 0xb3ba…ed8c · nonce not recorded · validBefore not recorded.Answer to the paid request: HTTP 422 · Content-Type application/json · 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
  6. answerpool.io/v1/sec/13f/changesGET
    Latest attempt
    2026-09-07 01:01 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.05 USDC · payTo 0xb3ba…ed8c. 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.05 USDC · payTo 0xb3ba…ed8c · nonce 0x72e6…8912 · validBefore not recorded.Answer to the paid request: HTTP 422 · Content-Type application/json · 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 422 · no tx · held as unsettled_4xx (the paid request got a 4xx with no settlement receipt and no transaction)In export.csv?days=24: the row with attempted_at 2026-09-07T01:01:01Z and resource_key answerpool.io/v1/sec/13f/changes.Dispute this purchaseEmail me when this result changes
  7. answerpool.io/v1/sec/insider/clustersGET
    Latest attempt
    2026-09-07 01: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.05 USDC · payTo 0xb3ba…ed8c. 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.05 USDC · payTo 0xb3ba…ed8c · nonce 0x6ab3…854c · validBefore not recorded.Answer to the paid request: HTTP 200 · Content-Type application/json · PAYMENT-RESPONSE: success true, names a transaction.Recorded (L1 paid purchase): settled (vet402 confirmed the USDC transfer on-chain) · HTTP 200 · tx 0x4c3d9d2b…bc2dIn export.csv?days=24: the row with attempted_at 2026-09-07T01:00:34Z and resource_key answerpool.io/v1/sec/insider/clusters.Dispute this purchaseEmail me when this result changes
  8. answerpool.io/v1/funding/signalsGET
    Latest attempt
    not tried yet
    Result
    —
    Whose side
    —
    vet402 has not tried to buy this listing yet.Email me when this result changes
  9. answerpool.io/v1/graph/auditorGET
    Latest attempt
    not tried yet
    Result
    —
    Whose side
    —
    vet402 has not tried to buy this listing yet.Email me when this result changes
  10. answerpool.io/v1/graph/interlocksGET
    Latest attempt
    not tried yet
    Result
    —
    Whose side
    —
    vet402 has not tried to buy this listing yet.Email me when this result changes
  11. answerpool.io/v1/graph/personGET
    Latest attempt
    not tried yet
    Result
    —
    Whose side
    —
    vet402 has not tried to buy this listing yet.Email me when this result changes
  12. answerpool.io/v1/graph/subsidiariesGET
    Latest attempt
    not tried yet
    Result
    —
    Whose side
    —
    vet402 has not tried to buy this listing yet.Email me when this result changes
  13. answerpool.io/v1/impact/cfrGET
    Latest attempt
    not tried yet
    Result
    —
    Whose side
    —
    vet402 has not tried to buy this listing yet.Email me when this result changes
  14. answerpool.io/v1/impact/companyGET
    Latest attempt
    not tried yet
    Result
    —
    Whose side
    —
    vet402 has not tried to buy this listing yet.Email me when this result changes
  15. answerpool.io/v1/impact/docketGET
    Latest attempt
    not tried yet
    Result
    —
    Whose side
    —
    vet402 has not tried to buy this listing yet.Email me when this result changes
  16. answerpool.io/v1/impact/ruleGET
    Latest attempt
    not tried yet
    Result
    —
    Whose side
    —
    vet402 has not tried to buy this listing yet.Email me when this result changes
  17. answerpool.io/v1/ipo/calendarGET
    Latest attempt
    not tried yet
    Result
    —
    Whose side
    —
    vet402 has not tried to buy this listing yet.Email me when this result changes
  18. answerpool.io/v1/ipo/companyGET
    Latest attempt
    not tried yet
    Result
    —
    Whose side
    —
    vet402 has not tried to buy this listing yet.Email me when this result changes
  19. answerpool.io/v1/ipo/pricedGET
    Latest attempt
    not tried yet
    Result
    —
    Whose side
    —
    vet402 has not tried to buy this listing yet.Email me when this result changes
  20. answerpool.io/v1/ipo/registrationsGET
    Latest attempt
    not tried yet
    Result
    —
    Whose side
    —
    vet402 has not tried to buy this listing yet.Email me when this result changes
  21. answerpool.io/v1/ipo/withdrawnGET
    Latest attempt
    not tried yet
    Result
    —
    Whose side
    —
    vet402 has not tried to buy this listing yet.Email me when this result changes
  22. answerpool.io/v1/peers/industryGET
    Latest attempt
    not tried yet
    Result
    —
    Whose side
    —
    vet402 has not tried to buy this listing yet.Email me when this result changes
  23. answerpool.io/v1/peers/similarGET
    Latest attempt
    not tried yet
    Result
    —
    Whose side
    —
    vet402 has not tried to buy this listing yet.Email me when this result changes
  24. answerpool.io/v1/regs/cfrGET
    Latest attempt
    not tried yet
    Result
    —
    Whose side
    —
    vet402 has not tried to buy this listing yet.Email me when this result changes
  25. answerpool.io/v1/regs/comment-deadlinesGET
    Latest attempt
    not tried yet
    Result
    —
    Whose side
    —
    vet402 has not tried to buy this listing yet.Email me when this result changes
  26. answerpool.io/v1/regs/digestGET
    Latest attempt
    not tried yet
    Result
    —
    Whose side
    —
    vet402 has not tried to buy this listing yet.Email me when this result changes
  27. answerpool.io/v1/regs/effectiveGET
    Latest attempt
    not tried yet
    Result
    —
    Whose side
    —
    vet402 has not tried to buy this listing yet.Email me when this result changes
  28. answerpool.io/v1/regs/eoGET
    Latest attempt
    not tried yet
    Result
    —
    Whose side
    —
    vet402 has not tried to buy this listing yet.Email me when this result changes
  29. answerpool.io/v1/regs/rulesGET
    Latest attempt
    not tried yet
    Result
    —
    Whose side
    —
    vet402 has not tried to buy this listing yet.Email me when this result changes
  30. answerpool.io/v1/regs/significantGET
    Latest attempt
    not tried yet
    Result
    —
    Whose side
    —
    vet402 has not tried to buy this listing yet.Email me when this result changes
  31. answerpool.io/v1/regs/watchGET
    Latest attempt
    not tried yet
    Result
    —
    Whose side
    —
    vet402 has not tried to buy this listing yet.Email me when this result changes
  32. answerpool.io/v1/sec/13f/holdersGET
    Latest attempt
    not tried yet
    Result
    —
    Whose side
    —
    vet402 has not tried to buy this listing yet.Email me when this result changes
  33. answerpool.io/v1/sec/13f/topGET
    Latest attempt
    not tried yet
    Result
    —
    Whose side
    —
    vet402 has not tried to buy this listing yet.Email me when this result changes
  34. answerpool.io/v1/sec/8kGET
    Latest attempt
    not tried yet
    Result
    —
    Whose side
    —
    vet402 has not tried to buy this listing yet.Email me when this result changes
  35. answerpool.io/v1/sec/8k/auditor-changeGET
    Latest attempt
    not tried yet
    Result
    —
    Whose side
    —
    vet402 has not tried to buy this listing yet.Email me when this result changes
  36. answerpool.io/v1/sec/8k/bankruptcyGET
    Latest attempt
    not tried yet
    Result
    —
    Whose side
    —
    vet402 has not tried to buy this listing yet.Email me when this result changes
  37. answerpool.io/v1/sec/8k/cyberGET
    Latest attempt
    not tried yet
    Result
    —
    Whose side
    —
    vet402 has not tried to buy this listing yet.Email me when this result changes
  38. answerpool.io/v1/sec/8k/delistingGET
    Latest attempt
    not tried yet
    Result
    —
    Whose side
    —
    vet402 has not tried to buy this listing yet.Email me when this result changes
  39. answerpool.io/v1/sec/8k/earningsGET
    Latest attempt
    not tried yet
    Result
    —
    Whose side
    —
    vet402 has not tried to buy this listing yet.Email me when this result changes
  40. answerpool.io/v1/sec/8k/historyGET
    Latest attempt
    not tried yet
    Result
    —
    Whose side
    —
    vet402 has not tried to buy this listing yet.Email me when this result changes
  41. answerpool.io/v1/sec/8k/impairmentGET
    Latest attempt
    not tried yet
    Result
    —
    Whose side
    —
    vet402 has not tried to buy this listing yet.Email me when this result changes
  42. answerpool.io/v1/sec/8k/maGET
    Latest attempt
    not tried yet
    Result
    —
    Whose side
    —
    vet402 has not tried to buy this listing yet.Email me when this result changes
  43. answerpool.io/v1/sec/8k/officer-changeGET
    Latest attempt
    not tried yet
    Result
    —
    Whose side
    —
    vet402 has not tried to buy this listing yet.Email me when this result changes
  44. answerpool.io/v1/sec/8k/restatementGET
    Latest attempt
    not tried yet
    Result
    —
    Whose side
    —
    vet402 has not tried to buy this listing yet.Email me when this result changes
  45. answerpool.io/v1/sec/calendarGET
    Latest attempt
    not tried yet
    Result
    —
    Whose side
    —
    vet402 has not tried to buy this listing yet.Email me when this result changes
  46. answerpool.io/v1/sec/digestGET
    Latest attempt
    not tried yet
    Result
    —
    Whose side
    —
    vet402 has not tried to buy this listing yet.Email me when this result changes
  47. answerpool.io/v1/sec/eventsGET
    Latest attempt
    not tried yet
    Result
    —
    Whose side
    —
    vet402 has not tried to buy this listing yet.Email me when this result changes
  48. answerpool.io/v1/sec/filings/cadenceGET
    Latest attempt
    not tried yet
    Result
    —
    Whose side
    —
    vet402 has not tried to buy this listing yet.Email me when this result changes
  49. answerpool.io/v1/sec/filings/topGET
    Latest attempt
    not tried yet
    Result
    —
    Whose side
    —
    vet402 has not tried to buy this listing yet.Email me when this result changes
  50. answerpool.io/v1/sec/formd/fundsGET
    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.