x402swag.com/api/agent/catalog
1.Catalog declaration
| Resource URL | https://x402swag.com/api/agent/catalog |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0xf4f7182508895812f235c5d1c47c0cfc89fdab5b |
| Declared price (base units) | 50000 |
| 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 / 5 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-19 13:40 UTC | GET | pass | 402 | 199 ms | — |
| 2026-10-17 16:40 UTC | GET | pass | 402 | 151 ms | — |
| 2026-10-16 12:40 UTC | GET | pass | 402 | 143 ms | — |
| 2026-10-14 21:40 UTC | GET | pass | 402 | 119 ms | — |
| 2026-10-13 15:40 UTC | GET | pass | 402 | 336 ms | — |
| 2026-10-12 12:40 UTC | GET | pass | 402 | 159 ms | — |
| 2026-10-11 12:40 UTC | GET | pass | 402 | 197 ms | — |
| 2026-10-10 12:40 UTC | GET | pass | 402 | 104 ms | — |
| 2026-10-09 12:40 UTC | GET | pass | 402 | 358 ms | — |
| 2026-10-08 04:40 UTC | GET | pass | 402 | 206 ms | — |
| 2026-10-07 04:40 UTC | GET | pass | 402 | 726 ms | — |
| 2026-10-06 04:41 UTC | GET | pass | 402 | 443 ms | — |
| 2026-10-04 16:40 UTC | GET | pass | 402 | 103 ms | — |
| 2026-10-03 22:40 UTC | GET | pass | 402 | 322 ms | — |
| 2026-10-03 04:40 UTC | GET | pass | 402 | 2098 ms | — |
| 2026-10-02 13:40 UTC | GET | pass | 402 | 144 ms | — |
| 2026-10-01 13:40 UTC | GET | pass | 402 | 292 ms | — |
| 2026-09-30 16:40 UTC | GET | pass | 402 | 197 ms | — |
| 2026-09-29 22:40 UTC | GET | pass | 402 | 180 ms | — |
| 2026-09-29 04:40 UTC | GET | pass | 402 | 103 ms | — |
| 2026-09-28 13:40 UTC | GET | pass | 402 | 98 ms | — |
| 2026-09-27 16:40 UTC | GET | pass | 402 | 68 ms | — |
| 2026-09-26 22:40 UTC | GET | pass | 402 | 92 ms | — |
| 2026-09-26 13:40 UTC | GET | pass | 402 | 567 ms | — |
| 2026-09-25 16:40 UTC | GET | pass | 402 | 136 ms | — |
| 2026-09-24 22:40 UTC | GET | pass | 402 | 118 ms | — |
| 2026-09-24 04:40 UTC | GET | pass | 402 | 400 ms | — |
| 2026-09-23 13:40 UTC | GET | pass | 402 | 444 ms | — |
| 2026-09-22 16:40 UTC | GET | pass | 402 | 268 ms | — |
| 2026-09-21 22:40 UTC | GET | pass | 402 | 104 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 match- the response parsed as JSON and had the keys the listing marks as required. With an example that marks no key as required, a JSON object or array is enough.
L2 mismatch- the content type was not JSON although the listing marks required keys, or the body read in full did not parse as JSON, was JSON but not an object or array, or lacked a key the listing marks as required.
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-11 23:012026-10-11 23:01 UTC | settled (nonce-bound) | 200 | 0x7638ae01…9c05 | 1062 ms |
| 50000 units (≈ $0.05 USDC) · L2 matchWhose side: no failure (delivered) | ||||
| 09-07 19:012026-09-07 19:01 UTC | settled (nonce-bound) | 200 | 0x5a04c421…04e3 | 1076 ms |
| 50000 units (≈ $0.05 USDC) · L2 mismatchWhose 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/8f4d7a3b-87f6-4602-b753-9e7dd94949c8)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.