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

api.stelardigital.com/telemetry

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://api.stelardigital.com/telemetry
Sourcecdp_bazaar
Declared methodGET
Networkeip155:8453
Receiving address0x32d711c66dd1ad0c42d0cfe48e58ee5f2de7c243
Declared price (base units)5000
Catalog statusactive
First seen / last seen2026-08-14 08:39 UTC / 2026-09-05 01:03 UTC
Catalog-reported calls / payers (30d)5 / 5

2.Probe history

2026-08-142026-09-04
Figure 1. Probe timeline, last 8 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-09-04 17:40 UTCGETpass402269 ms—
2026-09-04 05:40 UTCGETpass402433 ms—
2026-09-03 17:40 UTCGETpass4021069 ms—
2026-09-03 05:40 UTCGETpass402285 ms—
2026-09-02 17:40 UTCGETpass4021768 ms—
2026-09-02 05:40 UTCGETpass4021513 ms—
2026-09-01 23:40 UTCGETpass402423 ms—
2026-08-14 08:53 UTCGETpass402284 ms—

3.L1 — real purchases

3 of 3 paid attempts settled with a receipt, and 3 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 4xx or 5xx counts as settled and not as delivered — definitions.

3/3
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
08-28 12:18settled (amount + payee)2000x03528d55…a1221857 ms
5000 units (≈ $0.005 USDC) · L2 no_declaration
08-21 08:32settled (amount + payee)2000x7d490431…1d151897 ms
5000 units (≈ $0.005 USDC) · L2 no_declaration
08-14 10:05settled (amount + payee)2000x66756b25…f2a41676 ms
5000 units (≈ $0.005 USDC) · L2 no_declaration

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 states a measurement, not a rating.

vet402: 3 of 3 paid attempts settled, 3 delivered

[![vet402 receipt](https://vet402.com/api/badge/endpoint/5d134813-a705-4bcd-bc23-30aa88277da1.svg)](https://vet402.com/observatory/e/5d134813-a705-4bcd-bc23-30aa88277da1)

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.