Independent MeasurementEndpoint record (L0 · L1)Published state: passLast probed: 2026-09-29 · 1 day ago

api.strale.io/x402/german-company-data

1.Catalog declaration

Catalog declaration for this endpoint
Resource URL	https://api.strale.io/x402/german-company-data
Source	cdp_bazaar
Declared method	GET
Network	base
Receiving address	0x66d7c2f952362bfb24fd7f02a9bec9c754ea83bc
Declared price (base units)	—
Catalog status	active
First seen / last seen	2026-08-14 08:52 UTC / 2026-09-30 01:03 UTC
Catalog-reported calls / payers (30d)	16 / 1

2.Probe history

2026-09-172026-09-29

Figure 1. Probe timeline, last 5 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 at	Method	Verdict	HTTP	Latency	Reason
2026-09-29 07:38 UTC	GET	pass	402	316 ms	—
2026-09-25 10:30 UTC	GET	fail	402	103 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.
2026-09-21 11:24 UTC	GET	fail	402	27 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.
2026-09-17 16:19 UTC	GET	fail	402	218 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.
2026-09-17 12:35 UTC	GET	fail	402	764 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-09-17	relisted	`{"status":"delisted"}`	`{"status":"active"}`
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.