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

taskfleet.net/scrape

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://taskfleet.net/scrape
Sourcecdp_bazaar
Declared methodPOST
Networkeip155:8453
Receiving address0x04cce6f938fb8e48afc10dab0ff2f09cce392a7b
Declared price (base units)20000
Catalog statusactive
First seen / last seen2026-08-14 08:52 UTC / 2026-09-27 01:02 UTC
Catalog-reported calls / payers (30d)3 / 1

2.Probe history

2026-09-252026-09-26
Figure 1. Probe timeline, last 3 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 16:40 UTCPOSTpass402175 ms—
2026-09-25 22:40 UTCPOSTpass4022309 ms—
2026-09-25 10:30 UTCPOSTpass402374 ms—

3.L1 — real purchases

1 of 1 paid attempts settled with a receipt, and 1 of those also returned a 2xx response (delivered). Each settled row carries its on-chain transaction hash — the receipt is the evidence. A settled row reads as nonce-bound when the on-chain re-read also matched the one-time signature nonce we generated for that purchase, and amount + payee when it matched amount, payee, asset and chain with no nonce on record — the binding shipped on 2026-09-04, so earlier rows carry the weaker evidence and keep their label rather than being demoted (methodology). settled is the transfer we confirmed on-chain; delivered is the response arriving. A settled row whose paid request answered 5xx counts as settled and not as delivered — definitions.

1/1
Figure 2. Settle-through: one cell per paid attempt. Filled = settled with an on-chain receipt, crossed = paid but no receipt.
L1 purchase history, newest first
Attempted atResultHTTPReceipt (tx)Latency
09-25 12:01settled (nonce-bound)2000x8bccb03a…a6b03031 ms
20000 units (≈ $0.02 USDC) · L2 no_declaration

Embed this record

Run this endpoint? Show the settle-through record vet402 measured — the badge reads 1/1 settled · 1 delivered and updates as the record grows. It carries the host it is about and the date it was last measured, so a saved copy cannot pass itself off as current. It states a measurement, not a rating.

vet402: 1 of 1 paid attempts settled with an on-chain receipt, and 1 of those also returned a 2xx response. settled is the confirmed transfer; delivered is the response arriving. A measurement of what happened when vet402 paid this endpoint, not a recommendation. (taskfleet.net · measured 2026-09-25)

[![vet402 receipt](https://vet402.com/api/badge/endpoint/1e65a168-a338-4f9d-91c0-756e75668ab6.svg)](https://vet402.com/observatory/e/1e65a168-a338-4f9d-91c0-756e75668ab6)

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-25relisted{"status":"delisted"}{"status":"active"}
2026-08-30delisted{"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.