Skip to main content
Independent MeasurementEndpoint record (L0 · L1)Published state: passLast probed: 2026-09-02 · today

money-agent-production-736f.up.railway.app/v1/radar

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://money-agent-production-736f.up.railway.app/v1/radar
Sourcecdp_bazaar
Declared methodGET
Networkeip155:8453
Receiving address0xc0a707f63df3120e018f119ddf44fc8eaab40e72
Declared price (base units)50000
Catalog statusactive
First seen / last seen2026-08-16 01:07 UTC / 2026-09-02 01:03 UTC
Catalog-reported calls / payers (30d)6 / 3

2.Probe history

2026-09-012026-09-02
Figure 1. Probe timeline, last 2 probes for this endpoint (UTC). Filled = pass, crossed = fail, dashed = unverified. Same-day probes overlap.
L0 probe history, newest first
Probed atMethodVerdictHTTPLatencyReason
2026-09-02 05:40 UTCGETpass402129 ms
2026-09-01 23:14 UTCGETpass40253 ms

3.L1 — real purchases

1 of 1 paid attempts settled with a receipt. Each settled row carries its on-chain transaction hash — the receipt is the evidence.

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 atResultReceipt (tx)Latency
09-02 01:00settled0xccfba1be…4d0a1451 ms
50000 units (≈ $0.05 USDC) · HTTP 200 · L2 match

Embed this record

Run this endpoint? Show the settle-through record vet402 measured — the badge reads 1/1 settled and updates as the record grows. It states a measurement, not a rating.

vet402: 1 of 1 paid attempts settled

[![vet402 receipt](https://vet402.com/api/badge/endpoint/b9e499f1-a948-4ba4-b660-cd761392f326.svg)](https://vet402.com/observatory/e/b9e499f1-a948-4ba4-b660-cd761392f326)

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.

money-agent-production-736f.up.railway.app/v1/radar — L0 observations | vet402