Skip to main content
Independent MeasurementEndpoint record (L0 · L1)Published state: passLast probed: 2026-10-17 · today

api.sitecheck-api.workers.dev/api/media/transcript

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://api.sitecheck-api.workers.dev/api/media/transcript
Sourcecdp_bazaar
Declared methodGET
Networkeip155:8453
Receiving address0xb8491f953e6860d3b5840b73c60883ff099ceafa
Declared price (base units)6500
Catalog statusactive
First seen / last seen2026-10-15 13:03 UTC / 2026-10-17 01:04 UTC
Catalog-reported calls / payers (30d)2 / 2

2.Probe history

2026-10-162026-10-17
Figure 1. Probe timeline, last 2 probes for this endpoint (UTC). Filled = pass, crossed = fail, dashed = unverified. Same-day probes overlap.
L0 probe history, newest first
Probed atMethodVerdictHTTPLatencyReason
2026-10-17 10:30 UTCGETpass402133 ms—
2026-10-16 10:30 UTCGETfail402676 msprice_mismatchDeclared 4500 of 0x8335…2913; the 402 offered 6500 of 0x8335…2913, 6500 of EPjFWd…Dt1v, 6500 of 0x3600…0000.

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

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.

20–2,000 characters · 0 so far