api-production-36692.up.railway.app

Algorand

From vet402-algorand, a separate project; graded apart from Solana, Tempo and Base. Listed on the Algorand page.

vet402 paid this seller 2 times with its own money (Algorand 2), most recently on 2026-09-28 (UTC). 1 with a settlement receipt; 1 came back with an answer.

It costs the seller nothing, and there is nothing to sign up for.

… measuring · Measuring: a rank number needs 10 counted purchases on 2 different days; this seller has 1 on 1.

Came back, of counted, per chain: Algorand 1/1. 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: 1 of 1 checked.

Not counted

Counted against this seller

None.

How each failure is assigned

Recent purchases

Each tx links to a public explorer.

1. 2026-09-28 01:26 UTC · Algorand · can't tell: timeout
   https://api-production-36692.up.railway.app/metric/tinyman/tvl?fresh=false&basis=all_pools_usd_priced
2. 2026-09-27 04:39 UTC · Algorand · came back with an answer 3GFE3KI6…M5ZVZA
   https://api-production-36692.up.railway.app/metric/tinyman/tvl?fresh=false&basis=all_pools_usd_priced

Are you the seller?

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.

Tell vet402 a row is wrong (GitHub issue, prefilled)

Signed records of failed purchases are published only after the seller is told. More for sellers