defillama.use.x402atlas.com/protocol
1.Catalog declaration
| Resource URL | https://defillama.use.x402atlas.com/protocol |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0xcb8025d951e5e45be7d288b658eeee6f05713006 |
| Declared price (base units) | 5000 |
| Catalog status | active |
| First seen / last seen | 2026-08-16 01:06 UTC / 2026-10-20 01:01 UTC |
| Catalog-reported calls / payers (30d) | 6 / 5 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-18 22:40 UTC | GET | pass | 402 | 111 ms | — |
| 2026-10-17 16:40 UTC | GET | pass | 402 | 260 ms | — |
| 2026-10-15 21:40 UTC | GET | pass | 402 | 50 ms | — |
| 2026-10-14 15:40 UTC | GET | pass | 402 | 23 ms | — |
| 2026-10-13 15:40 UTC | GET | pass | 402 | 149 ms | — |
| 2026-10-12 03:40 UTC | GET | pass | 402 | 165 ms | — |
| 2026-10-11 03:40 UTC | GET | pass | 402 | 61 ms | — |
| 2026-10-10 03:40 UTC | GET | pass | 402 | 53 ms | — |
| 2026-10-08 22:40 UTC | GET | pass | 402 | 76 ms | — |
| 2026-10-07 22:40 UTC | GET | pass | 402 | 16 ms | — |
| 2026-10-06 22:40 UTC | GET | pass | 402 | 22 ms | — |
| 2026-10-06 04:41 UTC | GET | pass | 402 | 326 ms | — |
| 2026-09-30 10:30 UTC | GET | pass | 402 | 162 ms | — |
| 2026-09-25 10:30 UTC | GET | pass | 402 | 97 ms | — |
| 2026-09-20 11:24 UTC | GET | pass | 402 | 7 ms | — |
| 2026-09-17 12:35 UTC | GET | pass | 402 | 57 ms | — |
| 2026-09-14 11:24 UTC | GET | pass | 402 | 27 ms | — |
| 2026-09-10 11:24 UTC | GET | pass | 402 | 18 ms | — |
| 2026-09-06 11:24 UTC | GET | pass | 402 | 35 ms | — |
| 2026-09-01 23:14 UTC | GET | pass | 402 | 148 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 not_checked- not checked: the paid request did not answer 200, so there was no response to check against the listing's output schema.
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-08 00:022026-10-08 00:02 UTC | settled (nonce-bound) | 200 | 0xf8ab3807…7b9b | 1693 ms |
| 5000 units (≈ $0.005 USDC) · L2 not_checkedWhose 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/bf566e50-079e-41ca-9593-7ca911da62b0)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.