Skip to main content
vet402
Independent MeasurementSeller: purchase results on BaseRead from the database 2026-09-29 08:08 UTC · reused for up to 5 min
vet402Sellers · What to fix firstMethodology

agents.daedalusdevelopmentgroup.com: x402 purchase results on Base, latest attempt 2026-09-25

113 Base listings. Latest result about the seller at each listing: 1 delivered · 0 failed on the seller's side · 4 with no such result among the attempts shown · 108 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: 1 delivered · 0 failed on the seller's side · 0 on vet402's side · 4 not sorted (vet402 cannot show the failure was not its own) · 108 not tried yet.

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

1.Your listings

  1. agents.daedalusdevelopmentgroup.com/v1/test-runnerPOST
    Latest attempt
    not tried yet
    Result
    —
    Whose side
    —
    vet402 has not tried to buy this listing yet.
    After a fixEmail me when this result changes
  2. agents.daedalusdevelopmentgroup.com/v1/timestampPOST
    Latest attempt
    not tried yet
    Result
    —
    Whose side
    —
    vet402 has not tried to buy this listing yet.
    After a fixEmail me when this result changes
  3. agents.daedalusdevelopmentgroup.com/v1/tine-diff-explainPOST
    Latest attempt
    not tried yet
    Result
    —
    Whose side
    —
    vet402 has not tried to buy this listing yet.
    After a fixEmail me when this result changes
  4. agents.daedalusdevelopmentgroup.com/v1/tls-version-checkPOST
    Latest attempt
    not tried yet
    Result
    —
    Whose side
    —
    vet402 has not tried to buy this listing yet.
    After a fixEmail me when this result changes
  5. agents.daedalusdevelopmentgroup.com/v1/translatePOST
    Latest attempt
    not tried yet
    Result
    —
    Whose side
    —
    vet402 has not tried to buy this listing yet.
    After a fixEmail me when this result changes
  6. agents.daedalusdevelopmentgroup.com/v1/trust/checkPOST
    Latest attempt
    not tried yet
    Result
    —
    Whose side
    —
    vet402 has not tried to buy this listing yet.
    After a fixEmail me when this result changes
  7. agents.daedalusdevelopmentgroup.com/v1/trust/historyPOST
    Latest attempt
    not tried yet
    Result
    —
    Whose side
    —
    vet402 has not tried to buy this listing yet.
    After a fixEmail me when this result changes
  8. agents.daedalusdevelopmentgroup.com/v1/url-fetchPOST
    Latest attempt
    not tried yet
    Result
    —
    Whose side
    —
    vet402 has not tried to buy this listing yet.
    After a fixEmail me when this result changes
  9. agents.daedalusdevelopmentgroup.com/v1/url-statusPOST
    Latest attempt
    not tried yet
    Result
    —
    Whose side
    —
    vet402 has not tried to buy this listing yet.
    After a fixEmail me when this result changes
  10. agents.daedalusdevelopmentgroup.com/v1/uuid-generatePOST
    Latest attempt
    not tried yet
    Result
    —
    Whose side
    —
    vet402 has not tried to buy this listing yet.
    After a fixEmail me when this result changes
  11. agents.daedalusdevelopmentgroup.com/v1/wake/feedPOST
    Latest attempt
    not tried yet
    Result
    —
    Whose side
    —
    vet402 has not tried to buy this listing yet.
    After a fixEmail me when this result changes
  12. agents.daedalusdevelopmentgroup.com/v1/wake/schedulePOST
    Latest attempt
    not tried yet
    Result
    —
    Whose side
    —
    vet402 has not tried to buy this listing yet.
    After a fixEmail me when this result changes
  13. agents.daedalusdevelopmentgroup.com/v1/web-searchPOST
    Latest attempt
    not tried yet
    Result
    —
    Whose side
    —
    vet402 has not tried to buy this listing yet.
    After a fixEmail 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)” 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 “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. The codes that decided the answer come first, each with one sentence on what it means for that listing (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. Say what you saw instead. The row is not deleted on dispute; a correction is published with the same weight.