vet402 paid this seller 138 times with its own money (Algorand 138), most recently on 2026-09-28 (UTC). 120 with a settlement receipt; 120 came back with an answer.
It costs the seller nothing, and there is nothing to sign up for.
B grade B: comes back with an answer 75%+ of the time · Rank 8 of 24 on this page.
120 / 130 came back, of counted (92.3%)
0.86 to 0.96 95% interval
2026-09-28 last bought · 2 days counted
00.51
Came back, of counted, per chain: Algorand 120/130. Came back with an answer = vet402's payment settled, then the seller answered 2xx with a non-empty body. vet402 did not check that the answer is what the listing promised; whether its keys matched what the seller declared is a separate column.
Separate column, not in the grade. Answer matched what the seller declared: 99 of 120 checked.
Not counted
1vet402 or facilitator sidenot counted
payment tx rejected 1
7can't tellnot counted
timeout 5, request rejected 4xx 2
Counted against this seller
10seller sidecounted in the grade
server error 5xx 10
2026-09-28 01:48 UTC · Algorand · server error 5xx · HTTP 503
https://algorand.ottoai.services/mega-report
runner said: payment_failed · status 503, no settlement receipt
2026-09-28 01:48 UTC · Algorand · server error 5xx · HTTP 503
Is a row wrong? A seller who thinks a row is wrong opens a GitHub issue with the URL or tx. vet402 checks it against the chain and the raw result; a wrong row is fixed and the fix is noted in the change log.