x402.ochinimus.app/api/squeeze-score
1.Catalog declaration
| Resource URL | https://x402.ochinimus.app/api/squeeze-score |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp |
| Receiving address | 4a8o45skRPcyjAdyR8yES215Swvh8uTpZD6KLarhxCJ7 |
| Declared price (base units) | 100000 |
| 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 / 2 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-20 16:40 UTC | GET | pass | 402 | 317 ms | — |
| 2026-10-19 13:40 UTC | GET | pass | 402 | 148 ms | — |
| 2026-10-17 22:40 UTC | GET | pass | 402 | 404 ms | — |
| 2026-10-16 12:40 UTC | GET | pass | 402 | 2378 ms | — |
| 2026-10-14 21:40 UTC | GET | pass | 402 | 512 ms | — |
| 2026-10-13 15:40 UTC | GET | pass | 402 | 395 ms | — |
| 2026-10-12 12:40 UTC | GET | pass | 402 | 116 ms | — |
| 2026-10-11 12:40 UTC | GET | pass | 402 | 123 ms | — |
| 2026-10-10 12:40 UTC | GET | pass | 402 | 163 ms | — |
| 2026-10-09 12:40 UTC | GET | pass | 402 | 134 ms | — |
| 2026-10-08 04:40 UTC | GET | pass | 402 | 281 ms | — |
| 2026-10-07 04:40 UTC | GET | pass | 402 | 326 ms | — |
| 2026-10-06 04:41 UTC | GET | pass | 402 | 133 ms | — |
| 2026-10-04 22:40 UTC | GET | pass | 402 | 787 ms | — |
| 2026-10-03 22:40 UTC | GET | pass | 402 | 548 ms | — |
| 2026-10-03 04:40 UTC | GET | pass | 402 | 447 ms | — |
| 2026-10-02 13:40 UTC | GET | pass | 402 | 181 ms | — |
| 2026-10-01 13:40 UTC | GET | pass | 402 | 275 ms | — |
| 2026-09-30 16:40 UTC | GET | pass | 402 | 167 ms | — |
| 2026-09-29 22:40 UTC | GET | pass | 402 | 209 ms | — |
| 2026-09-29 04:40 UTC | GET | pass | 402 | 178 ms | — |
| 2026-09-28 13:40 UTC | GET | pass | 402 | 494 ms | — |
| 2026-09-27 16:40 UTC | GET | pass | 402 | 482 ms | — |
| 2026-09-26 22:40 UTC | GET | pass | 402 | 125 ms | — |
| 2026-09-26 13:40 UTC | GET | pass | 402 | 461 ms | — |
| 2026-09-22 11:24 UTC | GET | pass | 402 | 338 ms | — |
| 2026-09-18 11:24 UTC | GET | pass | 402 | 397 ms | — |
| 2026-09-16 11:24 UTC | GET | pass | 402 | 465 ms | — |
| 2026-09-12 11:24 UTC | GET | pass | 402 | 339 ms | — |
| 2026-09-08 11:24 UTC | GET | pass | 402 | 439 ms | — |
3.L1 — real purchases
3 of 3 paid attempts settled on-chain, and 3 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-08 12:002026-10-08 12:00 UTC | settled (nonce-bound) | 200 | CuKrWgUHD1…7Q4r | 3352 ms |
| 100000 units (≈ $0.10 USDC) · L2 matchWhose side: no failure (delivered) | ||||
| 10-02 09:302026-10-02 09:30 UTC | settled (nonce-bound) | 200 | 59SWc8CJqw…BDV1 | 2980 ms |
| 100000 units (≈ $0.10 USDC) · L2 matchWhose side: no failure (delivered) | ||||
| 09-26 06:002026-09-26 06:00 UTC | settled (nonce-bound) | 200 | 754eFeYUw3…rTmE | 2965 ms |
| 100000 units (≈ $0.10 USDC) · L2 matchWhose side: no failure (delivered) | ||||
Embed this record
Run this endpoint? Show the settle-through record vet402 measured — the badge reads 3/3 settled · 3 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/f80f319a-6bbd-4336-892e-3efced2671e3)4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-09-02 | relisted | {"status":"delisted"} | {"status":"active"} |
| 2026-08-18 | 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.