Skip to main content
vet402
MenuClose
Independent MeasurementSeller: purchase results on BaseRead from the database 2026-11-09 14:56 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-09

58 Base listings. Latest result about the seller at each listing: 16 delivered · 0 failed on the seller's side · 0 with no such result among the attempts shown · 42 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: 16 delivered · 0 failed on the seller's side · 0 on vet402's side · 42 with no Base purchase.

Latest attempt: 2026-11-09 12:02 UTC. This page read the ledger at 2026-11-09 14:56 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

  1. sift.srv1996466.hstgr.cloud/v1/video/inspectGET
    Latest attempt
    not tried on Base yet
    Result
    not tried on Base yet
    Whose side
    not tried on Base yet
    Decision API now: asking… · 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 changesDispute this recordA dispute does not start a purchase. The signed dispute route runs one fresh L0 check, an unpaid request.
  2. sift.srv1996466.hstgr.cloud/v1/video/storyboardGET
    Latest attempt
    not tried on Base yet
    Result
    not tried on Base yet
    Whose side
    not tried on Base yet
    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).
    No Base purchase is on this listing.
    After a fixEmail me when this result changesDispute this recordA dispute does not start a purchase. The signed dispute route runs one fresh L0 check, an unpaid request.
  3. sift.srv1996466.hstgr.cloud/v1/x402-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 changesDispute this recordA dispute does not start a purchase. The signed dispute route runs one fresh L0 check, an unpaid request.
  4. sift.srv1996466.hstgr.cloud/v1/yt/check-subtitlesGET
    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-21 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 changesDispute this recordA dispute does not start a purchase. The signed dispute route runs one fresh L0 check, an unpaid request.
  5. sift.srv1996466.hstgr.cloud/v1/yt/metadataGET
    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 changesDispute this recordA dispute does not start a purchase. The signed dispute route runs one fresh L0 check, an unpaid request.
  6. sift.srv1996466.hstgr.cloud/v1/yt/scriptGET
    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 changesDispute this recordA dispute does not start a purchase. The signed dispute route runs one fresh L0 check, an unpaid request.
  7. sift.srv1996466.hstgr.cloud/v1/yt/thumbnail-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-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 changesDispute this recordA dispute does not start a purchase. The signed dispute route runs one fresh L0 check, an unpaid request.
  8. sift.srv1996466.hstgr.cloud/v1/yt/translate-subtitlesGET
    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 22:40 UTC. Probes run oldest first, so there is no booked time. The next one usually comes by 2026-11-13 22:40 UTC (within 120 hours of the last).
    No Base purchase is on this listing.
    After a fixEmail me when this result changesDispute 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.