api.clawinabox.xyz/paid/v1/guard/check
1.Catalog declaration
| Resource URL | https://api.clawinabox.xyz/paid/v1/guard/check |
| Source | cdp_bazaar |
| Declared method | POST |
| Network | eip155:8453 |
| Receiving address | 0x46f297e342bc0b44b9f9c427e53c56e9f83bb660 |
| Declared price (base units) | 10000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-10-20 01:01 UTC |
| Catalog-reported calls / payers (30d) | 5 / 3 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-20 04:40 UTC | POST | pass | 402 | 294 ms | — |
| 2026-10-18 13:40 UTC | POST | pass | 402 | 319 ms | — |
| 2026-10-17 04:40 UTC | POST | pass | 402 | 394 ms | — |
| 2026-10-15 15:40 UTC | POST | pass | 402 | 506 ms | — |
| 2026-10-14 12:40 UTC | POST | pass | 402 | 547 ms | — |
| 2026-10-12 21:40 UTC | POST | pass | 402 | 319 ms | — |
| 2026-10-11 21:40 UTC | POST | pass | 402 | 281 ms | — |
| 2026-10-10 21:40 UTC | POST | pass | 402 | 504 ms | — |
| 2026-10-09 21:40 UTC | POST | pass | 402 | 395 ms | — |
| 2026-10-08 16:40 UTC | POST | pass | 402 | 372 ms | — |
| 2026-10-07 13:40 UTC | POST | pass | 402 | 212 ms | — |
| 2026-10-06 16:40 UTC | POST | pass | 402 | 228 ms | — |
| 2026-10-05 04:40 UTC | POST | pass | 402 | 1476 ms | — |
| 2026-10-04 13:40 UTC | POST | pass | 402 | 213 ms | — |
| 2026-10-03 16:40 UTC | POST | pass | 402 | 338 ms | — |
| 2026-10-02 16:40 UTC | POST | pass | 402 | 2262 ms | — |
| 2026-10-01 22:40 UTC | POST | pass | 402 | 2277 ms | — |
| 2026-10-01 04:40 UTC | POST | pass | 402 | 261 ms | — |
| 2026-09-30 13:40 UTC | POST | pass | 402 | 268 ms | — |
| 2026-09-29 16:40 UTC | POST | pass | 402 | 307 ms | — |
| 2026-09-28 22:40 UTC | POST | pass | 402 | 234 ms | — |
| 2026-09-28 04:40 UTC | POST | pass | 402 | 141 ms | — |
| 2026-09-27 13:40 UTC | POST | pass | 402 | 2409 ms | — |
| 2026-09-26 16:40 UTC | POST | pass | 402 | 157 ms | — |
| 2026-09-25 22:40 UTC | POST | pass | 402 | 236 ms | — |
| 2026-09-25 04:40 UTC | POST | pass | 402 | 2187 ms | — |
| 2026-09-24 13:40 UTC | POST | pass | 402 | 318 ms | — |
| 2026-09-23 16:40 UTC | POST | pass | 402 | 266 ms | — |
| 2026-09-22 22:40 UTC | POST | pass | 402 | 454 ms | — |
| 2026-09-22 04:40 UTC | POST | pass | 402 | 340 ms | — |
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-12 23:022026-10-12 23:02 UTC | settled (nonce-bound) | 200 | 0x25840dd9…dd38 | 1261 ms |
| 10000 units (≈ $0.01 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 09-21 06:002026-09-21 06:00 UTC | settled (nonce-bound) | 200 | 0xbcb1eb1d…be29 | 1166 ms |
| 10000 units (≈ $0.01 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/e20db242-3426-4df5-a30d-b92b3afdc0a7)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.