x402.ottoai.services/protocol-revenue-leaders
1.Catalog declaration
| Resource URL | https://x402.ottoai.services/protocol-revenue-leaders |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0x0e84ddedaae6a779c462c22a59f301ec31b6b808 |
| Declared price (base units) | 1000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-09-30 01:03 UTC |
| Catalog-reported calls / payers (30d) | 6 / 5 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-30 16:40 UTC | GET | pass | 402 | 210 ms | — |
| 2026-09-29 22:40 UTC | GET | pass | 402 | 301 ms | — |
| 2026-09-29 04:40 UTC | GET | pass | 402 | 389 ms | — |
| 2026-09-28 13:40 UTC | GET | pass | 402 | 383 ms | — |
| 2026-09-27 16:40 UTC | GET | pass | 402 | 300 ms | — |
| 2026-09-26 22:40 UTC | GET | pass | 402 | 333 ms | — |
| 2026-09-26 04:40 UTC | GET | pass | 402 | 378 ms | — |
| 2026-09-25 13:40 UTC | GET | pass | 402 | 231 ms | — |
| 2026-09-24 16:40 UTC | GET | pass | 402 | 194 ms | — |
| 2026-09-23 22:40 UTC | GET | pass | 402 | 300 ms | — |
| 2026-09-23 04:40 UTC | GET | pass | 402 | 117 ms | — |
| 2026-09-22 13:40 UTC | GET | pass | 402 | 121 ms | — |
| 2026-09-21 16:40 UTC | GET | pass | 402 | 116 ms | — |
| 2026-09-21 04:40 UTC | GET | pass | 402 | 385 ms | — |
| 2026-09-20 13:40 UTC | GET | pass | 402 | 217 ms | — |
| 2026-09-19 16:40 UTC | GET | pass | 402 | 172 ms | — |
| 2026-09-18 22:40 UTC | GET | pass | 402 | 129 ms | — |
| 2026-09-18 04:40 UTC | GET | pass | 402 | 148 ms | — |
| 2026-09-17 16:19 UTC | GET | pass | 402 | 240 ms | — |
| 2026-09-14 11:24 UTC | GET | pass | 402 | 154 ms | — |
| 2026-09-11 11:24 UTC | GET | pass | 402 | 129 ms | — |
| 2026-09-07 11:24 UTC | GET | pass | 402 | 212 ms | — |
| 2026-09-02 11:24 UTC | GET | pass | 402 | 145 ms | — |
| 2026-08-14 08:53 UTC | GET | fail | 402 | 114 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
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 |
|---|---|---|---|---|
| 09-30 15:302026-09-30 15:30 UTC | settled (nonce-bound) | 200 | 0x87a1ff8b…b3ab | 3990 ms |
| 1000 units (≈ $0.001 USDC) · L2 matchWhose side: no failure (delivered) | ||||
| 09-24 12:012026-09-24 12:01 UTC | settled (nonce-bound) | 200 | 0xfed21ee7…c101 | 3644 ms |
| 1000 units (≈ $0.001 USDC) · L2 matchWhose side: no failure (delivered) | ||||
| 09-18 06:002026-09-18 06:00 UTC | settled (nonce-bound) | 200 | 0xfdb8779f…c457 | 4383 ms |
| 1000 units (≈ $0.001 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/aaaecfe2-18f5-43c9-b2a0-73a73d1dffc2)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.