rubric-protocol.com/v1/x402/hedera-facts/all
1.Catalog declaration
| Resource URL | https://rubric-protocol.com/v1/x402/hedera-facts/all |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0xab6731a0bcdf511c2842c768a03448075ab654ca |
| Declared price (base units) | 3000 |
| Catalog status | active |
| First seen / last seen | 2026-08-22 01:53 UTC / 2026-10-20 01:01 UTC |
| Catalog-reported calls / payers (30d) | 6 / 5 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-18 16:40 UTC | GET | pass | 402 | 156 ms | — |
| 2026-10-17 13:40 UTC | GET | pass | 402 | 380 ms | — |
| 2026-10-15 21:40 UTC | GET | pass | 402 | 188 ms | — |
| 2026-10-14 15:40 UTC | GET | pass | 402 | 87 ms | — |
| 2026-10-13 03:40 UTC | GET | pass | 402 | 66 ms | — |
| 2026-10-12 03:40 UTC | GET | pass | 402 | 79 ms | — |
| 2026-10-11 03:40 UTC | GET | pass | 402 | 87 ms | — |
| 2026-10-10 03:40 UTC | GET | pass | 402 | 164 ms | — |
| 2026-10-08 22:40 UTC | GET | pass | 402 | 164 ms | — |
| 2026-10-07 22:40 UTC | GET | pass | 402 | 90 ms | — |
| 2026-10-06 22:40 UTC | GET | pass | 402 | 141 ms | — |
| 2026-10-05 22:40 UTC | GET | pass | 402 | 90 ms | — |
| 2026-10-04 16:40 UTC | GET | pass | 402 | 2054 ms | — |
| 2026-10-03 22:40 UTC | GET | pass | 402 | 66 ms | — |
| 2026-10-03 04:40 UTC | GET | pass | 402 | 97 ms | — |
| 2026-10-02 04:40 UTC | GET | pass | 402 | 199 ms | — |
| 2026-10-01 13:40 UTC | GET | pass | 402 | 173 ms | — |
| 2026-09-30 16:40 UTC | GET | pass | 402 | 109 ms | — |
| 2026-09-29 22:40 UTC | GET | pass | 402 | 214 ms | — |
| 2026-09-29 04:40 UTC | GET | pass | 402 | 180 ms | — |
| 2026-09-28 13:40 UTC | GET | pass | 402 | 185 ms | — |
| 2026-09-27 16:40 UTC | GET | pass | 402 | 146 ms | — |
| 2026-09-26 22:40 UTC | GET | pass | 402 | 88 ms | — |
| 2026-09-26 04:40 UTC | GET | pass | 402 | 239 ms | — |
| 2026-09-25 13:40 UTC | GET | pass | 402 | 355 ms | — |
| 2026-09-24 16:40 UTC | GET | pass | 402 | 75 ms | — |
| 2026-09-23 22:40 UTC | GET | pass | 402 | 112 ms | — |
| 2026-09-23 04:40 UTC | GET | pass | 402 | 142 ms | — |
| 2026-09-22 13:40 UTC | GET | pass | 402 | 65 ms | — |
| 2026-09-21 22:40 UTC | GET | pass | 402 | 147 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 mismatch- the content type was not JSON although the listing marks required keys, or the body read in full did not parse as JSON, was JSON but not an object or array, or lacked a key the listing marks as required.
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:002026-09-16 18:00 UTC | settled (nonce-bound) | 200 | 0xd4a1172a…4444 | 3716 ms |
| 3000 units (≈ $0.003 USDC) · L2 mismatchWhose side: no failure (delivered) | ||||
| 09-10 12:082026-09-10 12:08 UTC | settled (nonce-bound) | 200 | 0x2049e368…4eb8 | 2113 ms |
| 3000 units (≈ $0.003 USDC) · L2 mismatchWhose side: no failure (delivered) | ||||
| 09-04 07:022026-09-04 07:02 UTC | settled (amount + payee) | 200 | 0x8a984706…d7bc | 1676 ms |
| 3000 units (≈ $0.003 USDC) · L2 mismatchWhose 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/8f5bda3b-d4af-4bb2-a8cc-5d4d49b89a9f)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.