x402-endpoints.onrender.com/macro/snapshot
1.Catalog declaration
| Resource URL | https://x402-endpoints.onrender.com/macro/snapshot |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0x1d1b81247c407521e2a01f3e21514870dcf1620f |
| Declared price (base units) | 5000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-10-01 01:03 UTC |
| Catalog-reported calls / payers (30d) | 2 / 2 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-01 04:40 UTC | GET | pass | 402 | 377 ms | — |
| 2026-09-30 13:40 UTC | GET | pass | 402 | 234 ms | — |
| 2026-09-29 16:40 UTC | GET | pass | 402 | 163 ms | — |
| 2026-09-28 22:40 UTC | GET | pass | 402 | 310 ms | — |
| 2026-09-28 04:40 UTC | GET | pass | 402 | 2170 ms | — |
| 2026-09-27 13:40 UTC | GET | pass | 402 | 500 ms | — |
| 2026-09-26 16:40 UTC | GET | pass | 402 | 350 ms | — |
| 2026-09-25 22:40 UTC | GET | pass | 402 | 252 ms | — |
| 2026-09-25 04:40 UTC | GET | pass | 402 | 523 ms | — |
| 2026-09-24 13:40 UTC | GET | pass | 402 | 480 ms | — |
| 2026-09-23 16:40 UTC | GET | pass | 402 | 464 ms | — |
| 2026-09-22 22:40 UTC | GET | pass | 402 | 390 ms | — |
| 2026-09-22 04:40 UTC | GET | pass | 402 | 479 ms | — |
| 2026-09-21 13:40 UTC | GET | pass | 402 | 339 ms | — |
| 2026-09-20 16:40 UTC | GET | pass | 402 | 547 ms | — |
| 2026-09-20 04:40 UTC | GET | pass | 402 | 342 ms | — |
| 2026-09-19 13:40 UTC | GET | pass | 402 | 287 ms | — |
| 2026-09-18 16:40 UTC | GET | pass | 402 | 348 ms | — |
| 2026-09-17 22:40 UTC | GET | pass | 402 | 175 ms | — |
| 2026-09-17 04:40 UTC | GET | pass | 402 | 161 ms | — |
| 2026-09-16 16:40 UTC | GET | pass | 402 | 207 ms | — |
| 2026-09-15 16:40 UTC | GET | pass | 402 | 358 ms | — |
| 2026-09-15 04:40 UTC | GET | pass | 402 | 424 ms | — |
| 2026-09-14 13:40 UTC | GET | pass | 402 | 518 ms | — |
| 2026-09-13 22:40 UTC | GET | pass | 402 | 607 ms | — |
| 2026-09-13 04:40 UTC | GET | pass | 402 | 935 ms | — |
| 2026-09-12 16:40 UTC | GET | pass | 402 | 627 ms | — |
| 2026-09-11 22:40 UTC | GET | pass | 402 | 530 ms | — |
| 2026-09-11 13:40 UTC | GET | pass | 402 | 308 ms | — |
| 2026-09-10 23:40 UTC | GET | pass | 402 | 220 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 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-12 06:012026-09-12 06:01 UTC | settled (nonce-bound) | 200 | 0xfac077cd…386d | 2379 ms |
| 5000 units (≈ $0.005 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 09-02 12:082026-09-02 12:08 UTC | settled (amount + payee) | 200 | 0x70213e5a…8a56 | 2447 ms |
| 5000 units (≈ $0.005 USDC) · L2 no_declarationWhose 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/6ad83468-dc8b-431a-8f96-1fc1c925448d)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.