Skip to main content
vet402
Independent MeasurementEndpoint record (L0 · L1)Published state: failLast probed: 2026-09-26 · 1 day ago
vet402Back to the registerMethodology

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

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://api.strale.io/x402/belgian-company-data
Sourcecdp_bazaar
Declared methodGET
Networkbase
Receiving address0x66d7c2f952362bfb24fd7f02a9bec9c754ea83bc
Declared price (base units)—
Catalog statusdelisted (since 2026-09-27 01:02 UTC)
First seen / last seen2026-08-14 08:52 UTC / 2026-09-26 01:02 UTC
Catalog-reported calls / payers (30d)1 / 1

2.Probe history

2026-08-292026-09-26
Figure 1. Probe timeline, last 8 probes for this endpoint (UTC). Filled = pass, crossed = fail, dashed = unverified. Same-day probes overlap.
L0 probe history, newest first
Probed atMethodVerdictHTTPLatencyReason
2026-09-26 10:30 UTCGETfail40224 msaccepts_invalid
2026-09-22 11:24 UTCGETfail40237 msaccepts_invalid
2026-09-18 11:24 UTCGETfail40286 msaccepts_invalid
2026-09-15 11:24 UTCGETfail40244 msaccepts_invalid
2026-09-11 11:24 UTCGETfail40230 msaccepts_invalid
2026-09-08 11:24 UTCGETfail40226 msaccepts_invalid
2026-09-03 11:24 UTCGETfail40224 msaccepts_invalid
2026-08-29 11:24 UTCGETfail40230 msaccepts_invalid

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-09-27delisted{"status":"active"}{"status":"delisted"}
2026-08-28relisted{"status":"delisted"}{"status":"active"}
2026-08-18delisted{"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.