Independent MeasurementEndpoint record (L0 · L1)Published state: passLast probed: 2026-09-02 · 35 days ago
cdo-production.up.railway.app/v1/gb/solutions/invoice-payee-verification
1.Catalog declaration
| Resource URL | https://cdo-production.up.railway.app/v1/gb/solutions/invoice-payee-verification |
| Source | cdp_bazaar |
| Declared method | POST |
| Network | eip155:8453 |
| Receiving address | 0x0d0e3539da45c573af8730045e7d5f634243f3d3 |
| Declared price (base units) | 90000 |
| Catalog status | delisted (since 2026-09-05 01:03 UTC) |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-09-04 01:03 UTC |
| Catalog-reported calls / payers (30d) | 2 / 1 |
2.Probe history
2026-08-202026-09-02
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-02 11:25 UTC | POST | pass | 402 | 26 ms | — |
| 2026-08-20 10:50 UTC | POST | fail | 402 | 25 ms | accepts_invalid402 without a payable accept in the header or the body (which part was missing was 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-05 | 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.