402.com.tr/api/x402/gas-oracle
1.Catalog declaration
| Resource URL | https://402.com.tr/api/x402/gas-oracle |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0x973a31858f4d2125f48c880542da11a2796f12d6 |
| Declared price (base units) | 10000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-09-29 01:03 UTC |
| Catalog-reported calls / payers (30d) | 7 / 2 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-28 22:40 UTC | GET | pass | 402 | 596 ms | — |
| 2026-09-28 04:40 UTC | GET | pass | 402 | 469 ms | — |
| 2026-09-27 13:40 UTC | GET | pass | 402 | 394 ms | — |
| 2026-09-26 16:40 UTC | GET | pass | 402 | 3232 ms | — |
| 2026-09-25 22:40 UTC | GET | pass | 402 | 3276 ms | — |
| 2026-09-25 04:40 UTC | GET | pass | 402 | 1096 ms | — |
| 2026-09-24 13:40 UTC | GET | pass | 402 | 650 ms | — |
| 2026-09-23 16:40 UTC | GET | pass | 402 | 650 ms | — |
| 2026-09-22 22:40 UTC | GET | pass | 402 | 591 ms | — |
| 2026-09-22 04:40 UTC | GET | pass | 402 | 488 ms | — |
| 2026-09-21 16:40 UTC | GET | pass | 402 | 617 ms | — |
| 2026-09-20 22:40 UTC | GET | pass | 402 | 352 ms | — |
| 2026-09-20 04:40 UTC | GET | pass | 402 | 455 ms | — |
| 2026-09-19 13:40 UTC | GET | pass | 402 | 479 ms | — |
| 2026-09-18 16:40 UTC | GET | pass | 402 | 1267 ms | — |
| 2026-09-17 22:40 UTC | GET | pass | 402 | 530 ms | — |
| 2026-09-17 13:40 UTC | GET | pass | 402 | 752 ms | — |
| 2026-09-15 11:24 UTC | GET | pass | 402 | 418 ms | — |
| 2026-09-11 11:24 UTC | GET | pass | 402 | 281 ms | — |
| 2026-09-07 11:24 UTC | GET | pass | 402 | 378 ms | — |
| 2026-09-02 11:25 UTC | GET | pass | 402 | 395 ms | — |
| 2026-08-17 10:39 UTC | GET | fail | 402 | 386 ms | accepts_invalid |
3.L1 — real purchases
1 of 1 paid attempts settled with a receipt, and 1 of those also returned a 2xx response (delivered). Each settled row carries its on-chain transaction hash — the receipt is the evidence. 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.
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 | Receipt (tx) | Latency |
|---|---|---|---|---|
| 09-17 06:002026-09-17 06:00 UTC | settled (nonce-bound) | 200 | 0x108fb99e…3ae5 | 1887 ms |
| 10000 units (≈ $0.01 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
Embed this record
Run this endpoint? Show the settle-through record vet402 measured — the badge reads 1/1 settled · 1 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/478e33ba-02df-4135-89b2-64f344bc124e)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.
About the purchase at 2026-09-17T06:00:46Z (UTC). The form starts with that time; add what you saw instead.