quartermaster.surewhynot.app/v1/x402/inspect
1.Catalog declaration
| Resource URL | https://quartermaster.surewhynot.app/v1/x402/inspect |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0x5253666c40432f009ebd99908b9cd2a7fd1019cb |
| Declared price (base units) | 2000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-10-20 01:01 UTC |
| Catalog-reported calls / payers (30d) | 7 / 6 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-19 13:40 UTC | GET | pass | 402 | 235 ms | — |
| 2026-10-17 22:40 UTC | GET | pass | 402 | 1452 ms | — |
| 2026-10-16 15:40 UTC | GET | pass | 402 | 1306 ms | — |
| 2026-10-15 03:40 UTC | GET | pass | 402 | 773 ms | — |
| 2026-10-13 21:40 UTC | GET | pass | 402 | 816 ms | — |
| 2026-10-12 15:40 UTC | GET | pass | 402 | 1083 ms | — |
| 2026-10-11 12:40 UTC | GET | pass | 402 | 681 ms | — |
| 2026-10-10 12:40 UTC | GET | pass | 402 | 469 ms | — |
| 2026-10-09 12:40 UTC | GET | pass | 402 | 1168 ms | — |
| 2026-10-08 04:40 UTC | GET | pass | 402 | 778 ms | — |
| 2026-10-07 04:40 UTC | GET | pass | 402 | 676 ms | — |
| 2026-10-06 04:41 UTC | GET | pass | 402 | 1059 ms | — |
| 2026-10-04 22:40 UTC | GET | pass | 402 | 622 ms | — |
| 2026-10-04 04:40 UTC | GET | pass | 402 | 756 ms | — |
| 2026-10-01 10:30 UTC | GET | pass | 402 | 422 ms | — |
| 2026-09-25 10:31 UTC | GET | pass | 402 | 616 ms | — |
| 2026-09-21 11:24 UTC | GET | pass | 402 | 584 ms | — |
| 2026-09-17 16:19 UTC | GET | pass | 402 | 653 ms | — |
| 2026-09-14 11:24 UTC | GET | pass | 402 | 50 ms | — |
| 2026-09-11 11:24 UTC | GET | pass | 402 | 296 ms | — |
| 2026-09-07 11:24 UTC | GET | pass | 402 | 303 ms | — |
| 2026-09-02 11:24 UTC | GET | pass | 402 | 112 ms | — |
| 2026-08-14 08:53 UTC | GET | fail | 402 | 493 ms | accepts_invalid402 without a payable accept in the header or the body (which part was missing was not recorded before the 2026-09-29 change). |
3.L1 — real purchases
2 of 2 paid attempts settled on-chain, and 2 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 no_declaration- the listing's output schema gave vet402 nothing to check this response against (no schema, a schema with no required keys and no example properties, or example properties with a content type that is not JSON). An output example the seller puts in the 402 (extensions.bazaar.info.output.example) is not checked yet.
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-10 14:312026-10-10 14:31 UTC | settled (nonce-bound) | 200 | 0x67657d58…5e8d | 1376 ms |
| 2000 units (≈ $0.002 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 10-04 12:022026-10-04 12:02 UTC | settled (nonce-bound) | 200 | 0x2a8ee802…000e | 1301 ms |
| 2000 units (≈ $0.002 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/316380fc-4ac6-4d98-8c24-a83f469744e2)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.