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

tripadvisor.x402.paysponge.com/api/v1/location/nearby_search

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://tripadvisor.x402.paysponge.com/api/v1/location/nearby_search
Sourcecdp_bazaar
Declared methodGET
Networkeip155:8453
Receiving address0x6302d9e6dbb22fec3c350551568bb39b4b35ad57
Declared price (base units)10000
Catalog statusactive
First seen / last seen2026-08-14 08:39 UTC / 2026-09-06 01:03 UTC
Catalog-reported calls / payers (30d)2 / 2

2.Probe history

2026-08-242026-09-06
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-06 11:24 UTCGETpass402385 ms—
2026-08-24 11:11 UTCGETpass402381 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.

4.Catalog listing events

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