Independent MeasurementEndpoint record (L0 · L1)Published state: passLast probed: 2026-09-02 · 2 days ago

agent402.tools/api/treasury-yield-history

1.Catalog declaration

Catalog declaration for this endpoint
Resource URL	https://agent402.tools/api/treasury-yield-history
Source	cdp_bazaar
Declared method	GET
Network	eip155:8453
Receiving address	0xabf4fabd7c416fb67202e5f9002389fc75e2a9d0
Declared price (base units)	15000
Catalog status	active
First seen / last seen	2026-08-14 08:39 UTC / 2026-09-05 01:03 UTC
Catalog-reported calls / payers (30d)	1 / 1

2.Probe history

2026-08-222026-09-02

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 at	Method	Verdict	HTTP	Latency	Reason
2026-09-02 11:25 UTC	GET	pass	402	87 ms	—
2026-08-22 11:02 UTC	GET	fail	402	87 ms	accepts_invalid

3.L1 — real purchases

No covert purchases recorded for this endpoint yet.

4.Catalog listing events

Catalog listing events, newest first
Detected on	Event	Before	After
2026-09-01	relisted	`{"status":"delisted"}`	`{"status":"active"}`
2026-08-24	delisted	`{"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.