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

screenshot-api-production-fe7e.up.railway.app/capture/screenshot

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://screenshot-api-production-fe7e.up.railway.app/capture/screenshot
Sourcecdp_bazaar
Declared methodPOST
Networkeip155:8453
Receiving address0xffc458db291b4abce020fe3de4f91f2770e537b1
Declared price (base units)2000
Catalog statusactive
First seen / last seen2026-08-14 08:52 UTC / 2026-10-20 01:01 UTC
Catalog-reported calls / payers (30d)2 / 2

2.Probe history

2026-08-302026-10-19
Figure 1. Probe timeline, last 12 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 16:40 UTCPOSTpass402181 ms—
2026-10-18 04:40 UTCPOSTpass402567 ms—
2026-10-16 21:40 UTCPOSTpass402360 ms—
2026-10-15 12:40 UTCPOSTpass402261 ms—
2026-10-14 03:40 UTCPOSTpass402252 ms—
2026-09-25 10:30 UTCPOSTpass402221 ms—
2026-09-20 11:24 UTCPOSTpass402195 ms—
2026-09-17 12:35 UTCPOSTpass402213 ms—
2026-09-14 11:24 UTCPOSTpass402234 ms—
2026-09-10 11:24 UTCPOSTpass402197 ms—
2026-09-06 11:24 UTCPOSTpass40293 ms—
2026-08-30 11:24 UTCPOSTpass40284 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-13relisted{"status":"delisted"}{"status":"active"}
2026-09-26delisted{"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