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

agentworld.me/api/mlb/duke/ask

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://agentworld.me/api/mlb/duke/ask
Sourcecdp_bazaar
Declared methodPOST
Catalog networkeip155:8453
Receiving address0x367f1b3d8ca90d1e087481a9a40d585bf3451a03
Declared price (base units)2000
Catalog statusactive
First seen / last seen2026-08-14 08:52 UTC / 2026-10-21 13:01 UTC
Catalog-reported calls / payers (30d)1 / 1

2.Probe history

2026-09-052026-10-20
Figure 1. Probe timeline, last 20 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-20 16:40 UTCPOSTpass402348 ms—
2026-10-18 22:40 UTCPOSTpass402258 ms—
2026-10-17 16:40 UTCPOSTpass402644 ms—
2026-10-16 12:40 UTCPOSTpass402362 ms—
2026-10-14 21:40 UTCPOSTpass402506 ms—
2026-10-13 15:40 UTCPOSTpass402378 ms—
2026-10-12 12:40 UTCPOSTpass402356 ms—
2026-10-11 12:40 UTCPOSTpass402427 ms—
2026-10-10 12:40 UTCPOSTpass402468 ms—
2026-10-08 22:40 UTCPOSTpass402664 ms—
2026-10-07 22:40 UTCPOSTpass402804 ms—
2026-10-06 22:40 UTCPOSTfail—10000 mstimeoutNo response headers arrived within 10 seconds.
2026-10-06 04:41 UTCPOSTpass402577 ms—
2026-09-30 10:30 UTCPOSTpass402314 ms—
2026-09-25 10:30 UTCPOSTpass402350 ms—
2026-09-19 11:24 UTCPOSTfail—10027 mstimeoutNo response headers arrived within 10 seconds.
2026-09-17 11:24 UTCPOSTpass402112 ms—
2026-09-12 11:24 UTCPOSTpass402144 ms—
2026-09-09 11:24 UTCPOSTpass402116 ms—
2026-09-05 11:24 UTCPOSTpass402241 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-10-06relisted{"status":"delisted"}{"status":"active"}
2026-10-03delisted{"status":"active"}{"status":"delisted"}
2026-09-25relisted{"status":"delisted"}{"status":"active"}
2026-09-20delisted{"status":"active"}{"status":"delisted"}
2026-09-05relisted{"status":"delisted"}{"status":"active"}
2026-08-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