rubric-protocol.com/v1/x402/hedera-facts/gas-fees
1.Catalog declaration
| Resource URL | https://rubric-protocol.com/v1/x402/hedera-facts/gas-fees |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0xab6731a0bcdf511c2842c768a03448075ab654ca |
| Declared price (base units) | 1000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-10-02 01:04 UTC |
| Catalog-reported calls / payers (30d) | 12 / 7 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-02 16:40 UTC | GET | pass | 402 | 436 ms | — |
| 2026-10-01 22:40 UTC | GET | pass | 402 | 352 ms | — |
| 2026-10-01 04:40 UTC | GET | pass | 402 | 69 ms | — |
| 2026-09-30 13:40 UTC | GET | pass | 402 | 1897 ms | — |
| 2026-09-29 16:40 UTC | GET | pass | 402 | 88 ms | — |
| 2026-09-28 22:40 UTC | GET | pass | 402 | 254 ms | — |
| 2026-09-28 04:40 UTC | GET | pass | 402 | 403 ms | — |
| 2026-09-27 13:40 UTC | GET | pass | 402 | 334 ms | — |
| 2026-09-26 16:40 UTC | GET | pass | 402 | 35 ms | — |
| 2026-09-25 22:40 UTC | GET | pass | 402 | 26 ms | — |
| 2026-09-25 04:40 UTC | GET | pass | 402 | 135 ms | — |
| 2026-09-24 13:40 UTC | GET | pass | 402 | 52 ms | — |
| 2026-09-23 16:40 UTC | GET | pass | 402 | 98 ms | — |
| 2026-09-22 22:40 UTC | GET | pass | 402 | 45 ms | — |
| 2026-09-22 13:40 UTC | GET | pass | 402 | 116 ms | — |
| 2026-09-21 16:40 UTC | GET | pass | 402 | 72 ms | — |
| 2026-09-20 22:40 UTC | GET | pass | 402 | 157 ms | — |
| 2026-09-20 04:40 UTC | GET | pass | 402 | 24 ms | — |
| 2026-09-19 13:40 UTC | GET | pass | 402 | 133 ms | — |
| 2026-09-18 16:40 UTC | GET | pass | 402 | 24 ms | — |
| 2026-09-17 22:40 UTC | GET | pass | 402 | 132 ms | — |
| 2026-09-17 13:40 UTC | GET | pass | 402 | 86 ms | — |
| 2026-09-16 16:40 UTC | GET | pass | 402 | 23 ms | — |
| 2026-09-15 22:40 UTC | GET | pass | 402 | 477 ms | — |
| 2026-09-15 04:40 UTC | GET | pass | 402 | 46 ms | — |
| 2026-09-14 13:40 UTC | GET | pass | 402 | 97 ms | — |
| 2026-09-13 22:40 UTC | GET | pass | 402 | 74 ms | — |
| 2026-09-13 04:40 UTC | GET | pass | 402 | 123 ms | — |
| 2026-09-12 16:40 UTC | GET | pass | 402 | 195 ms | — |
| 2026-09-12 04:40 UTC | GET | pass | 402 | 97 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:002026-09-16 18:00 UTC | settled (nonce-bound) | 200 | 0x3ebb7f14…b37a | 1178 ms |
| 1000 units (≈ $0.001 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 09-10 12:082026-09-10 12:08 UTC | settled (nonce-bound) | 200 | 0x6b9048c9…1023 | 1264 ms |
| 1000 units (≈ $0.001 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 08-31 12:082026-08-31 12:08 UTC | settled (amount + payee) | 200 | 0x86365f5e…96ad | 1263 ms |
| 1000 units (≈ $0.001 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 08-24 23:392026-08-24 23:39 UTC | settled (amount + payee) | 200 | 0x53da8d5b…e6a0 | 1554 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 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/8c6b6b95-6b8a-44a7-87f6-b177eb3a8496)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.