rubric-protocol.com/v1/x402/regwatch-feed
1.Catalog declaration
| Resource URL | https://rubric-protocol.com/v1/x402/regwatch-feed |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0xab6731a0bcdf511c2842c768a03448075ab654ca |
| Declared price (base units) | 50000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-10-03 01:04 UTC |
| Catalog-reported calls / payers (30d) | 5 / 4 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-03 16:40 UTC | GET | pass | 402 | 226 ms | — |
| 2026-10-02 16:40 UTC | GET | pass | 402 | 506 ms | — |
| 2026-10-01 22:40 UTC | GET | pass | 402 | 396 ms | — |
| 2026-10-01 04:40 UTC | GET | pass | 402 | 195 ms | — |
| 2026-09-30 13:40 UTC | GET | pass | 402 | 1965 ms | — |
| 2026-09-29 16:40 UTC | GET | pass | 402 | 86 ms | — |
| 2026-09-28 22:40 UTC | GET | pass | 402 | 335 ms | — |
| 2026-09-28 04:40 UTC | GET | pass | 402 | 550 ms | — |
| 2026-09-27 13:40 UTC | GET | pass | 402 | 356 ms | — |
| 2026-09-26 16:40 UTC | GET | pass | 402 | 80 ms | — |
| 2026-09-25 22:40 UTC | GET | pass | 402 | 37 ms | — |
| 2026-09-25 04:40 UTC | GET | pass | 402 | 101 ms | — |
| 2026-09-24 13:40 UTC | GET | pass | 402 | 99 ms | — |
| 2026-09-23 16:40 UTC | GET | pass | 402 | 101 ms | — |
| 2026-09-22 22:40 UTC | GET | pass | 402 | 63 ms | — |
| 2026-09-22 13:40 UTC | GET | pass | 402 | 438 ms | — |
| 2026-09-21 16:40 UTC | GET | pass | 402 | 80 ms | — |
| 2026-09-20 22:40 UTC | GET | pass | 402 | 42 ms | — |
| 2026-09-20 04:40 UTC | GET | pass | 402 | 32 ms | — |
| 2026-09-19 13:40 UTC | GET | pass | 402 | 37 ms | — |
| 2026-09-18 16:40 UTC | GET | pass | 402 | 47 ms | — |
| 2026-09-17 22:40 UTC | GET | pass | 402 | 299 ms | — |
| 2026-09-17 13:40 UTC | GET | pass | 402 | 1881 ms | — |
| 2026-09-16 16:40 UTC | GET | pass | 402 | 62 ms | — |
| 2026-09-15 22:40 UTC | GET | pass | 402 | 343 ms | — |
| 2026-09-15 04:40 UTC | GET | pass | 402 | 62 ms | — |
| 2026-09-14 13:40 UTC | GET | pass | 402 | 83 ms | — |
| 2026-09-13 22:40 UTC | GET | pass | 402 | 66 ms | — |
| 2026-09-13 04:40 UTC | GET | pass | 402 | 104 ms | — |
| 2026-09-12 16:40 UTC | GET | pass | 402 | 202 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 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 | 0x474cf68b…f494 | 1080 ms |
| 50000 units (≈ $0.05 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 09-10 12:082026-09-10 12:08 UTC | settled (nonce-bound) | 200 | 0x11d2b52a…9311 | 1116 ms |
| 50000 units (≈ $0.05 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 08-28 12:202026-08-28 12:20 UTC | settled (amount + payee) | 200 | 0xe32deb3a…7969 | 1296 ms |
| 50000 units (≈ $0.05 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 08-21 12:212026-08-21 12:21 UTC | settled (amount + payee) | 200 | 0xb29c22fe…6016 | 1252 ms |
| 50000 units (≈ $0.05 USDC) · L2 no_declarationWhose 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/84a4cda6-ba2d-4f9d-a378-a62ca238ebce)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.