Skip to main content
Independent MeasurementEndpoint record (L0 · L1)Published state: passLast probed: 2026-10-19 · 1 day ago

api.agentstools.dev/unlock/upcoming

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://api.agentstools.dev/unlock/upcoming
Sourcecdp_bazaar
Declared methodGET
Networkeip155:8453
Receiving address0xf22e558a00d91ee12a1f50c52186fecb8ddff493
Declared price (base units)50000
Catalog statusactive
First seen / last seen2026-08-18 01:06 UTC / 2026-10-20 01:01 UTC
Catalog-reported calls / payers (30d)2 / 2

2.Probe history

2026-09-012026-10-19
Figure 1. Probe timeline, last 27 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-10-19 13:40 UTCGETpass402817 ms—
2026-10-17 22:40 UTCGETpass4022250 ms—
2026-10-16 15:40 UTCGETpass402505 ms—
2026-10-15 03:40 UTCGETpass402689 ms—
2026-10-13 21:40 UTCGETpass402197 ms—
2026-10-12 15:40 UTCGETpass402185 ms—
2026-10-11 15:40 UTCGETpass402247 ms—
2026-10-10 15:40 UTCGETpass402351 ms—
2026-10-09 12:40 UTCGETpass402582 ms—
2026-10-08 04:40 UTCGETpass402224 ms—
2026-10-07 04:40 UTCGETpass402139 ms—
2026-10-06 13:40 UTCGETpass402165 ms—
2026-10-04 22:40 UTCGETpass402460 ms—
2026-10-04 04:40 UTCGETpass402208 ms—
2026-10-03 13:40 UTCGETpass402175 ms—
2026-10-02 13:40 UTCGETpass402645 ms—
2026-10-01 16:40 UTCGETpass4021628 ms—
2026-09-30 22:40 UTCGETpass402455 ms—
2026-09-30 04:40 UTCGETpass402600 ms—
2026-09-29 13:40 UTCGETpass402676 ms—
2026-09-25 10:30 UTCGETpass402432 ms—
2026-09-20 11:24 UTCGETpass402214 ms—
2026-09-17 12:35 UTCGETpass402439 ms—
2026-09-14 11:24 UTCGETpass402179 ms—
2026-09-10 11:24 UTCGETpass402415 ms—
2026-09-07 11:24 UTCGETpass402211 ms—
2026-09-01 23:14 UTCGETpass402140 ms—

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

Catalog listing events, newest first
Detected onEventBeforeAfter
2026-09-17relisted{"status":"delisted"}{"status":"active"}
2026-09-17delisted{"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.

20–2,000 characters · 0 so far