Independent MeasurementEndpoint record (L0 · L1)Published state: passLast probed: 2026-10-18 · 2 days ago
x402.orthogonal.com/aviato/person/enrich
1.Catalog declaration
| Resource URL | https://x402.orthogonal.com/aviato/person/enrich |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0x3078368e0740fa5f8d9b900ea428c946a1006cb7 |
| Declared price (base units) | 30000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:52 UTC / 2026-10-20 01:01 UTC |
| Catalog-reported calls / payers (30d) | 5 / 1 |
2.Probe history
2026-09-012026-10-18
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-18 22:40 UTC | GET | pass | 402 | 181 ms | — |
| 2026-10-17 13:40 UTC | GET | pass | 402 | 156 ms | — |
| 2026-10-15 21:40 UTC | GET | pass | 402 | 85 ms | — |
| 2026-10-14 15:40 UTC | GET | pass | 402 | 50 ms | — |
| 2026-10-13 10:30 UTC | GET | pass | 402 | 145 ms | — |
| 2026-09-08 11:24 UTC | GET | pass | 402 | 55 ms | — |
| 2026-09-03 11:24 UTC | GET | pass | 402 | 128 ms | — |
| 2026-09-01 11:24 UTC | GET | fail | 402 | 146 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-10-09 | relisted | {"status":"delisted"} | {"status":"active"} |
| 2026-09-09 | 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.