api.zerion.io/v1/dapps
1.Catalog declaration
| Resource URL | https://api.zerion.io/v1/dapps/ |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0xd07c06a650a88bbcf4f0c4fbf2c6c08c9a60acc6 |
| Declared price (base units) | 10000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:52 UTC / 2026-10-20 13:01 UTC |
| Catalog-reported calls / payers (30d) | 4 / 3 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-20 13:40 UTC | GET | pass | 402 | 201 ms | — |
| 2026-10-18 22:40 UTC | GET | pass | 402 | 71 ms | — |
| 2026-10-17 13:40 UTC | GET | pass | 402 | 54 ms | — |
| 2026-10-15 21:40 UTC | GET | pass | 402 | 105 ms | — |
| 2026-10-14 15:40 UTC | GET | pass | 402 | 106 ms | — |
| 2026-10-13 10:30 UTC | GET | pass | 402 | 132 ms | — |
| 2026-09-06 11:24 UTC | GET | pass | 402 | 29 ms | — |
| 2026-09-01 23:13 UTC | GET | pass | 402 | 58 ms | — |
3.L1 — real purchases
1 of 1 paid attempts settled on-chain, and 1 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 match- the response parsed as JSON and had the keys the listing marks as required. With an example that marks no key as required, a JSON object or array is enough.
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 |
|---|---|---|---|---|
| 10-18 09:312026-10-18 09:31 UTC | settled (nonce-bound) | 200 | 0x43a753f5…da1d | 946 ms |
| 10000 units (≈ $0.01 USDC) · L2 matchWhose side: no failure (delivered) | ||||
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/96444050-4f34-4042-8482-c72eeea677e4)4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-10-07 | relisted | {"status":"delisted"} | {"status":"active"} |
| 2026-09-10 | 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.