x402.shizu.me/llama/protocols
1.Catalog declaration
| Resource URL | https://x402.shizu.me/llama/protocols |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0x217e5fe265eb78b29067bf8324ef03a7d8e167c4 |
| Declared price (base units) | 8000 |
| Catalog status | delisted (since 2026-09-30 01:03 UTC) |
| First seen / last seen | 2026-08-14 08:52 UTC / 2026-09-29 01:03 UTC |
| Catalog-reported calls / payers (30d) | 1 / 1 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-29 16:40 UTC | GET | pass | 402 | 454 ms | — |
| 2026-09-28 22:40 UTC | GET | pass | 402 | 470 ms | — |
| 2026-09-28 04:40 UTC | GET | pass | 402 | 461 ms | — |
| 2026-09-27 13:40 UTC | GET | pass | 402 | 591 ms | — |
| 2026-09-26 16:40 UTC | GET | pass | 402 | 482 ms | — |
| 2026-09-25 22:40 UTC | GET | pass | 402 | 687 ms | — |
| 2026-09-25 04:40 UTC | GET | pass | 402 | 533 ms | — |
| 2026-09-24 13:40 UTC | GET | pass | 402 | 474 ms | — |
| 2026-09-23 16:40 UTC | GET | pass | 402 | 575 ms | — |
| 2026-09-22 22:40 UTC | GET | pass | 402 | 500 ms | — |
| 2026-09-22 04:40 UTC | GET | pass | 402 | 803 ms | — |
| 2026-09-21 13:40 UTC | GET | pass | 402 | 505 ms | — |
| 2026-09-20 16:40 UTC | GET | pass | 402 | 490 ms | — |
| 2026-09-19 22:40 UTC | GET | pass | 402 | 617 ms | — |
| 2026-09-19 04:40 UTC | GET | pass | 402 | 382 ms | — |
| 2026-09-18 16:40 UTC | GET | pass | 402 | 413 ms | — |
| 2026-09-17 22:40 UTC | GET | pass | 402 | 486 ms | — |
| 2026-09-17 04:40 UTC | GET | pass | 402 | 445 ms | — |
| 2026-09-16 16:40 UTC | GET | pass | 402 | 712 ms | — |
| 2026-09-15 16:40 UTC | GET | pass | 402 | 485 ms | — |
| 2026-09-14 22:40 UTC | GET | pass | 402 | 484 ms | — |
| 2026-09-14 13:40 UTC | GET | pass | 402 | 565 ms | — |
| 2026-09-13 16:40 UTC | GET | pass | 402 | 479 ms | — |
| 2026-09-13 04:40 UTC | GET | pass | 402 | 564 ms | — |
| 2026-09-12 13:40 UTC | GET | pass | 402 | 475 ms | — |
| 2026-09-11 22:40 UTC | GET | pass | 402 | 873 ms | — |
| 2026-09-11 13:40 UTC | GET | pass | 402 | 512 ms | — |
| 2026-09-10 17:40 UTC | GET | pass | 402 | 431 ms | — |
| 2026-09-10 05:40 UTC | GET | pass | 402 | 792 ms | — |
| 2026-09-09 17:40 UTC | GET | pass | 402 | 463 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 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-08 01:002026-09-08 01:00 UTC | settled (nonce-bound) | 200 | 0x1d937f4c…e929 | 1926 ms |
| 8000 units (≈ $0.008 USDC) · L2 no_declarationWhose 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/859190a7-20ab-4138-9edb-972be02ae35c)4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-09-30 | 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.