Skip to main content
Independent MeasurementEndpoint record (L0 · L1)Published state: passLast probed: 2026-09-04 · 28 days ago

eleven.tokens.fun/speak

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://eleven.tokens.fun/speak
Sourcecdp_bazaar
Declared methodPOST
Networkeip155:8453
Receiving address0x0a84bcc15048c336ca603511363f7ae37579d358
Declared price (base units)30000
Catalog statusdelisted (since 2026-09-05 01:03 UTC)
First seen / last seen2026-08-14 08:39 UTC / 2026-09-04 01:03 UTC
Catalog-reported calls / payers (30d)2 / 1

2.Probe history

2026-08-142026-09-04
Figure 1. Probe timeline, last 8 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-04 23:40 UTCPOSTpass402658 ms—
2026-09-04 14:40 UTCPOSTpass402220 ms—
2026-09-03 23:40 UTCPOSTpass4021459 ms—
2026-09-03 14:40 UTCPOSTpass402419 ms—
2026-09-02 23:40 UTCPOSTpass402364 ms—
2026-09-02 14:40 UTCPOSTpass402863 ms—
2026-09-02 05:40 UTCPOSTpass402223 ms—
2026-08-14 08:53 UTCPOSTfail402142 msaccepts_invalid402 without a payable accept in the header or the body (which part was missing was not recorded before the 2026-09-29 change).

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