trader.rigoblock.com/api/tools
1.Catalog declaration
| Resource URL | https://trader.rigoblock.com/api/tools |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0xa0f9c380ad1e1be09046319fd907335b2b452b37 |
| Declared price (base units) | 2400 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-10-03 01:04 UTC |
| Catalog-reported calls / payers (30d) | 3 / 3 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-02 16:40 UTC | GET | pass | 402 | 1137 ms | — |
| 2026-10-01 22:40 UTC | GET | pass | 402 | 1095 ms | — |
| 2026-10-01 04:40 UTC | GET | pass | 402 | 1264 ms | — |
| 2026-09-30 13:40 UTC | GET | pass | 402 | 932 ms | — |
| 2026-09-29 16:40 UTC | GET | pass | 402 | 1061 ms | — |
| 2026-09-28 22:40 UTC | GET | pass | 402 | 976 ms | — |
| 2026-09-28 04:40 UTC | GET | pass | 402 | 903 ms | — |
| 2026-09-27 13:40 UTC | GET | pass | 402 | 1067 ms | — |
| 2026-09-26 16:40 UTC | GET | pass | 402 | 928 ms | — |
| 2026-09-25 22:40 UTC | GET | pass | 402 | 1264 ms | — |
| 2026-09-25 04:40 UTC | GET | pass | 402 | 998 ms | — |
| 2026-09-24 13:40 UTC | GET | pass | 402 | 872 ms | — |
| 2026-09-23 16:40 UTC | GET | pass | 402 | 983 ms | — |
| 2026-09-22 22:40 UTC | GET | pass | 402 | 1021 ms | — |
| 2026-09-22 04:40 UTC | GET | pass | 402 | 2216 ms | — |
| 2026-09-21 13:40 UTC | GET | pass | 402 | 895 ms | — |
| 2026-09-20 16:40 UTC | GET | pass | 402 | 1235 ms | — |
| 2026-09-19 22:40 UTC | GET | pass | 402 | 2704 ms | — |
| 2026-09-19 04:40 UTC | GET | pass | 402 | 867 ms | — |
| 2026-09-18 13:40 UTC | GET | pass | 402 | 1737 ms | — |
| 2026-09-17 16:40 UTC | GET | pass | 402 | 996 ms | — |
| 2026-09-17 04:40 UTC | GET | pass | 402 | 700 ms | — |
| 2026-09-16 13:40 UTC | GET | pass | 402 | 1029 ms | — |
| 2026-09-15 13:40 UTC | GET | pass | 402 | 862 ms | — |
| 2026-09-14 22:40 UTC | GET | pass | 402 | 1359 ms | — |
| 2026-09-14 04:40 UTC | GET | pass | 402 | 696 ms | — |
| 2026-09-13 16:40 UTC | GET | pass | 402 | 2295 ms | — |
| 2026-09-12 22:40 UTC | GET | pass | 402 | 1156 ms | — |
| 2026-09-12 13:40 UTC | GET | pass | 402 | 644 ms | — |
| 2026-09-11 16:40 UTC | GET | pass | 402 | 263 ms | — |
3.L1 — real purchases
2 of 2 paid attempts settled on-chain, and 2 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.
L2 mismatch- the response lacked fields the listing's output schema declares.
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-15 23:502026-09-15 23:50 UTC | settled (nonce-bound) | 200 | 0xf511c72e…1974 | 1772 ms |
| 2400 units (≈ $0.0024 USDC) · L2 mismatchWhose side: no failure (delivered) | ||||
| 09-06 12:092026-09-06 12:09 UTC | settled (nonce-bound) | 200 | 0x41646e19…5501 | 1605 ms |
| 2400 units (≈ $0.0024 USDC) · L2 mismatchWhose side: no failure (delivered) | ||||
Embed this record
Run this endpoint? Show the settle-through record vet402 measured — the badge reads 2/2 settled · 2 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/75888300-ace9-4223-8619-04821a1cd5d8)4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-08-30 | relisted | {"status":"delisted"} | {"status":"active"} |
| 2026-08-28 | delisted | {"status":"active"} | {"status":"delisted"} |
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.