Independent MeasurementSeller: purchase results on BaseRead from the database 2026-11-09 11:18 UTC. Refreshed after a view, so the first view after a quiet period can be older.

vet402Sellers · What to fix first · Methodology

sift.srv1996466.hstgr.cloud: x402 purchase results on Base, latest attempt 2026-11-06

58 Base listings. Latest result about the seller at each listing: 14 delivered · 0 failed on the seller's side · 0 with no such result among the attempts shown · 44 with no Base purchase. This counts, for each listing, the newest Base purchase that delivered or the newest Base 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: 14 delivered · 0 failed on the seller's side · 0 on vet402's side · 44 with no Base purchase.

Latest attempt: 2026-11-06 18:02 UTC. This page read the ledger at 2026-11-09 11:18 UTC and reuses that read for up to 5 min. The first view after a quiet period can show an older read.

Rows marked census or retest were bought to give this seller a row of its own, to buy again after a failure on vet402's side, or to read again a listing whose latest delivery missed declared keys.

1.Your listings

sift.srv1996466.hstgr.cloud/v1/crypto/gasGET
Latest attempt
2026-11-06 18:02 UTC
Result
delivered
Whose side
no failure (delivered)
Decision API now: asking… · the full answer
Latest L0 check (the 402 to an unpaid request): pass at 2026-11-07 16:40 UTC. Probes run oldest first, so there is no booked time. The next one usually comes by 2026-11-12 16:40 UTC (within 120 hours of the last).
What vet402 saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.The 402 terms vet402 paid: exact · 0.001 USDC · payTo 0x33d2…fa0d. Input sent: body none, query empty. The listing's maxTimeoutSeconds is 120. vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.001 USDC · payTo 0x33d2…fa0d · nonce 0x6706…d502 · 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 re-read the transfer on-chain in that chain's pinned settlement asset) · HTTP 200 · tx 0x0f4bdf68…f2f3In export.csv?days=4: the row with attempted_at 2026-11-06T18:02:21Z and resource_key sift.srv1996466.hstgr.cloud/v1/crypto/gas.
After a fixNext purchase by vet402: Not before 2026-12-06 18:02 UTC (this listing has 3 or more settled purchases, so it is bought at most once every 30 days). After that it depends on the daily budget and the order of demand, so this is the earliest date, not a booking.Email me when this result changes Dispute this purchaseA dispute does not start a purchase. The signed dispute route runs one fresh L0 check, an unpaid request.
Earlier attempts
1. 2026-10-30 18:02 UTC · delivered · no failure (delivered)settled (vet402 re-read the transfer on-chain in that chain's pinned settlement asset) · HTTP 200 · tx 0x966a9aaf…2d0b
  What vet402 recorded
  Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.The 402 terms vet402 paid: exact · 0.001 USDC · payTo 0x33d2…fa0d. Input sent: body none, query empty. The listing's maxTimeoutSeconds is 120. vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.001 USDC · payTo 0x33d2…fa0d · nonce 0xbc1e…ee9a · validBefore not recorded.Answer to the paid request: HTTP 200 · Content-Type application/json · PAYMENT-RESPONSE: success true, names a transaction.
  Dispute this purchase
2. 2026-10-24 03:32 UTC · delivered · no failure (delivered)settled (vet402 re-read the transfer on-chain in that chain's pinned settlement asset) · HTTP 200 · tx 0x3d0aeff7…4d22
  What vet402 recorded
  Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.The 402 terms vet402 paid: exact · 0.001 USDC · payTo 0x33d2…fa0d. Input sent: body none, query empty. The listing's maxTimeoutSeconds is 120. vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.001 USDC · payTo 0x33d2…fa0d · nonce 0x06f9…ddcd · validBefore not recorded.Answer to the paid request: HTTP 200 · Content-Type application/json · PAYMENT-RESPONSE: success true, names a transaction.
  Dispute this purchase
sift.srv1996466.hstgr.cloud/v1/linksGET
Latest attempt
2026-11-01 12:02 UTC
Result
delivered
Whose side
no failure (delivered)
Decision API now: asking… · the full answer
Latest L0 check (the 402 to an unpaid request): pass at 2026-11-09 04:40 UTC. Probes run oldest first, so there is no booked time. The next one usually comes by 2026-11-14 04:40 UTC (within 120 hours of the last).
What vet402 saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.The 402 terms vet402 paid: exact · 0.002 USDC · payTo 0x33d2…fa0d. Input sent: body none, query declared. The listing's maxTimeoutSeconds is 120. vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.002 USDC · payTo 0x33d2…fa0d · nonce 0xa903…96d4 · 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 re-read the transfer on-chain in that chain's pinned settlement asset) · HTTP 200 · tx 0x231ebafc…7a01In export.csv?days=9: the row with attempted_at 2026-11-01T12:02:31Z and resource_key sift.srv1996466.hstgr.cloud/v1/links.
After a fixNext purchase by vet402: The regular sweep can pick this listing again since 2026-11-07 12:02 UTC (a listing is bought at most once every 6 days). When it does depends on the daily budget and the order of demand, so there is no booked date.Email me when this result changes Dispute this purchaseA dispute does not start a purchase. The signed dispute route runs one fresh L0 check, an unpaid request.
sift.srv1996466.hstgr.cloud/v1/metadataGET
Latest attempt
2026-10-31 00:02 UTC
Result
delivered
Whose side
no failure (delivered)
Decision API now: · the full answer
Latest L0 check (the 402 to an unpaid request): pass at 2026-11-08 16:40 UTC. Probes run oldest first, so there is no booked time. The next one usually comes by 2026-11-13 16:40 UTC (within 120 hours of the last).
What vet402 saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.The 402 terms vet402 paid: exact · 0.002 USDC · payTo 0x33d2…fa0d. Input sent: body none, query declared. The listing's maxTimeoutSeconds is 120. vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.002 USDC · payTo 0x33d2…fa0d · nonce 0x82a0…9ff5 · 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 re-read the transfer on-chain in that chain's pinned settlement asset) · HTTP 200 · tx 0xf2a88097…373cIn export.csv?days=11: the row with attempted_at 2026-10-31T00:02:35Z and resource_key sift.srv1996466.hstgr.cloud/v1/metadata.
After a fixNext purchase by vet402: The regular sweep can pick this listing again since 2026-11-06 00:02 UTC (a listing is bought at most once every 6 days). When it does depends on the daily budget and the order of demand, so there is no booked date.Email me when this result changes Dispute this purchaseA dispute does not start a purchase. The signed dispute route runs one fresh L0 check, an unpaid request.
sift.srv1996466.hstgr.cloud/v1/crypto/tokenGET
Latest attempt
2026-10-30 21:32 UTC
Result
delivered
Whose side
no failure (delivered)
Decision API now: · the full answer
Latest L0 check (the 402 to an unpaid request): pass at 2026-11-07 22:40 UTC. Probes run oldest first, so there is no booked time. The next one usually comes by 2026-11-12 22:40 UTC (within 120 hours of the last).
What vet402 saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.The 402 terms vet402 paid: exact · 0.002 USDC · payTo 0x33d2…fa0d. Input sent: body none, query declared. The listing's maxTimeoutSeconds is 120. vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.002 USDC · payTo 0x33d2…fa0d · nonce 0x714d…4660 · 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 re-read the transfer on-chain in that chain's pinned settlement asset) · HTTP 200 · tx 0xdf4e40b3…a6c5In export.csv?days=11: the row with attempted_at 2026-10-30T21:32:23Z and resource_key sift.srv1996466.hstgr.cloud/v1/crypto/token.
After a fixNext purchase by vet402: The regular sweep can pick this listing again since 2026-11-05 21:32 UTC (a listing is bought at most once every 6 days). When it does depends on the daily budget and the order of demand, so there is no booked date.Email me when this result changes Dispute this purchaseA dispute does not start a purchase. The signed dispute route runs one fresh L0 check, an unpaid request.
Earlier attempts
1. 2026-10-24 06:01 UTC · delivered · no failure (delivered)settled (vet402 re-read the transfer on-chain in that chain's pinned settlement asset) · HTTP 200 · tx 0x141ef746…a2ac
  What vet402 recorded
  Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.The 402 terms vet402 paid: exact · 0.002 USDC · payTo 0x33d2…fa0d. Input sent: body none, query declared. The listing's maxTimeoutSeconds is 120. vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.002 USDC · payTo 0x33d2…fa0d · nonce 0x02d7…33f3 · validBefore not recorded.Answer to the paid request: HTTP 200 · Content-Type application/json · PAYMENT-RESPONSE: success true, names a transaction.
  Dispute this purchase
sift.srv1996466.hstgr.cloud/v1/sitemapGET
Latest attempt
2026-10-30 09:32 UTC
Result
delivered
Whose side
no failure (delivered)
Decision API now: · the full answer
Latest L0 check (the 402 to an unpaid request): pass at 2026-11-09 04:40 UTC. Probes run oldest first, so there is no booked time. The next one usually comes by 2026-11-14 04:40 UTC (within 120 hours of the last).
What vet402 saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.The 402 terms vet402 paid: exact · 0.003 USDC · payTo 0x33d2…fa0d. Input sent: body none, query declared. The listing's maxTimeoutSeconds is 120. vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.003 USDC · payTo 0x33d2…fa0d · nonce 0xfde8…b186 · 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 re-read the transfer on-chain in that chain's pinned settlement asset) · HTTP 200 · tx 0x603bb61c…a094In export.csv?days=12: the row with attempted_at 2026-10-30T09:32:11Z and resource_key sift.srv1996466.hstgr.cloud/v1/sitemap.
After a fixNext purchase by vet402: The regular sweep can pick this listing again since 2026-11-05 09:32 UTC (a listing is bought at most once every 6 days). When it does depends on the daily budget and the order of demand, so there is no booked date.Email me when this result changes Dispute this purchaseA dispute does not start a purchase. The signed dispute route runs one fresh L0 check, an unpaid request.
sift.srv1996466.hstgr.cloud/v1/crypto/ensGET
Latest attempt
2026-10-29 18:02 UTC
Result
delivered
Whose side
no failure (delivered)
Decision API now: · the full answer
Latest L0 check (the 402 to an unpaid request): pass at 2026-11-07 16:40 UTC. Probes run oldest first, so there is no booked time. The next one usually comes by 2026-11-12 16:40 UTC (within 120 hours of the last).
What vet402 saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.The 402 terms vet402 paid: exact · 0.001 USDC · payTo 0x33d2…fa0d. Input sent: body none, query declared. The listing's maxTimeoutSeconds is 120. vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.001 USDC · payTo 0x33d2…fa0d · nonce 0x1533…d191 · 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 re-read the transfer on-chain in that chain's pinned settlement asset) · HTTP 200 · tx 0xe67cda91…bb01In export.csv?days=12: the row with attempted_at 2026-10-29T18:02:11Z and resource_key sift.srv1996466.hstgr.cloud/v1/crypto/ens.
After a fixNext purchase by vet402: The regular sweep can pick this listing again since 2026-11-04 18:02 UTC (a listing is bought at most once every 6 days). When it does depends on the daily budget and the order of demand, so there is no booked date.Email me when this result changes Dispute this purchaseA dispute does not start a purchase. The signed dispute route runs one fresh L0 check, an unpaid request.
Earlier attempts
1. 2026-10-19 12:02 UTC · delivered · no failure (delivered) [census]settled (vet402 re-read the transfer on-chain in that chain's pinned settlement asset) · HTTP 200 · tx 0xbf6bcc5a…352b · bought by the census
  What vet402 recorded
  Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.The 402 terms vet402 paid: exact · 0.001 USDC · payTo 0x33d2…fa0d. Input sent: body none, query declared. The listing's maxTimeoutSeconds is 120. vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.001 USDC · payTo 0x33d2…fa0d · nonce 0xfcfe…5f2e · validBefore not recorded.Answer to the paid request: HTTP 200 · Content-Type application/json · PAYMENT-RESPONSE: success true, names a transaction.
  Dispute this purchase
sift.srv1996466.hstgr.cloud/v1/crypto/txGET
Latest attempt
2026-10-29 18:02 UTC
Result
delivered
Whose side
no failure (delivered)
Decision API now: · the full answer
Latest L0 check (the 402 to an unpaid request): pass at 2026-11-07 16:40 UTC. Probes run oldest first, so there is no booked time. The next one usually comes by 2026-11-12 16:40 UTC (within 120 hours of the last).
What vet402 saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.The 402 terms vet402 paid: exact · 0.002 USDC · payTo 0x33d2…fa0d. Input sent: body none, query declared. The listing's maxTimeoutSeconds is 120. vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.002 USDC · payTo 0x33d2…fa0d · nonce 0xe45b…567d · 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 re-read the transfer on-chain in that chain's pinned settlement asset) · HTTP 200 · tx 0x31a83f3e…8d89In export.csv?days=12: the row with attempted_at 2026-10-29T18:02:07Z and resource_key sift.srv1996466.hstgr.cloud/v1/crypto/tx.
After a fixNext purchase by vet402: The regular sweep can pick this listing again since 2026-11-04 18:02 UTC (a listing is bought at most once every 6 days). When it does depends on the daily budget and the order of demand, so there is no booked date.Email me when this result changes Dispute this purchaseA dispute does not start a purchase. The signed dispute route runs one fresh L0 check, an unpaid request.
Earlier attempts
1. 2026-10-21 03:33 UTC · delivered · no failure (delivered)settled (vet402 re-read the transfer on-chain in that chain's pinned settlement asset) · HTTP 200 · tx 0xc8688474…992c
  What vet402 recorded
  Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.The 402 terms vet402 paid: exact · 0.002 USDC · payTo 0x33d2…fa0d. Input sent: body none, query declared. The listing's maxTimeoutSeconds is 120. vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.002 USDC · payTo 0x33d2…fa0d · nonce 0x1b1c…fa81 · validBefore not recorded.Answer to the paid request: HTTP 200 · Content-Type application/json · PAYMENT-RESPONSE: success true, names a transaction.
  Dispute this purchase
sift.srv1996466.hstgr.cloud/v1/whoisGET
Latest attempt
2026-10-27 08:02 UTC
Result
delivered
Whose side
no failure (delivered)
Decision API now: · the full answer
Latest L0 check (the 402 to an unpaid request): pass at 2026-11-07 22:40 UTC. Probes run oldest first, so there is no booked time. The next one usually comes by 2026-11-12 22:40 UTC (within 120 hours of the last).
What vet402 saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.The 402 terms vet402 paid: exact · 0.003 USDC · payTo 0x33d2…fa0d. Input sent: body none, query declared. The listing's maxTimeoutSeconds is 120. vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.003 USDC · payTo 0x33d2…fa0d · nonce 0x240c…3477 · 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 re-read the transfer on-chain in that chain's pinned settlement asset) · HTTP 200 · tx 0xfe130cbd…eafbIn export.csv?days=15: the row with attempted_at 2026-10-27T08:02:29Z and resource_key sift.srv1996466.hstgr.cloud/v1/whois.
After a fixNext purchase by vet402: The regular sweep can pick this listing again since 2026-11-02 08:02 UTC (a listing is bought at most once every 6 days). When it does depends on the daily budget and the order of demand, so there is no booked date.Email me when this result changes Dispute this purchaseA dispute does not start a purchase. The signed dispute route runs one fresh L0 check, an unpaid request.
sift.srv1996466.hstgr.cloud/v1/email-checkGET
Latest attempt
2026-10-27 08:02 UTC
Result
delivered
Whose side
no failure (delivered)
Decision API now: · the full answer
Latest L0 check (the 402 to an unpaid request): pass at 2026-11-08 16:40 UTC. Probes run oldest first, so there is no booked time. The next one usually comes by 2026-11-13 16:40 UTC (within 120 hours of the last).
What vet402 saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.The 402 terms vet402 paid: exact · 0.002 USDC · payTo 0x33d2…fa0d. Input sent: body none, query declared. The listing's maxTimeoutSeconds is 120. vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.002 USDC · payTo 0x33d2…fa0d · nonce 0x9b2c…2803 · 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 re-read the transfer on-chain in that chain's pinned settlement asset) · HTTP 200 · tx 0x9d07d72f…31c8In export.csv?days=15: the row with attempted_at 2026-10-27T08:02:00Z and resource_key sift.srv1996466.hstgr.cloud/v1/email-check.
After a fixNext purchase by vet402: The regular sweep can pick this listing again since 2026-11-02 08:02 UTC (a listing is bought at most once every 6 days). When it does depends on the daily budget and the order of demand, so there is no booked date.Email me when this result changes Dispute this purchaseA dispute does not start a purchase. The signed dispute route runs one fresh L0 check, an unpaid request.
sift.srv1996466.hstgr.cloud/v1/feedsGET
Latest attempt
2026-10-27 05:32 UTC
Result
delivered
Whose side
no failure (delivered)
Decision API now: · the full answer
Latest L0 check (the 402 to an unpaid request): pass at 2026-11-07 16:40 UTC. Probes run oldest first, so there is no booked time. The next one usually comes by 2026-11-12 16:40 UTC (within 120 hours of the last).
What vet402 saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.The 402 terms vet402 paid: exact · 0.002 USDC · payTo 0x33d2…fa0d. Input sent: body none, query declared. The listing's maxTimeoutSeconds is 120. vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.002 USDC · payTo 0x33d2…fa0d · nonce 0x4cad…23d5 · 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 re-read the transfer on-chain in that chain's pinned settlement asset) · HTTP 200 · tx 0xaced5200…068fIn export.csv?days=15: the row with attempted_at 2026-10-27T05:32:27Z and resource_key sift.srv1996466.hstgr.cloud/v1/feeds.
After a fixNext purchase by vet402: The regular sweep can pick this listing again since 2026-11-02 05:32 UTC (a listing is bought at most once every 6 days). When it does depends on the daily budget and the order of demand, so there is no booked date.Email me when this result changes Dispute this purchaseA dispute does not start a purchase. The signed dispute route runs one fresh L0 check, an unpaid request.
sift.srv1996466.hstgr.cloud/v1/geo/inspectGET
Latest attempt
2026-10-21 03:33 UTC
Result
delivered
Whose side
no failure (delivered)
Decision API now: · the full answer
Latest L0 check (the 402 to an unpaid request): pass at 2026-11-07 16:40 UTC. Probes run oldest first, so there is no booked time. The next one usually comes by 2026-11-12 16:40 UTC (within 120 hours of the last).
What vet402 saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.The 402 terms vet402 paid: exact · 0.005 USDC · payTo 0x33d2…fa0d. Input sent: body none, query declared. The listing's maxTimeoutSeconds is 120. vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.005 USDC · payTo 0x33d2…fa0d · nonce 0x6c3f…085f · 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 re-read the transfer on-chain in that chain's pinned settlement asset) · HTTP 200 · tx 0x4170b8d3…b75bIn export.csv?days=21: the row with attempted_at 2026-10-21T03:33:08Z and resource_key sift.srv1996466.hstgr.cloud/v1/geo/inspect.
After a fixNext purchase by vet402: The regular sweep can pick this listing again since 2026-10-27 03:33 UTC (a listing is bought at most once every 6 days). When it does depends on the daily budget and the order of demand, so there is no booked date.Email me when this result changes Dispute this purchaseA dispute does not start a purchase. The signed dispute route runs one fresh L0 check, an unpaid request.
sift.srv1996466.hstgr.cloud/v1/ocrGET
Latest attempt
2026-10-21 03:33 UTC
Result
delivered
Whose side
no failure (delivered)
Decision API now: · the full answer
Latest L0 check (the 402 to an unpaid request): pass at 2026-11-07 16:40 UTC. Probes run oldest first, so there is no booked time. The next one usually comes by 2026-11-12 16:40 UTC (within 120 hours of the last).
What vet402 saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.The 402 terms vet402 paid: exact · 0.004 USDC · payTo 0x33d2…fa0d. Input sent: body none, query declared. The listing's maxTimeoutSeconds is 150. vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.004 USDC · payTo 0x33d2…fa0d · nonce 0xaaa6…898f · 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 re-read the transfer on-chain in that chain's pinned settlement asset) · HTTP 200 · tx 0x0ce95b23…cf27In export.csv?days=21: the row with attempted_at 2026-10-21T03:33:07Z and resource_key sift.srv1996466.hstgr.cloud/v1/ocr.
After a fixNext purchase by vet402: The regular sweep can pick this listing again since 2026-10-27 03:33 UTC (a listing is bought at most once every 6 days). When it does depends on the daily budget and the order of demand, so there is no booked date.Email me when this result changes Dispute this purchaseA dispute does not start a purchase. The signed dispute route runs one fresh L0 check, an unpaid request.
sift.srv1996466.hstgr.cloud/v1/askGET
Latest attempt
2026-10-21 03:33 UTC
Result
delivered
Whose side
no failure (delivered)
Decision API now: · the full answer
Latest L0 check (the 402 to an unpaid request): pass at 2026-11-07 16:40 UTC. Probes run oldest first, so there is no booked time. The next one usually comes by 2026-11-12 16:40 UTC (within 120 hours of the last).
What vet402 saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.The 402 terms vet402 paid: exact · 0.01 USDC · payTo 0x33d2…fa0d. Input sent: body none, query declared. The listing's maxTimeoutSeconds is 120. vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.01 USDC · payTo 0x33d2…fa0d · nonce 0xe504…3734 · 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 re-read the transfer on-chain in that chain's pinned settlement asset) · HTTP 200 · tx 0x104de526…2197In export.csv?days=21: the row with attempted_at 2026-10-21T03:33:05Z and resource_key sift.srv1996466.hstgr.cloud/v1/ask.
After a fixNext purchase by vet402: The regular sweep can pick this listing again since 2026-10-27 03:33 UTC (a listing is bought at most once every 6 days). When it does depends on the daily budget and the order of demand, so there is no booked date.Email me when this result changes Dispute this purchaseA dispute does not start a purchase. The signed dispute route runs one fresh L0 check, an unpaid request.
sift.srv1996466.hstgr.cloud/v1/techGET
Latest attempt
2026-10-21 03:33 UTC
Result
delivered
Whose side
no failure (delivered)
Decision API now: · the full answer
Latest L0 check (the 402 to an unpaid request): pass at 2026-11-07 16:40 UTC. Probes run oldest first, so there is no booked time. The next one usually comes by 2026-11-12 16:40 UTC (within 120 hours of the last).
What vet402 saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.The 402 terms vet402 paid: exact · 0.003 USDC · payTo 0x33d2…fa0d. Input sent: body none, query declared. The listing's maxTimeoutSeconds is 120. vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.003 USDC · payTo 0x33d2…fa0d · nonce 0xa2b3…4288 · 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 re-read the transfer on-chain in that chain's pinned settlement asset) · HTTP 200 · tx 0x26eed253…85a1In export.csv?days=21: the row with attempted_at 2026-10-21T03:33:01Z and resource_key sift.srv1996466.hstgr.cloud/v1/tech.
After a fixNext purchase by vet402: The regular sweep can pick this listing again since 2026-10-27 03:33 UTC (a listing is bought at most once every 6 days). When it does depends on the daily budget and the order of demand, so there is no booked date.Email me when this result changes Dispute this purchaseA dispute does not start a purchase. The signed dispute route runs one fresh L0 check, an unpaid request.
sift.srv1996466.hstgr.cloud/v1/audio-notesGET
Latest attempt
not tried on Base yet
Result
not tried on Base yet
Whose side
not tried on Base yet
Decision API now: · the full answer
Latest L0 check (the 402 to an unpaid request): none yet. Listings never probed go near the front of the daily L0 run. Not probed is not a failure.
No Base purchase is on this listing.
After a fixEmail me when this result changes Dispute this recordA dispute does not start a purchase. The signed dispute route runs one fresh L0 check, an unpaid request.
sift.srv1996466.hstgr.cloud/v1/audio/analyzeGET
Latest attempt
not tried on Base yet
Result
not tried on Base yet
Whose side
not tried on Base yet
Decision API now: · the full answer
Latest L0 check (the 402 to an unpaid request): pass at 2026-10-19 10:30 UTC. The next probe is due. Probes run oldest first, so there is no booked time.
No Base purchase is on this listing.
After a fixEmail me when this result changes Dispute this recordA dispute does not start a purchase. The signed dispute route runs one fresh L0 check, an unpaid request.
sift.srv1996466.hstgr.cloud/v1/audio/normalizeGET
Latest attempt
not tried on Base yet
Result
not tried on Base yet
Whose side
not tried on Base yet
Decision API now: · the full answer
Latest L0 check (the 402 to an unpaid request): pass at 2026-11-07 13:40 UTC. Probes run oldest first, so there is no booked time. The next one usually comes by 2026-11-12 13:40 UTC (within 120 hours of the last).
No Base purchase is on this listing.
After a fixEmail me when this result changes Dispute this recordA dispute does not start a purchase. The signed dispute route runs one fresh L0 check, an unpaid request.
sift.srv1996466.hstgr.cloud/v1/classifyGET
Latest attempt
not tried on Base yet
Result
not tried on Base yet
Whose side
not tried on Base yet
Decision API now: · the full answer
Latest L0 check (the 402 to an unpaid request): pass at 2026-10-20 10:30 UTC. The next probe is due. Probes run oldest first, so there is no booked time.
No Base purchase is on this listing.
After a fixEmail me when this result changes Dispute this recordA dispute does not start a purchase. The signed dispute route runs one fresh L0 check, an unpaid request.
sift.srv1996466.hstgr.cloud/v1/crypto/balanceGET
Latest attempt
not tried on Base yet
Result
not tried on Base yet
Whose side
not tried on Base yet
Decision API now: · the full answer
Latest L0 check (the 402 to an unpaid request): pass at 2026-10-19 10:30 UTC. The next probe is due. Probes run oldest first, so there is no booked time.
No Base purchase is on this listing.
After a fixEmail me when this result changes Dispute this recordA dispute does not start a purchase. The signed dispute route runs one fresh L0 check, an unpaid request.
sift.srv1996466.hstgr.cloud/v1/crypto/contractGET
Latest attempt
not tried on Base yet
Result
not tried on Base yet
Whose side
not tried on Base yet
Decision API now: · the full answer
Latest L0 check (the 402 to an unpaid request): pass at 2026-10-20 10:30 UTC. The next probe is due. Probes run oldest first, so there is no booked time.
No Base purchase is on this listing.
After a fixEmail me when this result changes Dispute this recordA dispute does not start a purchase. The signed dispute route runs one fresh L0 check, an unpaid request.
sift.srv1996466.hstgr.cloud/v1/crypto/token-riskGET
Latest attempt
not tried on Base yet
Result
not tried on Base yet
Whose side
not tried on Base yet
Decision API now: · the full answer
Latest L0 check (the 402 to an unpaid request): pass at 2026-10-20 10:30 UTC. The next probe is due. Probes run oldest first, so there is no booked time.
No Base purchase is on this listing.
After a fixEmail me when this result changes Dispute this recordA dispute does not start a purchase. The signed dispute route runs one fresh L0 check, an unpaid request.
sift.srv1996466.hstgr.cloud/v1/dmarc/inspectGET
Latest attempt
not tried on Base yet
Result
not tried on Base yet
Whose side
not tried on Base yet
Decision API now: · the full answer
Latest L0 check (the 402 to an unpaid request): pass at 2026-10-19 10:30 UTC. The next probe is due. Probes run oldest first, so there is no booked time.
No Base purchase is on this listing.
After a fixEmail me when this result changes Dispute this recordA dispute does not start a purchase. The signed dispute route runs one fresh L0 check, an unpaid request.
sift.srv1996466.hstgr.cloud/v1/dmarc/parseGET
Latest attempt
not tried on Base yet
Result
not tried on Base yet
Whose side
not tried on Base yet
Decision API now: · the full answer
Latest L0 check (the 402 to an unpaid request): pass at 2026-10-19 10:30 UTC. The next probe is due. Probes run oldest first, so there is no booked time.
No Base purchase is on this listing.
After a fixEmail me when this result changes Dispute this recordA dispute does not start a purchase. The signed dispute route runs one fresh L0 check, an unpaid request.
sift.srv1996466.hstgr.cloud/v1/doc-to-markdownGET
Latest attempt
not tried on Base yet
Result
not tried on Base yet
Whose side
not tried on Base yet
Decision API now: · the full answer
Latest L0 check (the 402 to an unpaid request): pass at 2026-10-19 10:30 UTC. The next probe is due. Probes run oldest first, so there is no booked time.
No Base purchase is on this listing.
After a fixEmail me when this result changes Dispute this recordA dispute does not start a purchase. The signed dispute route runs one fresh L0 check, an unpaid request.
sift.srv1996466.hstgr.cloud/v1/extractGET
Latest attempt
not tried on Base yet
Result
not tried on Base yet
Whose side
not tried on Base yet
Decision API now: · the full answer
Latest L0 check (the 402 to an unpaid request): pass at 2026-11-07 16:40 UTC. Probes run oldest first, so there is no booked time. The next one usually comes by 2026-11-12 16:40 UTC (within 120 hours of the last).
No Base purchase is on this listing.
After a fixEmail me when this result changes Dispute this recordA dispute does not start a purchase. The signed dispute route runs one fresh L0 check, an unpaid request.
sift.srv1996466.hstgr.cloud/v1/fact-checkGET
Latest attempt
not tried on Base yet
Result
not tried on Base yet
Whose side
not tried on Base yet
Decision API now: · the full answer
Latest L0 check (the 402 to an unpaid request): none yet. Listings never probed go near the front of the daily L0 run. Not probed is not a failure.
No Base purchase is on this listing.
After a fixEmail me when this result changes Dispute this recordA dispute does not start a purchase. The signed dispute route runs one fresh L0 check, an unpaid request.
sift.srv1996466.hstgr.cloud/v1/fetchGET
Latest attempt
not tried on Base yet
Result
not tried on Base yet
Whose side
not tried on Base yet
Decision API now: · the full answer
Latest L0 check (the 402 to an unpaid request): pass at 2026-10-19 10:30 UTC. The next probe is due. Probes run oldest first, so there is no booked time.
No Base purchase is on this listing.
After a fixEmail me when this result changes Dispute this recordA dispute does not start a purchase. The signed dispute route runs one fresh L0 check, an unpaid request.
sift.srv1996466.hstgr.cloud/v1/geo/convertGET
Latest attempt
not tried on Base yet
Result
not tried on Base yet
Whose side
not tried on Base yet
Decision API now: · the full answer
Latest L0 check (the 402 to an unpaid request): pass at 2026-11-07 16:40 UTC. Probes run oldest first, so there is no booked time. The next one usually comes by 2026-11-12 16:40 UTC (within 120 hours of the last).
No Base purchase is on this listing.
After a fixEmail me when this result changes Dispute this recordA dispute does not start a purchase. The signed dispute route runs one fresh L0 check, an unpaid request.
sift.srv1996466.hstgr.cloud/v1/imageGET
Latest attempt
not tried on Base yet
Result
not tried on Base yet
Whose side
not tried on Base yet
Decision API now: · the full answer
Latest L0 check (the 402 to an unpaid request): pass at 2026-11-09 04:40 UTC. Probes run oldest first, so there is no booked time. The next one usually comes by 2026-11-14 04:40 UTC (within 120 hours of the last).
No Base purchase is on this listing.
After a fixEmail me when this result changes Dispute this recordA dispute does not start a purchase. The signed dispute route runs one fresh L0 check, an unpaid request.
sift.srv1996466.hstgr.cloud/v1/money/address-checkGET
Latest attempt
not tried on Base yet
Result
not tried on Base yet
Whose side
not tried on Base yet
Decision API now: · the full answer
Latest L0 check (the 402 to an unpaid request): none yet. Listings never probed go near the front of the daily L0 run. Not probed is not a failure.
No Base purchase is on this listing.
After a fixEmail me when this result changes Dispute this recordA dispute does not start a purchase. The signed dispute route runs one fresh L0 check, an unpaid request.
sift.srv1996466.hstgr.cloud/v1/money/approvalsGET
Latest attempt
not tried on Base yet
Result
not tried on Base yet
Whose side
not tried on Base yet
Decision API now: · the full answer
Latest L0 check (the 402 to an unpaid request): none yet. Listings never probed go near the front of the daily L0 run. Not probed is not a failure.
No Base purchase is on this listing.
After a fixEmail me when this result changes Dispute this recordA dispute does not start a purchase. The signed dispute route runs one fresh L0 check, an unpaid request.
sift.srv1996466.hstgr.cloud/v1/money/bridge-routesGET
Latest attempt
not tried on Base yet
Result
not tried on Base yet
Whose side
not tried on Base yet
Decision API now: · the full answer
Latest L0 check (the 402 to an unpaid request): none yet. Listings never probed go near the front of the daily L0 run. Not probed is not a failure.
No Base purchase is on this listing.
After a fixEmail me when this result changes Dispute this recordA dispute does not start a purchase. The signed dispute route runs one fresh L0 check, an unpaid request.
sift.srv1996466.hstgr.cloud/v1/money/busyGET
Latest attempt
not tried on Base yet
Result
not tried on Base yet
Whose side
not tried on Base yet
Decision API now: · the full answer
Latest L0 check (the 402 to an unpaid request): none yet. Listings never probed go near the front of the daily L0 run. Not probed is not a failure.
No Base purchase is on this listing.
After a fixEmail me when this result changes Dispute this recordA dispute does not start a purchase. The signed dispute route runs one fresh L0 check, an unpaid request.
sift.srv1996466.hstgr.cloud/v1/money/feesGET
Latest attempt
not tried on Base yet
Result
not tried on Base yet
Whose side
not tried on Base yet
Decision API now: · the full answer
Latest L0 check (the 402 to an unpaid request): none yet. Listings never probed go near the front of the daily L0 run. Not probed is not a failure.
No Base purchase is on this listing.
After a fixEmail me when this result changes Dispute this recordA dispute does not start a purchase. The signed dispute route runs one fresh L0 check, an unpaid request.
sift.srv1996466.hstgr.cloud/v1/money/walletGET
Latest attempt
not tried on Base yet
Result
not tried on Base yet
Whose side
not tried on Base yet
Decision API now: · the full answer
Latest L0 check (the 402 to an unpaid request): none yet. Listings never probed go near the front of the daily L0 run. Not probed is not a failure.
No Base purchase is on this listing.
After a fixEmail me when this result changes Dispute this recordA dispute does not start a purchase. The signed dispute route runs one fresh L0 check, an unpaid request.
sift.srv1996466.hstgr.cloud/v1/money/whereGET
Latest attempt
not tried on Base yet
Result
not tried on Base yet
Whose side
not tried on Base yet
Decision API now: · the full answer
Latest L0 check (the 402 to an unpaid request): none yet. Listings never probed go near the front of the daily L0 run. Not probed is not a failure.
No Base purchase is on this listing.
After a fixEmail me when this result changes Dispute this recordA dispute does not start a purchase. The signed dispute route runs one fresh L0 check, an unpaid request.
sift.srv1996466.hstgr.cloud/v1/newsGET
Latest attempt
not tried on Base yet
Result
not tried on Base yet
Whose side
not tried on Base yet
Decision API now: · the full answer
Latest L0 check (the 402 to an unpaid request): none yet. Listings never probed go near the front of the daily L0 run. Not probed is not a failure.
No Base purchase is on this listing.
After a fixEmail me when this result changes Dispute this recordA dispute does not start a purchase. The signed dispute route runs one fresh L0 check, an unpaid request.
sift.srv1996466.hstgr.cloud/v1/page-watchGET
Latest attempt
not tried on Base yet
Result
not tried on Base yet
Whose side
not tried on Base yet
Decision API now: · the full answer
Latest L0 check (the 402 to an unpaid request): none yet. Listings never probed go near the front of the daily L0 run. Not probed is not a failure.
No Base purchase is on this listing.
After a fixEmail me when this result changes Dispute this recordA dispute does not start a purchase. The signed dispute route runs one fresh L0 check, an unpaid request.
sift.srv1996466.hstgr.cloud/v1/pdfGET
Latest attempt
not tried on Base yet
Result
not tried on Base yet
Whose side
not tried on Base yet
Decision API now: · the full answer
Latest L0 check (the 402 to an unpaid request): pass at 2026-10-19 10:30 UTC. The next probe is due. Probes run oldest first, so there is no booked time.
No Base purchase is on this listing.
After a fixEmail me when this result changes Dispute this recordA dispute does not start a purchase. The signed dispute route runs one fresh L0 check, an unpaid request.
sift.srv1996466.hstgr.cloud/v1/roastGET
Latest attempt
not tried on Base yet
Result
not tried on Base yet
Whose side
not tried on Base yet
Decision API now: · the full answer
Latest L0 check (the 402 to an unpaid request): pass at 2026-10-20 10:30 UTC. The next probe is due. Probes run oldest first, so there is no booked time.
No Base purchase is on this listing.
After a fixEmail me when this result changes Dispute this recordA dispute does not start a purchase. The signed dispute route runs one fresh L0 check, an unpaid request.
sift.srv1996466.hstgr.cloud/v1/screenshotGET
Latest attempt
not tried on Base yet
Result
not tried on Base yet
Whose side
not tried on Base yet
Decision API now: · the full answer
Latest L0 check (the 402 to an unpaid request): pass at 2026-10-19 10:30 UTC. The next probe is due. Probes run oldest first, so there is no booked time.
No Base purchase is on this listing.
After a fixEmail me when this result changes Dispute this recordA dispute does not start a purchase. The signed dispute route runs one fresh L0 check, an unpaid request.
sift.srv1996466.hstgr.cloud/v1/searchGET
Latest attempt
not tried on Base yet
Result
not tried on Base yet
Whose side
not tried on Base yet
Decision API now: · the full answer
Latest L0 check (the 402 to an unpaid request): pass at 2026-11-07 16:40 UTC. Probes run oldest first, so there is no booked time. The next one usually comes by 2026-11-12 16:40 UTC (within 120 hours of the last).
No Base purchase is on this listing.
After a fixEmail me when this result changes Dispute this recordA dispute does not start a purchase. The signed dispute route runs one fresh L0 check, an unpaid request.
sift.srv1996466.hstgr.cloud/v1/site-checkGET
Latest attempt
not tried on Base yet
Result
not tried on Base yet
Whose side
not tried on Base yet
Decision API now: · the full answer
Latest L0 check (the 402 to an unpaid request): pass at 2026-10-19 10:30 UTC. The next probe is due. Probes run oldest first, so there is no booked time.
No Base purchase is on this listing.
After a fixEmail me when this result changes Dispute this recordA dispute does not start a purchase. The signed dispute route runs one fresh L0 check, an unpaid request.
sift.srv1996466.hstgr.cloud/v1/solana/token-riskGET
Latest attempt
not tried on Base yet
Result
not tried on Base yet
Whose side
not tried on Base yet
Decision API now: · the full answer
Latest L0 check (the 402 to an unpaid request): pass at 2026-11-09 04:40 UTC. Probes run oldest first, so there is no booked time. The next one usually comes by 2026-11-14 04:40 UTC (within 120 hours of the last).
No Base purchase is on this listing.
After a fixEmail me when this result changes Dispute this recordA dispute does not start a purchase. The signed dispute route runs one fresh L0 check, an unpaid request.
sift.srv1996466.hstgr.cloud/v1/solana/txGET
Latest attempt
not tried on Base yet
Result
not tried on Base yet
Whose side
not tried on Base yet
Decision API now: · the full answer
Latest L0 check (the 402 to an unpaid request): pass at 2026-11-08 16:40 UTC. Probes run oldest first, so there is no booked time. The next one usually comes by 2026-11-13 16:40 UTC (within 120 hours of the last).
No Base purchase is on this listing.
After a fixEmail me when this result changes Dispute this recordA dispute does not start a purchase. The signed dispute route runs one fresh L0 check, an unpaid request.
sift.srv1996466.hstgr.cloud/v1/summarizeGET
Latest attempt
not tried on Base yet
Result
not tried on Base yet
Whose side
not tried on Base yet
Decision API now: · the full answer
Latest L0 check (the 402 to an unpaid request): pass at 2026-10-19 10:30 UTC. The next probe is due. Probes run oldest first, so there is no booked time.
No Base purchase is on this listing.
After a fixEmail me when this result changes Dispute this recordA dispute does not start a purchase. The signed dispute route runs one fresh L0 check, an unpaid request.
sift.srv1996466.hstgr.cloud/v1/tablesGET
Latest attempt
not tried on Base yet
Result
not tried on Base yet
Whose side
not tried on Base yet
Decision API now: · the full answer
Latest L0 check (the 402 to an unpaid request): pass at 2026-10-19 10:30 UTC. The next probe is due. Probes run oldest first, so there is no booked time.
No Base purchase is on this listing.
After a fixEmail me when this result changes Dispute this recordA dispute does not start a purchase. The signed dispute route runs one fresh L0 check, an unpaid request.
sift.srv1996466.hstgr.cloud/v1/transcribeGET
Latest attempt
not tried on Base yet
Result
not tried on Base yet
Whose side
not tried on Base yet
Decision API now: · the full answer
Latest L0 check (the 402 to an unpaid request): pass at 2026-11-08 16:40 UTC. Probes run oldest first, so there is no booked time. The next one usually comes by 2026-11-13 16:40 UTC (within 120 hours of the last).
No Base purchase is on this listing.
After a fixEmail me when this result changes Dispute this recordA dispute does not start a purchase. The signed dispute route runs one fresh L0 check, an unpaid request.
sift.srv1996466.hstgr.cloud/v1/translateGET
Latest attempt
not tried on Base yet
Result
not tried on Base yet
Whose side
not tried on Base yet
Decision API now: · the full answer
Latest L0 check (the 402 to an unpaid request): pass at 2026-10-20 10:30 UTC. The next probe is due. Probes run oldest first, so there is no booked time.
No Base purchase is on this listing.
After a fixEmail me when this result changes Dispute this recordA dispute does not start a purchase. The signed dispute route runs one fresh L0 check, an unpaid request.
sift.srv1996466.hstgr.cloud/v1/ttsGET
Latest attempt
not tried on Base yet
Result
not tried on Base yet
Whose side
not tried on Base yet
Decision API now: · the full answer
Latest L0 check (the 402 to an unpaid request): pass at 2026-11-09 04:40 UTC. Probes run oldest first, so there is no booked time. The next one usually comes by 2026-11-14 04:40 UTC (within 120 hours of the last).
No Base purchase is on this listing.
After a fixEmail me when this result changes Dispute this recordA dispute does not start a purchase. The signed dispute route runs one fresh L0 check, an unpaid request.

