agent402.tools/api/gas-estimate
1.Catalog declaration
| Resource URL | https://agent402.tools/api/gas-estimate |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0xabf4fabd7c416fb67202e5f9002389fc75e2a9d0 |
| Declared price (base units) | 1000 |
| Catalog status | active |
| First seen / last seen | 2026-08-27 01:15 UTC / 2026-10-20 01:01 UTC |
| Catalog-reported calls / payers (30d) | 8 / 6 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-19 13:40 UTC | GET | pass | 402 | 136 ms | — |
| 2026-10-17 22:40 UTC | GET | pass | 402 | 137 ms | — |
| 2026-10-16 12:40 UTC | GET | pass | 402 | 320 ms | — |
| 2026-10-14 21:40 UTC | GET | pass | 402 | 424 ms | — |
| 2026-10-13 15:40 UTC | GET | pass | 402 | 603 ms | — |
| 2026-10-12 12:40 UTC | GET | pass | 402 | 131 ms | — |
| 2026-10-11 12:40 UTC | GET | pass | 402 | 463 ms | — |
| 2026-10-10 12:40 UTC | GET | pass | 402 | 202 ms | — |
| 2026-10-09 12:40 UTC | GET | pass | 402 | 396 ms | — |
| 2026-10-08 04:40 UTC | GET | pass | 402 | 104 ms | — |
| 2026-10-07 04:40 UTC | GET | pass | 402 | 92 ms | — |
| 2026-10-06 04:41 UTC | GET | pass | 402 | 210 ms | — |
| 2026-10-04 22:40 UTC | GET | pass | 402 | 132 ms | — |
| 2026-10-03 22:40 UTC | GET | pass | 402 | 89 ms | — |
| 2026-10-03 04:40 UTC | GET | pass | 402 | 92 ms | — |
| 2026-10-02 13:40 UTC | GET | pass | 402 | 173 ms | — |
| 2026-10-01 16:40 UTC | GET | pass | 402 | 145 ms | — |
| 2026-09-30 16:40 UTC | GET | fail | 402 | 179 ms | price_mismatchDeclared 2000 of 0x8335…2913; the 402 offered 1000 of 0x8335…2913, 1000 of 0x3c49…3359, 1000 of 0xaf88…5831, 1000 of 0x7547…b603. |
| 2026-09-29 22:40 UTC | GET | fail | 402 | 87 ms | price_mismatchDeclared 2000 of 0x8335…2913; the 402 offered 1000 of 0x8335…2913, 1000 of 0x3c49…3359, 1000 of 0xaf88…5831, 1000 of 0x7547…b603. |
| 2026-09-29 07:38 UTC | GET | fail | 402 | 128 ms | price_mismatchDeclared 2000 of 0x8335…2913; the 402 offered 1000 of 0x8335…2913, 1000 of 0x3c49…3359, 1000 of 0xaf88…5831, 1000 of 0x7547…b603. |
| 2026-09-28 22:40 UTC | GET | fail | — | 10001 ms | timeoutNo response headers arrived within 10 seconds. |
| 2026-09-28 04:40 UTC | GET | fail | 402 | 86 ms | price_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change). |
| 2026-09-27 13:40 UTC | GET | fail | 402 | 261 ms | price_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change). |
| 2026-09-26 16:40 UTC | GET | fail | 402 | 170 ms | price_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change). |
| 2026-09-25 22:40 UTC | GET | fail | 402 | 1638 ms | price_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change). |
| 2026-09-25 04:40 UTC | GET | fail | 402 | 197 ms | price_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change). |
| 2026-09-24 13:40 UTC | GET | pass | 402 | 179 ms | — |
| 2026-09-23 16:40 UTC | GET | pass | 402 | 118 ms | — |
| 2026-09-23 04:40 UTC | GET | pass | 402 | 215 ms | — |
| 2026-09-22 11:25 UTC | GET | pass | 402 | 124 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.
L2 match- the response had the fields the listing's output schema declares.
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 |
|---|---|---|---|---|
| 10-18 21:302026-10-18 21:30 UTC | settled (nonce-bound) | 200 | 5dbfb4a6b2…312b | 9001 ms |
| 1000 units (≈ $0.001 USDC) · L2 matchWhose side: no failure (delivered) | ||||
| 10-11 17:002026-10-11 17:00 UTC | settled (nonce-bound) | 200 | 0x5580076a…238d | 15077 ms |
| 1000 units (≈ $0.001 USDC) · L2 matchWhose side: no failure (delivered) | ||||
| 09-23 06:002026-09-23 06:00 UTC | settled (nonce-bound) | 200 | 0xaaaa001a…c90b | 1806 ms |
| 2000 units (≈ $0.002 USDC) · L2 matchWhose 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/65687271-1205-4fb5-98c5-c88748cb416b)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.