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

api.metalift.ai/v1/scrape

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://api.metalift.ai/v1/scrape
Sourcecdp_bazaar
Declared methodPOST
Networkeip155:8453
Receiving address0x77761c2ae9545dfcd117afd9029ff141215c2e34
Declared price (base units)5000
Catalog statusactive
First seen / last seen2026-09-20 01:03 UTC / 2026-09-27 01:02 UTC
Catalog-reported calls / payers (30d)13 / 2

2.Probe history

2026-09-202026-09-27
Figure 1. Probe timeline, last 10 probes for this endpoint (UTC). Filled = pass, crossed = fail, dashed = unverified. Same-day probes overlap.
L0 probe history, newest first
Probed atMethodVerdictHTTPLatencyReason
2026-09-27 04:40 UTCPOSTfail402771 msprice_mismatch
2026-09-26 13:40 UTCPOSTfail402934 msprice_mismatch
2026-09-25 16:40 UTCPOSTfail402841 msprice_mismatch
2026-09-24 22:40 UTCPOSTfail402689 msprice_mismatch
2026-09-24 04:40 UTCPOSTfail402763 msprice_mismatch
2026-09-23 13:40 UTCPOSTfail402833 msprice_mismatch
2026-09-22 16:40 UTCPOSTfail402959 msprice_mismatch
2026-09-21 22:40 UTCPOSTfail4021018 msprice_mismatch
2026-09-21 11:24 UTCPOSTfail402780 msprice_mismatch
2026-09-20 11:24 UTCPOSTfail4023421 msprice_mismatch

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

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.