2.How to read this

Each listing shows its latest Base attempt and up to four earlier Base attempts. Result and Whose side follow that Base attempt. A purchase on another chain is listed under Other chains, with the chain name, time, status, HTTP status, and a transaction link when one was recorded. The record page shows that purchase in the Payment chain column. A row where vet402 signed a payment and sent the paid request is an L1 result: “Recorded (L1 paid purchase)” when the payment settled on-chain, and “signed, not settled on-chain” when it did not. 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 “attribution under review” while that review runs. The review has no set date. 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 when the purchase is on Base. “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 reads the same sorting as this page: a failure counts against the seller only when this page puts it on the seller's side. A paid attempt that took payment and did not deliver is a WARN, and two or more of them on the seller's side since the last delivery are the only way a failed purchase makes it a BLOCK; a listing whose failures this page leaves not sorted gets at most a WARN from them. An L0 check that is unverified (not probed yet, or not measurable) is a WARN, not a BLOCK. The codes that decided the answer come first, each with the meaning from the reason-code table (reason codes). “After a fix” gives the earliest date vet402's regular sweep can buy the listing again, where the rules let it be worked out, and the links to be told of a change or to dispute a row. 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. The time filled in is the latest Base attempt when that listing has a Base purchase. Say what you saw instead. The row is not deleted on dispute; a correction is published with the same weight.