Independent MeasurementEndpoint record (L0 · L1)Published state: passLast probed: 2026-10-21 · today
x402-seller-0ay3.onrender.com/api/defi/yields
1.Catalog declaration
| Resource URL | https://x402-seller-0ay3.onrender.com/api/defi/yields |
| Source | cdp_bazaar |
| Declared method | GET |
| Catalog network | eip155:8453 |
| Receiving address | 0x5c3db195a38f39074d8c891741a82f6d8f2a16cc |
| Declared price (base units) | 50000 |
| Catalog status | active |
| First seen / last seen | 2026-09-02 01:03 UTC / 2026-10-21 13:01 UTC |
| Catalog-reported calls / payers (30d) | 1 / 1 |
2.Probe history
2026-09-052026-10-21
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-21 04:40 UTC | GET | pass | 402 | 535 ms | — |
| 2026-10-19 16:40 UTC | GET | pass | 402 | 497 ms | — |
| 2026-10-18 04:40 UTC | GET | pass | 402 | 431 ms | — |
| 2026-10-16 21:40 UTC | GET | pass | 402 | 442 ms | — |
| 2026-10-15 12:40 UTC | GET | pass | 402 | 559 ms | — |
| 2026-10-14 03:40 UTC | GET | pass | 402 | 627 ms | — |
| 2026-10-04 10:31 UTC | GET | pass | 402 | 115 ms | — |
| 2026-09-28 10:30 UTC | GET | pass | 402 | 287 ms | — |
| 2026-09-23 10:30 UTC | GET | pass | 402 | 221 ms | — |
| 2026-09-19 11:24 UTC | GET | pass | 402 | 292 ms | — |
| 2026-09-17 11:24 UTC | GET | pass | 402 | 296 ms | — |
| 2026-09-13 11:24 UTC | GET | pass | 402 | 115 ms | — |
| 2026-09-09 11:24 UTC | GET | pass | 402 | 120 ms | — |
| 2026-09-05 11:24 UTC | GET | pass | 402 | 292 ms | — |
3.L1 — real purchases
No paid purchases recorded for this endpoint yet.
4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-10-11 | relisted | {"status":"delisted"} | {"status":"active"} |
| 2026-10-06 | 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.