Skip to main content
vet402
Independent MeasurementEndpoint record (L0 · L1)Published state: passLast probed: 2026-09-13 · today
vet402Back to the registerMethodology

open-pay.jp/api/paid/hello

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://open-pay.jp/api/paid/hello
Sourcecdp_bazaar
Declared methodGET
Networkeip155:8453
Receiving address0x52d4901142e2b5680027da5eb47c86cb02a3ca81
Declared price (base units)1000
Catalog statusactive
First seen / last seen2026-08-21 01:57 UTC / 2026-09-13 01:03 UTC
Catalog-reported calls / payers (30d)2 / 2

2.Probe history

2026-09-022026-09-13
Figure 1. Probe timeline, last 22 probes for this endpoint (UTC). Filled = pass, crossed = fail, dashed = unverified. Same-day probes overlap.
L0 probe history, newest first
Probed atMethodVerdictHTTPLatencyReason
2026-09-13 04:40 UTCGETpass402142 ms—
2026-09-12 13:40 UTCGETfail4022128 msprice_mismatch
2026-09-11 22:40 UTCGETfail402179 msprice_mismatch
2026-09-11 13:40 UTCGETfail402165 msprice_mismatch
2026-09-10 17:40 UTCGETfail402240 msprice_mismatch
2026-09-10 05:40 UTCGETfail402475 msprice_mismatch
2026-09-09 17:40 UTCGETfail402425 msprice_mismatch
2026-09-09 05:40 UTCGETfail402299 msprice_mismatch
2026-09-08 14:40 UTCGETfail402645 msprice_mismatch
2026-09-07 23:40 UTCGETfail402131 msprice_mismatch
2026-09-07 14:40 UTCGETfail402393 msprice_mismatch
2026-09-06 23:40 UTCGETfail402143 msprice_mismatch
2026-09-06 14:40 UTCGETfail402515 msprice_mismatch
2026-09-05 23:40 UTCGETfail402699 msprice_mismatch
2026-09-05 14:40 UTCGETfail402785 msprice_mismatch
2026-09-04 23:40 UTCGETfail402755 msprice_mismatch
2026-09-04 14:40 UTCGETfail402508 msprice_mismatch
2026-09-03 23:40 UTCGETfail402128 msprice_mismatch
2026-09-03 14:40 UTCGETfail402390 msprice_mismatch
2026-09-02 23:40 UTCGETfail402273 msprice_mismatch
2026-09-02 14:40 UTCGETfail402304 msprice_mismatch
2026-09-02 05:40 UTCGETfail402441 msprice_mismatch

3.L1 — real purchases

0 of 1 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.

0/1
Figure 2. Settle-through: one cell per paid attempt. Filled = settled with an on-chain receipt, crossed = paid but no receipt.
L1 purchase history, newest first
Attempted atResultHTTPReceipt (tx)Latency
09-13 06:00settle_failed402—351 ms
1000 units (≈ $0.001 USDC) · L2 not_checked

Get one email when this record's verdict changes. No digest, no marketing — one message per change, and only for this endpoint.

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.