Skip to main content
vet402
Independent MeasurementEndpoint record (L0 · L1)Published state: unverifiedLast probed: 2026-09-30 · 4 days ago
vet402Back to the registerMethodology

mpp.orthogonal.com/scrapecreators/v1/linkedin/ad

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://mpp.orthogonal.com/scrapecreators/v1/linkedin/ad
Sourcempp_directory
Declared methodGET
Networkeip155:4217
Receiving address—
Declared price (base units)20000
Catalog statusactive
First seen / last seen2026-09-17 12:35 UTC / 2026-10-03 01:05 UTC
Catalog-reported calls / payers (30d)— / —

2.Probe history

2026-09-172026-09-30
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 atMethodVerdictHTTPLatencyReason
2026-09-30 10:31 UTCGETunverified400153 msrequest_shapeUnpaid request answered 400 before any payment challenge; not measured (vet402 does not guess the input).
2026-09-25 10:30 UTCGETunverified400225 msrequest_shapeUnpaid request answered 400 before any payment challenge; not measured (vet402 does not guess the input).
2026-09-21 11:24 UTCGETunverified400188 msrequest_shapeUnpaid request answered 400 before any payment challenge; not measured (vet402 does not guess the input).
2026-09-17 16:19 UTCGETunverified400202 msrequest_shapeUnpaid request answered 400 before any payment challenge; not measured (vet402 does not guess the input).
2026-09-17 12:35 UTCGETfail400273 msno_402HTTP 400 instead of 402 to an unpaid GET.

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. We first send one confirmation email; nothing else goes out until you confirm.

4.Catalog listing events

No listing changes observed.

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.

20–2,000 characters · 0 so far