x402payswap.vercel.app/api/premium
1.Catalog declaration
| Resource URL | https://x402payswap.vercel.app/api/premium |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | base |
| Receiving address | 0xc0887adf2411c4db859e497c1f931c59600b1ec4 |
| Declared price (base units) | — |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:52 UTC / 2026-10-17 01:04 UTC |
| Catalog-reported calls / payers (30d) | 2 / 2 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-17 04:40 UTC | GET | pass | 402 | 1603 ms | — |
| 2026-10-15 15:40 UTC | GET | pass | 402 | 3216 ms | — |
| 2026-10-14 12:40 UTC | GET | pass | 402 | 1687 ms | — |
| 2026-10-12 21:40 UTC | GET | pass | 402 | 1151 ms | — |
| 2026-10-11 21:40 UTC | GET | pass | 402 | 180 ms | — |
| 2026-10-10 21:40 UTC | GET | pass | 402 | 166 ms | — |
| 2026-10-09 21:40 UTC | GET | pass | 402 | 1459 ms | — |
| 2026-10-08 16:40 UTC | GET | pass | 402 | 1338 ms | — |
| 2026-10-07 13:40 UTC | GET | pass | 402 | 1160 ms | — |
| 2026-10-06 16:40 UTC | GET | pass | 402 | 1304 ms | — |
| 2026-10-05 04:40 UTC | GET | pass | 402 | 1175 ms | — |
| 2026-10-04 13:40 UTC | GET | pass | 402 | 1088 ms | — |
| 2026-10-03 13:40 UTC | GET | pass | 402 | 997 ms | — |
| 2026-10-02 16:40 UTC | GET | pass | 402 | 1306 ms | — |
| 2026-10-01 16:40 UTC | GET | pass | 402 | 1425 ms | — |
| 2026-09-30 22:40 UTC | GET | pass | 402 | 3297 ms | — |
| 2026-09-30 04:40 UTC | GET | pass | 402 | 1320 ms | — |
| 2026-09-29 13:40 UTC | GET | pass | 402 | 1437 ms | — |
| 2026-09-28 16:40 UTC | GET | pass | 402 | 1200 ms | — |
| 2026-09-27 22:40 UTC | GET | pass | 402 | 1180 ms | — |
| 2026-09-27 04:40 UTC | GET | pass | 402 | 102 ms | — |
| 2026-09-26 13:40 UTC | GET | pass | 402 | 1138 ms | — |
| 2026-09-25 16:40 UTC | GET | pass | 402 | 1265 ms | — |
| 2026-09-24 22:40 UTC | GET | pass | 402 | 1465 ms | — |
| 2026-09-24 04:40 UTC | GET | pass | 402 | 1398 ms | — |
| 2026-09-23 13:40 UTC | GET | pass | 402 | 1339 ms | — |
| 2026-09-22 16:40 UTC | GET | pass | 402 | 1222 ms | — |
| 2026-09-21 22:40 UTC | GET | pass | 402 | 1336 ms | — |
| 2026-09-21 04:40 UTC | GET | pass | 402 | 1070 ms | — |
| 2026-09-20 16:40 UTC | GET | pass | 402 | 1369 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 |
|---|---|---|---|---|
| 10-01 18:002026-10-01 18:00 UTC | settled (nonce-bound) | 200 | 0x901955fc…8096 | 3421 ms |
| 10000 units (≈ $0.01 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 09-15 23:502026-09-15 23:50 UTC | settled (nonce-bound) | 200 | 0xfbdb0735…c2d4 | 2796 ms |
| 10000 units (≈ $0.01 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 09-02 01:002026-09-02 01:00 UTC | settled (amount + payee) | 200 | 0x3c2ccdc4…2d06 | 2661 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 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/e6556615-2110-48e2-9242-2a2cd8026cce)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.