Independent MeasurementEndpoint record (L0 · L1)Published state: passLast probed: 2026-09-29 · 2 days ago
agents.dyoeway.org/fx
1.Catalog declaration
| Resource URL | https://agents.dyoeway.org/fx |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0x834b189a1c087d0af169a905454979952f59e8ac |
| Declared price (base units) | 10000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:52 UTC / 2026-10-01 01:03 UTC |
| Catalog-reported calls / payers (30d) | 1 / 1 |
2.Probe history
2026-08-292026-09-29
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-29 10:31 UTC | GET | pass | 402 | 207 ms | — |
| 2026-09-18 11:24 UTC | GET | pass | 402 | 774 ms | — |
| 2026-09-15 11:24 UTC | GET | pass | 402 | 444 ms | — |
| 2026-09-11 11:24 UTC | GET | pass | 402 | 438 ms | — |
| 2026-09-08 11:24 UTC | GET | pass | 402 | 175 ms | — |
| 2026-09-03 11:24 UTC | GET | pass | 402 | 198 ms | — |
| 2026-08-29 11:24 UTC | GET | fail | 402 | 390 ms | metadata_mismatchpayTo or network differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change). |
3.L1 — real purchases
No paid purchases recorded for this endpoint yet.
4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-09-28 | relisted | {"status":"delisted"} | {"status":"active"} |
| 2026-09-20 | delisted | {"status":"active"} | {"status":"delisted"} |
| 2026-08-21 | relisted | {"status":"delisted"} | {"status":"active"} |
| 2026-08-15 | 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.