api.stakedbots.com/leaderboard
1.Catalog declaration
| Resource URL | https://api.stakedbots.com/leaderboard |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | base |
| Receiving address | 0x21b077b26bfda6d2b8fdf0130977362d61e18912 |
| Declared price (base units) | — |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-09-30 01:03 UTC |
| Catalog-reported calls / payers (30d) | 9 / 4 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-29 22:40 UTC | GET | pass | 402 | 621 ms | — |
| 2026-09-29 04:40 UTC | GET | pass | 402 | 430 ms | — |
| 2026-09-28 13:40 UTC | GET | pass | 402 | 397 ms | — |
| 2026-09-27 16:40 UTC | GET | pass | 402 | 2425 ms | — |
| 2026-09-26 22:40 UTC | GET | pass | 402 | 409 ms | — |
| 2026-09-26 04:40 UTC | GET | pass | 402 | 2523 ms | — |
| 2026-09-25 13:40 UTC | GET | pass | 402 | 365 ms | — |
| 2026-09-24 16:40 UTC | GET | pass | 402 | 2567 ms | — |
| 2026-09-23 22:40 UTC | GET | pass | 402 | 1299 ms | — |
| 2026-09-23 04:40 UTC | GET | pass | 402 | 391 ms | — |
| 2026-09-22 13:40 UTC | GET | pass | 402 | 586 ms | — |
| 2026-09-21 16:40 UTC | GET | pass | 402 | 404 ms | — |
| 2026-09-20 22:40 UTC | GET | pass | 402 | 815 ms | — |
| 2026-09-20 04:40 UTC | GET | pass | 402 | 366 ms | — |
| 2026-09-19 16:40 UTC | GET | pass | 402 | 409 ms | — |
| 2026-09-18 22:40 UTC | GET | pass | 402 | 2308 ms | — |
| 2026-09-18 04:40 UTC | GET | pass | 402 | 358 ms | — |
| 2026-09-17 13:40 UTC | GET | pass | 402 | 403 ms | — |
| 2026-09-16 22:40 UTC | GET | pass | 402 | 541 ms | — |
| 2026-09-15 22:40 UTC | GET | pass | 402 | 436 ms | — |
| 2026-09-15 04:40 UTC | GET | pass | 402 | 373 ms | — |
| 2026-09-14 16:40 UTC | GET | pass | 402 | 859 ms | — |
| 2026-09-13 22:40 UTC | GET | pass | 402 | 656 ms | — |
| 2026-09-13 13:40 UTC | GET | pass | 402 | 355 ms | — |
| 2026-09-12 16:40 UTC | GET | pass | 402 | 370 ms | — |
| 2026-09-12 04:40 UTC | GET | pass | 402 | 418 ms | — |
| 2026-09-11 16:40 UTC | GET | pass | 402 | 352 ms | — |
| 2026-09-10 23:40 UTC | GET | pass | 402 | 177 ms | — |
| 2026-09-10 14:40 UTC | GET | pass | 402 | 185 ms | — |
| 2026-09-09 23:40 UTC | GET | pass | 402 | 1376 ms | — |
3.L1 — real purchases
5 of 5 paid attempts settled on-chain, and 5 of those also returned a 2xx response (delivered). Each settled row carries its on-chain transaction hash, and that transaction is the evidence. On this page a receipt means the seller's own settlement receipt (PAYMENT-RESPONSE); a settled row can have none (see “tx from our index”). A settled row reads as nonce-bound when the on-chain re-read also matched the one-time signature nonce we generated for that purchase, and amount + payee when it matched amount, payee, asset and chain with no nonce on record — the binding shipped on 2026-09-04, so earlier rows carry the weaker evidence and keep their label rather than being demoted (methodology). settled is the transfer we confirmed on-chain; delivered is the response arriving. A settled row whose paid request answered 5xx counts as settled and not as delivered — definitions.
Terms in this table
settled (nonce-bound)- vet402 confirmed the USDC transfer on-chain, and the on-chain re-read also matched the one-time nonce vet402 signed for that purchase.
settled (amount + payee)- vet402 confirmed the USDC transfer on-chain; the on-chain re-read matched amount, payee, asset and chain; no nonce was on record (rows before 2026-09-04).
L2 no_declaration- the listing declares no output schema to check the response against.
Whose side- the same words as the seller page: seller's side only after failures on two different days (UTC), marked “under re-check”; vet402's side; or not sorted (the rules).
| Attempted at | Result | HTTP | On-chain tx | Latency |
|---|---|---|---|---|
| 09-16 18:002026-09-16 18:00 UTC | settled (nonce-bound) | 200 | 0xa58acb62…8d7b | 2167 ms |
| 20000 units (≈ $0.02 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 09-10 07:022026-09-10 07:02 UTC | settled (nonce-bound) | 200 | 0x6fe6ea81…6fe6 | 1892 ms |
| 20000 units (≈ $0.02 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 08-28 12:192026-08-28 12:19 UTC | settled (amount + payee) | 200 | 0x69aa6725…9a82 | 1571 ms |
| 20000 units (≈ $0.02 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 08-20 12:562026-08-20 12:56 UTC | settled (amount + payee) | 200 | 0xcf25f8f2…4cc9 | 1805 ms |
| 20000 units (≈ $0.02 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 08-14 10:032026-08-14 10:03 UTC | settled (amount + payee) | 200 | 0x85ff1b8d…7ff7 | 1741 ms |
| 20000 units (≈ $0.02 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
Embed this record
Run this endpoint? Show the settle-through record vet402 measured — the badge reads 5/5 settled · 5 delivered and updates as the record grows. It carries the host it is about and the date it was last measured, so a saved copy cannot pass itself off as current. It states a measurement, not a rating.
[](https://vet402.com/observatory/e/c50bb805-9bff-4f9d-afe7-24f2c03498b8)4.Catalog listing events
No listing changes observed.
unverified is not a failure; a fail is published only after two consecutive failing probes. Definitions: methodology.
5.Dispute this record
Think a measurement above is wrong? Say which probe or purchase and what you observed instead. One person reads it and replies. The record is never deleted on dispute: if it was wrong, the correction is published with the same weight; if it was right, it stands. Operators who control the receiving address can also sign a dispute via POST /api/v1/observatory/disputes (API reference), which re-measures through the normal publication gate.