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 |
| Catalog 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-11-17 10:05 UTC |
| Catalog-reported calls / payers (30d) | 16 / 9 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-11-16 16:40 UTC | GET | pass | 402 | 156 ms | — |
| 2026-11-13 04:40 UTC | GET | pass | 402 | 173 ms | — |
| 2026-11-10 22:40 UTC | GET | pass | 402 | 76 ms | — |
| 2026-11-08 22:40 UTC | GET | pass | 402 | 352 ms | — |
| 2026-11-06 16:40 UTC | GET | pass | 402 | 47 ms | — |
| 2026-11-04 13:40 UTC | GET | pass | 402 | 294 ms | — |
| 2026-11-01 13:40 UTC | GET | pass | 402 | 82 ms | — |
| 2026-10-30 13:40 UTC | GET | pass | 402 | 55 ms | — |
| 2026-10-28 13:40 UTC | GET | pass | 402 | 80 ms | — |
| 2026-10-26 18:40 UTC | GET | pass | 402 | 280 ms | — |
| 2026-10-25 00:40 UTC | GET | pass | 402 | 61 ms | — |
| 2026-10-22 22:40 UTC | GET | pass | 402 | 59 ms | — |
| 2026-10-21 13:40 UTC | GET | pass | 402 | 33 ms | — |
| 2026-10-20 04:40 UTC | GET | pass | 402 | 851 ms | — |
| 2026-10-18 13:40 UTC | GET | pass | 402 | 220 ms | — |
| 2026-10-17 04:40 UTC | GET | pass | 402 | 352 ms | — |
| 2026-10-15 15:40 UTC | GET | pass | 402 | 42 ms | — |
| 2026-10-14 12:40 UTC | GET | pass | 402 | 347 ms | — |
| 2026-10-12 21:40 UTC | GET | pass | 402 | 2055 ms | — |
| 2026-10-11 21:40 UTC | GET | pass | 402 | 358 ms | — |
| 2026-10-10 21:40 UTC | GET | pass | 402 | 2133 ms | — |
| 2026-10-09 21:40 UTC | GET | pass | 402 | 2159 ms | — |
| 2026-10-08 16:40 UTC | GET | pass | 402 | 222 ms | — |
| 2026-10-07 16:40 UTC | GET | pass | 402 | 40 ms | — |
| 2026-10-06 16:40 UTC | GET | pass | 402 | 93 ms | — |
| 2026-10-05 04:40 UTC | GET | pass | 402 | 2001 ms | — |
| 2026-10-04 13:40 UTC | GET | pass | 402 | 34 ms | — |
| 2026-10-03 16:40 UTC | GET | pass | 402 | 242 ms | — |
| 2026-10-02 16:40 UTC | GET | pass | 402 | 436 ms | — |
| 2026-10-01 22:40 UTC | GET | pass | 402 | 352 ms | — |
3.L1 — real purchases
5 of 5 paid attempts settled on-chain, and 5 of those also returned a deliverable 2xx response (delivered: other than 202 Accepted with a non-empty body). 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 matched the one-time value stored for that purchase, so the transaction is the one for this purchase. Stellar is not in this count. The Stellar re-read checks payer, payee, amount and asset. A row reads as amount + payee when the re-read matched payer, payee, amount and asset and did not bind a one-time value. That tier holds rows from before 2026-09-04 and Stellar rows. They keep the settled label rather than being demoted (methodology). settled is the transfer vet402 confirmed on-chain. delivered is a 2xx other than 202 with a non-empty body. A settled row whose paid request answered 5xx counts as settled and not as delivered. definitions.
Terms in this table
settled (nonce-bound)- vet402 re-read the transfer on-chain in that chain's pinned settlement asset, and the on-chain re-read matched the one-time value stored for that purchase, so the transaction is the one for this purchase. Stellar is not in this count.
settled (amount + payee)- vet402 re-read the transfer on-chain in that chain's pinned settlement asset: the on-chain re-read matched payer, payee, amount and asset and did not bind a one-time value (rows before 2026-09-04, and Stellar).
L2 no_declaration- the listing's output schema gave vet402 nothing to check this response against (no schema, a schema with no required keys and no example properties, or example properties with a content type that is not JSON). An output example in the 402 (extensions.bazaar.info.output.example) counts as a declaration. When the catalog also declares an output, the example's top-level keys are required. When it does not, vet402 checks that the response is a JSON object or array, and the record page reads match (no required keys).
Stage delivered- vet402 re-read the payment on the chain and the paid request returned HTTP 2xx other than 202 Accepted with a body vet402 did not record as empty.
Whose side- the same words as the seller page: seller's side only after failures on two different days (UTC), marked “attribution under review”; vet402's side; or not sorted (the rules).
| Attempted at | Result | HTTP | On-chain tx | Payment chain | Latency |
|---|---|---|---|---|---|
| 10-22 21:312026-10-22 21:31 UTC | settled (nonce-bound) | 200 | 0x5a8928ba…465d | Base | 1038 ms |
| 1000 units (≈ $0.001 USDC) · L2 no_declarationWhose side: no failure (delivered)Stage: delivered | |||||
| 09-16 18:002026-09-16 18:00 UTC | settled (nonce-bound) | 200 | 0x3ebb7f14…b37a | Base | 1178 ms |
| 1000 units (≈ $0.001 USDC) · L2 no_declarationWhose side: no failure (delivered)Stage: delivered | |||||
| 09-10 12:082026-09-10 12:08 UTC | settled (nonce-bound) | 200 | 0x6b9048c9…1023 | Base | 1264 ms |
| 1000 units (≈ $0.001 USDC) · L2 no_declarationWhose side: no failure (delivered)Stage: delivered | |||||
| 08-31 12:082026-08-31 12:08 UTC | settled (amount + payee) | 200 | 0x86365f5e…96ad | Base | 1263 ms |
| 1000 units (≈ $0.001 USDC) · L2 no_declarationWhose side: no failure (delivered)Stage: delivered | |||||
| 08-24 23:392026-08-24 23:39 UTC | settled (amount + payee) | 200 | 0x53da8d5b…e6a0 | Base | 1554 ms |
| 1000 units (≈ $0.001 USDC) · L2 no_declarationWhose side: no failure (delivered)Stage: delivered | |||||
Add this badge to your docs
Run this endpoint? Show the settle-through record vet402 measured — the badge reads 5/5 settled · 5 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
A dispute does not start a purchase. The signed dispute route runs one fresh L0 check, an unpaid request.
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. A dispute filed on the record form puts an active listing on a priority list. L0 runs probe that list before their ordinary queue, one run at a time. A listing whose URL has an unfilled path parameter is not put on that list. One run measures up to 50 priority listings, at most 5 from one site. Published fails whose catalog declaration changed, or that rest on probes recorded under earlier rules, take places first, and disputes fill the places left. A listing probed in the past 60 minutes waits for a later run. A dispute that no run reaches within 7 days leaves the list. The scheduled L0 run is at 10:30 UTC, and an L0 run at another time can measure the listing first. The record stays on this page. When a run measures the listing, the new probe is added to its history. Send the dispute to support@vet402.com. Published corrections are listed at /corrections. Operators who control the receiving address can also sign a dispute via POST /api/v1/observatory/disputes (API reference). That route runs one fresh L0 check under the normal publication gate. A later purchase comes from the regular schedule.