oyapicks.app

Algorand

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

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

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

C grade C: comes back with an answer 50%+ of the time · Rank 22 of 24 on this page.

14 / 16
came back, of counted (87.5%)
0.64 to 0.97
95% interval
2026-09-28
last bought · 2 days counted
00.51

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

Not counted

0vet402 or facilitator side not counted
4can't tell not counted
request rejected 4xx 4

Counted against this seller

2seller side counted in the grade
server error 5xx 2
  1. 2026-09-28 01:36 UTC · Algorand · server error 5xx · HTTP 503
    https://oyapicks.app/api/x402/volume-spikes-algo
    runner said: payment_failed · status 503, no settlement receipt
  2. 2026-09-27 04:52 UTC · Algorand · server error 5xx · HTTP 503
    https://oyapicks.app/api/x402/volume-spikes-algo
    runner said: payment_failed · status 503, no settlement receipt

How each failure is assigned

Recent purchases

Each tx links to a public explorer.

  1. 2026-09-28 01:37 UTC · Algorand · came back with an answer HDAT6JGR…G72PIQ
    https://oyapicks.app/api/x402/arbitrage-algo
  2. 2026-09-28 01:36 UTC · Algorand · seller side: server error 5xx
    https://oyapicks.app/api/x402/volume-spikes-algo
  3. 2026-09-28 01:36 UTC · Algorand · came back with an answer 2XYUTLCR…ZNAZCQ
    https://oyapicks.app/api/x402/resolutions-algo
  4. 2026-09-28 01:35 UTC · Algorand · can't tell: request rejected 4xx
    https://oyapicks.app/api/x402/probability-history-algo?q=world+cup
  5. 2026-09-28 01:34 UTC · Algorand · came back with an answer 3JASKXBQ…4UMDQQ
    https://oyapicks.app/api/x402/new-markets-algo
  6. 2026-09-28 01:33 UTC · Algorand · came back with an answer AIXM7X2G…BY7PHQ
    https://oyapicks.app/api/x402/movers-algo
  7. 2026-09-28 01:32 UTC · Algorand · came back with an answer · answer not as declared J4QB43HX…FFRHHQ
    https://oyapicks.app/api/x402/alpha-book
  8. 2026-09-28 01:31 UTC · Algorand · came back with an answer RCICSFWK…RV37KQ
    https://oyapicks.app/api/x402/search-algo?q=world+cup
  9. 2026-09-28 01:29 UTC · Algorand · came back with an answer L4R3OJKK…JTCLDA
    https://oyapicks.app/api/x402/closing-soon-algo
  10. 2026-09-28 01:26 UTC · Algorand · can't tell: request rejected 4xx
    https://oyapicks.app/api/x402/single-market-algo

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