gblin.digital/api/x402/attestation
1.Catalog declaration
| Resource URL | https://gblin.digital/api/x402/attestation |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0x0eba5d314f4f5dcb7a094953fa9311a45172dd1b |
| Declared price (base units) | 3000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-09-05 01:03 UTC |
| Catalog-reported calls / payers (30d) | 9 / 4 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-04 23:40 UTC | GET | pass | 402 | 83 ms | — |
| 2026-09-04 14:40 UTC | GET | pass | 402 | 181 ms | — |
| 2026-09-04 05:40 UTC | GET | pass | 402 | 334 ms | — |
| 2026-09-03 17:40 UTC | GET | pass | 402 | 516 ms | — |
| 2026-09-03 05:40 UTC | GET | pass | 402 | 163 ms | — |
| 2026-09-02 17:40 UTC | GET | pass | 402 | 266 ms | — |
| 2026-09-02 05:40 UTC | GET | pass | 402 | 524 ms | — |
| 2026-09-01 23:40 UTC | GET | pass | 402 | 254 ms | — |
| 2026-08-14 08:53 UTC | GET | pass | 402 | 49 ms | — |
3.L1 — real purchases
3 of 3 paid attempts settled with a receipt, and 3 of those also returned a 2xx response (delivered). Each settled row carries its on-chain transaction hash — the receipt is the evidence. 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 4xx or 5xx counts as settled and not as delivered — definitions.
| Attempted at | Result | HTTP | Receipt (tx) | Latency |
|---|---|---|---|---|
| 08-29 12:072026-08-29 12:07 UTC | settled (amount + payee) | 200 | 0x462e875b…7475 | 3180 ms |
| 3000 units (≈ $0.003 USDC) · L2 no_declaration | ||||
| 08-21 08:322026-08-21 08:32 UTC | settled (amount + payee) | 200 | 0xf7191da3…bc00 | 1191 ms |
| 3000 units (≈ $0.003 USDC) · L2 no_declaration | ||||
| 08-14 10:022026-08-14 10:02 UTC | settled (amount + payee) | 200 | 0x6ed55121…fdd7 | 1392 ms |
| 3000 units (≈ $0.003 USDC) · L2 no_declaration | ||||
Embed this record
Run this endpoint? Show the settle-through record vet402 measured — the badge reads 3/3 settled · 3 delivered and updates as the record grows. It states a measurement, not a rating.
[](https://vet402.com/observatory/e/fdbe578c-c2c6-471a-9775-5c8993046161)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.