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

agent402.tools/api/unemployment-rate

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://agent402.tools/api/unemployment-rate
Sourcecdp_bazaar
Declared methodGET
Networkeip155:8453
Receiving address0xabf4fabd7c416fb67202e5f9002389fc75e2a9d0
Declared price (base units)10000
Catalog statusactive
First seen / last seen2026-08-14 08:52 UTC / 2026-09-05 01:03 UTC
Catalog-reported calls / payers (30d)4 / 2

2.Probe history

2026-08-312026-09-04
Figure 1. Probe timeline, last 7 probes for this endpoint (UTC). Filled = pass, crossed = fail, dashed = unverified. Same-day probes overlap.
L0 probe history, newest first
Probed atMethodVerdictHTTPLatencyReason
2026-09-04 17:40 UTCGETpass40293 ms—
2026-09-04 05:40 UTCGETpass402102 ms—
2026-09-03 23:40 UTCGETpass40296 ms—
2026-09-03 14:40 UTCGETpass40285 ms—
2026-09-02 23:40 UTCGETpass4022065 ms—
2026-09-02 14:40 UTCGETpass402166 ms—
2026-08-31 11:24 UTCGETfail40289 msaccepts_invalid

3.L1 — real purchases

1 of 1 paid attempts settled with a receipt, and 1 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.

1/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-04 01:02settled (amount + payee)2000xc9f25321…42361471 ms
10000 units (≈ $0.01 USDC) · L2 match

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

vet402: 1 of 1 paid attempts settled, 1 delivered

[![vet402 receipt](https://vet402.com/api/badge/endpoint/ad1d83f3-e1d1-4ce9-bbe2-10b6cb35ed55.svg)](https://vet402.com/observatory/e/ad1d83f3-e1d1-4ce9-bbe2-10b6cb35ed55)

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

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