Skip to main content
vet402
Independent MeasurementEndpoint record (L0 · L1)Published state: failLast probed: 2026-10-04 · today
vet402Back to the registerMethodology

x402.shizu.me/predictions

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://x402.shizu.me/predictions
Sourcecdp_bazaar
Declared methodGET
Networkeip155:8453
Receiving address0x217e5fe265eb78b29067bf8324ef03a7d8e167c4
Declared price (base units)7000
Catalog statusactive
First seen / last seen2026-08-14 08:39 UTC / 2026-10-03 01:04 UTC
Catalog-reported calls / payers (30d)1 / 1

2.Probe history

2026-09-132026-10-04
Figure 1. Probe timeline, last 30 probes for this endpoint (UTC). Filled = pass, crossed = fail, dashed = unverified. Same-day probes overlap. Marks closer than one mark width are stepped down one lane.
L0 probe history, newest first
Probed atMethodVerdictHTTPLatencyReason
2026-10-04 04:40 UTCGETfail402547 msprice_mismatchDeclared 7000 of 0x8335…2913; the 402 offered 6000 of 0x8335…2913.
2026-10-03 04:40 UTCGETfail4021155 msprice_mismatchDeclared 7000 of 0x8335…2913; the 402 offered 6000 of 0x8335…2913.
2026-10-02 13:40 UTCGETfail402228 msprice_mismatchDeclared 7000 of 0x8335…2913; the 402 offered 6000 of 0x8335…2913.
2026-10-01 16:40 UTCGETfail402636 msprice_mismatchDeclared 7000 of 0x8335…2913; the 402 offered 6000 of 0x8335…2913.
2026-09-30 22:40 UTCGETfail402428 msprice_mismatchDeclared 7000 of 0x8335…2913; the 402 offered 6000 of 0x8335…2913.
2026-09-29 22:40 UTCGETfail402600 msprice_mismatchDeclared 7000 of 0x8335…2913; the 402 offered 6000 of 0x8335…2913.
2026-09-29 10:30 UTCGETfail402623 msprice_mismatchDeclared 7000 of 0x8335…2913; the 402 offered 6000 of 0x8335…2913.
2026-09-29 07:38 UTCGETfail402280 msprice_mismatchDeclared 7000 of 0x8335…2913; the 402 offered 6000 of 0x8335…2913.
2026-09-28 16:40 UTCGETfail402936 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-27 22:40 UTCGETfail402691 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-27 04:40 UTCGETpass402953 ms—
2026-09-26 13:40 UTCGETfail402848 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-25 16:40 UTCGETfail402722 msprice_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 UTCGETfail402509 msprice_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 UTCGETfail402545 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-23 16:40 UTCGETfail402595 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-22 22:40 UTCGETfail402560 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-22 04:40 UTCGETfail402522 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-21 13:40 UTCGETfail402558 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-20 16:40 UTCGETfail402444 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-19 22:40 UTCGETfail402571 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-19 04:40 UTCGETfail402542 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-18 13:40 UTCGETfail402617 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-17 16:40 UTCGETfail402659 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-17 04:40 UTCGETfail402443 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-16 13:40 UTCGETfail402548 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-15 16:40 UTCGETfail402461 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-14 22:40 UTCGETfail402533 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-14 04:40 UTCGETfail402480 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-13 16:40 UTCGETfail402557 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).

3.L1 — real purchases

1 of 1 paid attempts settled on-chain, and 1 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 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).
1/1
Figure 2. Settle-through: one cell per paid attempt. Filled = settled on-chain, crossed = signed, and not settled on-chain.
L1 purchase history, newest first
Attempted atResultHTTPOn-chain txLatency
09-06 19:00settled (nonce-bound)2000x290cf7f5…3d351720 ms
5000 units (≈ $0.005 USDC) · L2 no_declarationWhose side: no failure (delivered)

Embed this record

Run this endpoint? Show the settle-through record vet402 measured — the badge reads 1/1 settled · 1 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.

vet402: 1 of 1 paid attempts settled with an on-chain receipt, and 1 of those also returned a 2xx response. settled is the confirmed transfer; delivered is the response arriving. A measurement of what happened when vet402 paid this endpoint, not a recommendation. (x402.shizu.me · measured 2026-09-06)

[![vet402 receipt](https://vet402.com/api/badge/endpoint/0219f025-0cb3-4962-b7bf-86abf5968ac3.svg)](https://vet402.com/observatory/e/0219f025-0cb3-4962-b7bf-86abf5968ac3)

Get one email when this record's verdict changes. No digest, no marketing — one message per change, and only for this endpoint. We first send one confirmation email; nothing else goes out until you confirm.

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.

20–2,000 characters · 0 so far