api.n0brains.com/x402/macro
1.Catalog declaration
| Resource URL | https://api.n0brains.com/x402/macro |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0xc1793b8aa0d25193117ef025f145994e1c02011f |
| Declared price (base units) | 2000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-10-09 13:03 UTC |
| Catalog-reported calls / payers (30d) | 3 / 3 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-09 15:40 UTC | GET | pass | 402 | 569 ms | — |
| 2026-09-29 16:40 UTC | GET | pass | 402 | 716 ms | — |
| 2026-09-28 22:40 UTC | GET | fail | 530 | 168 ms | no_402HTTP 530 instead of 402 to an unpaid GET. |
| 2026-09-28 04:40 UTC | GET | pass | 402 | 302 ms | — |
| 2026-09-27 13:40 UTC | GET | pass | 402 | 282 ms | — |
| 2026-09-26 16:40 UTC | GET | pass | 402 | 2139 ms | — |
| 2026-09-25 22:40 UTC | GET | pass | 402 | 348 ms | — |
| 2026-09-25 04:40 UTC | GET | pass | 402 | 171 ms | — |
| 2026-09-24 13:40 UTC | GET | pass | 402 | 295 ms | — |
| 2026-09-23 16:40 UTC | GET | pass | 402 | 352 ms | — |
| 2026-09-22 22:40 UTC | GET | pass | 402 | 268 ms | — |
| 2026-09-22 04:40 UTC | GET | pass | 402 | 184 ms | — |
| 2026-09-21 13:40 UTC | GET | pass | 402 | 169 ms | — |
| 2026-09-20 16:40 UTC | GET | pass | 402 | 178 ms | — |
| 2026-09-19 22:40 UTC | GET | pass | 402 | 179 ms | — |
| 2026-09-19 13:40 UTC | GET | pass | 402 | 146 ms | — |
| 2026-09-18 16:40 UTC | GET | pass | 402 | 2196 ms | — |
| 2026-09-17 22:40 UTC | GET | pass | 402 | 307 ms | — |
| 2026-09-17 04:40 UTC | GET | pass | 402 | 200 ms | — |
| 2026-09-16 16:40 UTC | GET | pass | 402 | 408 ms | — |
| 2026-09-15 16:40 UTC | GET | pass | 402 | 1502 ms | — |
| 2026-09-15 04:40 UTC | GET | pass | 402 | 548 ms | — |
| 2026-09-14 13:40 UTC | GET | pass | 402 | 124 ms | — |
| 2026-09-13 22:40 UTC | GET | pass | 402 | 449 ms | — |
| 2026-09-13 04:40 UTC | GET | pass | 402 | 427 ms | — |
| 2026-09-12 16:40 UTC | GET | pass | 402 | 417 ms | — |
| 2026-09-11 22:40 UTC | GET | pass | 402 | 453 ms | — |
| 2026-09-11 13:40 UTC | GET | pass | 402 | 632 ms | — |
| 2026-09-10 23:40 UTC | GET | pass | 402 | 925 ms | — |
| 2026-09-10 05:40 UTC | GET | pass | 402 | 614 ms | — |
3.L1 — real purchases
3 of 3 paid attempts settled on-chain, and 3 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-16 12:092026-09-16 12:09 UTC | settled (nonce-bound) | 200 | 0xd07b1b15…15c5 | 1336 ms |
| 2000 units (≈ $0.002 USDC) · L2 matchWhose side: no failure (delivered) | ||||
| 09-10 01:012026-09-10 01:01 UTC | settled (nonce-bound) | 200 | 0xcf8876f3…4770 | 1340 ms |
| 2000 units (≈ $0.002 USDC) · L2 matchWhose side: no failure (delivered) | ||||
| 09-02 07:012026-09-02 07:01 UTC | settled (amount + payee) | 200 | 0x1a077c4f…09e9 | 1216 ms |
| 2000 units (≈ $0.002 USDC) · L2 matchWhose side: no failure (delivered) | ||||
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 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/a4c6a284-d4b3-4f0c-9fa1-3be3c2b0d255)4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-10-09 | relisted | {"status":"delisted"} | {"status":"active"} |
| 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.