x402-bazaar-rank.x402-bazaar-rank-worker.workers.dev/in-onchain
1.Catalog declaration
| Resource URL | https://x402-bazaar-rank.x402-bazaar-rank-worker.workers.dev/in-onchain |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0xeca891e34b3e5873181fb779672564e198c55354 |
| Declared price (base units) | 32000 |
| Catalog status | active |
| First seen / last seen | 2026-09-20 01:03 UTC / 2026-09-27 01:02 UTC |
| Catalog-reported calls / payers (30d) | 2 / 2 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-26 22:40 UTC | GET | pass | 402 | 1255 ms | — |
| 2026-09-26 04:40 UTC | GET | pass | 402 | 1156 ms | — |
| 2026-09-25 13:40 UTC | GET | pass | 402 | 5125 ms | — |
| 2026-09-24 16:40 UTC | GET | pass | 402 | 5150 ms | — |
| 2026-09-23 22:40 UTC | GET | pass | 402 | 5342 ms | — |
| 2026-09-23 04:40 UTC | GET | pass | 402 | 5179 ms | — |
| 2026-09-22 13:40 UTC | GET | fail | 402 | 5386 ms | price_mismatch |
| 2026-09-21 16:40 UTC | GET | unverified | 429 | 72 ms | rate_limited |
| 2026-09-21 04:40 UTC | GET | fail | 402 | 858 ms | price_mismatch |
| 2026-09-20 11:24 UTC | GET | fail | 402 | 335 ms | price_mismatch |
3.L1 — real purchases
1 of 1 paid attempts settled with a receipt, and 1 of those also returned a 2xx response (delivered). Each settled row carries its on-chain transaction hash — the receipt is the evidence. 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.
A row marked tx from our index came back with no settlement receipt from the seller. Our own index of on-chain settlements found the transfer afterwards — our payer, this endpoint's payee, the exact amount, inside the time window — and the row goes through the same on-chain re-read as any other before it reads settled. The seller did not name that transaction; we did (methodology).
| Attempted at | Result | HTTP | Receipt (tx) | Latency |
|---|---|---|---|---|
| 09-23 06:012026-09-23 06:01 UTC | settled (nonce-bound)tx from our index | 200 | 0x7001e6e5…4587 | 6737 ms |
| 32000 units (≈ $0.03 USDC) · L2 no_declaration | ||||
Embed this record
Run this endpoint? Show the settle-through record vet402 measured — the badge reads 1/1 settled · 1 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/a0a2d414-31ff-4986-aae5-52f5aab37477)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.