funding-arb.api.klymax402.com/api/scan
1.Catalog declaration
| Resource URL | https://funding-arb.api.klymax402.com/api/scan |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0x6e8b64638b24c6d625b045dd353120d850064e2e |
| Declared price (base units) | 2000 |
| Catalog status | delisted (since 2026-09-19 01:03 UTC) |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-09-18 01:03 UTC |
| Catalog-reported calls / payers (30d) | 10 / 7 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-18 22:40 UTC | GET | unverified | — | 250 ms | tlsThe TLS handshake failed; vet402 cannot tell its own side from the seller's, so nothing is published against the seller. |
| 2026-09-18 04:40 UTC | GET | unverified | — | 225 ms | tlsThe TLS handshake failed; vet402 cannot tell its own side from the seller's, so nothing is published against the seller. |
| 2026-09-17 16:40 UTC | GET | pass | 402 | 654 ms | — |
| 2026-09-16 22:40 UTC | GET | pass | 402 | 453 ms | — |
| 2026-09-15 22:40 UTC | GET | pass | 402 | 382 ms | — |
| 2026-09-15 13:40 UTC | GET | pass | 402 | 463 ms | — |
| 2026-09-14 16:40 UTC | GET | pass | 402 | 346 ms | — |
| 2026-09-14 04:40 UTC | GET | pass | 402 | 345 ms | — |
| 2026-09-13 13:40 UTC | GET | pass | 402 | 585 ms | — |
| 2026-09-12 22:40 UTC | GET | pass | 402 | 690 ms | — |
| 2026-09-12 04:40 UTC | GET | pass | 402 | 540 ms | — |
| 2026-09-11 16:40 UTC | GET | pass | 402 | 614 ms | — |
| 2026-09-10 23:40 UTC | GET | pass | 402 | 899 ms | — |
| 2026-09-10 14:40 UTC | GET | pass | 402 | 383 ms | — |
| 2026-09-09 23:40 UTC | GET | pass | 402 | 563 ms | — |
| 2026-09-09 14:40 UTC | GET | pass | 402 | 405 ms | — |
| 2026-09-08 17:40 UTC | GET | pass | 402 | 356 ms | — |
| 2026-09-08 05:40 UTC | GET | pass | 402 | 408 ms | — |
| 2026-09-07 17:40 UTC | GET | pass | 402 | 504 ms | — |
| 2026-09-07 05:40 UTC | GET | pass | 402 | 584 ms | — |
| 2026-09-06 17:40 UTC | GET | pass | 402 | 501 ms | — |
| 2026-09-06 05:40 UTC | GET | pass | 402 | 399 ms | — |
| 2026-09-05 17:40 UTC | GET | pass | 402 | 661 ms | — |
| 2026-09-05 05:40 UTC | GET | pass | 402 | 503 ms | — |
| 2026-09-04 17:40 UTC | GET | pass | 402 | 405 ms | — |
| 2026-09-04 05:40 UTC | GET | pass | 402 | 366 ms | — |
| 2026-09-03 17:40 UTC | GET | pass | 402 | 492 ms | — |
| 2026-09-03 05:40 UTC | GET | pass | 402 | 402 ms | — |
| 2026-09-02 17:40 UTC | GET | pass | 402 | 438 ms | — |
| 2026-09-02 05:40 UTC | GET | pass | 402 | 360 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.
settled (amount + payee)- vet402 confirmed the USDC transfer on-chain; the on-chain re-read matched amount, payee, asset and chain; no nonce was on record (rows before 2026-09-04).
L2 no_declaration- the listing declares no output schema to check the response against.
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-10 19:022026-09-10 19:02 UTC | settled (nonce-bound) | 200 | 0x446f50e4…6e0e | 2754 ms |
| 2000 units (≈ $0.002 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 08-30 12:082026-08-30 12:08 UTC | settled (amount + payee) | 200 | 0x3a239c79…3687 | 3053 ms |
| 2000 units (≈ $0.002 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 08-23 12:442026-08-23 12:44 UTC | settled (amount + payee) | 200 | 0x4ae696e5…1c36 | 2879 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 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/f845f190-d513-4c7a-990c-016e9cd45885)4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-09-19 | 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.