Independent MeasurementEndpoint record (L0 · L1)Published state: unverifiedLast probed: 2026-09-25 · 2 days ago

api.xynaptic.io/v1/crypto/validate

1.Catalog declaration

Catalog declaration for this endpoint
Resource URL	https://api.xynaptic.io/v1/crypto/validate
Source	cdp_bazaar
Declared method	GET
Network	eip155:8453
Receiving address	0x4ff893df9ab8603d5460fbbaee0d9b8c0fa4d5e9
Declared price (base units)	100000
Catalog status	delisted (since 2026-09-26 01:02 UTC)
First seen / last seen	2026-09-25 01:02 UTC / 2026-09-25 01:02 UTC
Catalog-reported calls / payers (30d)	3 / 1

2.Probe history

2026-09-25

Figure 1. Probe timeline, last 1 probe for this endpoint (UTC). Filled = pass, crossed = fail, dashed = unverified. Same-day probes overlap.

L0 probe history, newest first
Probed at	Method	Verdict	HTTP	Latency	Reason
2026-09-25 10:30 UTC	GET	fail	404	10 ms	no_402

3.L1 — real purchases

No paid purchases recorded for this endpoint yet.

4.Catalog listing events

Catalog listing events, newest first
Detected on	Event	Before	After
2026-09-26	delisted	`{"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.