Independent MeasurementEndpoint record (L0 · L1)Published state: unverifiedLast probed: 2026-09-29 · 3 days ago

mcp.dropenginehq.com/api/route-tool

1.Catalog declaration

Catalog declaration for this endpoint
Resource URL	https://mcp.dropenginehq.com/api/route-tool
Source	cdp_bazaar
Declared method	POST
Network	eip155:8453
Receiving address	0xc7693f1ba43e6d1f1885292e1194dc1fdc6e7585
Declared price (base units)	2000
Catalog status	active
First seen / last seen	2026-09-28 22:59 UTC / 2026-10-02 01:04 UTC
Catalog-reported calls / payers (30d)	1 / 1

2.Probe history

2026-09-29

Figure 1. Probe timeline, last 1 probe for this endpoint (UTC). Filled = pass, crossed = fail, dashed = unverified. Same-day probes overlap.

L0 probe history, newest first
Probed at	Method	Verdict	HTTP	Latency	Reason
2026-09-29 10:30 UTC	POST	unverified	400	92 ms	request_shapeUnpaid POST with an empty JSON body answered 400 before any payment challenge; not measured (vet402 does not guess the input).

3.L1 — real purchases

No paid purchases recorded for this endpoint yet.

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.