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

worxai.tech/api/x402/v2/ledger

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://worxai.tech/api/x402/v2/ledger
Sourcecdp_bazaar
Declared methodGET
Networkeip155:8453
Receiving address0xd5f951c86b0a4022c72c38ab5ba66a682a259420
Declared price (base units)35000
Catalog statusactive
First seen / last seen2026-09-04 01:03 UTC / 2026-09-17 12:35 UTC
Catalog-reported calls / payers (30d)10 / 1

2.Probe history

2026-09-052026-09-17
Figure 1. Probe timeline, last 10 probes for this endpoint (UTC). Filled = pass, crossed = fail, dashed = unverified. Same-day probes overlap.
L0 probe history, newest first
Probed atMethodVerdictHTTPLatencyReason
2026-09-17 13:40 UTCGETpass402370 ms—
2026-09-16 16:40 UTCGETfail402437 msprice_mismatch
2026-09-15 22:40 UTCGETfail402515 msprice_mismatch
2026-09-15 04:40 UTCGETfail402256 msprice_mismatch
2026-09-14 13:40 UTCGETfail402208 msprice_mismatch
2026-09-13 22:40 UTCGETfail402512 msprice_mismatch
2026-09-13 11:24 UTCGETfail402161 msprice_mismatch
2026-09-10 11:24 UTCGETfail402313 msprice_mismatch
2026-09-06 11:24 UTCGETfail402130 msprice_mismatch
2026-09-05 11:24 UTCGETfail40281 msprice_mismatch

3.L1 — real purchases

No paid purchases recorded for this endpoint yet.

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.