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

api.magentlab.com/api/calc/ort_oud

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://api.magentlab.com/api/calc/ort_oud
Sourcecdp_bazaar
Declared methodPOST
Networkeip155:8453
Receiving address0x836be278f1739fb4308091cd1852f7971bc19ee2
Declared price (base units)5000
Catalog statusactive
First seen / last seen2026-09-01 01:03 UTC / 2026-09-29 01:03 UTC
Catalog-reported calls / payers (30d)2 / 1

2.Probe history

2026-09-05
Figure 1. Probe timeline, last 1 probe for this endpoint (UTC). Filled = pass, crossed = fail, dashed = unverified. Same-day probes overlap.
L0 probe history, newest first
Probed atMethodVerdictHTTPLatencyReason
2026-09-05 11:24 UTCPOSTpass40219 ms—

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.

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).
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-29 00:00settle_failed402—304 ms
5000 units (≈ $0.005 USDC) · L2 not_checkedWhose side: not sorted: vet402 unproven

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

Catalog listing events, newest first
Detected onEventBeforeAfter
2026-09-28relisted{"status":"delisted"}{"status":"active"}
2026-09-08delisted{"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.

About the purchase at 2026-09-29T00:00:43Z (UTC). The form starts with that time; add what you saw instead.