Independent MeasurementEndpoint record (L0 · L1)Published state: failLast probed: 2026-09-23 · 4 days ago

pulsefeed.dev/mcp/drift/history

1.Catalog declaration

Catalog declaration for this endpoint
Resource URL	https://pulsefeed.dev/mcp/drift/history
Source	cdp_bazaar
Declared method	GET
Network	base
Receiving address	0x7f5f784ba98cecfc0ba4336f0e48222a3d4d69a8
Declared price (base units)	—
Catalog status	active
First seen / last seen	2026-08-31 01:03 UTC / 2026-09-28 01:02 UTC
Catalog-reported calls / payers (30d)	1 / 1

2.Probe history

2026-09-052026-09-23

Figure 1. Probe timeline, last 7 probes for this endpoint (UTC). Filled = pass, crossed = fail, dashed = unverified. Same-day probes overlap.

L0 probe history, newest first
Probed at	Method	Verdict	HTTP	Latency	Reason
2026-09-23 10:31 UTC	GET	fail	200	1805 ms	no_402
2026-09-19 11:24 UTC	GET	fail	200	1745 ms	no_402
2026-09-17 11:24 UTC	GET	fail	200	1357 ms	no_402
2026-09-13 11:24 UTC	GET	fail	200	1324 ms	no_402
2026-09-09 11:24 UTC	GET	fail	200	871 ms	no_402
2026-09-06 11:24 UTC	GET	fail	200	922 ms	no_402
2026-09-05 11:24 UTC	GET	fail	200	749 ms	no_402

3.L1 — real purchases

No paid purchases recorded for this endpoint yet.

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.