x402.ottoai.services/base-season
1.Catalog declaration
| Resource URL | https://x402.ottoai.services/base-season |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0x0e84ddedaae6a779c462c22a59f301ec31b6b808 |
| Declared price (base units) | 2000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-09-29 01:02 UTC |
| Catalog-reported calls / payers (30d) | 305 / 11 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-28 16:40 UTC | GET | pass | 402 | 272 ms | — |
| 2026-09-27 22:40 UTC | GET | pass | 402 | 356 ms | — |
| 2026-09-27 04:40 UTC | GET | pass | 402 | 487 ms | — |
| 2026-09-26 13:40 UTC | GET | pass | 402 | 577 ms | — |
| 2026-09-25 16:40 UTC | GET | pass | 402 | 418 ms | — |
| 2026-09-24 22:40 UTC | GET | pass | 402 | 133 ms | — |
| 2026-09-24 04:40 UTC | GET | pass | 402 | 259 ms | — |
| 2026-09-23 13:40 UTC | GET | pass | 402 | 200 ms | — |
| 2026-09-22 16:40 UTC | GET | pass | 402 | 141 ms | — |
| 2026-09-21 22:40 UTC | GET | pass | 402 | 195 ms | — |
| 2026-09-21 04:40 UTC | GET | pass | 402 | 2183 ms | — |
| 2026-09-20 13:40 UTC | GET | pass | 402 | 2127 ms | — |
| 2026-09-19 22:40 UTC | GET | pass | 402 | 766 ms | — |
| 2026-09-17 16:19 UTC | GET | pass | 402 | 317 ms | — |
| 2026-09-14 11:24 UTC | GET | pass | 402 | 142 ms | — |
| 2026-09-11 11:24 UTC | GET | pass | 402 | 120 ms | — |
| 2026-09-07 11:24 UTC | GET | pass | 402 | 330 ms | — |
| 2026-09-02 11:24 UTC | GET | pass | 402 | 157 ms | — |
| 2026-08-14 08:52 UTC | GET | fail | 402 | 160 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
2 of 2 paid attempts settled with a receipt, and 0 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.
A row marked tx from our index came back with no settlement receipt from the seller. Our own index of on-chain settlements found the transfer afterwards — our payer, this endpoint's payee, the exact amount, inside the time window — and the row goes through the same on-chain re-read as any other before it reads settled. The seller did not name that transaction; we did (methodology).
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 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 | Receipt (tx) | Latency |
|---|---|---|---|---|
| 09-26 06:012026-09-26 06:01 UTC | settled (nonce-bound)tx from our index | — | 0xc89f4721…b117 | 20290 ms |
| 2000 units (≈ $0.002 USDC) · L2 not_checkedWhose side: not sorted: vet402 unproven | ||||
| 09-20 00:002026-09-20 00:00 UTC | settled (nonce-bound)tx from our index | — | 0xbdc463e5…cf90 | 20443 ms |
| 2000 units (≈ $0.002 USDC) · L2 not_checkedWhose side: not sorted: vet402 unproven | ||||
Embed this record
Run this endpoint? Show the settle-through record vet402 measured — the badge reads 2/2 settled · 0 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/7a89f5f3-d9fe-4c92-8432-06380b1adb2f)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.