x402-seller.onrender.com/treasury/debt
1.Catalog declaration
| Resource URL | https://x402-seller.onrender.com/treasury/debt |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0xbd61dfb01f81c91f02b0ccd51b0220e0c8918639 |
| Declared price (base units) | 1000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-09-29 01:02 UTC |
| Catalog-reported calls / payers (30d) | 2 / 2 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-29 13:40 UTC | GET | pass | 402 | 383 ms | — |
| 2026-09-28 16:40 UTC | GET | pass | 402 | 373 ms | — |
| 2026-09-27 22:40 UTC | GET | pass | 402 | 225 ms | — |
| 2026-09-27 04:40 UTC | GET | pass | 402 | 396 ms | — |
| 2026-09-26 16:40 UTC | GET | pass | 402 | 124 ms | — |
| 2026-09-25 22:40 UTC | GET | pass | 402 | 196 ms | — |
| 2026-09-25 04:40 UTC | GET | pass | 402 | 321 ms | — |
| 2026-09-24 13:40 UTC | GET | pass | 402 | 96 ms | — |
| 2026-09-23 16:40 UTC | GET | pass | 402 | 85 ms | — |
| 2026-09-22 22:40 UTC | GET | pass | 402 | 184 ms | — |
| 2026-09-22 04:40 UTC | GET | pass | 402 | 304 ms | — |
| 2026-09-21 13:40 UTC | GET | pass | 402 | 59 ms | — |
| 2026-09-20 16:40 UTC | GET | pass | 402 | 115 ms | — |
| 2026-09-19 22:40 UTC | GET | pass | 402 | 61 ms | — |
| 2026-09-19 04:40 UTC | GET | pass | 402 | 44 ms | — |
| 2026-09-18 16:40 UTC | GET | pass | 402 | 66 ms | — |
| 2026-09-17 22:40 UTC | GET | pass | 402 | 62 ms | — |
| 2026-09-17 04:40 UTC | GET | pass | 402 | 44 ms | — |
| 2026-09-16 16:40 UTC | GET | pass | 402 | 226 ms | — |
| 2026-09-15 16:40 UTC | GET | pass | 402 | 549 ms | — |
| 2026-09-14 22:40 UTC | GET | pass | 402 | 185 ms | — |
| 2026-09-14 13:40 UTC | GET | pass | 402 | 66 ms | — |
| 2026-09-13 16:40 UTC | GET | pass | 402 | 104 ms | — |
| 2026-09-13 04:40 UTC | GET | pass | 402 | 27 ms | — |
| 2026-09-12 16:40 UTC | GET | pass | 402 | 157 ms | — |
| 2026-09-11 22:40 UTC | GET | pass | 402 | 1898 ms | — |
| 2026-09-11 13:40 UTC | GET | pass | 402 | 64 ms | — |
| 2026-09-10 23:40 UTC | GET | pass | 402 | 166 ms | — |
| 2026-09-10 05:40 UTC | GET | pass | 402 | 328 ms | — |
| 2026-09-09 17:40 UTC | GET | pass | 402 | 89 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.
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 match- the response had the fields the listing's output schema declares.
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-12 00:022026-09-12 00:02 UTC | settled (nonce-bound) | 200 | 0x4373050e…4023 | 1220 ms |
| 1000 units (≈ $0.001 USDC) · L2 matchWhose side: no failure (delivered) | ||||
| 09-03 01:002026-09-03 01:00 UTC | settled (amount + payee) | 200 | 0x7de0e51b…a089 | 1365 ms |
| 1000 units (≈ $0.001 USDC) · L2 matchWhose 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/6c5d1e79-fcdd-4ac3-ad68-a3decfe48da9)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.