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

mcpfax-intel.bowling-anthony.workers.dev: x402 purchase results on Base, latest attempt 2026-09-15

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

Latest attempt: 2026-09-15 23:51 UTC. This page read the ledger at 2026-09-29 07:11 UTC and reuses that read for up to 5 min.

1.Your listings

  1. mcpfax-intel.bowling-anthony.workers.dev/moversGET
    Latest attempt
    2026-09-15 23:51 UTC
    Result
    Refused, and no payment was taken
    Whose side
    not sorted: no charge
    What we saw: vet402 signed the payment and the paid request got a 4xx other than 402, with no settlement receipt and no transaction on the row. No money moved, and vet402 cannot rule out that its own request was the problem (held_reason unsettled_4xx), so this page does not count the row as the seller's fault. Since 2026-09-16 23:25 UTC vet402 sends the request body the seller's 402 declares (an empty JSON body when it declares none), and since 2026-09-27 23:27 UTC it adds the query parameters the seller's 402 declares on Base.Last result about the seller: none among the attempts shown. The latest attempt is not sorted; vet402 has not bought this listing again since.The 402 terms vet402 signed: vet402 signed: exact · 0.01 USDC · payTo 0x1831…ebbd. Input sent: body not recorded, query not recorded. The listing's maxTimeoutSeconds is 120; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.01 USDC · payTo 0x1831…ebbd · nonce 0x7d66…821f · validBefore not recorded.Answer to the paid request: HTTP 404 · Content-Type application/json; charset=utf-8 · no PAYMENT-RESPONSE recorded.What to fix: This page does not count it as the seller's fault. If the request was meant to succeed, declare the input in the listing (body or query) with example values that work as written.Decision API now: asking… · the full answerRecorded (L1 paid purchase): settle_failed (vet402 signed a payment and got no settlement receipt back) · HTTP 404 · 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-15T23:51:12Z and resource_key mcpfax-intel.bowling-anthony.workers.dev/movers.Dispute this purchaseEmail me when this result changes
    Earlier attempts
    1. 2026-09-09 19:00 UTC · Refused, and no payment was taken · not sorted: no chargesettle_failed (vet402 signed a payment and got no settlement receipt back) · HTTP 404 · no tx · held as unsettled_4xx (the paid request got a 4xx with no settlement receipt and no transaction)
      What vet402 recordedvet402 signed the payment and the paid request got a 4xx other than 402, with no settlement receipt and no transaction on the row. No money moved, and vet402 cannot rule out that its own request was the problem (held_reason unsettled_4xx), so this page does not count the row as the seller's fault. Since 2026-09-16 23:25 UTC vet402 sends the request body the seller's 402 declares (an empty JSON body when it declares none), and since 2026-09-27 23:27 UTC it adds the query parameters the seller's 402 declares on Base.The 402 terms vet402 signed: vet402 signed: exact · 0.01 USDC · payTo 0x1831…ebbd. Input sent: body not recorded, query not recorded. The listing's maxTimeoutSeconds is 120; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.01 USDC · payTo 0x1831…ebbd · nonce 0x2139…66dc · validBefore not recorded.Answer to the paid request: HTTP 404 · Content-Type application/json; charset=utf-8 · no PAYMENT-RESPONSE recorded.
      Dispute this purchase
  2. mcpfax-intel.bowling-anthony.workers.dev/category-demandGET
    Latest attempt
    2026-09-14 18:00 UTC
    Result
    vet402's wallet was out of USDC
    Whose side
    vet402's side
    What we saw: Between 2026-09-13 00:00 and 2026-09-15 23:49 UTC, vet402's Base payer wallet had run out of USDC. The seller refused a payment that had nothing behind it (402 or 5xx).Last result about the seller: delivered on 2026-09-05 07:01 UTC. The latest attempt failed on vet402's side; vet402 has not bought this listing again since.The 402 terms vet402 signed: vet402 signed: exact · 0.005 USDC · payTo 0x1831…ebbd. Input sent: body not recorded, query not recorded. The listing's maxTimeoutSeconds is 120; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.005 USDC · payTo 0x1831…ebbd · nonce 0x2e52…e2de · validBefore not recorded.Answer to the paid request: HTTP 402 · Content-Type application/json; charset=utf-8 · no PAYMENT-RESPONSE recorded.What to fix: Nothing for the seller to fix.Decision API now: asking… · the full answerThis failure was on vet402's side, not the seller's.Recorded (L1 paid purchase): settle_failed (vet402 signed a payment and got no settlement receipt back) · HTTP 402 · no tx · held as payer_unfunded (a 402 or 5xx while vet402's Base wallet was out of USDC (2026-09-13 to 2026-09-15))In export.csv?days=16: the row with attempted_at 2026-09-14T18:00:54Z and resource_key mcpfax-intel.bowling-anthony.workers.dev/category-demand.Dispute this purchaseEmail me when this result changes
    Earlier attempts
    1. 2026-09-05 07:01 UTC · delivered · no failure (delivered)settled (vet402 confirmed the USDC transfer on-chain) · HTTP 200 · tx 0x61ec1b76…a032
      What vet402 recordedPaid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.The 402 terms vet402 paid: vet402 signed: exact · 0.005 USDC · payTo 0x1831…ebbd. Input sent: body not recorded, query not recorded. The listing's maxTimeoutSeconds is 120; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.005 USDC · payTo 0x1831…ebbd · nonce 0xc714…b235 · validBefore not recorded.Answer to the paid request: HTTP 200 · Content-Type application/json; charset=utf-8 · PAYMENT-RESPONSE: success true, names a transaction.
      Dispute this purchase
  3. mcpfax-intel.bowling-anthony.workers.dev/trendingGET
    Latest attempt
    2026-09-14 06: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: delivered on 2026-09-05 01:02 UTC. The latest attempt failed on vet402's side; vet402 has not bought this listing again since.The 402 terms vet402 signed: vet402 signed: exact · 0.01 USDC · payTo 0x1831…ebbd. Input sent: body not recorded, query not recorded. The listing's maxTimeoutSeconds is 120; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.01 USDC · payTo 0x1831…ebbd · nonce 0xee47…8aa9 · validBefore not recorded.Answer to the paid request: HTTP 402 · Content-Type application/json; charset=utf-8 · no PAYMENT-RESPONSE recorded.What to fix: Nothing for the seller to fix.Decision API now: · the full answerThis failure was on vet402's side, not the seller's.Recorded (L1 paid purchase): settle_failed (vet402 signed a payment and got no settlement receipt back) · HTTP 402 · no tx · held as payer_unfunded (a 402 or 5xx while vet402's Base wallet was out of USDC (2026-09-13 to 2026-09-15))In export.csv?days=17: the row with attempted_at 2026-09-14T06:01:15Z and resource_key mcpfax-intel.bowling-anthony.workers.dev/trending.Dispute this purchaseEmail me when this result changes
    Earlier attempts
    1. 2026-09-05 01:02 UTC · delivered · no failure (delivered)settled (vet402 confirmed the USDC transfer on-chain) · HTTP 200 · tx 0x5131bf10…1717
      What vet402 recordedPaid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.The 402 terms vet402 paid: vet402 signed: exact · 0.01 USDC · payTo 0x1831…ebbd. Input sent: body not recorded, query not recorded. The listing's maxTimeoutSeconds is 120; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.01 USDC · payTo 0x1831…ebbd · nonce 0xdb70…ee93 · validBefore not recorded.Answer to the paid request: HTTP 200 · Content-Type application/json; charset=utf-8 · PAYMENT-RESPONSE: success true, names a transaction.
      Dispute this purchase
  4. mcpfax-intel.bowling-anthony.workers.dev/market-reportGET
    Latest attempt
    2026-09-11 18: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.01 USDC · payTo 0x1831…ebbd. Input sent: body not recorded, query not recorded. The listing's maxTimeoutSeconds is 120; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.01 USDC · payTo 0x1831…ebbd · nonce 0xba90…075b · validBefore not recorded.Answer to the paid request: HTTP 200 · Content-Type application/json; charset=utf-8 · PAYMENT-RESPONSE: success true, names a transaction.Decision API now: · the full answerRecorded (L1 paid purchase): settled (vet402 confirmed the USDC transfer on-chain) · HTTP 200 · tx 0x5cd4370a…b75bIn export.csv?days=19: the row with attempted_at 2026-09-11T18:00:17Z and resource_key mcpfax-intel.bowling-anthony.workers.dev/market-report.Dispute this purchaseEmail me when this result changes
  5. mcpfax-intel.bowling-anthony.workers.dev/new-entrantsGET
    Latest attempt
    not tried yet
    Result
    —
    Whose side
    —
    vet402 has not tried to buy this listing yet.Email me when this result changes

2.How to read this

Each listing shows its latest attempt on Base and up to four earlier ones. A row where vet402 signed a payment and sent the paid request is an L1 result (“Recorded (L1 paid purchase)”); a row where vet402 did not sign is marked “not bought” and is not an L1 result. The listing's record page also shows the L0 state (“Published state”), which checks that an unpaid request gets a valid 402, so a listing can pass L0 and still fail here. Whose side puts a failure on the seller's side when the row shows vet402 was not at fault: it signed on the listing's terms, its wallet held the price, it sent the declared input, and the seller answered explicitly or had its declared time. Even then, one such failure is “not sorted: one failure so far”: a failure goes on the seller's side only when the same listing has one on two different days (UTC), and those rows are marked “under re-check” while we re-check them. A row that cannot show all of that is “not sorted”, and so is a held row (held_reason in the export), a failure where no payment was taken (“no charge”), and a payment that settled before the seller refused an input vet402 had not sent. “Signed payment” and “Answer to the paid request” show what the row recorded, and nothing else: the answer's body and header values are not published. The maxTimeoutSeconds on a row is the listing's value today; a declared price or address on a not-bought row is the value recorded at the time of the attempt. The transaction link opens the settlement on Basescan. “Decision API now” is what the decision API (GET /api/v1/resources/{id}/decision?role=payer, no key) answers for the listing when you open this page; your browser asks it for the first 2 listings, and for the others when you ask. It is cautious for the payer: it leaves out the attempts that show vet402's fault, are held, or took no payment, and counts the rest, so it can say WARN or BLOCK for a listing whose failures this page leaves not sorted (API reference). Listings removed from the Bazaar, and listings whose catalog network is not Base, are not on this page. The fix-first page groups the same results across sellers (methodology).

3.Think a row is wrong?

Use “Dispute this purchase” on the row: it opens Dispute this record on the listing's record page with the purchase time filled in. Say what you saw instead. The row is not deleted on dispute; a correction is published with the same weight.