api.run402.com/tiers/v1/prototype
1.Catalog declaration
| Resource URL | https://api.run402.com/tiers/v1/prototype |
| Source | cdp_bazaar |
| Declared method | POST |
| Network | eip155:8453 |
| Receiving address | 0x059d091d51a0f011c9872eaa63df538f5ce15945 |
| Declared price (base units) | 100000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-09-30 01:03 UTC |
| Catalog-reported calls / payers (30d) | 49 / 49 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-30 04:40 UTC | POST | pass | 402 | 291 ms | — |
| 2026-09-29 13:40 UTC | POST | pass | 402 | 2147 ms | — |
| 2026-09-28 16:40 UTC | POST | pass | 402 | 83 ms | — |
| 2026-09-27 22:40 UTC | POST | pass | 402 | 222 ms | — |
| 2026-09-27 04:40 UTC | POST | pass | 402 | 64 ms | — |
| 2026-09-26 13:40 UTC | POST | pass | 402 | 249 ms | — |
| 2026-09-25 16:40 UTC | POST | pass | 402 | 217 ms | — |
| 2026-09-24 22:40 UTC | POST | pass | 402 | 91 ms | — |
| 2026-09-24 04:40 UTC | POST | pass | 402 | 183 ms | — |
| 2026-09-23 13:40 UTC | POST | pass | 402 | 30 ms | — |
| 2026-09-22 16:40 UTC | POST | pass | 402 | 53 ms | — |
| 2026-09-21 22:40 UTC | POST | pass | 402 | 42 ms | — |
| 2026-09-21 04:40 UTC | POST | pass | 402 | 40 ms | — |
| 2026-09-20 16:40 UTC | POST | pass | 402 | 91 ms | — |
| 2026-09-19 22:40 UTC | POST | pass | 402 | 532 ms | — |
| 2026-09-19 04:40 UTC | POST | pass | 402 | 144 ms | — |
| 2026-09-18 13:40 UTC | POST | pass | 402 | 199 ms | — |
| 2026-09-17 16:40 UTC | POST | pass | 402 | 230 ms | — |
| 2026-09-17 04:40 UTC | POST | pass | 402 | 108 ms | — |
| 2026-09-16 13:40 UTC | POST | pass | 402 | 300 ms | — |
| 2026-09-15 13:40 UTC | POST | pass | 402 | 2088 ms | — |
| 2026-09-14 22:40 UTC | POST | pass | 402 | 154 ms | — |
| 2026-09-14 04:40 UTC | POST | pass | 402 | 252 ms | — |
| 2026-09-13 16:40 UTC | POST | pass | 402 | 62 ms | — |
| 2026-09-12 22:40 UTC | POST | pass | 402 | 156 ms | — |
| 2026-09-12 13:40 UTC | POST | pass | 402 | 31 ms | — |
| 2026-09-11 22:40 UTC | POST | pass | 402 | 47 ms | — |
| 2026-09-11 04:40 UTC | POST | pass | 402 | 89 ms | — |
| 2026-09-10 17:40 UTC | POST | pass | 402 | 25 ms | — |
| 2026-09-10 05:40 UTC | POST | pass | 402 | 2056 ms | — |
3.L1 — real purchases
1 of 4 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
delivered_no_receipt- the paid request answered 2xx without a settlement receipt.
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.
L2 not_checked- not checked: the paid request did not answer 200, so there was no response to check against the listing's output schema.
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-23 12:012026-09-23 12:01 UTC | delivered_no_receipt | 200 | — | 108 ms |
| 100000 units (≈ $0.10 USDC) · L2 no_declarationWhose side: not sorted: no charge | ||||
| 09-17 00:012026-09-17 00:01 UTC | delivered_no_receipt | 200 | — | 106 ms |
| 100000 units (≈ $0.10 USDC) · L2 no_declarationWhose side: not sorted: no charge | ||||
| 09-10 19:002026-09-10 19:00 UTC | delivered_no_receipt | 200 | — | 114 ms |
| 100000 units (≈ $0.10 USDC) · L2 no_declarationWhose side: not sorted: no charge | ||||
| 09-04 12:072026-09-04 12:07 UTC | settled (nonce-bound) | 201 | 0x50b1731d…c07c | 1026 ms |
| 100000 units (≈ $0.10 USDC) · L2 not_checkedWhose side: no failure (delivered) | ||||
Embed this record
Run this endpoint? Show the settle-through record vet402 measured — the badge reads 1/4 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/82e7ccf3-f942-4410-bd55-567c6b685e72)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.