api.kakerapetit.dev/v2/screener
1.Catalog declaration
| Resource URL | https://api.kakerapetit.dev/v2/screener |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0x3a43fdf92b1596b22ddf719d5b528c537da4237d |
| Declared price (base units) | 20000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-10-01 01:03 UTC |
| Catalog-reported calls / payers (30d) | 4 / 1 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-30 16:40 UTC | GET | pass | 402 | 2514 ms | — |
| 2026-09-29 22:40 UTC | GET | pass | 402 | 564 ms | — |
| 2026-09-29 04:40 UTC | GET | pass | 402 | 207 ms | — |
| 2026-09-28 13:40 UTC | GET | pass | 402 | 294 ms | — |
| 2026-09-27 16:40 UTC | GET | pass | 402 | 443 ms | — |
| 2026-09-26 22:40 UTC | GET | pass | 402 | 461 ms | — |
| 2026-09-26 04:40 UTC | GET | pass | 402 | 553 ms | — |
| 2026-09-25 13:40 UTC | GET | pass | 402 | 1011 ms | — |
| 2026-09-24 16:40 UTC | GET | pass | 402 | 272 ms | — |
| 2026-09-24 04:40 UTC | GET | pass | 402 | 598 ms | — |
| 2026-09-23 13:40 UTC | GET | pass | 402 | 773 ms | — |
| 2026-09-22 16:40 UTC | GET | pass | 402 | 311 ms | — |
| 2026-09-21 22:40 UTC | GET | pass | 402 | 618 ms | — |
| 2026-09-21 04:40 UTC | GET | pass | 402 | 549 ms | — |
| 2026-09-20 13:40 UTC | GET | pass | 402 | 2111 ms | — |
| 2026-09-19 16:40 UTC | GET | pass | 402 | 392 ms | — |
| 2026-09-18 22:40 UTC | GET | pass | 402 | 2528 ms | — |
| 2026-09-18 04:40 UTC | GET | pass | 402 | 466 ms | — |
| 2026-09-17 16:40 UTC | GET | pass | 402 | 629 ms | — |
| 2026-09-16 22:40 UTC | GET | pass | 402 | 413 ms | — |
| 2026-09-15 22:40 UTC | GET | pass | 402 | 245 ms | — |
| 2026-09-15 13:40 UTC | GET | pass | 402 | 378 ms | — |
| 2026-09-14 16:40 UTC | GET | pass | 402 | 505 ms | — |
| 2026-09-14 04:40 UTC | GET | pass | 402 | 583 ms | — |
| 2026-09-13 13:40 UTC | GET | pass | 402 | 118 ms | — |
| 2026-09-12 22:40 UTC | GET | pass | 402 | 276 ms | — |
| 2026-09-12 04:40 UTC | GET | pass | 402 | 517 ms | — |
| 2026-09-11 16:40 UTC | GET | pass | 402 | 161 ms | — |
| 2026-09-11 04:40 UTC | GET | pass | 402 | 813 ms | — |
| 2026-09-10 14:40 UTC | GET | pass | 402 | 548 ms | — |
3.L1 — real purchases
1 of 1 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
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 mismatch- the response lacked fields the listing's output schema declares.
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-05 07:012026-09-05 07:01 UTC | settled (nonce-bound) | 200 | 0xf07e33fc…bf84 | 2498 ms |
| 20000 units (≈ $0.02 USDC) · L2 mismatchWhose side: no failure (delivered) | ||||
Embed this record
Run this endpoint? Show the settle-through record vet402 measured — the badge reads 1/1 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/224899a5-f16a-4236-a535-e4ffda26e842)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.