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

x402-mcp.onrender.com/tasks/us-rental-diligence

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://x402-mcp.onrender.com/tasks/us-rental-diligence
Sourcecdp_bazaar
Declared methodPOST
Networkeip155:8453
Receiving address0xab745e5f576667037696e78ba7da28e193e4423d
Declared price (base units)1500000
Catalog statusdelisted (since 2026-09-26 01:02 UTC)
First seen / last seen2026-08-17 01:06 UTC / 2026-09-25 01:02 UTC
Catalog-reported calls / payers (30d)1 / 1

2.Probe history

2026-09-062026-09-25
Figure 1. Probe timeline, last 30 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-25 13:40 UTCPOSTfail402461 msmetadata_mismatch
2026-09-24 16:40 UTCPOSTfail402339 msmetadata_mismatch
2026-09-23 22:40 UTCPOSTfail402504 msmetadata_mismatch
2026-09-23 04:40 UTCPOSTfail402380 msmetadata_mismatch
2026-09-22 13:40 UTCPOSTfail402152 msmetadata_mismatch
2026-09-21 16:40 UTCPOSTfail402318 msmetadata_mismatch
2026-09-20 22:40 UTCPOSTfail402389 msmetadata_mismatch
2026-09-20 04:40 UTCPOSTfail402330 msmetadata_mismatch
2026-09-19 13:40 UTCPOSTfail402507 msmetadata_mismatch
2026-09-18 16:40 UTCPOSTfail402540 msmetadata_mismatch
2026-09-18 04:40 UTCPOSTfail402591 msmetadata_mismatch
2026-09-17 13:40 UTCPOSTfail402416 msmetadata_mismatch
2026-09-16 16:40 UTCPOSTfail402284 msmetadata_mismatch
2026-09-15 22:40 UTCPOSTfail402262 msmetadata_mismatch
2026-09-15 04:40 UTCPOSTfail402168 msmetadata_mismatch
2026-09-14 13:40 UTCPOSTfail402376 msmetadata_mismatch
2026-09-13 22:40 UTCPOSTfail402342 msmetadata_mismatch
2026-09-13 13:40 UTCPOSTfail402321 msmetadata_mismatch
2026-09-12 16:40 UTCPOSTfail402281 msmetadata_mismatch
2026-09-12 04:40 UTCPOSTfail402273 msmetadata_mismatch
2026-09-11 13:40 UTCPOSTfail4021979 msmetadata_mismatch
2026-09-10 23:40 UTCPOSTfail402136 msmetadata_mismatch
2026-09-10 14:40 UTCPOSTfail402293 msmetadata_mismatch
2026-09-09 17:40 UTCPOSTfail402303 msmetadata_mismatch
2026-09-09 05:40 UTCPOSTfail402353 msmetadata_mismatch
2026-09-08 17:40 UTCPOSTfail402311 msmetadata_mismatch
2026-09-08 05:40 UTCPOSTfail402371 msmetadata_mismatch
2026-09-07 17:40 UTCPOSTfail402278 msmetadata_mismatch
2026-09-07 05:40 UTCPOSTfail402383 msmetadata_mismatch
2026-09-06 14:40 UTCPOSTfail402406 msmetadata_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

Catalog listing events, newest first
Detected onEventBeforeAfter
2026-09-26delisted{"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.