crypto.openverbs.com/v1/protocol
1.Catalog declaration
| Resource URL | https://crypto.openverbs.com/v1/protocol |
| Source | cdp_bazaar |
| Declared method | POST |
| Network | eip155:8453 |
| Receiving address | 0xb3f4de103f34b99f0da19b4f16d6b53a14c2194a |
| Declared price (base units) | 1000 |
| Catalog status | active |
| First seen / last seen | 2026-09-14 01:03 UTC / 2026-09-29 01:03 UTC |
| Catalog-reported calls / payers (30d) | 4 / 4 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-28 22:40 UTC | POST | pass | 402 | 310 ms | — |
| 2026-09-28 04:40 UTC | POST | pass | 402 | 615 ms | — |
| 2026-09-27 13:40 UTC | POST | pass | 402 | 644 ms | — |
| 2026-09-26 16:40 UTC | POST | pass | 402 | 552 ms | — |
| 2026-09-25 22:40 UTC | POST | pass | 402 | 1371 ms | — |
| 2026-09-25 04:40 UTC | POST | pass | 402 | 286 ms | — |
| 2026-09-24 13:40 UTC | POST | pass | 402 | 265 ms | — |
| 2026-09-23 16:40 UTC | POST | pass | 402 | 266 ms | — |
| 2026-09-22 22:40 UTC | POST | pass | 402 | 300 ms | — |
| 2026-09-22 04:40 UTC | POST | pass | 402 | 463 ms | — |
| 2026-09-21 13:40 UTC | POST | pass | 402 | 266 ms | — |
| 2026-09-20 22:40 UTC | POST | pass | 402 | 801 ms | — |
| 2026-09-20 04:40 UTC | POST | pass | 402 | 240 ms | — |
| 2026-09-19 13:40 UTC | POST | pass | 402 | 1621 ms | — |
| 2026-09-18 16:40 UTC | POST | pass | 402 | 201 ms | — |
| 2026-09-17 22:40 UTC | POST | pass | 402 | 159 ms | — |
| 2026-09-17 12:35 UTC | POST | pass | 402 | 103 ms | — |
| 2026-09-14 11:24 UTC | POST | pass | 402 | 211 ms | — |
3.L1 — real purchases
2 of 2 paid attempts settled with a receipt, and 2 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.
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 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 | Receipt (tx) | Latency |
|---|---|---|---|---|
| 09-24 18:022026-09-24 18:02 UTC | settled (nonce-bound) | 200 | 0xae14ebcb…118a | 2052 ms |
| 1000 units (≈ $0.001 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 09-18 06:022026-09-18 06:02 UTC | settled (nonce-bound) | 200 | 0xd2ec10aa…9955 | 2793 ms |
| 1000 units (≈ $0.001 USDC) · L2 no_declarationWhose 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/78f56ea8-9776-48b4-a880-9a3bffb846b6)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.
About the purchase at 2026-09-18T06:02:02Z (UTC). The form starts with that time; add what you saw instead.