Independent MeasurementEndpoint record (L0 · L1)Published state: passLast probed: 2026-10-20 · today
zeroclick.affiliate.com/v1/tools/convert/url-to-barcode
1.Catalog declaration
| Resource URL | https://zeroclick.affiliate.com/v1/tools/convert/url-to-barcode |
| Source | cdp_bazaar |
| Declared method | POST |
| Network | eip155:8453 |
| Receiving address | 0x6e9c2ebca537f861fe9242f8f974d99b3df762b2 |
| Declared price (base units) | 20000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:52 UTC / 2026-10-20 01:01 UTC |
| Catalog-reported calls / payers (30d) | 4 / 1 |
2.Probe history
2026-08-262026-10-20
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-20 04:40 UTC | POST | pass | 402 | 650 ms | — |
| 2026-10-18 16:40 UTC | POST | pass | 402 | 1147 ms | — |
| 2026-10-17 13:40 UTC | POST | pass | 402 | 1378 ms | — |
| 2026-10-02 10:30 UTC | POST | pass | 402 | 587 ms | — |
| 2026-09-26 10:30 UTC | POST | pass | 402 | 399 ms | — |
| 2026-09-22 11:24 UTC | POST | pass | 402 | 653 ms | — |
| 2026-09-18 11:24 UTC | POST | pass | 402 | 773 ms | — |
| 2026-09-15 11:24 UTC | POST | pass | 402 | 536 ms | — |
| 2026-09-11 11:24 UTC | POST | pass | 402 | 571 ms | — |
| 2026-09-08 11:24 UTC | POST | pass | 402 | 536 ms | — |
| 2026-09-03 11:24 UTC | POST | pass | 402 | 408 ms | — |
| 2026-08-26 10:33 UTC | POST | fail | 402 | 768 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-10-13 | relisted | {"status":"delisted"} | {"status":"active"} |
| 2026-10-10 | 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.