Skip to main content
Independent MeasurementEndpoint record (L0 · L1)Published state: passLast probed: 2026-10-19 · 1 day ago

x402.orthogonal.com/tomba/v1/people/find

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://x402.orthogonal.com/tomba/v1/people/find
Sourcecdp_bazaar
Declared methodGET
Networkeip155:8453
Receiving address0xac9ad2609466fb92c69640fa2b9ee7b22a76e8fe
Declared price (base units)10000
Catalog statusactive
First seen / last seen2026-08-14 08:52 UTC / 2026-10-20 01:01 UTC
Catalog-reported calls / payers (30d)4 / 3

2.Probe history

2026-09-012026-10-19
Figure 1. Probe timeline, last 12 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-10-19 16:40 UTCGETpass402439 ms—
2026-10-17 22:40 UTCGETpass4022219 ms—
2026-10-16 15:40 UTCGETpass402230 ms—
2026-10-15 03:40 UTCGETpass402212 ms—
2026-10-13 21:40 UTCGETpass402133 ms—
2026-10-12 15:40 UTCGETpass402255 ms—
2026-10-11 15:40 UTCGETpass402378 ms—
2026-10-10 15:40 UTCGETpass402180 ms—
2026-10-09 15:40 UTCGETpass402330 ms—
2026-10-08 13:40 UTCGETpass402278 ms—
2026-09-06 11:24 UTCGETpass402244 ms—
2026-09-01 23:13 UTCGETpass402137 ms—

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. 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-10-07relisted{"status":"delisted"}{"status":"active"}
2026-09-09delisted{"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.

20–2,000 characters · 0 so far

x402.orthogonal.com/tomba/v1/people/find — x402 purchase and probe record | vet402