api.utilia.ink/base/v1/fees/priority
1.Catalog declaration
| Resource URL | https://api.utilia.ink/base/v1/fees/priority |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0xbf9305e6ee38e92c296aa3fb0a844977307520fa |
| Declared price (base units) | 2000 |
| Catalog status | delisted (since 2026-09-07 01:03 UTC) |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-09-06 01:03 UTC |
| Catalog-reported calls / payers (30d) | 7 / 6 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-06 17:40 UTC | GET | fail | — | 127 ms | networkThe connection failed (refused or reset) before a response. |
| 2026-09-06 05:40 UTC | GET | unverified | — | 280 ms | tlsThe TLS handshake failed; vet402 cannot tell its own side from the seller's, so nothing is published against the seller. |
| 2026-09-05 17:40 UTC | GET | unverified | — | 227 ms | tlsThe TLS handshake failed; vet402 cannot tell its own side from the seller's, so nothing is published against the seller. |
| 2026-09-05 05:40 UTC | GET | pass | 402 | 348 ms | — |
| 2026-09-04 17:40 UTC | GET | pass | 402 | 665 ms | — |
| 2026-09-04 05:40 UTC | GET | pass | 402 | 348 ms | — |
| 2026-09-03 17:40 UTC | GET | pass | 402 | 332 ms | — |
| 2026-09-03 05:40 UTC | GET | pass | 402 | 340 ms | — |
| 2026-09-02 17:40 UTC | GET | pass | 402 | 357 ms | — |
| 2026-09-02 05:40 UTC | GET | pass | 402 | 428 ms | — |
| 2026-09-01 23:40 UTC | GET | pass | 402 | 437 ms | — |
| 2026-08-14 08:53 UTC | GET | pass | 402 | 101 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 (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 |
|---|---|---|---|---|
| 08-27 12:312026-08-27 12:31 UTC | settled (amount + payee) | 200 | 0x297d7313…430a | 1589 ms |
| 2000 units (≈ $0.002 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 08-20 12:562026-08-20 12:56 UTC | settled (amount + payee) | 200 | 0x1b295f3d…deaa | 1810 ms |
| 2000 units (≈ $0.002 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 08-14 09:562026-08-14 09:56 UTC | settled (amount + payee) | 200 | 0x57a3b9af…2a69 | 1660 ms |
| 2000 units (≈ $0.002 USDC) · L2 no_declarationWhose 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/ecda8c6c-337c-4e5d-ab94-65d1f46a6526)4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-09-07 | delisted | {"status":"active"} | {"status":"delisted"} |
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.