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

defi-api.agenticfi.wtf/api/defi/yields

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://defi-api.agenticfi.wtf/api/defi/yields
Sourcecdp_bazaar
Declared methodGET
Networkeip155:8453
Receiving address0xb3e9391f04f791462ed2a1ebafabe254d7afe3a5
Declared price (base units)1000
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-09-042026-10-19
Figure 1. Probe timeline, last 13 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 UTCGETpass402203 ms—
2026-10-18 04:40 UTCGETpass402198 ms—
2026-10-16 21:40 UTCGETpass402139 ms—
2026-10-15 12:40 UTCGETpass402174 ms—
2026-10-14 03:40 UTCGETpass402291 ms—
2026-10-04 10:30 UTCGETpass40252 ms—
2026-09-27 10:30 UTCGETpass40247 ms—
2026-09-22 11:24 UTCGETpass40252 ms—
2026-09-18 11:24 UTCGETpass402127 ms—
2026-09-16 11:24 UTCGETpass402179 ms—
2026-09-12 11:24 UTCGETpass402322 ms—
2026-09-08 11:24 UTCGETpass40262 ms—
2026-09-04 11:24 UTCGETpass4023333 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-06relisted{"status":"delisted"}{"status":"active"}
2026-10-06delisted{"status":"active"}{"status":"delisted"}
2026-09-04relisted{"status":"delisted"}{"status":"active"}
2026-08-27delisted{"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

defi-api.agenticfi.wtf/api/defi/yields — x402 purchase and probe record | vet402