rpc.nodeflare.app/base/x402
1.Catalog declaration
| Resource URL | https://rpc.nodeflare.app/base/x402 |
| Source | cdp_bazaar |
| Declared method | POST |
| Network | eip155:8453 |
| Receiving address | 0x9d86e0e74333b297b1d0b6ba30d2ed1b5f01f296 |
| 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) | 45 / 9 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-28 22:40 UTC | POST | pass | 402 | 387 ms | — |
| 2026-09-28 04:40 UTC | POST | pass | 402 | 217 ms | — |
| 2026-09-27 16:40 UTC | POST | pass | 402 | 649 ms | — |
| 2026-09-26 22:40 UTC | POST | pass | 402 | 150 ms | — |
| 2026-09-26 04:40 UTC | POST | pass | 402 | 2161 ms | — |
| 2026-09-25 13:40 UTC | POST | pass | 402 | 507 ms | — |
| 2026-09-24 16:40 UTC | POST | pass | 402 | 585 ms | — |
| 2026-09-23 22:40 UTC | POST | pass | 402 | 140 ms | — |
| 2026-09-23 04:40 UTC | POST | pass | 402 | 382 ms | — |
| 2026-09-22 13:40 UTC | POST | pass | 402 | 289 ms | — |
| 2026-09-21 16:40 UTC | POST | pass | 402 | 285 ms | — |
| 2026-09-20 22:40 UTC | POST | pass | 402 | 1962 ms | — |
| 2026-09-20 04:40 UTC | POST | pass | 402 | 641 ms | — |
| 2026-09-19 13:40 UTC | POST | pass | 402 | 118 ms | — |
| 2026-09-18 22:40 UTC | POST | pass | 402 | 592 ms | — |
| 2026-09-18 04:40 UTC | POST | pass | 402 | 2161 ms | — |
| 2026-09-17 13:40 UTC | POST | pass | 402 | 129 ms | — |
| 2026-09-16 16:40 UTC | POST | pass | 402 | 251 ms | — |
| 2026-09-15 22:40 UTC | POST | pass | 402 | 2128 ms | — |
| 2026-09-15 04:40 UTC | POST | pass | 402 | 239 ms | — |
| 2026-09-14 16:40 UTC | POST | pass | 402 | 300 ms | — |
| 2026-09-13 22:40 UTC | POST | pass | 402 | 367 ms | — |
| 2026-09-13 13:40 UTC | POST | pass | 402 | 144 ms | — |
| 2026-09-12 16:40 UTC | POST | pass | 402 | 47 ms | — |
| 2026-09-12 04:40 UTC | POST | pass | 402 | 565 ms | — |
| 2026-09-11 16:40 UTC | POST | pass | 402 | 180 ms | — |
| 2026-09-10 23:40 UTC | POST | pass | 402 | 439 ms | — |
| 2026-09-10 14:40 UTC | POST | pass | 402 | 294 ms | — |
| 2026-09-09 23:40 UTC | POST | pass | 402 | 365 ms | — |
| 2026-09-09 05:40 UTC | POST | pass | 402 | 369 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 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-16 18:012026-09-16 18:01 UTC | settled (nonce-bound) | 200 | 0x05104416…fb0e | 1358 ms |
| 1000 units (≈ $0.001 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 09-10 01:022026-09-10 01:02 UTC | settled (nonce-bound) | 200 | 0xd873b435…8a73 | 2466 ms |
| 1000 units (≈ $0.001 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 09-02 12:082026-09-02 12:08 UTC | settled (amount + payee) | 200 | 0xb392e31f…1452 | 1736 ms |
| 1000 units (≈ $0.001 USDC) · L2 no_declarationWhose 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/79aec767-fda7-4d77-91b0-1b98f2f8dda4)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.