x402.tbs-digital.com/crypto/bundle
1.Catalog declaration
| Resource URL | https://x402.tbs-digital.com/crypto/bundle |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0xd6fce15298fc9d60f867d9455d497177da9bfb0a |
| Declared price (base units) | 1000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-10-03 01:04 UTC |
| Catalog-reported calls / payers (30d) | 6 / 6 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-03 04:40 UTC | GET | pass | 402 | 2313 ms | — |
| 2026-10-02 04:40 UTC | GET | pass | 402 | 436 ms | — |
| 2026-10-01 13:40 UTC | GET | pass | 402 | 504 ms | — |
| 2026-09-30 16:40 UTC | GET | pass | 402 | 510 ms | — |
| 2026-09-29 22:40 UTC | GET | pass | 402 | 413 ms | — |
| 2026-09-29 04:40 UTC | GET | pass | 402 | 458 ms | — |
| 2026-09-28 13:40 UTC | GET | pass | 402 | 503 ms | — |
| 2026-09-27 16:40 UTC | GET | pass | 402 | 413 ms | — |
| 2026-09-26 22:40 UTC | GET | pass | 402 | 488 ms | — |
| 2026-09-26 04:40 UTC | GET | pass | 402 | 502 ms | — |
| 2026-09-25 13:40 UTC | GET | pass | 402 | 576 ms | — |
| 2026-09-24 16:40 UTC | GET | pass | 402 | 408 ms | — |
| 2026-09-23 22:40 UTC | GET | pass | 402 | 473 ms | — |
| 2026-09-23 04:40 UTC | GET | pass | 402 | 346 ms | — |
| 2026-09-22 13:40 UTC | GET | pass | 402 | 410 ms | — |
| 2026-09-21 16:40 UTC | GET | pass | 402 | 473 ms | — |
| 2026-09-21 04:40 UTC | GET | pass | 402 | 340 ms | — |
| 2026-09-20 13:40 UTC | GET | pass | 402 | 443 ms | — |
| 2026-09-19 16:40 UTC | GET | pass | 402 | 440 ms | — |
| 2026-09-18 22:40 UTC | GET | pass | 402 | 368 ms | — |
| 2026-09-18 04:40 UTC | GET | pass | 402 | 781 ms | — |
| 2026-09-17 13:40 UTC | GET | pass | 402 | 563 ms | — |
| 2026-09-16 22:40 UTC | GET | pass | 402 | 543 ms | — |
| 2026-09-15 22:40 UTC | GET | pass | 402 | 534 ms | — |
| 2026-09-15 13:40 UTC | GET | pass | 402 | 778 ms | — |
| 2026-09-14 16:40 UTC | GET | pass | 402 | 368 ms | — |
| 2026-09-13 22:40 UTC | GET | pass | 402 | 474 ms | — |
| 2026-09-13 13:40 UTC | GET | pass | 402 | 2157 ms | — |
| 2026-09-12 22:40 UTC | GET | pass | 402 | 441 ms | — |
| 2026-09-12 04:40 UTC | GET | pass | 402 | 490 ms | — |
3.L1 — real purchases
4 of 4 paid attempts settled on-chain, and 4 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-10 12:082026-09-10 12:08 UTC | settled (nonce-bound) | 200 | 0x831ec0d7…6a44 | 2281 ms |
| 1000 units (≈ $0.001 USDC) · L2 matchWhose side: no failure (delivered) | ||||
| 08-29 12:082026-08-29 12:08 UTC | settled (amount + payee) | 200 | 0x3466789b…91bf | 3075 ms |
| 1000 units (≈ $0.001 USDC) · L2 matchWhose side: no failure (delivered) | ||||
| 08-21 08:332026-08-21 08:33 UTC | settled (amount + payee) | 200 | 0x92b78e81…f856 | 2157 ms |
| 1000 units (≈ $0.001 USDC) · L2 matchWhose side: no failure (delivered) | ||||
| 08-14 10:052026-08-14 10:05 UTC | settled (amount + payee) | 200 | 0xf09a1a32…13cb | 2836 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 4/4 settled · 4 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/0d86f1c9-0d97-4e47-ab2f-7e4686ce88cf)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.