vape-x402.vapex402.workers.dev/data/protocol_fees
1.Catalog declaration
| Resource URL | https://vape-x402.vapex402.workers.dev/data/protocol_fees |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0x8aab9a6d28e9aba2a15a613c90f24f352f0cce15 |
| Declared price (base units) | 10000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-10-06 07:55 UTC |
| Catalog-reported calls / payers (30d) | 6 / 2 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-05 22:40 UTC | GET | pass | 402 | 937 ms | — |
| 2026-10-04 16:40 UTC | GET | pass | 402 | 794 ms | — |
| 2026-10-03 16:40 UTC | GET | pass | 402 | 6614 ms | — |
| 2026-10-02 22:40 UTC | GET | pass | 402 | 720 ms | — |
| 2026-10-01 22:40 UTC | GET | pass | 402 | 640 ms | — |
| 2026-10-01 04:40 UTC | GET | pass | 402 | 324 ms | — |
| 2026-09-30 13:40 UTC | GET | pass | 402 | 525 ms | — |
| 2026-09-29 16:40 UTC | GET | pass | 402 | 513 ms | — |
| 2026-09-28 22:40 UTC | GET | pass | 402 | 758 ms | — |
| 2026-09-28 04:40 UTC | GET | pass | 402 | 864 ms | — |
| 2026-09-27 13:40 UTC | GET | pass | 402 | 807 ms | — |
| 2026-09-26 16:40 UTC | GET | pass | 402 | 822 ms | — |
| 2026-09-25 22:40 UTC | GET | pass | 402 | 566 ms | — |
| 2026-09-25 13:40 UTC | GET | pass | 402 | 1046 ms | — |
| 2026-09-24 16:40 UTC | GET | pass | 402 | 690 ms | — |
| 2026-09-23 22:40 UTC | GET | pass | 402 | 702 ms | — |
| 2026-09-23 04:40 UTC | GET | pass | 402 | 963 ms | — |
| 2026-09-22 13:40 UTC | GET | pass | 402 | 638 ms | — |
| 2026-09-21 16:40 UTC | GET | pass | 402 | 777 ms | — |
| 2026-09-20 22:40 UTC | GET | pass | 402 | 685 ms | — |
| 2026-09-20 04:40 UTC | GET | pass | 402 | 597 ms | — |
| 2026-09-19 13:40 UTC | GET | pass | 402 | 856 ms | — |
| 2026-09-18 16:40 UTC | GET | pass | 402 | 614 ms | — |
| 2026-09-17 22:40 UTC | GET | pass | 402 | 857 ms | — |
| 2026-09-17 13:40 UTC | GET | pass | 402 | 1218 ms | — |
| 2026-09-16 11:24 UTC | GET | pass | 402 | 889 ms | — |
| 2026-09-11 11:24 UTC | GET | pass | 402 | 6329 ms | — |
| 2026-09-07 11:24 UTC | GET | pass | 402 | 854 ms | — |
| 2026-09-02 11:24 UTC | GET | pass | 402 | 2345 ms | — |
| 2026-08-14 08:53 UTC | GET | fail | 402 | 131 ms | accepts_invalid402 without a payable accept in the header or the body (which part was missing was not recorded before the 2026-09-29 change). |
3.L1 — real purchases
0 of 1 paid attempts settled on-chain, and 0 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
settle_failed- vet402 signed a payment and got no settlement receipt back.
L2 not_checked- not checked: the paid request did not answer 200, so there was no response to check against the listing's output schema.
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-19 12:082026-09-19 12:08 UTC | settle_failed | 502 | — | 751 ms |
| 10000 units (≈ $0.01 USDC) · L2 not_checkedWhose side: not sorted: vet402 unproven | ||||
4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-09-16 | relisted | {"status":"delisted"} | {"status":"active"} |
| 2026-09-14 | 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.