Independent MeasurementEndpoint record (L0 · L1)Published state: passLast probed: 2026-10-13 · today
agent-robotics-compliance.iykykblog.workers.dev/check
1.Catalog declaration
| Resource URL | https://agent-robotics-compliance.iykykblog.workers.dev/check |
| Source | cdp_bazaar |
| Declared method | POST |
| Network | eip155:8453 |
| Receiving address | 0x329b4b66afbc407bb3a22daeb465487c6faa08c1 |
| Declared price (base units) | 100000 |
| Catalog status | active |
| First seen / last seen | 2026-10-10 01:02 UTC / 2026-10-13 01:02 UTC |
| Catalog-reported calls / payers (30d) | 5 / 1 |
2.Probe history
2026-10-122026-10-13
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-13 10:30 UTC | POST | pass | 402 | 433 ms | — |
| 2026-10-12 10:31 UTC | POST | fail | 402 | 356 ms | metadata_mismatchDeclared payTo 0x0764…e1aa on eip155:8453; the 402 offered 0x329b…08C1 on eip155:8453. |
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.