Independent MeasurementEndpoint record (L0 · L1)Published state: unverifiedLast probed: 2026-08-14 · 46 days ago

three.ws/api/x402/permit2-paid-demo

1.Catalog declaration

Catalog declaration for this endpoint
Resource URL	https://three.ws/api/x402/permit2-paid-demo
Source	cdp_bazaar
Declared method	GET
Network	eip155:8453
Receiving address	0x4022de2d36c334e73c7a108805cea11c0564f402
Declared price (base units)	1000
Catalog status	delisted (since 2026-08-27 01:15 UTC)
First seen / last seen	2026-08-14 08:39 UTC / 2026-08-26 01:39 UTC
Catalog-reported calls / payers (30d)	1 / 1

2.Probe history

2026-08-14

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-08-14 08:53 UTC	GET	fail	402	1070 ms	accepts_invalidRecorded before the 2026-09-29 change, when the probe read only the first 4,000 bytes of the 402 body; this body began like an x402 envelope, so the fail may be vet402's measuring error rather than the seller's.

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-08-27	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.