Skip to main content
Independent MeasurementEndpoint record (L0 · L1)Published state: failLast probed: 2026-09-03 · 33 days ago

agents.ai-rook.com/api/ai-analysis

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://agents.ai-rook.com/api/ai-analysis
Sourcecdp_bazaar
Declared methodPOST
Networkeip155:8453
Receiving address0xd5f96558fcb1f127c77c7d95eea067f526d08618
Declared price (base units)1000
Catalog statusdelisted (since 2026-09-04 01:03 UTC)
First seen / last seen2026-08-14 08:39 UTC / 2026-09-03 01:04 UTC
Catalog-reported calls / payers (30d)5 / 1

2.Probe history

2026-08-232026-09-03
Figure 1. Probe timeline, last 4 probes for this endpoint (UTC). Filled = pass, crossed = fail, dashed = unverified. Same-day probes overlap.
L0 probe history, newest first
Probed atMethodVerdictHTTPLatencyReason
2026-09-03 14:40 UTCPOSTfail—10002 mstimeoutNo response headers arrived within 10 seconds.
2026-09-02 23:40 UTCPOSTfail—10005 mstimeoutNo response headers arrived within 10 seconds.
2026-09-02 14:40 UTCPOSTfail2006310 msno_402HTTP 200 instead of 402 to an unpaid POST.
2026-08-23 10:51 UTCPOSTfail2007960 msno_402HTTP 200 instead of 402 to an unpaid POST.

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-04delisted{"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